WO2016112774A1

WO2016112774A1 - Position update method and mobility management unit

Info

Publication number: WO2016112774A1
Application number: PCT/CN2015/098283
Authority: WO
Inventors: 卢飞; 刘竞翔; 梁爽
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-01-15
Filing date: 2015-12-22
Publication date: 2016-07-21
Also published as: CN105848132A

Abstract

A position update method and mobility management unit, the method comprising: during transmission of context of a UE, obtaining, by a target mobility management unit, circuit domain position information registered by the UE and in an original system before the UE moves; and enabling a target MSC to initiate a position update request to an HSS by the obtained circuit domain position information registered by the UE and in the original system before the UE moves. The above technical solution avoids unnecessary signaling costs, ensures successfully being called by the UE, and reduces a risk of the HSS tendency to be congested.

Description

Method for realizing location update and mobile management unit

Technical field

This paper deals with technology mobility management technology, especially a method for implementing location update and a mobility management unit.

Background technique

Currently, the Standardization Working Group of the 3rd Generation Partnership Project (3GPP) is working on the PS Core (Packet Switch Core) and the Global Mobile Telecommunications System Radio Access Network (UTRAN, Universal Mobile). Evolution of Telecommunication System Radio Access Network). The research topic is called System Architecture Evolution (SAE), which aims to enable EPC (Evolved Packet Core) to provide higher transmission rate and shorter transmission delay to optimize packet and support. Mobility management between evolved UTRAN (E-UTRAN, Evolved UTRAN), UTRAN, Wireless Local Area Network (WLAN), and other non-3GPP access networks.

FIG. 1 is a schematic structural diagram of an architecture of an SAE in the related art, where the SAE includes an EV (E-RAN, Evolved Radio Access Network) and an EPC. The E-RAN includes an eNodeB (Evolved NodeB), which is configured to provide a wireless resource for the user's access, and a Packet Data Network (PDN), which is configured to provide services for the user. EPC, set to provide lower transmission delay and allow more wireless access systems to access, EPC includes: Mobility Management Entity (MME), Serving Gateway (SGW), Packet Data Network Gateway (PGW, PDN Gateway), Policy and Charging Rules Function (PCRF), Home Subscriber Server (HSS). The MME is a mobility management unit of the SAE system. In the Universal Mobile Telecommunications System (UMTS), the mobility management unit is configured to serve a General Packet Radio Service (GPRS) support node (SGSN, Serving). GPRS Support Node).

In order to support the circuit domain service, 3GPP introduces a Circuit Switched Fallback (CSFB) mechanism in the network. In the CSFB mechanism, as shown in Figure 1, the MME passes the SGs interface and the Mobile Switching Center (MSC, Mobile Switched Center). ) Connection, in the actual network, the MSC and the Visitor Location Register (VLR, Visitor Location Register) can be combined in the same entity.

2 is a schematic flowchart of a tracking area update and activation of an SGs connection in the related art. As shown in FIG. 2, it is assumed that a user equipment (UE, User Equipment) registered under the UTRAN coverage area moves to an E-UTRAN coverage area and is tracking. The SGs are activated during the TAU (Tracking Area Update) process, including the following steps:

Step 200: The UE moves to the E-UTRAN coverage area under the destination MME (such as MME1 in FIG. 2), and sends a tracking area update request message to the MME1 to request registration in the new area. The tracking area update request message carries the SGSN. Packet-Temporary Mobile Subscriber Identity (P-TMSI) assigned to the UE.

Step 201: The MME1 searches for the original SGSN according to the P-TMSI identifier (such as SGSN1 in FIG. 2), and sends a context request to the SGSN1 to acquire the context of the UE.

Step 202: The SGSN1 sends the mobility management and bearer information of the user to the MME1 by using a context response.

Step 203: MME1 confirms the context after receiving the context response.

Step 204: The MME1 initiates an update bearer request message to the SGW, where the update bearer request message carries the original GPRS Tunneling Protocol-Control Plane (GTP-C) tunnel identifier and the destination GTP-C tunnel identifier, and the SGW updates the bearer. Binding relationship.

Step 205: The SGW sends an update bearer request to the PGW, and sends the SGW's own address information, the SGW's own tunnel identification information, and the access technology type to the PGW.

Step 206: The PGW updates its own context and returns an update bearer response message to the SGW. The update bearer response message carries information such as the address of the PGW and the GTP-C tunnel identifier of the PGW.

Step 207: The SGW returns an update bearer response to the MME1, the destination GTP-C tunnel identifier specified by the SGW, the address of the SGW itself, and the address of the PGW and the tunnel information of the PGW. And so on to carry to MME1.

Step 208: The MME1 notifies the change of the HSS registration location by the location update message.

Step 209: The HSS sends location cancellation signaling to the SGSN1, and the HSS maintains the registration of the MME1.

Step 210: The SGSN1 returns a location cancellation response to the HSS.

Step 211: The HSS confirms the location update of the MME1.

Step 212: MME1 may select an MSC according to an International Mobile Subscriber Identification (IMSI) hash algorithm, and assume that MME1 selects MSC2, and MME1 sends a location update to the destination MSC (ie, MSC2 in FIG. 2). The request message is requested to establish an SGs connection, and the location update request message carries parameters such as an IMSI, an MME1 name, and a location update type. The location update request message further carries the old location area identifier (LAI, Location Area Identity) and the old temporary mobile user that the UE has carried in the original system, that is, the registration in the UTRAN coverage area, which is carried in the step 200. Identification (TMSI, Temporary Mobile Subscriber Identity).

