WO2009018754A1

WO2009018754A1 - Network acquiring temporary identity method, system and control plane entity

Info

Publication number: WO2009018754A1
Application number: PCT/CN2008/071813
Authority: WO
Inventors: Wanqiang Zhang; Lan Liu; Xiaolong Guo; Ming Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-03
Filing date: 2008-07-30
Publication date: 2009-02-12
Also published as: CN101360323A; CN101360323B

Abstract

Network acquiring temporary identity method, system and control plane entity are disclosed. The method includes: new control plane entity receives request message sent by use equipment, with first temporary mobile identity message in said request message; said new control plane entity sends request message to first old control plane entity according to said first temporary mobile identity message; said new control plane entity receives its request message or error response sent by said first old control plane entity; if said new control plane entity receives said error response, it requests second temporary mobile identity message from user equipment.

Description

Method, system and control plane entity for obtaining temporary identification on the network This application claims to be submitted to the Chinese Patent Office on August 3, 2007, with the application number of 200710075630.5, and the Chinese patent entitled "A Method and System for Temporary Identification of Network" Priority of the application, the entire contents of which are incorporated herein by reference.

Technical field

The present invention relates to the field of mobile communications, and in particular, to a method, system and device for acquiring a temporary identifier by a network.

Background technique

In the third generation mobile communication system, the most popular one is the Universal Mobile Telecommunications System (Universal Mobile Telecommunications System), which uses the Wideband Code Division Multiple Access (WCDMA) communication system air interface technology. UMTS), at the same time UMTS is also a third-generation wireless communication network technology standard defined by the Third Generation Partnership Project (3GPP) organization. As shown in Figure 1, the UMTS system consists of three parts, namely Core Network (CN), Universal Mobile Telecommunications System (UMTS Terrestrial Radio Access Network, UTRAN) and User Equipment (User Equipment, Referred to as UE).

The CN is logically divided into a Circuit Switched (CS) domain and a Packet Switched (PS) domain. The Mobile Switching Center/Visitor Location Register (MSC/VLR) and the Gateway Mobile Services Switching Center (GMSC) belong to the CS domain, and the general packet radio service support node. The Serving GPRS Support Node (SGSN) and the GPRS Gateway Support Node (GGSN) belong to the PS domain, and the Home Location Register (HLR) belongs to the CS domain and the PS domain. node.

At present, in 3GPP, various vendors are actively studying Long Term Evolved (LTE) System Architecture Evolved (S ΑΕ ), where LTE is used to provide a method for reducing latency and improving User data rates, improved system capacity, and low-cost networks covered, using PS domain services, the bearer networks are all IP bearers. 2 is an existing LTE/SAE network architecture. In the evolved packet core network: mobility management entity (Mobility Management Entity (MME), SAE Gateway, and Policy and Charging Rules Function (PCRF). among them:

The SAE gateway includes a Serving Gateway (S-GW) and a PDN Gateway (P-GW), where the S-GW and the P-GW are two logical entities, which may exist in the same or different On the physical entity. Different radio access technologies (Radio Access Technology, RAT for short) between SAE and Pre-SAE (that is, 2G/3G networks) have limitations signaling problems, that is, if UEs move between different RATs (such as 2G/3G networks and evolved networks). ), the UE will be stationed in different networks and frequently cause the network registration process. The frequent network registration process is a great waste to the air interface.

As shown in Figure 3, the multi-RAT network structure, RA1 and RA2 are the existing 2G/3G Routing Areas (RAs). The existing 2G/3G UEs initiate routing area updates every time the RA is replaced. (Routing Area Update, referred to as RAU) process. Of course, the UE also has a periodic location update process without changing the RA. The function is to enable the network to know that the UE is still in the network, and prevent the UE from leaving the network without knowing the network and continuously paging the UE. The following is not considered for the periodic update of the UE.

TA1, TA2, TA3, and TA4 are tracking areas of the evolved network. When a multimode UE moves in these areas, frequent network registration procedures occur. For example, the UE enters the RA1 to register with the SGSN of the 2G/3G. When the UE enters the TA1, the UE enters the TA1. Registering with the MME/UPE of the evolved network, when the UE moves out of TA1 and enters RA1, it registers with the SGSN of 2G/3G. The purpose of registration is to enable the network to page to the UE in a certain RAT, but this will result in a large amount of registration signaling overhead.

However, the UEs in the prior art only perform UE attachment in the respective systems. Similarly, in the existing routing area update and Tracking Area Update (TAU), the UE also needs to rely on the UE in the routing area update. The only temporary identifier carried.

Summary of the invention

Embodiments of the present invention provide a method, system, and device for acquiring a temporary identifier by a network, which implements attachment and routing area/updated area update under dual systems, thereby saving air interface resources and reducing network load.

An embodiment of the present invention provides a method for a network to obtain a temporary identifier, including:

The new control plane entity receives the request information sent by the user equipment, where the request information carries the first temporary mobile identity information; Sending, by the new control plane entity, request information to the first old control plane entity according to the first temporary mobile identity information;

Receiving, by the new control plane entity, information or an error response requested by the new control plane entity sent by the first old control plane entity;

If the new control plane entity receives the error response, requesting the second temporary mobile identity information from the user equipment.

The embodiment of the present invention further provides another method for the network to obtain the temporary identifier, the method comprising: the new control plane entity receiving the request information sent by the user equipment, where the request information carries the first temporary mobile identifier information and the second temporary mobile identifier information, And identifying the first temporary mobile identity information as the latest temporary mobile identity information;

Sending, by the new control plane entity, request information to the first old control plane entity according to the first temporary mobile identity information;

And if the new control plane entity receives the error response, sending the request information to the second old control plane entity according to the second temporary mobile identity information.

And sending, by the new control plane entity, the request information to the first old control plane entity and the second old control plane entity to the first old control plane entity according to the first temporary mobility identifier information and the second temporary mobility identifier information. The request information carries the first temporary mobile identity information, and the request information sent to the second old control plane entity carries the second temporary mobile identity information;

Receiving, by the new control plane entity, information or an error response requested by the new control plane entity sent by the first old control plane entity, and information requested by the new control plane entity sent by the second old control plane entity Or an error response;

The new control plane entity first obtains the first old control plane entity according to the received information or error response of the new control plane entity sent by the first old control plane entity. Identifying the first temporary mobile identity information, if the new control plane entity receives the error response, and then according to the information or error response requested by the new control plane entity sent according to the received second old control plane entity Obtaining a case where the second old control plane entity identifies the second temporary mobile identification information.

An embodiment of the present invention further provides a system for obtaining a temporary identifier by a network, including:

a new control plane entity, configured to receive request information sent by the user equipment, where the request information carries the first temporary mobile identity information and the second temporary mobile identity information;

a first old control plane entity, configured to receive request information sent by the new control plane entity, and determine whether the first temporary mobile identity information can be identified, where the first old control plane entity is corresponding to the first An entity that temporarily moves identification information;

a second old control plane entity, configured to receive request information sent by the new control plane entity, and determine whether the second temporary mobile identity information can be identified, where the second old new control plane entity is corresponding to the second An entity that temporarily moves identification information.

An embodiment of the present invention further provides a control plane entity, including:

a module for receiving request information sent by a user equipment, where the request information carries first temporary mobile identification information;

And a module, configured to send the request information to the first old control plane entity according to the first temporary mobile identity information, where the request information carries the first temporary mobile identity information;

a module for receiving information or error response requested by the control plane entity sent by the first old control plane entity;

And, after receiving the error response, requesting, from the user equipment, a module of the second time mobile identification information.

And a module for receiving the request information sent by the user equipment, where the request information carries the first temporary mobile identity information and the second temporary mobile identity information, and the first temporary mobile identity information is the latest temporary mobile identity information;

Information for receiving the control plane entity request sent by the first old control plane entity Or a module that responds incorrectly;

And a module for transmitting request information to the second old control plane entity according to the second temporary mobile identifier information, after the receiving the error response, the request information carrying the second temporary mobile identification information;

a module for receiving information or error response requested by the control plane entity sent by the second old control plane entity;

A module for requesting IMSI information from a user equipment after receiving the error response. An embodiment of the present invention further provides a control plane entity, including:

And a module for transmitting request information to the first old control plane entity and the second old control plane entity according to the first temporary mobility identifier information and the second temporary mobility identifier information, and sending the request information to the first old control plane entity The request information carries the first temporary mobile identity information, and the request information sent to the second old control plane entity carries the second temporary mobile identity information;

a module for receiving information or an error response requested by the new control plane entity sent by the first old control plane entity;

Means for receiving information or error response requested by the new control plane entity sent by the second old control plane entity.

Embodiments of the present invention carry different identifiers (for example, S-TMSI/TAI, or P-TMSI/RAI) information in an attach request, and perform corresponding processing on them, and request IMSI and security parameters to the corresponding SGSN or MME. Information, the process of attaching user equipment in a dual system network. At the same time, the routing area update or the tracking area update request carries different TMSI information and processes it correspondingly, and the corresponding SGSN/MME requests the context information, and the RAU or TAIL of the user equipment in the dual-system network is realized not only the dual system is implemented. Under the attachment and routing area / tracking area update, and can save air interface resources and reduce network burden.

