Ask some questions about paging type 2 of TD system.

Paging type 1 is a paging message sent by the network side to the UE in idle state, and paging type 2 is a paging message sent by the network side to the UE in cell DCH and cell FACH state.

I have encountered this problem several times in the field test, that is, after the calling call, the called party has just reselected from GSM network to TD network, and the location update has been completed. Before the RRC connection is released, the called party receives a page from the network side. It is paging type 2. After receiving the paging message, the UE does not respond to the paging, but directly releases the RRC connection and turns to idle, resulting in the caller being disconnected. This phenomenon mostly occurs in the edge area covered by TD. Why did the UE clearly receive the paging message, but did not respond to the paging?

This kind of disconnection caused by location update is very common and many. In the past, every time I pulled the net, a lot appeared. Later, after the RNC entered the pool, it was obviously reduced, but it still happened. It can only reduce the probability, but it cannot be completely eliminated. Is this problem generally ignored? The landlord can check with the jar for specific reasons. There are similar posts, and I also saved some. Now for your convenience, I'll post them:

"What are the advantages of mscpool in solving the network disconnection caused by location update? Ask experts for answers. Thanks in advance.

Location update causes disconnection:

A. Before the location update:

1. Called: MS has arrived at the new LA to read the system message, but has not initiated and completed the LAU, and the page has been sent from the original LA.

Two. Called: TMSI is used for the first paging. When the mobile phone updates its location, TMSI will be reassigned. Until this is completed, TMSI paging will be invalid.

Three. Calling party: location update is not completed after crossing MSC, and cm service is refused when calling (imsi in vlr is unknown). B. In the process of location update:

When the mobile phone updates its location or receives (sends) a short message, SDCCH is occupied. The user is in dedicated mode, so he can't listen to PCH channel, so he can't receive paging messages, which leads to paging failure.

C. After the location is updated:

During the paging process, the cross-office location area/routing area of the MS is updated, but the paging message is still distributed in the original office location area/routing area, which leads to the UE not receiving the paging message. The reason is: for the 1 paging failure caused by location update in MSC, the second paging can be set to IMSI+ global paging (if it is set to local, the VLR LA where the MS is located will not be searched, and paging from the original LA will fail again), then both location update and periodic location update in MSC can be paged to users through the second paging. However, the inter-office location update cannot be solved, because the second paging will not be handed over to the new MSC/VLR for execution.

-If MSC POOL is enabled, when the network sends the second paging, the called mobile phone has successfully updated the location area, MSC POOL updates the location area information of the called mobile phone, and sends the paging through the new location area, so that the called mobile phone can receive the paging message.

Called location update, resulting in disconnection.

What is the root cause?

1 indicates that the location update occupies the SDCCH of Ms.

When it comes to location update, MS does not belong to any LAC before and after, so it cannot be paged effectively.

What is the solution?

Answers to the questions of the forum webmaster searched:

In the process of location update, the user is in dedicated mode, so he can't listen to PCH channel, so he can't receive paging messages, which leads to paging failure. In fact, for the paging failure caused by location update, the secondary paging can be turned into global paging, so that users can be paged through secondary paging, no matter the location update in the office or the periodic location update, and the effect is good. Of course, there is still no way to update the position of the cross-bureau. "