However, it should be noted that, for the unupgraded UE used in the network in the related art, the interaction of step 200 does not carry two parameters of LAI and TMSI. That is to say, at this time, the location update request message sent by the MME1 to the MSC2 does not carry the old LAI and the old TMSI. It should be noted that the 3GPP standard is a version of the version. For the UEs of the version 8 to version 10, the two parameters are not carried, and the UEs of the version 11 to version 12 carry the above two parameters. The UE that is not upgraded refers to the UE of Release 8 to Release 10 specified by the protocol.

It can be seen from the flow in the related art that the destination mobility management unit, such as the new MME, may not obtain the circuit domain location information registered in the original system before the UE moves, such as the old LAI and the old TMSI. .

Step 213: The MSC2 determines whether to send a location update request message to the HSS according to the old LAI and the TMSI carried in the step 212. When the MSC2 considers that the old LAI and the old TSI are not available, that is, the old LAI and the TMSI are not allocated by the MSC2, the MSC2 Sending a location update request message to the HSS;

If the old LAI and the old TMSI are not carried in step 212, MSC2 can only decide whether to send a location update request message to the HSS according to whether the UE has the context of the UE, only when When MSC2 does not have the context of the UE, MSC2 sends a Location Update Request message to the HSS.

If the old LAI and the old TMSI are not carried in step 212, and when the MSC2 has the context of the UE, step 213-step 216 is ignored, and the process proceeds directly to step 217.

Step 214: The HSS sends location cancellation signaling to the old MSC (i.e., MSC1 in Figure 2), and the HSS maintains registration of MSC2.

Step 215: MSC1 returns a location cancellation response message to the HSS, and MSC1 deletes the context of the UE.

Step 216: The HSS returns a location update confirmation message to the MSC2.

Step 217: The MSC2 returns a location update accept message to the MME1, where the location update accept message may carry the TMSI allocated by the MSC2 for the user.

Step 218: If the MME1 confirms that the UE is valid in the current tracking area, it sends a Tracking Area Update (TAU) accept message to the UE, and carries the LAI and TMSI in the TAU accept message.

Step 219: If the MME1 allocates a new Globally Unique Temporary Identity (GUTI) to the UE through the TAU procedure, the UE returns a Tracking Area Update Complete message to the MME1 for confirmation.

The flow area update (RAU) process initiated by the UEs that are registered in the E-UTRAN coverage area and moved to the UTRAN coverage area is similar to the process shown in FIG. 2 and will not be described here.

In the actual network operation, the link connecting the original MSC may be interrupted. As a result, when the UE used in the network in the related art moves from MSC1 to MSC2, MSC1 may not receive the HSS in step 214 in FIG. 2 normally. The sent location cancel message. In this case, MSC1 does not delete the context of the UE it saves. When the UE moves back to MSC1 again, at this time, MSC1 is the destination MSC. For the UE used in the relevant network, MSC1 can only decide whether to send a location update request message to the HSS according to whether it has the context of the UE. MSC1 finds that the context of the UE already exists, and MSC1 will not send a location update request message to the HSS, thereby causing the identity of MSC2 to still be stored in the HSS. In this way, the MSC2 will arrive when paging the terminal, and the UE actually works in the MSC1, causing the called party to the UE to fail.

In order to solve the above problem of the called party failure, the present invention mainly includes: even if the MSC1 already has the context of the UE, the MSC1 sends a location update request message to the HSS when the UE moves back to the MSC1. However, if the MSC stored in the HSS happens to be the identity of the MSC1, such a processing obviously causes the MSC1 to send unnecessary signaling to the HSS, and it is easy to cause HSS congestion.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the present invention provides a method for implementing location update and a mobility management unit, which can avoid unnecessary signaling overhead and ensure successful calling of the UE, and can also reduce the risk of HSS being easily congested.

An embodiment of the present invention provides a method for implementing location update, including: in a context transfer process of a user equipment UE, the destination mobility management unit acquires circuit domain location information registered in the original system before the UE moves;

The destination mobility management unit uses the obtained circuit domain location information registered in the original system before the UE moves, so that the destination mobile switching center MSC initiates a location update request to the home subscriber server HSS.

The destination mobility management unit acquires circuit domain location information that is registered in the original system before the UE moves, including:

Transmitting, by the destination mobility management unit, context request signaling to the original mobility management unit to obtain a context of the UE;

Obtaining, from the context response message from the original mobility management unit, circuit domain location information registered in the original system before the UE moves; wherein the context response message carries the obtained circuit domain location registered in the original system before the UE moves information.

The destination mobility management unit uses the obtained circuit domain location information registered in the original system before the UE moves to cause the destination MSC to initiate a location update request to the HSS, including:

The destination mobility management unit carries the obtained circuit domain location information in the location update request The information is sent to the destination MSC, so that the destination MSC determines, according to the obtained circuit domain location information, that the UE is not under its own jurisdiction, and sends a location update request message to the HSS.

The destination mobility management unit uses the obtained circuit domain location information registered in the original system before the UE moves, so that the destination MSC initiates a location update request to the HSS, including:

When the destination mobility management unit determines that the MSC changes according to the obtained circuit domain location information, the destination mobility management unit carries a special identifier for instructing the destination MSC to initiate a location update request to the HSS in the location update request message. The location area identifier is such that after the destination MSC receives the special location area identifier, it sends a location update request message to the HSS.