DRAWINGS

1 is a schematic structural view of a UMTS system in the prior art.

2 is a schematic diagram of a LTE/SAE network architecture in the prior art. FIG. 3 is a schematic structural diagram of a multi-RAT network in the prior art.

4 is a flow chart of obtaining a temporary identifier of a dual-system network network according to an embodiment of the present invention.

Fig. 5 is a flow chart showing the attachment of the first embodiment of the present invention.

Figure 6 is a flow chart showing the attachment of the second embodiment of the present invention.

Fig. 7 is a flow chart showing the attachment of the third embodiment of the present invention.

Figure 8 is a flow chart showing the routing area update of the fourth embodiment of the present invention.

Figure 9 is a flow chart showing the routing area update of the fifth embodiment of the present invention.

ί 0 is a flowchart of routing area update in the sixth embodiment of the present invention.

1 is a flowchart of attachment of a seventh embodiment of the present invention.

[2] is an attachment flowchart of the eighth embodiment of the present invention.

Ί3 is an attachment flow chart of a ninth embodiment of the present invention.

ί 4 is a flowchart of routing area update in the tenth embodiment of the present invention.

It is a flowchart of the routing area update in the eleventh embodiment of the present invention.

[6] is a flowchart of the routing area update in the twelfth embodiment of the present invention.

Ί7 is a connection flowchart of the thirteenth embodiment of the present invention.

Ί8 is a flowchart of attachment of the fourteenth embodiment of the present invention.

Ί9 is a connection flowchart of the fifteenth embodiment of the present invention.

Figure 20 is a flow chart showing the update of the tracking area in the sixteenth embodiment of the present invention.

Figure 21 is a flow chart showing the update of the tracking area in the seventeenth embodiment of the present invention.

Figure 22 is a flow chart showing the update of the tracking area in the eighteenth embodiment of the present invention.

Figure 23 is a flow chart showing the attachment of the nineteenth embodiment of the present invention.

Figure 24 is a flow chart showing the attachment of the twentieth embodiment of the present invention.

Figure 25 is a flow chart showing the attachment of the twenty-first embodiment of the present invention.

Figure 26 is a flow chart showing the update of the tracking area in the twenty-second embodiment of the present invention.

Figure 27 is a flow chart showing the tracking area update of the twenty-third embodiment of the present invention.

Figure 28 is a flow chart showing the tracking area update of the twenty-fourth embodiment of the present invention.

detailed description

In the process of implementing the present invention, the inventors have found that only the single system is considered in the prior art, that is, the P-TMSI/RAI (Packet Temporary Mobile) is carried in the attach request in the UMTS network. Subscriber Identity/Routing Area Identity, the packet temporary mobile subscriber ID/route area identifier, and the SAE network carrying the S-TMSI/TAI (SAE Temporary Mobile Subscriber Identity/Tracking Area Identity SAE) The information requests the IMSI identity and security parameter information from the old SGSN and the MME, respectively. However, the prior art does not take into account the case where the UE carries another system information when it is attached in one system in the dual system, for example, attaching another system and initiating an attach request in the new system to the dual system network. The attachment of users is difficult. In addition, in the routing area update and tracking area update process, the network also relies on the unique temporary identifier provided by the UE to request context information, without considering the dual system. To this end, the embodiment of the present invention provides a method, system, and device for acquiring a temporary identifier by using a dual system, and implementing attachment and routing area/changing area update under dual systems to save air interface resources and reduce network. burden.

In order to make the technical solutions and advantages of the embodiments of the present invention more clear, the present invention will be further described in detail below with reference to the accompanying drawings.

The process for obtaining temporary identification of the network in the dual system network of the present invention is as shown in FIG. 4, wherein:

In step S301, the UE sends the request information to the new control plane entity, where the new control plane entity may be a new SGSN or a new MME, and the request information carries the latest TMSI information, and the latest TMSI information may be For the P-TMSI/RAI or the S-TMSI/TAI, the UE sends the request information to the request information in the new control plane entity, and the UE may send the request attachment information to the new SGSN/MME or the UE sends a request routing area update to the new SGSN. The information or the UE sends the request tracking area update information to the new MME;

Step S302: The new SGSN or the MME sends the request information to the corresponding old control plane entity according to the latest TMSI information, where the old control plane entity may be an old SGSN or an old MME, and the request information in the attach request is IMSI and security. Parameter; request information in the routing area update or tracking area update request is context request information;

Step S303, the old SGSN or MME determines whether the latest TMSI information can be identified, and if so, sends a response to the new SGSN or MME, returns the information to be requested, and if not, proceeds to step S304 or S308;

Step S304, the new SGSN or the MME requests another temporary mobile identity information from the UE.

Step S305, the UE confirms whether there is another temporary mobile identification information, and if yes, step S306 is performed. If yes, go to step S308, or directly send the IMSI information to the new SGSN or MME; Step S306, the new SGSN or MME requests information according to another temporary mobile identity information to the corresponding old SGSN/MME, where the request is in the attach request The request information is the context request information in the IMSI and the security parameter, the routing area update, or the tracking area update request.

Step S307, the old SGSN or the MME determines whether another temporary mobile identity information can be identified, and if yes, sends a response to the new MME, and returns the information to be requested. If not, step S308 is performed; Step S308, the UE sends the IMSI information to the new The SGSN or MME completes the network acquisition temporary identification. In step S301, if the request message carries P-TMSI/RAI and S-TMSI/TAI, and identifies which one is the latest TMSI information, step S302 may be performed, or may be simultaneously performed to the corresponding old SGSN or The MME requests the information, and preferentially uses the old SGSN or the old MME corresponding to the latest TMSI information to return the request information, and steps S304 and S305 are omitted.

In step S301, if the request message only carries the TMSI information of the system, in step S302, the new SGSN or the MME requests the information only from the corresponding old SGSN/MME according to the TMSI information.

The specific implementation manners of carrying in the attachment, routing area update or tracking area update of the user equipment in the dual system network according to the attachment request, the routing area update or the tracking area update request carrying different TMSI information and corresponding processing are as follows:

As shown in FIG. 5, the UE is attached to the UMTS according to the first embodiment of the present invention, and the latest TMSI information is an attaching flowchart of the S-TMSI/TAI, where:

In step 401, the UE sends an attach request message to the new SGSN, where the attach request message carries the latest TMSI information as S-TMSI/TAI information, and the mobile identifier as shown in Table 1 may be at a value of 100. Medium-identifying the S-TMSI information or adding a new value 110 to identify the S-TMSI information;

Step 402: The new SGSN sends an identity authentication request to the old MME, that is, the new SGSN requests the IMSI and the security parameter information according to the S-TMSI/TAI to the old MME, and the old MME confirms whether the S-TMSI/TAI can be identified, and if yes, sends the identity. The authentication response is sent to the new SGSN, and the information to be requested is returned. If not, step 403 is performed;

Step 403: The old MME sends an identity authentication response to the new SGSN, and sends an error indication to the new SGSN. After receiving the error indication, the new SGSN may perform step 404, or directly perform steps 408 and 409; Step 404, the new SGSN receives an error indication. Then, the identity request is sent to the UE, that is, the new SGSN requests the P-TMSI/RAI identification information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/RAI, as shown in Table 2 In the identifier type, the category 101 in the extended identifier type is P-TMSI, 110 is S-TMSI, and the UE determines whether there is P-TMSI/RAI, and if yes, step 405 is performed, and if not, directly responds to the IMSI information to the new one. SGSN;

Type of class

3 2 1

0 0 1 IMIS

0 1 0 IMEI

0 1 1 IMEISV

1 0 0 TMSI

1 0 1 P-TMSI

1 1 0 S-TMSI Table 2

Step 405: The UE sends an identifier request response to the new SGSN, that is, the UE sends the P-TMSI/RAI information to the new SGSN.

Step 406: The new SGSN sends an identity authentication request to the old SGSN, that is, the new SGSN requests the IMSI and the security parameter information by using the P-TMSI/RAI information to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if so, Sending an identity authentication response to the new SGSN, returning the information to be requested; if not, executing step 407;

Step 407: The old SGSN sends an identity authentication response to the new SGSN, and the old SGSN sends an error indication to the new SGSN.

Step 408: The new SGSN sends an IMSI information request to the UE.

Step 409: The UE sends the IMSI identification information to the new SGSN.

As shown in FIG. 6, the UE is attached to the UMTS according to the second embodiment of the present invention, and carries the S-TMSI/TAI and P-TMSI/RAI information, and the latest TMSI information is an attached flowchart of the S-TMSI/TAI, where :

Step 501: The UE sends an attach request message to the new SGSN, where the attach request message carries the S-TMSI/TAI and P-TMSI/RAI information, and the mobile identifier as shown in Table 1 may be in the value 100. The extension identifies the S-TMSI information or adds a new value 110 to identify the S-TMSI information. At the same time, the TMSI status information 11 is extended in Table 3, the latest TMSI information is identified as S-TMSI, the extended TMSI status information 10 is identified, the latest TMSI information is identified as P-TMSI, or a new P- is added as shown in Table 4. TMSI/S-TMSI status information, wherein a new P-TMSI/S-TMSI status information is added in Table 4 to identify the latest P-TMS and S-TMSI information.