The circuit domain location information registered in the original system includes a location area identifier LAI, and/or a network resource identifier NRI.

The original mobility management unit is a general packet radio service GPRS support node SGSN, and the Gs interface is supported between the SGSN and the MSC, and the UE moves to the UTRAN coverage area of the global mobile communication system radio access network under the jurisdiction of the SGSN, or The original mobility management unit is a mobility management entity MME, and an SGs interface is supported between the MME and the MSC, and when the UE moves to an E-UTRAN coverage area of an evolved Global System for Mobile Communications system radio access network under the jurisdiction of the MME, The original mobile management unit acquires the circuit domain location information registered in the original system before the UE moves, including:

The original mobility management unit uses the tracking area update TAU or the routing area to update the RAU process, and obtains the circuit domain registered in the original system before the UE moves by using the location update response message returned by the network element MSC of the circuit domain selected by the original mobility management unit itself. location information.

The location update response message returned by the MSC carries at least a temporary mobile subscriber identity (TMSI), LAI, and MSC name, wherein the NRI is obtained according to the TMSI.

When the original mobility management unit is an SGSN, and the Gs interface is not supported between the SGSN and the MSC, the method further includes: the UE moves to a UTRAN coverage area under the MSC, and sends a location area update request message to the circuit domain MSC. Request to register in a new area;

The original mobility management unit acquires circuit domain location information that is registered in the original system before the UE moves, including:

When the UE needs to use a packet domain service, the original mobility management unit uses the routing area to update The RNC is sent by the RNC that receives the routing area update request to the original mobility management unit through the RANAP message, where the RANAP message carries the circuit domain MSC identity or NRI, and the LRI is stored by the RNC after selecting the circuit domain MSC. The NRI corresponding to the selected MSC.

The original mobility management unit is an SGSN, the method further includes: the UE moving to a UTRAN coverage area under the jurisdiction of the MSC, and sending a location area update request message to the circuit domain MSC, requesting registration in a new area;

The MSC sends the user IMSI and the MSC address in the location area update message to the HSS, where the MSC address may be an NRI or MSC name;

When the UE needs to use the packet domain service and moves to the coverage area under the jurisdiction of the original mobility management unit, sending routing area update request information to the original mobility management unit; the original mobility management unit sends the location to the HSS Update the message, the location update acknowledge message returned by the HSS to the original mobility management unit carries the IMSI, MSC address information;

The original mobility management unit obtains an MSC address according to it.

The embodiment of the present invention further provides a mobility management unit, including an acquiring unit and a determining unit, where the mobility management unit is a destination mobility management unit, where

An acquiring unit, configured to acquire circuit domain location information registered in the original system before the UE moves in a context transfer process of the UE;

The determining unit is configured to use the obtained circuit domain location information registered in the original system before the UE moves, so that the destination MSC initiates a location update request to the HSS.

The acquiring unit is configured to: send context request signaling to the original mobility management unit to acquire a context of the UE; and obtain, by using a context response message from the original mobility management unit, circuit domain location information that is registered in the original system before the UE moves.

The determining unit is configured to: carry the obtained circuit domain location information in a location update request message, and send the information to the destination MSC, so that the destination MSC determines, according to the obtained circuit domain location information, that the UE is not under its own jurisdiction. At the time, a location update request is initiated to the HSS.

The determining unit is configured to: determine that the MSC occurs according to the obtained circuit domain location information When the change is made, the location update request message carries a special location area identifier for instructing the destination MSC to initiate a location update request, so that the destination MSC sends a location update request to the HSS after receiving the special location area identifier. Message.

When the mobility management unit is the original mobility management unit,

The obtaining unit is further configured to: obtain, by using a TAU or RAU procedure, a location update response message returned by the network element MSC of the circuit domain selected by the original mobility management unit to which the original mobility management unit belongs, and obtain the circuit domain location information registered in the original system before the UE moves. .

When the mobility management unit is the original mobility management unit,

The obtaining unit is further configured to: receive, by using a routing area update process, a RANAP message sent by the RNC received by the routing area update request, where the RANAP message carries a circuit domain MSC identifier or NRI, and the LAI, where the NRI is The NRI corresponding to the selected MSC stored by the RNC after selecting the circuit domain MSC.

When the mobility management unit is the original mobility management unit,

The obtaining unit is further configured to: when the UE needs to use a packet domain service, and move to a coverage area under the jurisdiction of the original mobility management unit, receive routing area update request information from the UE; and send a location update message to the HSS. The location update acknowledge message received from the HSS carries the IMSI, the MSC address information, and obtains the NRI according to the obtained MSC address.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the above method.

Compared with the related art, the technical solution of the present application includes, during a context transfer process of the UE, the destination mobility management unit acquires circuit domain location information registered in the original system before the UE moves; and the circuit domain registered in the original system according to the obtained UE movement The location information causes the destination MSC to initiate a location update request to the HSS. The technical solution provided by the embodiment of the present invention avoids unnecessary signaling overhead, ensures successful calling of the UE, and reduces the risk of the HSS being easily congested.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a schematic structural diagram of an architecture of a SAE in the related art;

2 is a schematic flowchart of a tracking area update and activation of an SGs connection in the related art;

3 is a flowchart of a method for implementing location update according to an embodiment of the present invention;

4 is a schematic flowchart of implementing location update according to a first embodiment of the present invention;

FIG. 5 is a schematic flowchart of implementing location update according to a second embodiment of the present invention; FIG.

FIG. 6 is a schematic flowchart of acquiring circuit domain location information according to a first embodiment of the present invention; FIG.

FIG. 7 is a schematic flowchart of acquiring circuit domain location information according to a second embodiment of the present invention; FIG.

FIG. 8 is a schematic flowchart of acquiring circuit domain location information according to a third embodiment of the present invention; FIG.

FIG. 9 is a schematic structural diagram of a structure of a mobility management unit that implements location update according to an embodiment of the present invention.

Embodiments of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

3 is a flowchart of a method for implementing location update according to an embodiment of the present invention. When a UE moves to a coverage area under the jurisdiction of a destination mobility management unit, a tracking area update request is sent to the destination mobility management unit to request to perform in a new area. Registration, as shown in Figure 3, includes:

Step 300: During the context transfer process of the UE, the destination mobility management unit acquires circuit domain location information registered in the original system before the UE moves.

The step further includes: the UE moves to the jurisdiction of the destination mobility management unit, and initiates a location update request to the destination mobility management unit, where the location update request message carries the P-TMSI identifier allocated by the original mobility management unit for the UE.

The circuit domain location information registered in the original system includes an LAI and/or a Network Resource Indicator (NRI).

The destination mobility management unit in this step acquires the circuit domain location information registered in the original system before the UE moves, including:

The destination mobility management unit searches the original mobility management unit according to the P-TMSI identifier, and sends context request signaling to the original mobility management unit to obtain the context of the UE.

The original mobility management unit sends the user's mobility management and bearer information to the destination mobility management unit through the context response message, and the original mobility management unit carries the obtained circuit domain registered in the original system before the UE moves in the context response message. The location information is LAI and/or NRI.

The original mobility management unit acquires the circuit domain location information, that is, the LAI and the NRI, which are registered in the original system before the UE moves, and includes:

When the original mobility management unit is the MME or the SGSN, that is, the MME and the SGSN are combined, and the SGs interface is supported between the MME and the MSC, and the UE moves to the E-UTRAN coverage area under the MME; or between the SGSN and the MSC Support Gs interface, when the UE moves to the UTRAN coverage area under the jurisdiction of the SGSN

The original mobility management unit uses the tracking area update TAU or the routing area update RAU process to obtain the circuit domain location information registered in the original system before the UE moves by the location update response message returned by the network element MSC of the circuit domain selected by the original mobility management unit itself. That is, LAI and NRI. The location update response message returned by the MSC carries at least the TMSI, LAI, and MSC name, wherein the NRI can be obtained according to the TMSI. Here, it has been explained that the NRI is a part of the TMSI on the standard protocol. Therefore, it is a known technique for the person to obtain the NRI according to the TMSI for those skilled in the art, and details are not described herein again.

When the original mobility management unit is an SGSN, and the Gs interface is not supported between the SGSN and the MSC, the UE moves to the UTRAN coverage area under the MSC, and sends a location area update request message to the circuit domain MSC to request registration in the new area. When, including:

When the UE needs to use the packet domain service, the original mobility management unit uses the routing area update process, and the RNC that receives the routing area update request sends a message to the original mobility management through a Radio Access Network Application Part (RANAP) message. The unit carries the circuit domain MSC identity or NRI and the LAI in the RANAP message. Wherein, because there is no TMSI in the RANAP message, the NRI is the NRI corresponding to the selected MSC stored by the RNC after selecting the circuit domain MSC.

When the original mobility management unit is an SGSN, and whether the UE supports the Gs interface between the SGSN and the MSC, the UE moves to the UTRAN coverage area under the jurisdiction of the MSC, and sends a location area update request message to the circuit domain MSC, requesting to perform in a new area. When registering, include:

The MSC carries the user IMSI and MSC address in the location area update message and sends it to the HSS. The MSC address may be an NRI or an MSC name or the like;

When the UE needs to use the packet domain service and moves to the coverage area under the jurisdiction of the original mobility management unit, the routing area update request information is sent to the original mobility management unit; the original mobility management unit sends a location update message to the HSS, and the HSS sends the location update message to the original mobility management unit. The returned location update confirmation message carries the IMSI, MSC address information;

The original mobility management unit obtains the MSC address.

Step 301: Using the obtained circuit domain location information registered in the original system before the UE moves, the destination MSC initiates a location update request to the HSS. This step includes:

The destination mobility management unit carries the obtained circuit domain location information in the location update request message to the destination MSC; the destination MSC sends a location update request message to the HSS when it determines that it is not under its own jurisdiction according to the obtained circuit domain location information;

Alternatively, the destination mobility management unit determines, according to the obtained circuit domain location information, that the destination mobility management unit carries a special location area identifier for indicating that the destination MSC initiates the location update request in the location update request message; the destination MSC After receiving the special location area identifier, a location update request message is sent to the HSS.

In the method of the embodiment of the present invention, since the destination mobility management unit obtains the circuit domain location information registered in the original system before the UE moves in the context transfer process of the UE, the link of the MSC of the coverage area where the original mobility management unit is located is An interrupt is generated and the location cancel message sent by the HSS in step 214 in FIG. 2 cannot be normally received, but since the destination mobility management unit has obtained the circuit domain location information registered in the original system before the UE moves, when the UE again When moving back to the original MSC, the original MSC is the new destination MSC. Even for the unupgraded UE, the new destination MSC can still determine whether to send a location update request message to the HSS to delete the previous MSC stored in the HSS. Logo. In this way, when paging the terminal, it will reach the new destination MSC where the UE is currently working, ensuring successful calling of the UE, avoiding unnecessary signaling overhead, and reducing the congestion of the HSS. risk.