table 3

Table 4

Step 502: After receiving the request information, the new SGSN preferentially uses the latest S-TMSI/TAI information, requests the IMSI and the security parameter information from the old MME according to the latest S-TMSI/TAI information; and the old MME confirms whether it can identify The S-TMSI/TAI information, if yes, sends an identity authentication response to the new SGSN, and returns information to be requested; if not, step 503 is performed.

Step 503, sending an identity authentication response to the new SGSN, sending an error indication to the new SGSN, after receiving the error indication, the new SGSN may perform step 504, or may directly perform steps 506, 507;

Step 504: After receiving the error indication, the new SGSN requests the old SGSN to use the IMSI and the security parameter information by using the P-TMSI/RAI information.

Step 505: The old SGSN confirms whether the SGSN can be identified, and if yes, sends an identity authentication response to the new SGSN, and returns information to be requested; if not, returns an error indication to the new SGSN; Step 506, the new SGSN sends the message to the UE. IMSI information request;

Step 507: The UE receives the IMSI information request, and sends the IMSI identification information to the new SGSN.

As shown in FIG. 7, in the third embodiment of the present invention, the UE is attached to the UMTS, and carries the P-TMSI/RAI information of the system, and the latest TMSI information is an attached flowchart of the S-TMSI/TAI, where: 601, the UE sends an attach request message to the new SGSN, where the attach request message carries the P-TMSI/RAI information in the system;

Step 602: The new SGSN sends an identity authentication request to the old SGSN, that is, the new SGSN requests the IMSI and the security parameter information according to the P-TMSI/RAI to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if yes, sends The identity authentication response is sent to the new SGSN, and the information to be requested is returned; if not, step 603 is performed;

Step 603: The old SGSN sends an identity authentication response to the new SGSN, and sends an error indication to the new SGSN. After receiving the error indication, the new SGSN may perform step 604, or directly perform steps 608 and 609; Step 604: After receiving the error indication, the new SGSN sends an identifier request to the UE, that is, the new SGSN requests the S-TMSI/TAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the type of the identifier in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is the S-TMSI. The UE determines whether there is an S-TMSI/TAI. If yes, step 405 is performed. No, directly responding to the IMSI information to the new SGSN;

Step 605: The UE sends the S-TMSI/TAI information to the new SGSN.

Step 606: The new SGSN sends an identity authentication request to the old MME, that is, the new SGSN requests the IMSI and the security parameter information by using the S-TMSI/TAI information to the old MME, and the old MME confirms whether the S-TMSI/TAI information can be identified, and if so, Sending an identity authentication response to the new SGSN, returning the information bundle to be requested, and if not, executing step 607;

Step 607: The old MME sends an identity authentication response to the new SGSN, and sends an error indication to the new SGSN. Step 608: The new SGSN sends an IMSI information request to the UE.

Step 609: The UE receives the IMSI information request, and sends the IMSI identification information to the new SGSN.

As shown in FIG. 8, in the fourth embodiment of the present invention, the UE initiates a routing area update in the UMTS, and the latest TMSI information is an update flowchart of the S-TMSI/TAI, where:

In step 4001, the UE sends a routing area update request message to the new SGSN, where the attach request message carries the latest TMSI information as S-TMSI/TAI information, and the mobile identifier is as shown in Table 1, and may be in the value. Extending the S-TMSI information in 100 or adding a new value 110 to identify the S-TMSI information;

Step 4002: The new SGSN sends a context request to the old MME, that is, the new SGSN requests context information according to the S-TMSI/TAI to the old MME, and the old MME confirms whether the S-TMSI/TAI can be identified, and if yes, sends a context response to the new SGSN. , returning the information to be requested; if not, executing step 4003;

Step 4003, the old MME sends a context response to the new SGSN, and sends an error indication to the new SGSN, where the new SGSN may perform step 4004 after receiving the error indication, or directly execute 4008;

Step 4004: After receiving the error indication, the new SGSN sends an identifier request to the UE, that is, the new SGSN requests the P-TMSI/RAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the type of the identifier in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is the S-TMSI. The UE determines whether there is a P-TMSI/RAI. If yes, step 4005 is performed. If not, directly responding to the IMSI information to the new SGSN;

Step 4005, the UE sends an identity response to the new SGSN, that is, the UE sends the P-TMSI/RAI information to the new SGSN.

Step 4006, the new SGSN sends a context request to the old SGSN, that is, the new SGSN requests the context information through the P-TMSI/RAI information to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if so, sends a context response to The new SGSN, returning the information to be requested; if not, executing step 4007;

Step 4007: The old SGSN sends a context response to the new SGSN, and the old SGSN sends an error indication to the new SGSN.

Step 4008: After receiving the error indication, the new SGSN performs a security function with the UE. As shown in FIG. 9, the UE initiates a routing area update in UMTS according to the fifth embodiment of the present invention, and carries S-TMSI/TAI and P-TMSI/RAI information, and the S-TMSI/TAI information is the latest TMSI information. Routing area update flowchart, where:

Step 5001: The UE sends a routing area update request message to the new SGSN, where the routing area update request message carries the S-TMSI/TAI and P-TMSI/RAI information, and the mobile identifier is as shown in Table 1. The S-TMSI information is extended in 100 or a new value 110 is added to identify the S-TMSI information. Meanwhile, the extended TMSI status information 11 in Table 3 identifies that the latest TMSI information is S-TMSI, extends TMSI status information 10, identifies that the latest TMSI information is P-TMSI, or adds a new P-TMSI as shown in Table 4. /S-TMSI status information, wherein a new P-TMSI/S-TMSI status information is added in Table 4 to identify the latest P-TMS and S-TMSI information.

Step 5002: After receiving the request information, the new SGSN preferentially uses the latest S-TMSI/TAI/information, and requests context information from the old MME according to the latest S-TMSI/TAI information; the old MME confirms whether the S can be identified. - TMSI/TAI information, if yes, sending a context response to the new SGSN, returning the information to be requested, and if not, executing step 5003,

Step 5003, sending a context response to the new SGSN, sending an error indication to the new SGSN, after receiving the error indication, the new SGSN may perform step 5004, or may directly execute 5006;

Step 5004: After receiving the error indication, the new SGSN requests the old SGSN for context information by using the P-TMSI/RAI information.

Step 5005, the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if so, Sending a context response to the new SGSN, returning the information to be requested; if not, returning an error indication to the new SGSN;

Step 5006: After receiving the error indication, the new SGSN performs a security function with the UE. Wherein, in step 5002, the following 5002a may also be substituted.

Step 5002a, the new SGSN requests context information from the old SGSN and the old MME according to the S-TMSI/TAI and the P-TMSI/RAI information, and preferentially uses the old MME to return information. If the old MME returns an error message, the old SGSN returns information. If the old SGSN returns an error message, step 5006 is performed.

As shown in FIG. 10, in the sixth embodiment of the present invention, a UE initiates a routing area update in UMTS, and carries P-TMSI/RAI information of the system, and the latest TMSI information is a routing area update flowchart of S-TMSI/TAI. , among them:

In step 6001, the UE sends a routing area update request message to the new SGSN, where the attach request message carries P-TMSI/RAI information in the system;

Step 6002: The new SGSN sends a context request to the old SGSN, that is, the new SGSN requests the context information according to the P-TMSI/RAI to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI can be identified, and if yes, sends a context response to the new SGSN. , returning the information to be requested; if not, executing step 6003;

Step 6003: The old SGSN sends a context response to the new SGSN, that is, sends an error indication to the new SGSN, where the new SGSN may perform step 6004 after receiving the error indication, or directly perform step 6008; Step 6004, after receiving the error indication, the new SGSN receives the error indication. Sending a request to the UE, that is, the new SGSN requests the S-TMSI/TAI identification information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI, as shown in Table 2, the identification type in the identification request, extension The category 101 in the identifier type is P-TMSI, 110 is S-TMSI, and the UE determines whether there is S-TMSI/TAI, if yes, step 6005 is performed, and if not, directly responds to the IMSI information to the new SGSN;

Step 6005, the UE sends the S-TMSI/TAI information to the new SGSN.

Step 6006, the new SGSN sends a context request to the old MME, that is, the new SGSN requests the context information by using the S-TMSI/TAI information to the old MME, and the old MME confirms whether the S-TMSI/TAI information can be identified, and if yes, sends a context response to The new SGSN, returning the information to be requested; if not, executing step 6007;

Step 6007, the old MME sends a context response to the new SGSN, that is, the old SGSN sends the new SGSN to the new SGSN. Error indication

Step 6008: After the new SGSN receives the error indication, the new SGSN and the UE perform a security function. As shown in FIG. 11, the UE is attached to the UMTS according to the seventh embodiment of the present invention, and the latest TMSI information is attached to the P-TMSI/RAI, where:

In step 701, the UE sends an attach request message to the new SGSN, where the attach request message carries the latest P-TMSI/RAI information;