The method of the embodiment of the present invention further includes: the HSS notifying the original MSC to perform location cancellation, and returning the location update confirmation information to the UE via the destination MSC and the destination mobility management unit to complete the location update.

An embodiment of the present invention further provides a computer storage medium, where the computer storage medium is stored Computer executable instructions are stored for performing the methods described above.

The method of the present invention will be described in detail below with reference to specific embodiments.

FIG. 4 is a schematic flowchart of the implementation of the location update according to the first embodiment of the present invention. In the first embodiment, the destination mobility management unit is the destination MME, and the original mobility management unit is the original SGSN. As shown in FIG. 4, the method includes the following steps:

Step 400: The UE moves to the E-UTRAN coverage area of the destination MME, and sends a tracking area update request message to the destination MME to request registration in the new area. The tracking area update request message carries the P-TMSI allocated by the SGSN for the UE. .

Step 401: The target MME searches for the original SGSN according to the P-TMSI identifier, and sends context request signaling to the original SGSN to obtain the context of the UE.

Step 402: The original SGSN sends the user's mobility management and bearer information to the destination MME through the context response. At the same time, the original SGSN carries the obtained original LAI and/or the original NRI in the context response message.

The implementation of obtaining the original LAI and/or the original NRI in the original SGSN in this step is as shown in FIG. 6, FIG. 7 or FIG. 8, and will not be described in detail herein.

Step 403: The target MME confirms the context after receiving the context response, and the destination MME obtains the original LAI and/or the original NRI.

Step 404: The destination MME initiates an update bearer request message to the SGW, where the update bearer request message carries the original GTP-C tunnel identifier and the destination GTP-C tunnel identifier, and the SGW updates the binding relationship of the bearer.

Step 405: The SGW sends an update bearer request to the PGW, and sends the SGW's own address information, tunnel identification information, access technology type and other parameters to the PGW.

Step 406: The PGW updates its own context and returns an update bearer response message to the SGW. The update bearer response message carries information such as the address of the PGW and the GTP-C tunnel identifier.

Step 407: The SGW returns an update bearer response to the destination MME, and carries the destination GTP-C tunnel identifier, the address of the SGW itself, and the address and tunnel information of the PGW to the destination MME.

Step 408: The destination MME notifies the change of the HSS registration location by using the location update message.

Step 409: The HSS sends location cancellation signaling to the original SGSN, and the HSS maintains registration of the destination MME.

Step 410: The original SGSN returns a location cancellation response to the HSS.

Step 411: The HSS confirms the location update of the destination MME.

Step 412: The destination MME selects the MSC according to the IMSI hash algorithm. If the MME selects the destination MSC, the destination MME sends a location update request message to the destination MSC to request to establish an SGs connection. The location update request message carries the IMSI, the destination MME name, and Parameters such as location update type.

It should be noted that, for the UE that is not upgraded, although the original LAI and the original TMSI cannot be carried in step 400, the present embodiment obtains the original LAI and/or the original NRI through steps 402 and 403. In this step, the MME sends the obtained original LAI and/or the original NRI to the destination MSC in the location update request message.

Step 413: The destination MSC determines whether to send a location update request message to the HSS according to the obtained original LAI and/or the original NRI, as long as the destination MSC decides to send a location update request message to the HSS according to the obtained original LAI and/or the original NRI, the destination MSC. A Location Update Request message is sent to the HSS.

Step 414: The HSS sends location cancellation signaling to the original MSC, and the HSS maintains registration of the destination MSC.

Step 415: The original MSC returns a location cancellation response message to the HSS.

Step 416: The HSS returns a location update accept message to the destination MSC.

Step 417: The destination MSC returns a location update accept message to the destination MME, where the location update accept message carries the TMSI.

Step 418: If the destination MME confirms that the UE is valid in the current tracking area, send a tracking area update accept message to the UE, and carry the LAI and TMSI in the TAU accept message.

Step 419: If the destination MME allocates a new GUTI to the UE through the TAU procedure, the UE returns a tracking area update complete message to the destination MME for confirmation.

For the case where the original mobility management unit is the MME, the implementation is similar to that shown in FIG. 4. The specific implementation is well known to those skilled in the art on the basis of the process shown in FIG. 4, and details are not described herein again.

FIG. 5 is a schematic flowchart of the implementation of the location update according to the second embodiment of the present invention. In the second embodiment, the destination mobility management unit is the destination MME, and the original mobility management unit is the original SGSN. As shown in FIG. 5, the following steps are included:

Step 500: The UE moves to the E-UTRAN coverage area of the destination MME, and sends a tracking area update request message to the destination MME to request registration in the new area. The tracking area update request message carries the P-TMSI allocated by the SGSN for the UE. .

Step 501: The target MME searches for the original SGSN according to the P-TMSI identifier, and sends context request signaling to the original SGSN to obtain the context of the UE.

Step 502: The original SGSN sends the user's mobility management and bearer information to the destination MME through the context response. At the same time, the original SGSN carries the obtained original LAI and/or the original NRI in the context response message.

The specific implementation of the original SGSN to obtain the original LAI and/or the original NRI in this step is shown in FIG. 6, FIG. 7 or FIG. 8, and will not be described in detail herein.

Step 503: The target MME confirms the context after receiving the context response, and the destination MME obtains the original LAI and/or the original NRI.

Step 504: The destination MME initiates an update bearer request message to the SGW, where the update bearer request message carries the original GTP-C tunnel identifier and the destination GTP-C tunnel identifier, and the SGW updates the binding relationship of the bearer.

Step 505: The SGW sends an update bearer request to the PGW, and sends the SGW's own address information, tunnel identification information, access technology type and other parameters to the PGW.

Step 506: The PGW updates its own context and returns an update bearer response message to the SGW. The update bearer response message carries information such as the address of the PGW and the GTP-C tunnel identifier.

Step 507: The SGW returns an update bearer response to the destination MME, and carries the destination GTP-C tunnel identifier, the address of the SGW itself, and the address and tunnel information of the PGW to the destination MME.

Step 508: The destination MME notifies the change of the HSS registration location by using the location update message.

Step 509: The HSS sends location cancellation signaling to the original SGSN, and the HSS maintains registration of the destination MME.

Step 510: The original SGSN returns a location cancellation response to the HSS.

Step 511: The HSS confirms the location update of the destination MME.

Step 512: The destination MME selects the MSC according to the IMSI hash algorithm. If the MME selects the destination MSC, the destination MME sends a location update request message to the destination MSC to request to establish an SGs connection. The location update request message carries the IMSI, the destination MME name, and Parameters such as location update type.

It should be noted that, for the UE that is not upgraded, although the original LAI and the original TMSI cannot be carried in the step 400, the target MME obtains the original LAI and/or the original NRI through steps 502 and 503 in this embodiment. In this step, the destination MME determines that the MSC has changed according to the obtained original LAI and/or the original NRI, that is, the destination MSC cannot serve the original LAI and/or the original NRI for the UE, and the destination MSC is not the original MSC, then, The destination MME sends an un-broadcast special LAI in the location update request message sent to the destination MSC to indicate that the MSC has changed, and the destination MSC needs to initiate a location update request.

Step 513: The destination MSC determines, according to the obtained un-broadcast special LAI, that a location update request message needs to be sent to the HSS.

Step 514: The HSS sends location cancellation signaling to the original MSC, and the HSS maintains registration of the destination MSC.

Step 515: The original MSC returns a location cancellation response message to the HSS.

Step 516: The HSS returns a location update accept message to the destination MSC.

Step 517: The destination MSC returns a location update accept message to the destination MME, where the location update accept message carries the TMSI.

Step 518: If the destination MME confirms that the UE is valid in the current tracking area, send a tracking area update accept message to the UE, and carry the LAI and TMSI in the TAU accept message.

Step 519: If the destination MME allocates a new GUTI to the UE through the TAU procedure, the UE returns a tracking area update complete message to the destination MME for confirmation.

For the case where the original mobility management unit is the MME, the implementation is similar to that shown in FIG. 5, and the specific implementation is implemented. It will be readily understood by those skilled in the art based on the flow shown in FIG. 5, and details are not described herein again.

FIG. 6 is a schematic flowchart of acquiring circuit domain location information according to the first embodiment of the present invention. In the first embodiment, the original mobility management unit is an MME, and the SGs interface is supported between the MME and the MSC, or the original mobility management unit is an SGSN. The SGSN and the MSC support the Gs interface. As shown in FIG. 6, the original MME or the original SGSN acquires the circuit domain location information, including:

Step 600: The MME or the SGSN selects the network element MSC of the circuit domain, and sends a location update request message to the selected MSC. The location update request message carries information such as an IMSI, an MME or an SGSN name, and a location update type.

Step 601: The MSC returns a location update response message to the MME or the SGSN, and carries the information such as the TMSI, the LAI, and the MSC name in the location update response message.

Step 602: The MME or the SGSN may acquire and store the NRI and/or LAI of the circuit domain MSC according to the obtained TMSI and LAI. Among them, the NRI can be obtained according to the obtained TMSI.

FIG. 7 is a schematic flowchart of acquiring circuit domain location information according to a second embodiment of the present invention. In the second embodiment, the original mobility management unit is an SGSN, and the Gs interface is not supported between the SGSN and the MSC, as shown in FIG. The SGSN acquires circuit domain location information including:

Step 700: The UE moves to the UTRAN coverage area under the jurisdiction of the MSC, and the UE sends a location area update request to the RNC to request registration in the new area.

Step 701: The RNC selects the MSC, and stores the NRI of the selected MSC, and the RNC forwards the location area update request message to the selected MSC.

Step 702: The MSC returns a location update response message to the UE, where the location update response message carries the allocated TMSI, LAI.

Step 703: When the UE needs to use the packet domain service and move to the coverage area under the jurisdiction of the SGSN, the UE sends the routing area update request information to the RNC.

Step 704: The RNC receives the routing area update request message, and obtains the circuit domain MSC identifier NRI and/or LAI. The NRI is stored in the RNC after the RNC selects the MSC in step 701.

Step 705: The RNC forwards the received routing area update request message to the SGSN, where the circuit domain MSC identifier NRI and/or LAI is carried.

Step 706: The SGSN confirms that the UE is valid in the current routing area, and sends a routing area to the UE. Update acceptance message.

FIG. 8 is a schematic flowchart of acquiring circuit domain location information according to a third embodiment of the present invention. In the third embodiment, the original mobility management unit is an SGSN. As shown in FIG. 8, the original SGSN acquires circuit domain location information, including:

Step 800: The UE moves to the UTRAN coverage area under the jurisdiction of the MSC, and sends a location area update request message to the MSC to request registration in the new area.

Step 801: The MSC sends a location update message to the HSS, where the location update message carries the user IMSI and the MSC address, where the MSC address may be an NRI or an MSC name.

Step 802: The HSS returns a location update acknowledgement message to the MSC, where the location constant acknowledgement message carries the IMSI.

Step 803: The MSC returns a location update response message to the UE, where the location update response message carries the allocated TMSI, LAI.

Step 804: When the UE needs to use the packet domain service and move to the coverage area under the jurisdiction of the SGSN, the UE sends the routing area update request information to the SGSN.

Step 805: The SGSN sends a location update message to the HSS, where the location update message carries the user IMSI.

Step 806: The HSS returns a location update acknowledgement message to the SGSN, where the location update acknowledgement message carries the IMSI, MSC address.

Step 807: The SGSN confirms that the UE is valid in the current routing area, and sends a routing area update accept message to the UE.

FIG. 9 is a schematic structural diagram of a structure of a mobility management unit for implementing location update according to an embodiment of the present invention. As shown in FIG. 9, the mobility management unit includes an obtaining unit and a determining unit. When the mobility management unit is a destination mobility management unit, where

Optionally,

The obtaining unit is configured to: send context request signaling to the original mobility management unit to acquire the context of the UE; and receive circuit domain location information, that is, LAI and/or NRI, registered in the original system before the UE moves from the original mobility management unit.

Optionally, when the mobility management unit is the original mobility management unit,

The obtaining unit is configured to: obtain, by using a TAU or RAU procedure, a location update response message returned by the network element MSC of the circuit domain selected by the original mobility management unit to which the UE belongs to obtain the LAI and the circuit domain location information registered in the original system before the UE moves. / or NRI. The location update response message returned by the MSC carries at least the TMSI, LAI, and MSC name, wherein the NRI can be acquired according to the TMSI.

Alternatively, the obtaining unit is configured to: receive, by using the routing area update process, a RANAP message sent by the RNC received by the routing area update request, where the RANAP message carries the circuit domain MSC identity or NRI, and the LAI, wherein the RANAP message There is no TMSI in the middle, and the NRI is the NRI corresponding to the selected MSC stored by the RNC after selecting the circuit domain MSC.

Alternatively, the obtaining unit is configured to: when the UE needs to use the packet domain service, and move to the coverage area under the jurisdiction of the original mobility management unit, receive routing area update request information from the UE; send a location update message to the HSS, and receive the return from the HSS. The location update acknowledgement message carries the IMSI, MSC address information, and obtains the MSC address.

The determining unit is configured to: carry the obtained circuit domain location information in the location update request message and send the information to the destination MSC. Thus, when the destination MSC determines that it is not under its own jurisdiction based on the obtained circuit domain location information, it sends a location update request message to the HSS.

Alternatively, the determining unit is configured to: when determining that the MSC changes according to the obtained circuit domain location information, the location update request message carries a special location area identifier for indicating that the destination MSC initiates the location update request. In this way, after receiving the special location area identifier, the destination MSC sends a location update request message to the HSS.

Those skilled in the art should understand that the technical solutions of the present invention may be modified or The equivalents of the present invention are intended to be included in the scope of the appended claims.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function. The invention is not limited to any specific form of combination of hardware and software.

Industrial applicability

The foregoing technical solution avoids unnecessary signaling overhead, ensures successful calling of the UE, and reduces the risk that the HSS is easily congested.

Claims

A method of implementing location update, including:

During the context transfer process of the user equipment UE, the destination mobility management unit acquires circuit domain location information registered in the original system before the UE moves;

The destination mobility management unit uses the obtained circuit domain location information registered in the original system before the UE moves, so that the destination mobile switching center MSC initiates a location update request to the home subscriber server HSS.
The method of claim 1 wherein

The destination mobility management unit acquires circuit domain location information that is registered in the original system before the UE moves, including:

Transmitting, by the destination mobility management unit, context request signaling to the original mobility management unit to obtain a context of the UE;

Obtaining, from the context response message from the original mobility management unit, circuit domain location information registered in the original system before the UE moves; wherein the context response message carries the obtained circuit domain location registered in the original system before the UE moves information.
The method according to claim 1, wherein the destination mobility management unit uses the obtained circuit domain location information registered in the original system before the UE moves, so that the destination MSC initiates a location update request to the HSS, including:

The destination mobility management unit carries the obtained circuit domain location information in the location update request message and sends the information to the destination MSC, so that the destination MSC determines, according to the obtained circuit domain location information, that the UE is not under its own jurisdiction. A location update request message is sent to the HSS.
The method according to claim 1, wherein the destination mobility management unit uses the obtained circuit domain location information registered in the original system before the UE moves, so that the destination MSC initiates a location update request to the HSS, including:

When the destination mobility management unit determines that the MSC changes according to the obtained circuit domain location information, the destination mobility management unit carries a special identifier for instructing the destination MSC to initiate a location update request to the HSS in the location update request message. Location area identification for the purpose After receiving the special location area identifier, the MSC sends a location update request message to the HSS.
The method according to any one of claims 1 to 4, wherein the circuit domain location information registered in the original system comprises a location area identifier LAI, and/or a network resource identifier NRI.
The method of claim 2, wherein