Step 702: The new SGSN sends an identity authentication request to the old SGSN, that is, the new SGSN requests the IMSI and the security parameter information according to the P-TMSI/RAI to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI can be identified, and if yes, sends the identity. Authenticating to the new SGSN, returning the information to be requested; if not, executing step 703;

Step 703: The old SGSN sends an identity authentication response to the new SGSN, and sends an error indication to the new SGSN. After receiving the error indication, the new SGSN may perform step 704, or directly perform steps 708 and 709;

Step 704: After receiving the error indication, the new SGSN sends an authentication request to the UE, that is, the new SGSN requests the S-TMSI/TAI identification information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, 110 is S-TMSI, and the UE determines whether there is S-TMSI/TAI. If yes, step 705 is performed, if no , directly responding to the IMSI information to the new SGSN;

Step 705: The UE sends the S-TMSI/TAI information to the new SGSN.

Step 706: The new SGSN sends an identity authentication request to the old MME, that is, the new SGSN requests the IMSI and the security parameter information by using the S-TMSI/TAI information to the old MME, and the old MME confirms whether the S-TMSI/TAI information can be identified, and if so, Sending an identity authentication response to the new SGSN, returning the information to be requested; if not, executing step 707;

Step 707: The old MME sends an identity authentication response to the new SGSN, and the old SGSN sends an error indication to the new SGSN.

Step 708: The new SGSN sends an IMSI information request to the UE.

Step 709: The UE receives the IMSI information request, and sends the IMSI identification information to the new SGSN.

As shown in FIG. 12, the UE is attached to the UMTS according to the eighth embodiment of the present invention, and carries the S-TMSI/TAI and P-TMSI/RAI information, and the latest TMSI information is the attached flow of the P-TMSI/RAI. Chengtu, where:

Step 801: The UE sends an attach request message to the new SGSN, where the attach request message carries the S-TMSI/TAI and P-TMSI/RAI information, and the mobile identifier is extended as shown in Table 1. The S-TMSI information is identified or a new value 110 is added to identify the S-TMSI information. At the same time, the TMSI status information 11 is extended in Table 3, the latest TMSI information is identified as S-TMSI, the extended TMSI status information 10 is identified, the latest TMSI information is identified as P-TMSI, or a new P- is added as shown in Table 4. TMSI/S-TMSI status information, in which a new P-TMSI or S-TMSI status information is added in Table 4 to identify the latest P-TMS and S-TMSI information.

Step 802: After receiving the request information, the new SGSN preferentially uses the latest P-TMSI/RAI information, requests the IMSI and the security parameter information from the old SGSN according to the latest P-TMSI/RAI information; and the old SGSN confirms whether it can identify The P-TMSI/RAI information, if yes, sends an identity authentication response to the new SGSN, and returns the information to be requested; if not, step 803 is performed.

Step 803, sending an identity authentication response to the new SGSN, sending an error indication to the new SGSN, after receiving the error indication, the new SGSN may perform step 804, or may directly perform steps 806, 807;

Step 804: After receiving the error indication, the new SGSN requests the old MME to request the IMSI and the security parameter information by using the S-TMSI/TAI information.

Step 805: The old MME confirms whether the S-TMSI/TAI information can be identified, and if yes, sends an identity authentication response to the new SGSN, and returns the information to be requested; if not, returns an error indication to the new SGSN;

Step 806: After receiving the error indication, the new SGSN sends an IMSI information request to the UE. Step 807: After receiving the IMSI information request, the UE sends the IMSI identification information to the SGSN.

In step 802, after the new SGSN receives the request information, according to the S-TMSI/TAI and

The P-TMSI/RAI information requests IMSI and security parameter information from the old SGSN and the old MME at the same time, and preferentially uses the old SGSN to return information. If the old SGSN returns an error indication, steps 805, 806, and 807 are performed.

As shown in FIG. 13, the UE is attached to the UMTS according to the ninth embodiment of the present invention, and carries the system at the same time.

P-TMSI/RAI information, and the latest TMSI information is an attaching flowchart of the P-TMSI/RAI, where: In step 901, the UE sends an attach request message to the new SGSN, where the attach request message carries the system Internal P-TMSI/RAI information;

Step 902: The new SGSN sends an identity authentication request to the old SGSN, that is, the new SGSN is configured according to The P-TMSI/RAI requests the IMSI and the security parameter information from the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI can be identified, and if so, sends an identity authentication response to the new SGSN, and returns the information to be requested; if not, executes Step 903;

Step 903: The old SGSN sends an identity authentication response to the new SGSN, and sends an error indication to the new SGSN, where the new SGSN may perform step 904 after receiving the error indication, or directly perform steps 908, 909;

Step 904: After receiving the error indication, the new SGSN sends an identifier request to the UE, that is, the new SGSN requests the S-TMSI/TAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, 110 is S-TMSI, and the UE determines whether there is S-TMSI/TAI. If yes, step 905 is performed, if no , directly responding to the IMSI information to the new SGSN;

Step 905: The UE sends the S-TMSI/TAI information to the new SGSN.

Step 906: The new SGSN sends an identity authentication request to the old MME, that is, the new SGSN requests the IMSI and the security parameter information by using the S-TMSI/TAI information to the old MME, and the old MME confirms whether the S-TMSI/TAI information can be identified, and if so, Sending an identity authentication response to the new SGSN, returning the information to be requested; if not, executing step 907;

Step 907: The old MME sends an identity authentication response to the new SGSN, that is, the old SGSN sends an error indication to the new SGSN.

Step 908: After receiving the error indication, the new SGSN sends an IMSI information request to the UE. Step 909: After receiving the IMSI information request, the UE sends the IMSI identification information to the SGSN.

As shown in FIG. 14, the UE performs a routing area update in UMTS according to the tenth embodiment of the present invention, and carries the latest TMSI information as a routing area update flowchart of P-TMSI/RAI, where:

In step 7001, the UE sends a routing area update request message to the new SGSN, where the routing area update request message carries the latest P-TMSI/RAI information;

Step 7002, the new SGSN sends a context request to the old SGSN, that is, the new SGSN is based on

P-TMSI/RAI requests context information from the old SGSN, and the old SGSN confirms whether this can be recognized.

P-TMSI/RAI, if yes, sending a context response to the new SGSN, returning the information to be requested; if not, executing step 7003;

Step 7003: The old SGSN sends a context response to the new SGSN, and sends an error indication to the new SGSN. The new SGSN may perform step 7004 after receiving the error indication, or directly perform step 7008;

Step 7004: After receiving the error indication, the new SGSN sends an identifier request to the UE, that is, the new SGSN requests the S-TMSI/TAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is S-TMSI. The UE determines whether there is S-TMSI/TAI. If yes, step 7005 is performed. , directly responding to the IMSI information to the new SGSN;

Step 7005: The UE sends the S-TMSI/TAI information to the new SGSN.

Step 7006: The new SGSN sends a context request to the old MME, that is, the new SGSN requests the context information by using the S-TMSI/TAI information to the old MME, and the old MME confirms whether the S-TMSI/TAI information can be identified, and if yes, sends a context response to The new SGSN, returning the information to be requested; if not, executing step 7007;

Step 7007: The old MME sends a context response to the new SGSN, and the old SGSN sends an error indication to the new SGSN.

Step 7008: After receiving the error indication, the new SGSN performs a security function with the UE. As shown in FIG. 15, the UE initiates a routing area update in UMTS according to the eleventh embodiment of the present invention, and carries S-TMSI/TAI and P-TMSI/RAI information, and the P-TMSI/RAI information is the latest TMSI information. Routing area update flowchart, where:

Step 8001: The UE sends a routing area update request message to the new SGSN, where the routing area update request message carries the S-TMSI/TAI and P-TMSI/RAI information, and the mobile identifier is as shown in Table 1. The S-TMSI information is extended in 100 or a new value 110 is added to identify the S-TMSI information. At the same time, the TMSI status information 11 is extended in Table 3, the latest TMSI information is identified as S-TMSI, the extended TMSI status information 10 is identified, the latest TMSI information is identified as P-TMS, or a new P- is added as shown in Table 4. TMSI/S-TMSI status information, wherein a new P-TMSI/S-TMSI status information is added in Table 4 to identify the latest P-TMS and S-TMSI information.

Step 8002: After receiving the context request information, the new SGSN preferentially uses the latest P-TMSI/RAI information, and requests context information from the old SGSN according to the latest P-TMSI/RAI information; the old SGSN confirms whether the P can be identified. - TMSI/RAI information, if yes, sending a context response to the new SGSN, returning the information to be requested; if not, executing step 8003,

Step 8003, sending a context response to the new SGSN, sending an error indication to the new SGSN, the new SGSN After receiving the error indication, step 8004 may be performed, or step 8006 may be directly performed;

Step 8004: After receiving the error indication, the new SGSN requests the context information from the old MME by using the S-TMSI/TAI information.

Step 8005: The old MME confirms whether the S-TMSI/TAI information can be identified, and if yes, sends a context response to the new SGSN, and returns the information to be requested; if not, returns an error indication to the new SGSN;