The original mobility management unit is a general packet radio service GPRS support node SGSN, and the Gs interface is supported between the SGSN and the MSC, and the UE moves to the UTRAN coverage area of the global mobile communication system radio access network under the jurisdiction of the SGSN, or The original mobility management unit is a mobility management entity MME, and an SGs interface is supported between the MME and the MSC, and when the UE moves to an E-UTRAN coverage area of an evolved Global System for Mobile Communications system radio access network under the jurisdiction of the MME, The original mobile management unit acquires the circuit domain location information registered in the original system before the UE moves, including:

The original mobility management unit uses the tracking area update TAU or the routing area to update the RAU process, and obtains the circuit domain registered in the original system before the UE moves by using the location update response message returned by the network element MSC of the circuit domain selected by the original mobility management unit itself. location information.
The method according to claim 6, wherein the location update response message returned by the MSC carries at least a temporary mobile subscriber identity (TMSI), LAI, MSC name, wherein the NRI is obtained according to the TMSI.
The method of claim 6 further comprising:

When the original mobility management unit is an SGSN, and the Gs interface is not supported between the SGSN and the MSC, the UE moves to the UTRAN coverage area under the MSC, and sends a location area update request message to the circuit domain MSC, requesting the new area. Registering;

The original mobility management unit acquires circuit domain location information that is registered in the original system before the UE moves, including:

When the UE needs to use the packet domain service, the original mobility management unit uses the routing area update process, and the radio network controller RNC that receives the routing area update request sends the partial RANAP message to the original mobility management through the radio access network access part. The unit carries the circuit domain MSC identifier or the network resource identifier NRI and the location area identifier LAI in the RANAP message, where the NRI is the NRI corresponding to the selected MSC stored by the RNC after selecting the circuit domain MSC.
The method of claim 2, further comprising:

The original mobility management unit is an SGSN, and the UE moves to a UTRAN coverage area under the jurisdiction of the MSC, and sends a location area update request message to the circuit domain MSC to request registration in a new area;

The original mobility management unit acquires circuit domain location information that is registered in the original system before the UE moves, including:

The MSC sends the user's International Mobile Subscriber Identity (IMSI) and the MSC address in the location area update message to the HSS, where the MSC address is the network resource identifier NRI or the MSC name;

When the UE needs to use the packet domain service and moves to the coverage area under the jurisdiction of the original mobility management unit, sending routing area update request information to the original mobility management unit; the original mobility management unit sends the location to the HSS Update the message, the location update acknowledge message returned by the HSS to the original mobility management unit carries the IMSI, MSC address information;

The original mobility management unit obtains an MSC address according to it.
A mobility management unit includes: an acquiring unit and a determining unit;

When the mobility management unit is the destination mobility management unit,

An acquiring unit, configured to acquire circuit domain location information registered in the original system before the UE moves in a context transfer process of the user equipment UE;

The determining unit is configured to make the destination mobile switching center MSC initiate a location update request to the home subscriber server HSS by using the obtained circuit domain location information registered in the original system before the UE moves.
The mobility management unit according to claim 10, wherein

The acquiring unit is configured to: send context request signaling to the original mobility management unit to acquire a context of the UE; and obtain, by using a context response message from the original mobility management unit, circuit domain location information that is registered in the original system before the UE moves.
The mobility management unit according to claim 10, wherein

The determining unit is configured to: carry the obtained circuit domain location information in a location update request message, and send the information to the destination MSC, so that the destination MSC determines, according to the obtained circuit domain location information, that the UE is not under its own jurisdiction. At the time, a location update request is initiated to the HSS.
The mobility management unit according to claim 10, wherein

The determining unit is configured to: when determining that the MSC changes according to the obtained circuit domain location information, the location update request message carries a special location area identifier for indicating that the destination MSC initiates a location update request, so that the After receiving the special location area identifier, the destination MSC sends a location update request message to the HSS.
The mobility management unit according to any one of claims 10 to 13, wherein the circuit domain location information registered in the original system comprises a location area identifier LAI, and/or a network resource identifier NRI.
The mobility management unit according to claim 14, wherein when the mobility management unit is an original mobility management unit,

The obtaining unit is further configured to: use the tracking area update TAU or the routing area to update the RAU process, and obtain the location update response message returned by the network element MSC of the circuit domain selected by the original mobility management unit to which the original mobile management unit belongs to obtain the UE before moving in the original system. Registered circuit domain location information.
The mobility management unit according to claim 14, when the mobility management unit is an original mobility management unit,

The obtaining unit is further configured to: receive, by using a routing area update process, a radio access network access part RANAP message sent by a radio network controller RNC that receives the routing area update request, where the RANAP message carries the circuit domain MSC The identifier or network resource identifier NRI, and the location area identifier LAI, wherein the NRI is an NRI corresponding to the selected MSC stored by the RNC after selecting the circuit domain MSC.
The mobility management unit according to claim 14, wherein when the mobility management unit is an original mobility management unit,

The obtaining unit is further configured to: when the UE needs to use a packet domain service, and move to a coverage area under the jurisdiction of the original mobility management unit, receive routing area update request information from the UE; and send a location update message to the HSS. And receiving the international mobile subscriber identity (IMSI) and MSC address information carried in the location update confirmation message returned by the HSS, and obtaining the network resource identifier NRI according to the obtained MSC address.
A computer storage medium having stored therein computer executable instructions for performing the method of any one of claims 1-9.