Step 8006: After receiving the error indication, the new SGSN performs security functions with the UE.

In step 8002, after receiving the request context information, the new SGSN requests context information from the old SGSN and the old MME according to the S-TMSI/TAI and the P-TMSI/RAI information, and preferentially uses the old SGSN to return information, if If the old SGSN returns an error indication, steps 8005, 8006, and 8007 are performed.

As shown in FIG. 16, in the twelfth embodiment of the present invention, a UE initiates a routing area update in UMTS, and carries P-TMSI/RAI information of the system, and the latest TMSI information is a routing area update of P-TMSI/RAI. Flow chart, where:

In step 9001, the UE sends a routing area update request message to the new SGSN, where the routing area update request message carries the P-TMSI/RAI information in the system; and the mobile identifier is as shown in Table 1, and may be in the value Extending the S-TMSI information in 100 or adding a new value 110 to identify the S-TMSI information;

Step 9002: The new SGSN sends a context request to the old SGSN, that is, the new SGSN requests the context information according to the P-TMSI/RAI to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI can be identified, and if yes, sends a context response to the new SGSN. , returning the information to be requested; if not, executing step 9003;

Step 9003, the old SGSN sends a context response to the new SGSN, and sends an error indication to the new SGSN, where the new SGSN may perform step 9004 after receiving the error indication, or directly perform step 9008;

Step 9004: After receiving the error indication, the new SGSN sends an identifier request to the UE, that is, the new SGSN requests the S-TMSI/TAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is S-TMSI. The UE determines whether there is S-TMSI/TAI. If yes, step 9005 is performed. , directly responding to the IMSI information to the new SGSN;

Step 9005, the UE sends the S-TMSI/TAI information to the new SGSN. Step 9006, the new SGSN sends a context request to the old MME, that is, the new SGSN requests the context information by using the S-TMSI/TAI information to the old MME, and the old MME confirms whether the S-TMSI/TAI information can be identified, and if yes, sends a context response to The new SGSN, returning the information to be requested; if not, executing step 9007;

Step 9007, the old MME sends a context response to the new SGSN, and the old SGSN sends an error indication to the new SGSN.

Step 9008: After the new SGSN receives the error message, the new SGSN and the UE perform a security function. As shown in FIG. 17, the UE is attached to LTE according to the thirteenth embodiment of the present invention, and the latest TMSI information is an attaching flowchart of S-TMSI/TAI, where:

In step 1001, the UE sends an attach request message to the new MME, where the attach request message carries the latest TMSI information as S-TMSI/TAI information, and the mobile identifier is as shown in Table 1, and may be in the value 100. Extending the identifier S-TMSI information or adding a new value 110 to identify the S-TMSI information; Step 1002: The new MME sends an identity authentication request to the old MME, that is, the new MME requests the IMSI according to the S-TMSI/TAI to the old MME. Security parameter information, the old MME confirms whether the S-TMSI/TAI can be identified, and if so, sends an identity authentication response to the new MME, and returns the information to be requested; if not, step 1003 is performed;

Step 1003: The old MME sends an identity authentication response to the new MME, and sends an error indication to the new MME. After receiving the error indication, the new MME may perform step 1004, or directly perform steps 1008 and 1009.

Step 1004: After receiving the error indication, the new MME sends an identifier request to the UE, that is, the new MME requests the P-TMSI/RAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is S-TMSI. The UE determines whether there is a P-TMSI/RAI. If yes, step 1005 is performed. , directly responding to the IMSI information to the new SGSN;

Step 1005: The UE sends an identifier response to the new MME, that is, the UE sends the P-TMSI/RAI information to the new MME.

Step 1006: The new MME sends an authentication request to the old SGSN, that is, the new MME requests the IMSI and the security parameter information through the P-TMSI/RAI information to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if so, sends The identity authentication response is sent to the new MME, and the information to be requested is returned; If no, go to step 1007;

Step 1007: The old SGSN sends a verification response to the new MME, and the old SGSN sends an error indication to the new MME.

Step 1008: After receiving the error indication, the new MME sends an IMSI information request to the UE. Step 1009: After receiving the IMSI information request, the UE sends the IMSI identification information to the new MME. As shown in FIG. 18, the UE is attached to LTE and carries at the same time according to the fourteenth embodiment of the present invention.

S-TMSI/TAI and P-TMSI/RAI information, and the latest TMSI information is the attachment flow diagram of S-TMSI/TAI, where:

Step 1101: The UE sends an attach request message to the new MME, where the attach request message carries the S-TMSI/TAI and the P-TMSI/RAI information, and the mobile identifier is as shown in Table 1, and the identifier may be extended in the value 100. The S-TMSI information is either added with a new value of 110 to identify the S-TMSI information. At the same time, the TMSI status information 11 is extended in Table 3, the latest TMSI information is identified as S-TMSI, the extended TMSI status information 10 is identified, the latest TMSI information is identified as P-TMSI, or a new P- is added as shown in Table 4. TMSI/S-TMSI status information, wherein a new P-TMSI/S-TMSI status information is added in Table 4 to identify the latest P-TMS and S-TMSI information.

Step 1102: After receiving the request information, the new MME preferentially uses the latest S-TMSI/TAI information, and requests the IMSI and the security parameter information from the old MME according to the latest S-TMSI/TAI information; The S-TMSI/TAI information, if yes, sends an identity authentication response to the new MME, and returns information to be requested; if not, step 1103 is performed.

Step 1103: Send an identity authentication response to the new MME, and send an error indication to the new MME. After receiving the error indication, the new MME may perform step 1104, or may directly perform steps 1106, 1107; Step 1104, after receiving the error indication, the new MME receives the error indication. , requesting the IMSI and security parameter information from the old SGSN by using the P-TMSI/RAI information;

Step 1105: The old SGSN confirms whether the P-TMSI/RAI information can be identified, and if yes, sends an identity authentication response to the new MME, and returns information to be requested; if not, returns an error indication to the new MME;

Step 1106: After receiving the error indication, the new MME sends an IMSI information request to the UE. Step 1107: After receiving the IMSI information request, the UE sends the IMSI identification information to the new MME. In step 1102, the new MME may also be based on P-TMSI/RAI and S-TMSI/TAI simultaneously. The IMSI and the security parameter information are requested from the old SGSN and the old MME, and the information returned by the old MME is preferentially used. If the old MME returns an error indication, steps 1105, 1106, and 1107 are performed.

As shown in FIG. 19, the UE is attached to LTE according to the fifteenth embodiment of the present invention, and carries the latest TMSI information as an S-TMSI/TAI information attachment flowchart, where:

In step 1201, the UE sends an attach request message to the new MME, where the attach request message carries the S-TMSI/TAI information in the system, and the mobile identifier is as shown in Table 1, and the identifier may be extended in the value 100. S-TMSI information or a new value of 110 is added to identify S-TMSI information;

Step 1202: The new MME sends an identity authentication request to the old MME, that is, the new MME requests the IMSI and the security parameter information according to the S-TMSI/TAI to the old MME, and the old MME confirms whether the S-TMSI/TAI can be identified, and if yes, sends the identity. The authentication response is sent to the new MME, and the information to be requested is returned; if not, step 1203 is performed;

Step 1203: The old MME sends an identity authentication response to the new MME, and sends an error indication to the new MME. After receiving the error indication, the new MME may perform step 1204, or directly perform steps 1208 and 1209;

Step 1204: After receiving the error indication, the new MME sends an identifier request to the UE, that is, the new MME requests the P-TMSI/RAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is S-TMSI. The UE determines whether there is a P-TMSI/RAI. If yes, step 1205 is performed. , directly responding to the IMSI information to the new SGSN;

Step 1205, the UE confirms whether there is P-TMSI/RAI information, and if yes, step 1206 is performed, and if not, the IMSI information is directly sent to the new MME;

Step 1206: The new MME sends an identity authentication request to the old SGSN, that is, the new MME requests the IMSI and the security parameter information by using the P-TMSI/RAI information to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if so, sends The identity authentication response is sent to the new MME, and the information to be requested is returned; if not, step 1207 is performed;

Step 1207: The old SGSN sends an identity authentication response to the new MME, and the old SGSN sends an error indication to the new MME.

Step 1208: After receiving the error indication, the new MME sends an IMSI information request to the UE. Step 1209: After receiving the IMSI information request, the UE sends the IMSI identification information to the new MME. As shown in FIG. 20, the UE initiates a tracking area update in LTE according to the sixteenth embodiment of the present invention, and the latest TMSI information is a tracking area update flowchart of the S-TMSI/TAI, where:

In step 1011, the UE sends a tracking area update request message to the new MME, where the tracking area update request message carries the latest TMSI information as S-TMSI/TAI information, and the mobile identifier is as shown in Table 1. Adding an identifier S-TMSI information in the value 100 or adding a new value 110 to identify the S-TMSI information;

Step 1012: The new MME sends a context request to the old MME, that is, the new MME requests the context information according to the S-TMSI/TAI to the old MME, and the old MME confirms whether the S-TMSI/TAI can be identified, and if yes, sends a context response to the new MME. , returning the information to be requested; if not, executing step 1013;

Step 1013, the old MME sends a context response to the new MME, and sends an error indication to the new MME, where the new MME can perform step 1014 after receiving the error indication, or directly execute step 1018;

Step 1014: After receiving the error indication, the new MME sends an authentication request to the UE, that is, the new MME requests the P-TMSI/RAI identification information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is S-TMSI. The UE determines whether there is a P-TMSI/RAI. If yes, step 1015 is performed. , directly responding to the IMSI information to the new SGSN;

Step 1015: The UE sends a verification response to the new MME, that is, the UE sends the P-TMSI/RAI information to the new MME.

Step 1016: The new MME sends a context request to the old SGSN, that is, the new MME requests the context information through the P-TMSI/RAI information to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if yes, sends a context response to The new MME, returns the information to be requested; if not, step 1017;

Step 1017: The old SGSN sends a context response to the new MME, that is, the old SGSN sends an error indication to the new MME.

Step 1008: After receiving the error indication, the new MME performs a security function with the UE.

As shown in FIG. 21, the UE initiates a tracking area update in LTE according to the seventeenth embodiment of the present invention, and carries S-TMSI/TAI and P-TMSI/RAI information, and the S-TMSI/TAI information is the latest TMSI information. Tracking area update flow chart, where:

Step 1111: The UE sends a tracking area update request message to the new MME, where the tracking area is updated. The message carries the S-TMSI/TAI and P-TMSI/RAI information, and the mobile identifier is as shown in Table 1. The identifier S-TMSI information may be extended in the value 100 or a new value 110 may be added to identify the S. - TMSI information. At the same time, the TMSI status information 11 is extended in Table 3, the latest TMSI information is identified as S-TMSI, the extended TMSI status information 10 is extended, the latest TMSI information is identified as P-TMSI, or a new P- is added as shown in Table 4. TMSI/S-TMSI status information, wherein a new P-TMSI/S-TMSI status information is added in Table 4 to identify the latest P-TMS and S-TMSI information.

Step 1112: After receiving the request information, the new MME preferentially uses the latest S-TMSI/TAI information, and requests context information from the old MME according to the latest S-TMSI/TAI information; the old MME confirms whether the S- can be identified. TMSI/TAI information, if yes, sending a context response to the new MME, returning the information to be requested; if not, executing step 1113,

Step 1113, sending a context response to the new MME, sending an error indication to the new MME, after receiving the error indication, the new MME may perform step 1114, or may directly perform step 1116;

Step 1114: After receiving the error indication, the new MME requests the old SGSN to use the P-TMSI/RAI information to request text information.

Step 1115, the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if so, the request information ends; if not, returns an error indication to the new MME;

Step 1116: After the new MME receives the error indication information, the new MME sends the execution security function to the UE.

•6匕

dagger.

In step 1112, the new MME may also request context information from the old SGSN and the old MME according to the P-TMSI/RAI and the S-TMSI/TAI, and preferentially use the information returned by the old MME, if the old MME returns an error indication, Then, steps 1115 and 1116 are performed.

As shown in FIG. 22, the UE initiates a tracking area update in LTE according to the eighteenth embodiment of the present invention, and carries the latest TMSI information as an S-TMSI/TAI information tracking area update flowchart, where:

In step 1211, the UE sends a tracking area update request message to the new MME, where the tracking area update request message carries the S-TMSI/TAI information in the system, and the mobile identifier is as shown in Table 1, and may be in the value. The S-TMSI/TAI information is extended in the 100 or a new value 110 is added to the original value to identify the S-TMSI/TAI information.

Step 1212: The new MME sends a context request to the old MME, that is, the new MME requests the context information according to the S-TMSI/TAI to the old MME, and the old MME confirms whether the S-TMSI/TAI can be identified, and if so, Then, the context response is sent to the new MME, and the information to be requested is returned; if not, step 1213 is performed; Step 1213, the old MME sends a context response to the new MME, and sends an error indication to the new MME, where the new MME receives the error indication. Go to step 1214, or directly to step 1218;

Step 1214: After receiving the error indication, the new MME sends an identifier request to the UE, that is, the new MME requests the P-TMSI/RAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is S-TMSI. The UE determines whether there is a P-TMSI/RAI. If yes, step 1215 is performed. , directly responding to the IMSI information to the new SGSN;

Step 1215, the UE confirms whether there is P-TMSI/RAI information, and if yes, step 1216 is performed, and if not, the IMSI information is directly sent to the new MME;

Step 1216, the new MME sends a context request to the old SGSN, that is, the new MME requests the context information through the P-TMSI/RAI information to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if so, sends a context response to The new MME, returning the information to be requested; if not, executing step 1217;

Step 1217: The old SGSN sends a context response to the new MME, and the old SGSN sends an error indication to the new MME.

Step 1208: After receiving the error information, the new MME performs a security function with the UE. As shown in FIG. 23, the UE is attached to LTE according to the nineteenth embodiment of the present invention, and the latest TMSI information is attached to the P-TMSI/RAI, where:

In step 1301, the UE sends an attach request message to the new MME, where the attach request message carries the latest P-TMSI/RAI information; and as shown in Table 1, the mobile identifier can be extended in the value 100. - TMSI information or add a new value 110 to identify S-TMSI information;

Step 1302: The new MME sends an identity authentication request to the old SGSN, that is, the new MME requests the IMSI and the security parameter information according to the P-TMSI/RAI to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI can be identified, and if yes, sends the identity. The authentication response is sent to the new MME, and the information to be requested is returned; if not, step 1303 is performed;

Step 1303, the old SGSN sends an identity authentication response to the new MME, and sends an error indication to the new MME, where the new MME may perform step 1304 after receiving the error indication, or directly perform steps 1308, 1309; Step 1304: After receiving the error indication, the new MME sends an identifier request to the UE, that is, the new MME requests the S-TMSI/TAI identifier information from the UE, where a new value needs to be extended to identify the P-TMSI/RAI and the S-TMSI/ The TAI, as shown in Table 2, identifies the identifier type in the request. The category 101 in the extended identifier type is P-TMSI, and 110 is S-TMSI. The UE confirms whether there is S-TMSI/TAI information. If yes, step 1305 is performed. , directly sending the IMSI information to the new MME;

Step 1305, the UE sends the S-TMSI/TAI information to the new MME.

Step 1306, the new MME sends an identity authentication request to the old MME, that is, the new MME requests the IMSI and the security parameter information by using the S-TMSI/TAI information to the old MME, and the old MME confirms whether the S-TMSI/TAI information can be identified, and if so, sends The identity authentication response is sent to the new MME, and the information to be requested is returned; if not, step 1207 is performed;

Step 1307: The old MME sends an identity authentication response to the new MME, and the old SGSN sends an error indication to the new MME.

Step 1308: After receiving the error indication, the new MME sends an IMSI information request to the UE. Step 1309: After receiving the error IMSI information request, the UE sends the IMSI identity information to the new MME. As shown in FIG. 24, the UE is attached to LTE and carries at the same time according to the twentieth embodiment of the present invention.

S-TMSI/TAI and P-TMSI/RAI information, and the latest TMSI information is an attachment flow diagram of P-TMSI/RAI, where:

Step 1401: The UE sends an attach request message to the new MME, where the attach request message carries the S-TMSI/TAI and P-TMSI/RAI information, and the mobile identifier is extended as shown in Table 1. The S-TMSI information is identified or a new value 110 is added to identify the S-TMSI information. At the same time, the TMSI status information 11 is extended in Table 3, the latest TMSI information is identified as S-TMSI, the extended TMSI status information 10 is identified, the latest TMSI information is identified as P-TMSI, or a new P- is added as shown in Table 4. TMSI/S-TMSI status information, wherein a new P-TMSI/S-TMSI status information is added in Table 4 to identify the latest P-TMS and S-TMSI information.

Step 1402: After receiving the request information, the new MME preferentially uses the latest P-TMSI/RAI/information, and requests the IMSI and the security parameter information from the old SGSN according to the latest P-TMSI/RAI information; Identifying the P-TMSI/RAI information, if yes, sending an identity authentication response to the new MME, returning the information to be requested; if not, executing step 1403,

Step 1403: Send an identity authentication response to the new MME, and send an error indication to the new MME, new. After receiving the error indication, the MME may perform step 1404, or may directly perform steps 1406, 1407; Step 1404, after receiving the error indication, the new MME requests the IMSI and the security parameter information from the old MME by using the S-TMSI/TAI information;

Step 1405: The old MME confirms whether the S-TMSI/TAI information can be identified, and if yes, sends an identity authentication response to the new MME, and returns information to be requested; if not, returns an error indication to the new MME;

Step 1406: After receiving the error indication, the new MME sends an IMSI information request to the UE. Step 1407: After receiving the IMSI information request, the UE sends the IMSI identification information to the new MME.

In step 1402, after receiving the request information, the new MME requests the IMSI and the security parameter information from the old SGSN and the old MME according to the S-TMSI/TAI and the P-TMSI/RAI information, and preferentially uses the old SGSN. Returning the information, if the old SGSN returns an error indication, steps 805, 806, and 807 are performed.

As shown in FIG. 25, the UE is attached to LTE according to the twenty-first embodiment of the present invention, and carries the S-TMSI/TAI information of the system, and the P-TMSI/RAI is the latest attachment flow chart of the TMSI information, where:

In step 1501, the UE sends an attach request message to the new MME, where the attach request message carries the S-TMSI/TAI information in the system, and the mobile identifier is as shown in Table 1, and the identifier may be extended in the value 100. S-TMSI information or a new value of 110 is added to identify S-TMSI information;

Step 1502: The new MME sends an identity authentication request to the old MME, that is, the new MME requests the IMSI and the security parameter information according to the S-TMSI/TAI to the old MME, and the old MME confirms whether the S-TMSI/TAI can be identified, and if yes, sends the identity. The authentication response is sent to the new MME, and the information to be requested is returned; if not, step 1503 is performed;

Step 1503: The old MME sends an identity authentication response to the new MME, and sends an error indication to the new MME. After receiving the error indication, the new MME may perform step 1504, or directly perform steps 1508 and 1509;

Step 1504: After receiving the error indication, the new MME sends an identifier request to the UE, that is, the new MME requests the P-TMSI/RAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI and the S-TMSI/TAI. As shown in Table 2, the identifier type in the request is identified. The category 101 in the extended identifier type is P-TMSI, and 110 is S-TMSI. The UE determines whether there is S-TMSI/TAI information. If yes, the steps are performed. 1505, if not, return IMSI information directly to the new MME;

Step 1505: The UE sends P-TMSI/RAI information to the new MME.

Step 1506: The new MME sends an identity authentication request to the old SGSN, that is, the new MME requests the IMSI and the security parameter information by using the P-TMSI/RAI information to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if so, Sending an identity authentication response to the new MME, returning the information to be requested; if not, executing step 1507;

Step 1507: The old SGSN sends an identity authentication response to the new MME, that is, the old SGSN sends an error indication to the new MME.

Step 1508: After receiving the error indication, the new MME sends an IMSI information request to the UE. Step 1509: After receiving the IMSI information request, the UE sends the IMSI identification information to the new MME.

As shown in FIG. 26, the UE initiates a tracking area update request in LTE according to the twenty-second embodiment of the present invention, and carries the latest TMSI information as a tracking area update process of the P-TMSI/RAI, where:

In step 1311, the UE sends a tracking area update request message to the new MME, where the tracking area update request message carries the latest P-TMSI/RAI information; and the mobile identifier is as shown in Table 1, and may be in the value 100. Extending the identifier S-TMSI information or adding a new value 110 to identify the S-TMSI information; Step 1312, the new MME sends a context request to the old SGSN, that is, the new MME requests the context information according to the P-TMSI/RAI to the old SGSN. The old SGSN confirms whether the P-TMSI/RAI can be identified, and if yes, sends a context response to the new MME, and returns the information to be requested; if not, step 1313 is performed; Step 1313, the old SGSN sends a context response to the new MME, and sends The error is indicated to the new MME, where the new MME may perform step 1314 after receiving the error indication, or directly execute 1318;

Step 1314: After receiving the error indication, the new MME sends an identifier request to the UE, that is, the new MME requests the S-TMSI/TAI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI and the S-TMSI. 2 indicates the identifier type in the identifier request, the category 101 in the extended identifier type is P-TMSI, 110 is S-TMSI, and the UE confirms whether there is S-TMSI/TAI information, if yes, step 1305 is performed, and if not, directly sent IMSI information to the new MME;

Step 1315: The UE sends the S-TMSI/TAI information to the new MME.

In step 1316, the new MME sends a context request to the old MME, that is, the new MME requests the text information from the old MME through the S-TMSI/TAI information, and the old MME confirms whether the S-TMSI/TAI information can be identified, and if so, sends a context response to the MME. New MME, return the information to be requested; if not, perform the steps 1217;

Step 1317: The old MME sends a context response to the new MME, and the old SGSN sends an error indication to the new MME.

Step 1318: After receiving the error indication, the new MME performs a security function with the UE. As shown in FIG. 27, the UE initiates a tracking area update request in LTE according to the twenty-third embodiment of the present invention, and carries S-TMSI/TAI and P-TMSI/RAI information, and the latest TMSI information is P-TMSI/ RAI tracking area update request flow chart, where:

Step 1411: The UE sends a tracking area update request message to the new MME, where the tracking area update request message carries the S-TMSI/TAI and P-TMSI/RAI information, and the mobile identifier is as shown in Table 1. The value 100 is extended to identify the S-TMSI information or a new value 110 is added to identify the S-TMSI information. At the same time, the TMSI status information 11 is extended in Table 3, the latest TMSI information is identified as S-TMSI, the extended TMSI status information 10 is extended, the latest TMSI information is identified as P-TMSI, or a new P- is added as shown in Table 4. TMSI/S-TMSI status information, wherein a new P-TMSI/S-TMSI status information is added in Table 4 to identify the latest P-TMS and S-TMSI information.

Step 1412: After receiving the request information, the new MME preferentially uses the latest P-TMSI/RAI information, and requests context information from the old SGSN according to the latest P-TMSI/RAI information; the old SGSN confirms whether the P- can be identified. The TMSI/RAI information, if yes, sends a context response to the new MME, and returns the information to be requested; if not, step 1413 is performed.

Step 1413, sending a context response to the new MME, sending an error indication to the new MME, after receiving the error indication, the new MME may perform step 1414, or may directly perform step 1416;

Step 1414: After receiving the error indication, the new MME requests the context information from the old MME by using the S-TMSI/TAI information.

Step 1415: The old MME confirms whether the S-TMSI/TAI information can be identified, and if so, the request information ends; if not, returns an error indication to the new MME;

Step 1416: After receiving the error indication, the new MME performs a security function with the UE. In step 1412, after receiving the request information, the new MME requests the context information from the old SGSN and the old MME according to the S-TMSI/TAI and the P-TMSI/RAI information, and preferentially uses the old SGSN to return information. The SGSN returns an error indication, and steps 1415, 1416 are performed.

As shown in FIG. 28, the UE in the twenty-fourth embodiment of the present invention initiates a tracking area update in LTE. The request carries both the S-TMSI/TAI information of the system, and the P-TMSI/RAI is the tracking area update flowchart of the latest TMSI information, where:

In step 1511, the UE sends a tracking area update request message to the new MME, where the tracking area update request message carries the S-TMSI/TAI information in the system, and the mobile identifier is as shown in Table 1. The extension identifies the S-TMSI information or adds a new value 110 to identify the S-TMSI information. In step 1512, the new MME sends a context request to the old MME, that is, the new MME requests the context information according to the S-TMSI/TAI to the old MME. The old MME confirms whether the S-TMSI/TAI can be identified, and if yes, sends a context response to the new MME, and returns the information to be requested; if not, step 1513 is performed; Step 1513, the old MME sends a context response to the new MME. Sending an error indication to the new MME, where the new MME may perform step 1514 after receiving the error indication, or directly perform step 1518;

Step 1514: After receiving the error indication, the new MME sends an identifier request to the UE, that is, the new MME requests the P-TMSI identifier information from the UE, where the new value needs to be extended to identify the P-TMSI and the S-TMSI, as shown in Table 2. Indicates the identifier type in the identifier request. The category 101 in the extended identifier type is P-TMSI, 110 is S-TMSI, and the UE determines whether there is P-TMSI/RAI information. If yes, step 1515 is performed, and if not, directly to the new The MME returns the IMSI information;

Step 1515: The UE sends P-TMSI/RAI information to the new MME.

Step 1516: The new MME sends a context request to the old SGSN, that is, the new MME requests the context information through the P-TMSI/RAI information to the old SGSN, and the old SGSN confirms whether the P-TMSI/RAI information can be identified, and if yes, sends a context response to the new MME. MME, return the information to be requested; if not, proceed to step 1517;

Step 1517: The old SGSN sends a context response to the new MME, and the old SGSN sends an error indication to the new MME.

Step 1508: After receiving the error indication, the new MME performs a security function with the UE.

In the foregoing implementation manner, the non-access state (NAS) message carries the temporary identifier of the user equipment, and may also carry the temporary identifier of the user equipment in the radio resource control (RRC) message. The RRC message carrying the user equipment temporary identifier can only carry the system TMSI information to complete the node selection function. However, the RRC message carries the temporary identifier of the user equipment to save the temporary identifier of the user equipment in the NAS message, and the TMSI information of the system carried in the NAS in the foregoing embodiment can be placed in the RRC message, instead of being in the NAS. Repeat to save air interface resources.

A person skilled in the art can understand that all or part of the steps in implementing the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium, the storage. Media, such as: ROM/RAM, disk, CD, etc.

It can be seen that the present invention carries different TMSI information in the attach request and processes it accordingly, and requests the corresponding SGSN/MME to request IMSI and security parameter information to complete the process of attaching the user equipment in the dual system network. At the same time, the routing area update or tracking area update request carries different TMSI information and processes it correspondingly, and the corresponding SGSN or MME requests context information to complete the RAU or TAIL of the user equipment in the dual system network.

In all the embodiments of the present invention, one solution carries the latest identification information to the old SGSN/MME request information, which can save air interface resources, reduce network load, and ensure the attachment and routing area/connection under dual systems. Track area update. However, the UE does not necessarily carry the latest identification information in the request information. Therefore, the embodiment of the present invention carries the two information or carries the system information to the old SGSN/MME request information, which is also an attachment and routing area under the dual system. Or another way to track zone updates.

While the invention has been illustrated and described with reference to the preferred embodiments embodiments The spirit and scope of the invention are not departed.

Claims

Rights request

A method for obtaining a temporary identifier by a network, which is characterized by comprising:

The new control plane entity receives the request information sent by the user equipment, where the request information carries the first temporary mobile identity information;

The method for obtaining a temporary identifier by the network according to claim 1, wherein the method further comprises:

Receiving, by the first old control plane entity, request information sent by the new control plane entity; determining whether the first temporary mobile identity information can be identified; if yes, sending the new control plane to the new control plane entity The information requested by the entity; if not, an error response is sent to the new control plane entity.

The method for obtaining a temporary identifier by the network according to claim 1, wherein the first temporary mobile identifier information is latest temporary mobile subscriber identity information or temporary mobile subscriber identity information in the system, where The system is the system in which the new control plane entity is currently located.

The method for obtaining a temporary identifier by the network according to claim 3, wherein the first temporary mobile subscriber identity information or the second mobile subscriber identity information is identified in the mobile identity.

The method for obtaining a temporary identifier by the network according to claim 2, wherein the method further comprises:

After the new control plane entity requests the second temporary mobile identity information from the user equipment, the new control plane entity receives the second temporary mobile identity information or the IMSI information sent by the user equipment; if the new control plane entity receives the The second temporary mobile identity information is sent to the second old control plane entity according to the second temporary mobile subscriber identity information, where the request information carries the second temporary mobile subscriber identity information;

Receiving, by the new control plane entity, the new control plane sent by the second old control plane entity Information requested by the entity or error response;

If the new control plane entity receives the error response, the new control plane entity requests IMSI information from the user equipment.

The method for obtaining a temporary identifier by the network according to claim 5, wherein the method further comprises:

Receiving, by the second old control plane entity, request information sent by the new control plane entity; determining whether the second temporary mobile subscriber identity information can be identified; if yes, sending the new control to the new control plane entity The information requested by the plane entity, if not, sends an error response to the new control plane entity.

The method for obtaining a temporary identifier by a network according to claim 5, wherein the first temporary mobile subscriber identity information or the second mobile subscriber identity information is identified in the identity request.

The method for obtaining a temporary identifier by a network according to any one of claims 1 to 6, wherein the new control plane entity is a new serving GPRS support node or a new mobility management entity; The mobile identity information is a packet temporary mobile subscriber identity, and the first old control plane entity is an old serving GPRS support node, the second old control plane entity is an old mobility management entity, and the second temporary mobile identity information is a temporary mobility of the SAE packet. User ID;

If the first temporary mobile identity information is a SAE packet temporary mobile subscriber identity, the first old control plane entity is an old mobility management entity, the second old control plane entity is an old serving GPRS support node, and the second temporary mobility is The identification information is a packet temporary mobile subscriber identity.

The method for obtaining a temporary identifier by the network according to claim 8, wherein the receiving, by the new control plane entity, the request information sent by the user equipment includes:

The new service GPRS support node or the new mobility management entity receives the attach request sent by the user equipment, and the request information sent by the new control plane entity to the first old control plane entity or the second old control plane entity is the identity authentication request information; or

The new service GPRS support node receives the routing area update request sent by the user equipment, and the request information sent by the new control plane entity to the first old control plane entity or the second old control plane entity is context request information; or

The new mobility management entity receives the tracking area update request sent by the user equipment, and the request information sent by the new control plane entity to the first old control plane entity or the second old control plane entity is a context request. Information.

The new control plane entity receives the request information sent by the user equipment, where the request information carries the first temporary mobile identity information and the second temporary mobile identity information, and the first temporary mobile identity information is the latest temporary mobile identity information;

The method for obtaining a temporary identifier by the network according to claim 10, wherein the method further comprises:

Receiving, by the new control plane entity, information or an error response requested by the new control plane entity sent by the second old control plane entity;

If the new control plane entity receives the error response, requesting from the user equipment

IMSI information.

The method for obtaining a temporary identifier by the network according to claim 11, wherein the method further comprises:

Receiving, by the second old control plane entity, request information sent by the new control plane entity; determining whether the second temporary mobile subscriber identity information can be identified; if yes, sending the new control to the new control plane entity Information requested by the plane entity; if not, an error response is sent to the new control plane entity.

The method for obtaining a temporary identifier by a network according to any one of claims 10 to 13, wherein the first temporary mobile subscriber identity information or the second mobile subscriber identity information is identified in a mobile identity.

The method for obtaining a temporary identifier by a network according to any one of claims 10 to 13, wherein: the first temporary mobile subscriber identity information and/or the second mobile subscriber identity information are in a temporary mobile subscriber identity state. Logo.

The method for obtaining a temporary identifier by the network according to claim 15, wherein the first temporary mobile subscriber identity information and the second mobile subscriber identity information are identified in the temporary mobile subscriber identity state as: Add a new value identifier to the user ID status, or add a new temporary mobile user ID status information identifier.

The method for obtaining a temporary identifier by a network according to any one of claims 10 to 13, wherein the new control plane entity is a new serving GPRS support node or a new mobility management entity.

If the first temporary mobile identity information is a packet temporary mobile subscriber identity, the first old control plane entity is an old serving GPRS support node, the second old control plane entity is an old mobility management entity, and the second temporary mobile identity is The information is a temporary mobile subscriber identity of the SAE packet;

The method for obtaining a temporary identifier by the network according to claim 17, wherein the receiving, by the new control plane entity, the request sent by the user equipment comprises:

The new service GPRS support node or the new mobility management receiving user equipment sends an attach request, and the request information sent by the new control plane entity to the first old control plane entity or the second old control plane entity is the identity authentication request information; or

The new service GPRS support node receives the routing information update request from the user equipment, and the request information sent by the new control plane entity to the first old control plane entity or the second old control plane entity is context request information; or

The new mobility management receiving user equipment sends a tracking area update request, and the request information sent by the new control plane entity to the first old control plane entity or the second old control plane entity is context request information.

19. A method for obtaining a temporary identifier by a network, comprising:

The new control plane entity first obtains, according to the received information or the error response of the new control plane entity sent by the first old control plane entity, the first old control plane entity to identify the first temporary mobile identifier information. If the new control plane entity receives the error response, the second old control plane entity identifier is obtained according to the information or the error response requested by the new control plane entity sent by the second old control plane entity. The case of the second temporary mobile identification information.

The method for obtaining a temporary identifier by a network according to claim 19, wherein the method further comprises: if the new control plane entity receives an error response sent by the first old control plane entity and The error response sent by the second old control plane entity requests the IMSI information from the user equipment.

The method for obtaining a temporary identifier by a network according to claim 19 or 20, wherein the method further comprises:

Receiving, by the first old control plane entity, request information sent by the new control plane entity; determining whether the first temporary mobile subscriber identity information can be identified, and if yes, sending the new control to the new control plane entity Information requested by the plane entity; if not, an error response is sent to the new control plane entity.

The method for obtaining a temporary identifier by a network according to claim 19 or 20, wherein the method further comprises: Receiving, by the second old control plane entity, request information sent by the new control plane entity; determining whether the second temporary mobile subscriber identity information can be identified, and if yes, sending the new control to the new control plane entity Information requested by the plane entity; if not, an error response is sent to the new control plane entity.

A system for obtaining a temporary identifier by a network, comprising:

24. The system for obtaining temporary identification by a network according to claim 23, wherein the new control plane entity is a new serving GPRS support node or a new mobility management entity.

The system for obtaining a temporary identifier by the network according to claim 23, wherein if the first temporary mobile identity information is a packet temporary mobile subscriber identity, the first old control plane entity is an old serving GPRS support node, The second old control plane entity is an old mobility management entity, and the second temporary mobility identifier information is a SAE packet temporary mobile user identifier;

26. A control plane entity, comprising:

a module for receiving information or error response requested by the control plane entity sent by the first old control plane entity; A module for requesting second temporary mobile identification information from a user equipment after receiving the error response.

27. A control plane entity, comprising:

A module for requesting IMSI information from a user equipment after receiving the error response.

28. A control plane entity, comprising:

29. The control plane entity of claim 28, wherein The control plane entity first obtains, according to the received information or the error response of the new control plane entity sent by the first old control plane entity, the first old control plane entity to identify the first temporary mobile identity information, And if the new control plane entity receives the error response, obtaining the second old control plane entity identification second according to the information or the error response requested by the new control plane entity sent according to the received second old control plane entity. The case of temporarily moving identification information.

The control plane entity according to claim 28 or 29, further comprising: an error response for transmitting the first old control plane entity and the second old control plane entity sending After the error response, the module that requests the IMSI information from the user equipment.