WO2013020293A1

WO2013020293A1 - Service restoration method and device

Info

Publication number: WO2013020293A1
Application number: PCT/CN2011/078268
Authority: WO
Inventors: 陈中平; 吴问付
Original assignee: 华为技术有限公司
Priority date: 2011-08-11
Filing date: 2011-08-11
Publication date: 2013-02-14
Also published as: CN103053209A; CN103053209B

Abstract

The present invention relates to a service restoration method and device, the service restoration method in an ISR state comprising: when a trigger message sent from a network side is received, setting a new TIN for a user equipment (UE) according to a currently accessed network and a current TIN on the UE; if a position update flow needs to be initiated according to the new TIN of the UE, then initiating the position update flow, wherein the position update flow is used to realize the service restoration. An embodiment of the present invention restores user context via the position update flow according to the currently accessed network and the TIN of the UE, rather than reestablishes the context only via an attach flow, thus improving service restoration efficiency.

Description

Method and equipment for business recovery

The present invention relates to the field of communications technologies, and in particular, to a method and device for service recovery. Background technique

In the process of network to broadband and mobile development, the 3rd Generation Partnership Program (3GPP) has proposed a Long Term Evolution (LTE) solution in the mobile access network. , the Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN), and the evolution of the system architecture in the mobile core network (System Architecture Evolution) The SAE scheme is the Evolved Packet Core (EPC). E-UTRAN and EPC form the Evolved Packet System (EPS). User Equipment (User Equipment, UE) In addition to accessing EPC through E-UTRAN, it can also be used by Universal Mobile Telecommunication System Territorial Radio Access Network (UTRAN) or global mobile. Global System for Mobile Communications (GSM) / Enhanced Data Rate for GSM Evolution (GSM) GSM Radio Access Network (GSM EDGE Radio Access Network) EPC. The logical function of the core network of the evolved packet network mainly includes SGSN (Serving GPRS Support Node), MME (Mobility Management Entity), S-GW (Serving Gateway), P- GW (Packet Data Network Gateway).

In this network structure, a successful Attach process means that the MME or SGSN creates a context for the UE. After attaching, the UE may also activate the EPS bearer to enjoy the packet service provided by the EPS. If the UE has completed the attach procedure, the subsequent UE reselects between E-UTRAN and UTRAN/GERAN, and a corresponding location update procedure occurs, for example, a Routing Area Update (RAU) process or a tracking area location update. TAU (Tracking Area Update) process. In the RAU process, the SGSN provides a packet service for the UE after acquiring the user context from the MME, which ensures continuity of the user service; in the TAU process, the MME After obtaining the user context, the SGSN provides the packet service for the UE, which ensures the continuity of the user service. Idle mode signaling reduction (Idle mode) is a mechanism for limiting UEs in idle mode to reselect signals generated by different radio access networks, and is used to reduce UEs in E-UTRAN and UTRAN/GERAN. Reselection between them results in frequent TAU and RAU processes. The ISR activation means that the UE is attached to both the MME and the SGSN; the mobility management MM (Mobility Management) parameters saved by the UE include parameters from the MME (for example, the global unique temporary identifier GUTI and the tracking area identifier TAI list). There are parameters from the SGSN (eg, Packet Temporary Mobile Subscriber Identity P-TMSI and Routing Area Identity RAI). After the ISR is activated, the idle state UE performs E-UTRAN and UTRAN/GERAN reselection, but does not leave the registration area (for example, the registered routing area RA or the tracking area TA), then the UE does not initiate the corresponding TAU or RAU procedure. , played a role in saving signaling.

In addition, in the network structure, if the UE has successfully completed the attach process and enjoys the packet service provided by the EPS, in some scenarios, for example, the UE receives the TAU Reject (Tracking Area Update Reject) sent by the MME. a message or a Service Reject message and the reason for the rejection in the message may indicate that the UE identity cannot be derived by the network; or the UE receives the IMSI (International Mobile Subscriber Identification Number, International Mobile) The user only has another ll code) and "CN domain indicator (Core Network Domain Indicator), "Paging" message set to "PS (Packet Domain)", etc., the UE will re-execute the attach procedure. To complete the reconstruction of the context, and additionally reactivate the EPS bearer (EPS Bearer) to enjoy the packet service provided by the EPS. Similarly, a similar scenario occurs when the UE resides in the GERAN/UTRAN network.

For the UE, the behavior of the bearer corresponding to the packet service that is triggered by the network to re-initiate the attach process and re-activate the EPS will cause the original service of the UE to be unable to continue, affecting the service experience of the user, and reducing the service recovery. effectiveness. Summary of the invention

Embodiments of the present invention provide a method and user equipment for service recovery, which can improve the efficiency of service recovery.

On the one hand, a method for service recovery under the ISR is provided, including: when receiving a trigger message sent by the network side, setting a user setting according to the current TIN on the current access network and the user equipment. A new TIN is prepared. If the location update process needs to be initiated according to the new TIN of the user equipment, a location update process is initiated, where the location update process is used to implement service recovery.

On the other hand, a method for service recovery under the ISR is provided, including: a trigger message sent to the user equipment, so that the user equipment sets a new TIN of the user equipment according to the current TIN on the current access network and the user equipment; Receiving a location update request message sent by the user equipment in the case that the location update process needs to be initiated according to the new TIN, and recovering the service of the user equipment.

In another aspect, a user equipment is provided, including: a setting unit, configured to: when receiving a trigger message sent by a network side, set a new TIN of the user equipment according to a current TIN on the current access network and the user equipment; The recovery unit is configured to initiate a location update process if the location update process needs to be initiated according to the new TIN of the user equipment, where the location update process is used to implement service recovery.

In another aspect, a mobile management network element device is provided, including: a sending unit, configured to send a trigger message to a user equipment, so that the user equipment uses the temporary according to the current access network and the current next update on the user equipment. The TIN is set to set a new TIN of the user equipment, and the receiving unit is configured to receive a location update request message sent by the user equipment to learn the location update process according to the new TIN, and restore the service of the user equipment.

In the embodiment of the present invention, the user context is restored through the location update process according to the TIN of the user equipment and the current access network, instead of only reestablishing the context through the attach procedure, thereby improving the efficiency of service recovery. DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only the present invention. For some embodiments, other drawings may be obtained from those skilled in the art without any inventive labor.

1 is a schematic structural diagram of a communication system to which an embodiment of the present invention is applicable.

2 is a flow chart of a method of service recovery in accordance with an embodiment of the present invention.

FIG. 3 is a schematic flow chart of a service recovery process according to an embodiment of the present invention.

4 is a schematic flow chart of a method for service recovery according to another embodiment of the present invention.

FIG. 5 is a flowchart of a method for service recovery according to another embodiment of the present invention.

Figure 6 is a block diagram of a user equipment in accordance with one embodiment of the present invention. 7 is a block diagram of a mobility management network element device in accordance with an embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

1 is a schematic structural diagram of a communication system to which an embodiment of the present invention is applicable. As shown in FIG. 1, the user equipment 101 is accessed through the local wireless access network 102, and the mobility management network element 103 is responsible for functions such as location management, connection management, security authentication, and gateway selection of the mobile user equipment. The service gateway 104 is a local access gateway of the user equipment, and is responsible for access technology related connection management and data forwarding. The packet data network gateway 105 is a gateway for user equipment to access an external data network.

The user equipment in the embodiment of the present invention may be: User Equipment (User Equipment); or Mobile Station (Mobile Station).

The radio access network in the embodiment of the present invention may be: E-UTRAN, and the access network element may be an E-UTRAN NodeB (E-UTRAN NodeB, called eNodeB); or GERAN, the access network element It may be a Base Transceiver Station (BTS); or a UTRAN, and its access network element may be a 3G base station (NodeB).

The mobility management network element in the embodiment of the present invention may be an MME or an SGSN.

The serving gateway in the embodiment of the present invention may be an S-GW.

The packet data network gateway in the embodiment of the present invention may be a P-GW.

The logical function of the EPC mainly includes the SGSN, the MME, the S-GW, and the P-GW. In addition to accessing the EPC through the E-UTRAN, the UE can access the EPC through UTRAN or GERAN. After the ISR is activated, the idle state UE performs E-UTRAN and UTRAN/GERAN reselection, and the UE does not initiate the corresponding TAU or RAU procedure. The embodiment of the present invention can restore the user context and maintain the EPS bearer of the user through the location update process or the attach process according to the TIN (Temporary Identity used in Next update) of the UE and the current access network. Rather than rebuilding the context by re-executing the attach process as in the prior art, the efficiency of business recovery is improved.

2 is a flow chart of a method for service recovery under an ISR according to an embodiment of the present invention. The method of Figure 2 is performed by a user equipment. 201. When receiving the trigger message sent by the network side, set a new TIN of the user equipment according to the current TIN on the current access network and the user equipment.

The trigger message may be a reject message sent by the mobility management network element after receiving the request message of the user equipment, or a paging message sent by the access network element.

For example, in a case where the current access network is E-UTRAN, the request message is a tracking area location update request message, the reject message is a tracking area reject message; or the request message is a service request message, and the reject message is a service reject message. In the case that the current access network is GERAN or UTRAN, the request message is a routing area location update request message, and the reject message is a routing area reject message; or the request message is a service request message, and the reject message is a service reject message.

Specifically, if the UE is currently accessing the E-UTRAN network, receiving the trigger message may include one of the following ways:

The UE sends a request message, for example, a tracking area location update request (TAU Request, Tracking Area Update Request) or a monthly service request (Service Request) message; the MME receiving the request message sends a reject message to the UE, for example The reject message may be a TAU Reject, Tracking Area Update Reject message or a Service Reject message. In addition, the reason for the rejection in the message may be indicated as UE identity can't be derived by the network or implicitly detached or No EPS bearer context activated.

Or the UE receives the paging message, where the paging message carries the user identifier IMSI

(International Mobile Subscriber Identification Number, international mobile subscriber only ll code) information, and CN domain indicator (Core Network Domain Indicator) is set to PS (Packet Domain).

Similarly, if the UE is currently accessing the GERAN/UTRAN network, receiving the trigger message may include one of the following methods:

Sending, by the UE, a request message, for example, a RAU Request (Routing Area Update Request) or a Service Request (Service Request) message; the SGSN receiving the request message sends a reject message to the UE, for example, The reject message may be a RAU Reject (Routing Area Update Reject) message or a Service Reject message. In addition, the reason for the rejection in the message may indicate that the UE's target i is not delicious (UE identity cannot be derived by the network) or implicitly separated. (Implicitly detached) or No EPS bearer context activated.

Alternatively, the UE receives the paging message, where the paging message carries the subscriber identity IMSI information, and the CN domain indicator (Core Network Domain Indicator) is set to PS (Packet Domain).

The TIN is a parameter of the UE context and is used to determine the UE identification information to be carried in the next UE-initiated message (for example, TAU Request or RAU Request or Attach Request). The value of the TIN can be, GUTI (Globally Unique Temporary Identity) or P-TMSK Packet Temporary Mobile Subscriber Identity, or RAT-related TMSI (radio acess technology-related Temporary Mobile) Subscriber Identity, the temporary mobile user identity associated with the wireless access technology).

For example, when the UE sends a TAU Request message, if the current TIN indicates GUTI or RAT-related TMSI, and the UE holds a valid GUTI, then the cell Old (old) GUTI in the TAU Request message is assigned this valid value. GUTI, that is, the cell Old GUTI indicates the GUTI that is valid for this; if the current TIN is indicated as P-TMSI, and the UE holds a valid P-TMSI and the RAI (Routing Area Identity) associated with the P-TMSI Zone ID;), then the cell Old GUTI in the TAU Request message is obtained by this valid P-TMSI and RAI mapping, ie, the cell Old GUTI indicates the P-TMSI that is valid for this and is associated with this P-TMSI RAL

When the UE initiates the RAU Request message, if the current TIN indicates P-TMSI or RAT-related TMSI, and the UE holds a valid P-TMSI and the RAI associated with the P-TMSI, then the message in the RAU Request message The meta Old P-TMSI and Old RAI are respectively assigned the valid P-TMSI and the RAI associated with this P-TMSI, ie, the cell Old P-TMSI indicates the P-TMSI that is valid for this, the cell Old RAI indication For the RAI associated with this P-TMSI; if the current TIN is indicated as GUTI, and the UE holds a valid GUTI, then the cells Old P-TMSI and Old RAI in the RAU Request message are obtained by this valid GUTI mapping, That is, this valid GUTI indication is the cells Old P-TMSI and Old RAI.

In addition, for the UE, the TIN can also be used to determine the state of the ISR. The TIN is set to RAT-related TMSI, which can be used to indicate that the UE is in an ISR active state; otherwise, the TIN is set to GUTI or P-TMSI, which can be used to indicate that the UE is in an ISR inactive state or deactivated. State. In addition, the RAT-related TMSI may also be used to indicate that the MME reserved for the UE and the UE context saved by the SGSN serving the UE are synchronized; the GUTI indicates that the UE context saved by the MME serving the UE is up to date; - The TMSI indicates that the UE context saved by the SGSN serving the UE is up to date.

Therefore, in the case that the current access network is an evolved UMTS terrestrial radio access network E-UTRAN, the above-mentioned setting of the UE's new TIN may include:

When the current TIN of the UE is RAT-related TMSI, the UE's new TIN is set to P-TMSI; or

When the current TIN of the UE is RAT-related TMSI, if there is a newly activated service bearer (for example, when the TIN of the UE is set to RAT-related TMSI, that is, after the ISR is activated, there is a newly activated service bearer), Keeping the UE's new TIN as RAT-related TMSI or setting the UE's new TIN to GUTI, if there is no newly activated service bearer, setting the UE's new TIN to P-TMSI; or

When the current TIN of the UE is GUTI, the UE's new TIN is kept as GUTI; or

When the current TIN of the UE is GUTI, if the UE saves the valid P-TMSI and the corresponding routing area identifier RAI, the new TIN of the UE is set to P-TMSI, if the UE does not save the valid P-TMSI and corresponding The RAI keeps the UE's new TIN as GUTI.

In summary, the UE currently accesses the E-UTRAN network and the new TIN set is P-TMSI, meaning that the SGSN serving the UE holds the UE context or the latest UE context. Therefore, the UE may initiate a TAU process, and the MME obtains the UE context or the latest UE context from the SGSN, so that the UE initiates the attach procedure and reconstructs the context.

In addition, in the case that the current access network is GERAN or UTRAN, the above-mentioned new TIN for setting the user equipment may include:

When the current TIN of the UE is RAT-related TMSI, the UE's new TIN is set to

GUTI; or

When the current TIN of the UE is RAT-related TMSI, if there is a newly activated service bearer (for example, after the TIN of the UE is set to RAT-related TMSI, that is, after the ISR is activated), the UE's new TIN is kept as RAT-related TMSI either sets the UE's new TIN to P-TMSI, and if there is no newly activated service bearer, sets the UE's new TIN to GUTI; or When the current TIN of the UE is P-TMSI, the UE's new TIN is kept as P-TMSI; or

When the current TIN of the UE is P-TMSI, if the UE saves the valid GUTI, the UE's new TIN is set to GUTI. If the UE does not save the valid GUTI, the UE's new TIN is kept as P-TMSL.

In summary, the UE currently accesses the GERAN/UTRAN network and the new TIN set is GUTI, meaning that the MME serving the UE holds the UE context or the latest UE context. Therefore, the UE may initiate a RAU procedure, so that the SGSN obtains the UE context or the latest UE context from the MME, and avoids the UE initiating the attach procedure and reestablishing the context.

202. If it is learned that the location update process needs to be initiated according to the new TIN of the user equipment, the location update process is initiated, where the location update process is used to implement service recovery.

Specifically, when the current access network is E-UTRAN, if the new TIN of the UE is P-TMSI, and it is learned that the location update process needs to be initiated, the tracking area location update process is initiated in the E-UTRAN; or the current access is performed. When the network is GERAN/UTRAN, if the UE's new TIN is GUTI, it is known that the location update procedure needs to be initiated, and the routing area location update procedure is initiated in GERAN/UTRAN.

In the embodiment of the present invention, the user context is restored through the location update process according to the TIN of the user equipment and the current access network, instead of only reestablishing the context through the attach procedure, thereby improving the efficiency of service recovery.

In addition, in the embodiment of the present invention, when the UE receives the foregoing trigger message, the UE needs to re-attach, and then the network re-establishes the context for the UE to re-provide the service for the UE, in the embodiment of the present invention, when the UE receives the trigger message described in step 201. When the new TIN of the UE is set, if the new TIN of the UE that is currently accessing the E-UTRAN and the UE is set to P-TMSI, a 3-track location update procedure is initiated to obtain the UE context from the SGSN; After the GERAN/UTRAN is entered and the new TIN of the set UE is GUTI, a routing area location update procedure is initiated to obtain the UE context from the MME, and the bearer update to the serving gateway is completed according to the acquired UE context. In these cases, there is no need to re-attach, rebuild the context and service bearers, improve the efficiency of business recovery, and at the same time ensure the continuity of the business and enhance the user experience.

Further, if it is known that the attach procedure needs to be initiated according to the new TIN of the user equipment, the attach procedure is initiated. Specifically, if the UE is currently accessing the E-UTRAN network, according to step 201, when the new TIN of the set UE is RAT-related TMSI or GUTI, the connection is initiated. If the UE is currently accessing the GERAN or UTRAN network, according to step 201, when the new TIN of the set UE is RAT-related TMSI or P-TMSI, the attach procedure is initiated.

Embodiments of the present invention are described in more detail below with reference to specific examples.

FIG. 3 is a schematic flow chart of a service recovery process according to an embodiment of the present invention. In the embodiment of FIG. 3, the UE accesses the E-UTRAN network, and the MME restarts as an example.

301. When the MME fails, the SGSN and the S-GW learn that the MME is faulty.

The SGSN and the S-GW can learn that the MME is faulty by, for example,

The S-GW or the SGSN sends an Echo Request message to the MME, and the MME returns an Echo Response message to the S-GW or the SGSN, where the message carries a restart counter (S-GW or SGSN according to the S-GW or the SGSN). The restart counter detects that the MME is restarted. After the MME restarts, the Echo Request message is sent to the S-GW or the SGSN. The message carries the restart counter. The S-GW or the SGSN detects the MME restart according to the restart counter.

It should be noted that, when the S-GW learns that the MME is faulty, step 302 may be performed immediately, or when the S-GW receives the downlink data (Downlink Data) of the UE sent by the P-GW, step 302 is performed.

302. The S-GW sends a Downlink Data Notification message to the MME. The downlink data notification message includes an identifier of the UE, and the UE identifier information may be an IMSI (International Mobile Subscriber Identity).

The step 302 may be: when the S-GW learns that the fault occurs, and immediately executes, or when the S-GW receives the downlink data of the UE sent by the P-GW, the S-GW determines, and sends a downlink data notification message to the MME. The downlink data notification message includes the UE identifier of the UE.

It should be noted that when the S-GW sends a downlink data notification message to the fault, the downlink data notification message includes the UE identifier of the UE. When the S-GW sends a downlink data notification message to the MME, the downlink data notification message may not carry the identifier information of the UE, and may be included in the message header of the downlink data notification message. The TEID (for the agreement information between the ΜΜΕ and the S-GW) retrieves the saved UE context and indirectly obtains the identity of the UE. For one ΜΜΕ, the MME TEID can uniquely identify one UE. If the MME fails, if the S-GW sends a downlink data notification message that does not include the identifier of the UE to the MME, the MME deletes the context information of the UE it saves due to the MME failure. Or release, the MME will not be able to confirm the specific UE or may confirm an erroneous UE. Therefore, when the MME fails, when the S-GW sends a downlink data notification message to the MME, the downlink data notification message must include the user identifier of the UE. .

It is to be noted that, because the MME deletes or releases the context of all the UEs stored therein when the MME fails, the S-GW sends a downlink data notification to the MME that provides the service for the UE according to the saved MME IP address information. When the message is sent, the downlink data notification message may be sent to the MME that has failed; or the downlink data notification message may be sent to any other non-faulty MME in the MME PooK MME pool where the failed MME is located, where MME The information of a non-faulty MME in the pool may be configured in the S-GW or obtained by the current location information of the UE. The downlink data notification message may also be sent to the non-faulty backup MME of the failed MME. The information of the MME and the backup MME can be configured in the S-GW. Which embodiment of the MME is specifically sent to the MME, which is not limited in this embodiment of the present invention.

303. The MME receives the downlink data notification message, and confirms whether it saves the UE context according to the UE identifier included in the downlink data notification message. If it is confirmed that the MME does not save the context of the UE, it sends a paging request to the access network element. The paging request carries the UE identity IMSI of the UE, and the core domain indication CN domain indicator is set to PS.

304. The UE receives the paging message sent by the access network element, and sets a new TIN of the UE.

For a new TIN of the UE, the UE may refer to the corresponding description in step 201 in FIG. 2, and details are not described herein again.

305. When the new TIN of the set UE is P-TMSI, it indicates that the UE context or the latest UE context is saved in the SGSN, so the UE initiates a tracking area location update process, that is, sends a TAU Request message to the MME, so that The MME receiving the TAU Request message acquires the user equipment context from the SGSN.

As shown in step 201 in FIG. 2, the TAU Request message carries the cells of the Old GUTI information, and the Old GUTI information is obtained by mapping the P-TMSI saved by the UE and the corresponding RAI. The MME that receives the TAU Request message may be the MME that previously served the UE but fails, or other MME.

306. The MME receives the TAU request message sent by the UE, where the TAU request message includes the old GUTI (Old GUTI) information, and obtains the address information of the SGSN according to the Old GUTI information.

307. The MME that receives the UE sending the TAU request message sends a context request message for acquiring the UE context to the SGSN. The UE context is obtained according to the context request message.

309. The SGSN sends the acquired UE context to the MME in a context response message.

310. The MME receives a context response message sent by the SGSN, where the context response message includes a UE context acquired by the SGSN according to the context request message.

311. After receiving the UE context, the MME sends a context determination message to the SGSN.

312. The MME updates the bearer to the serving gateway (S-GW) according to the UE context. It should be noted that the S-GW may be the S-GW of the previous serving UE, so that the S-GW sends the downlink data it receives to the UE.

313. The S-GW sends the downlink data to the UE.

Further, it should be noted that, when the UE accesses the GERAN or the UTRAN network, and the UE is called, if the SGSN fails, the processing manner after the fault may refer to the corresponding steps in steps 301 to 311. The difference is that the operations performed by the MME in steps 301 to 313 are interchanged with the operations performed by the SGSN, and will not be described herein.

In the embodiment of the present invention, when the mobility management network element fails, the serving gateway S-GW triggers paging the UE, and the UE resets the TIN of the UE. When the set TIN of the UE is P-TMSI, the UE initiates a TAU process to enable reception. The MME of the TAU Request message acquires the UE context from the SGSN. When the SGSN of the UE is set to be a GUTI, the UE initiates a RAU procedure, so that the SGSN that receives the RAU Request message acquires the UE context from the MME, and according to the acquired UE context to the serving gateway Hosting updates. In this way, the transmission of the service after the network element failure can be realized, and the re-attachment and the reconstruction of the context and the service bearer are not required, thereby improving the efficiency of the service recovery, ensuring the continuity of the service and enhancing the user experience.

4 is a schematic flow chart of a method for service recovery according to another embodiment of the present invention. In the embodiment of FIG. 4, the MME is faulty, and the UE actively initiates the NAS process in the E-UTRAN network as an example. This embodiment takes the MME restart as an example.

401. When the MME fails, the MME loses the context of the service UE before the failure.

402. The UE sends a NAS message, such as a Service Request message, to the MME, where the NAS message includes a UE identifier of the UE, such as a GUTI or an S-TMSL.

403. The MME receives the NAS message sent by the UE, and according to the NAS message.

The UE identity, such as GUTI or S-TMSI, confirms whether it itself holds the corresponding to the UE identity. UE's UE context.

404. If it is confirmed that the MME does not save the context of the UE, send a reject message to the UE. The reject message corresponds to the request message in step 401. When the UE sends a TAU Request message to the MME, the reject message may be a TAU Reject message; when the UE sends a Service Request message to the MME, the reject message may be a Service Reject message. The message may carry a specific reason, for example, the UE identity cannot be derived by the network.

405. The UE receives the reject message sent by the MME, and sets a new TIN of the UE.

For the method of setting a new TIN of the UE, reference may be made to the corresponding description in step 201 in FIG. 2, and details are not described herein again in this embodiment.

406. When the new TIN of the set UE is P-TMSI, initiate a 3-tracking area location update procedure to the MME, that is, send a TAU Request message to the MME, so that the MME that receives the TAU Request message acquires the user equipment context from the SGSN. .

As shown in step 202 in FIG. 2, the TAU Request message includes a cell carrying Old GUTI information, and the Old GUTI information is obtained by mapping the P-TMSI saved by the UE and the corresponding RAI. The MME that receives the TAU Request message may be the MME or other MME that previously served the UE but failed.

407. The MME receives the TAU request message sent by the UE, where the TAU request message includes the old GUTI (Old GUTI) information, and obtains the address information of the SGSN according to the Old GUTI information.

408. The MME that receives the TAU request message sent by the UE sends a context request message for obtaining the UE context to the SGSN. The context request message acquires the UE context.

410. The SGSN carries the acquired UE context in a context response message and sends the

MME.

411. The MME receives a context response message sent by the SGSN, where the context response message includes a UE context acquired by the SGSN according to the context request message.

412. After receiving the UE context, the MME sends a context determination message to the SGSN. 413. The MME updates the bearer to the S-GW according to the UE context, where it should be noted that,

The S-GW may be an S-GW that previously served the UE. Further, in the process of performing the UE to initiate the NAS process in the GERAN or UTRAN network, if the SGSN fails, the method of the post-fault processing may refer to the corresponding steps in steps 401 to 413. The difference is that the operations performed by the MME in steps 401 to 413 are interchanged with the operations performed by the SGSN, and the SGSN returns a reject message to the UE, and the UE sets the TIN. According to step 201 in FIG. 1, when the set TIN of the user equipment is GUTI, the UE initiates a RAU procedure to acquire a user equipment context from the MME; the RAU Request message carries Old P-TMSI and corresponding Old PAI cells, the Old P-TMSI and the corresponding Old RAI information are mapped to the Old P-TMSI and Old RAI of a valid GUTI saved by the UE, and will not be described here.

In the embodiment of the present invention, the MME sends a reject message to the UE, and the UE resets the TIN of the UE. When the set TIN of the UE is P-TMSI, the TAU process is initiated, so that the MME that receives the TAU Request message obtains the MME from the SGSN. The context of the UE. On the other hand, the SGSN sends a reject message to the UE, and the UE resets the TIN of the UE. When the TIN of the set UE is GUTI, the RAU process is initiated, so that the SGSN that receives the RAU Request message acquires the context of the UE from the MME. Then, according to the acquired UE context, the bearer update to the serving gateway can implement the transmission of the service after the network element fails, and does not need to be reattached, thereby improving the efficiency of service recovery, ensuring the continuity of the service and enhancing the user experience.

FIG. 5 is a flowchart of a method for service recovery according to another embodiment of the present invention. The method of Figure 5 is performed by a mobile management network element (e.g., MME or SGSN).

501. A trigger message sent to the user equipment, so that the user equipment sets a new TIN of the user equipment according to the current TIN on the current access network and the user equipment.

Similar to the step 201 of FIG. 2, the trigger message may be a reject message sent by the mobility management network element after receiving the request message of the user equipment, or a paging message.

For example, the reject message carries the reason for the rejection, the reason for the rejection indicates that the identity of the user equipment is unknown, or indicates an implicit separation, or indicates that the evolved packet system EPS bearer is not activated.

For example, the paging message carries the user identification information of the user equipment, and the core domain indication in the paging message is set to the packet domain PS.

For the specific trigger message, refer to the description in step 201 of FIG. 2, and details are not described herein again. 502. Receive a location update request message that is sent by the user equipment to obtain a location update process according to the new TIN, and restore the service of the user equipment.

The mobile management network element can obtain the user equipment from other mobile management network elements according to the location update process. Context, and completing the bearer update to the serving gateway according to the acquired user equipment context, and restoring the service of the user equipment.

In the embodiment of the present invention, when the UE receives the trigger message described in step 501, the new TIN of the UE is set, and if the new TIN of the UE that is currently accessing the E-UTRAN and the set UE is P-TMSI, the tracking area is initiated. a location update procedure, to obtain a UE context from the SGSN; if the current RAN of the UE that is currently accessing the GERAN/UTRAN and the set UE is a GUTI, initiate a routing area location update procedure, so as to acquire the UE context from the MME, and according to the acquired The UE context completes the bearer update to the serving gateway. In these cases, there is no need to re-attach, reconstruct the context and service bearer, improve the efficiency of service recovery, and at the same time ensure the continuity of the service and enhance the user experience.

Further, if it is known that the attach process needs to be initiated according to the new TIN of the user equipment, the attach procedure is initiated. Specifically, if the UE is currently accessing the E-UTRAN network, if the new TIN of the set UE is RAT-related TMSI or GUTI, the attach procedure is initiated; if the UE is currently accessing the GERAN or UTRAN network, according to step 201 As described, when the new TIN of the set UE is RAT-related TMSI or P-TMSI, an attach procedure is initiated. In this case, the mobility management network element recovers the services of the user equipment according to the attach procedure.

Figure 6 is a block diagram of a user equipment in accordance with one embodiment of the present invention. The user device 60 of Fig. 6 includes a setting unit 61 and a restoring unit 62.

The setting unit 61 sets the temporary identification TIN used for the next update of the user equipment when receiving the trigger message sent by the network side. The recovery unit 62 initiates a location update process or an attach procedure in the current access network according to the current access network of the user equipment and the TIN set by the setting unit.

At the same time, if the location update process is used to reply to the user context, the EPS bearer can be maintained, the efficiency of service recovery is improved, and the continuity of the service is guaranteed, and the user experience is enhanced.

The user equipment 60 can perform operations on the UE in the foregoing various method embodiments, and is not described in detail in order to avoid redundancy.

Optionally, as an embodiment, in a case where the current access network is E-UTRAN, The setting unit 61 is specifically configured to set the TIN of the user equipment to P-TMSI when the current TIN of the user equipment 60 is RAT-related TMSI; or if the current TIN of the user equipment 60 is RAT-related TMSI, if there is a new activation For the service bearer, the TIN of the user equipment is kept as RAT-related TMSI or the TIN of the user equipment 60 is set to GUTI, and if there is no newly activated service bearer, the TIN of the user equipment 60 is set to P-TMSI; or When the current TIN of the user equipment 60 is GUTI, the TIN of the user equipment 60 is kept unchanged as GUTI; or when the current TIN of the user equipment 60 is GUTI, if the user equipment 60 saves the valid P-TMSI and the corresponding The routing area identifies the RAI, and sets the TIN of the user equipment 60 to P-TMSI. If the user equipment 60 does not save the valid P-TMSI and the corresponding RAI, the TIN of the user equipment 60 is maintained as GUTI.

Optionally, in another embodiment, where the current access network is GERAN or UTRAN, the setting unit 61 sets the TIN of the user equipment 60 to GUTI when the current TIN of the user equipment 60 is RAT-related TMSI; Or when the current TIN of the user equipment 60 is RAT-related TMSI, if there is a newly activated service bearer, the TIN of the user equipment 60 is kept as RAT-related TMSI or the TIN of the user equipment 60 is set to P-TMSI, if If there is no newly activated service bearer, the TIN of the user equipment 60 is set to GUTI; or when the current TIN of the user equipment 60 is P-TMSI, the TIN of the user equipment 60 is kept as P-TMSI; or at the user equipment 60. When the current TIN is P-TMSI, if the user equipment 60 saves the valid GUTI, the TIN of the user equipment 60 is set to GUTI, and if the user equipment 60 does not save the valid GUTI, the TIN of the user equipment 60 is kept as P. -TMSL

Optionally, as another embodiment, the recovery unit 62 initiates a tracking area location update procedure in the E-UTRAN when the current access network is E-UTRAN and the TIN is P-TMSI; or the current access network is GERAN. When the UTRAN and the TIN are GUTI, the routing area location update procedure is initiated in GERAN or UTRAN.

Optionally, as another embodiment, the recovery unit 62 initiates an attach procedure in the E-UTRAN when the current access network is E-UTRAN and the TIN is RAT-related TMSI or GUTI;

At the time of P-TMSI, an attach procedure is initiated in the GERAN or UTRAN.

Optionally, in another embodiment, the trigger information is a reject message sent by the mobility management network element for the request message of the user equipment, or a paging message sent by the access network element.

For example, in the case that the current access network is E-UTRAN, the above request message is a tracking area. The location update request message, the reject message is a tracking area reject message; or, the request message is a service request message, and the reject message is a service reject message.

Or, in a case that the current access network is GERAN or UTRAN, the request message is a routing area location update request message, and the reject message is a routing area reject message; or the request message is a service request message, and the reject message is a service reject message. .

7 is a block diagram of a mobility management network element device in accordance with an embodiment of the present invention. An example of the mobility management network element device 70 of Figure 7 is an MME or SGSN, including a transmitting unit 71 and a receiving unit 72.

a triggering message sent by the sending unit 71 to the user equipment, so that the user equipment sets a new TIN of the user equipment according to the current TIN on the current access network and the user equipment; and a receiving unit, configured to receive the user equipment, according to the new TIN. The location update request message sent in the case of initiating the location update process is used to restore the service of the user equipment.

Optionally, as an embodiment, the trigger message is a reject message sent after receiving the request message of the user equipment, or is a paging message. For example, the reject message carries the reject reason, the reject reason indicates that the identifier of the user equipment is unknown, or indicates implicit separation, or indicates that the evolved packet system EPS bearer is not activated. Alternatively, the paging message carries the user identification information of the user equipment, and the core domain indication in the paging message is set to the packet domain PS.

Further, if it is known that the attach process needs to be initiated according to the new TIN of the user equipment, the attach procedure is initiated. In this case, the mobility management network element recovers the services of the user equipment according to the attach procedure.

For other functions of the various parts of the mobility management network element device 70, reference may be made to the operations related to the mobility management network element (e.g., MME or SGSN) in the embodiments of Figures 2 to 5 above, and redundant description is omitted to avoid redundancy.

The communication system according to an embodiment of the present invention may include the above-described user equipment 60 or mobility management network element device 70.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention. A person skilled in the art can clearly understand that, for the convenience and the cleaning of the description, the specific working processes of the system, the device and the unit described above can refer to the corresponding processes in the foregoing method embodiments, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.

The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential to the prior art or part of the technical solution, may be embodied in the form of a software product stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

Rights request

A method for restoring signaling in an idle mode, in which the service is restored in an ISR state, and includes:

When receiving the trigger message sent by the network side, setting a new TIN of the user equipment according to the current access network and the temporary identifier TIN used by the current next update on the user equipment; The new TIN, knowing that the location update process needs to be initiated, initiates a location update process.

The location update process is used to implement service recovery.

2. The method according to claim 1, wherein, in case the current access network is an evolved UMTS terrestrial radio access network E-UTRAN, the setting of the new TIN of the user equipment comprises :

When the current TIN on the user equipment is a radio access technology related temporary mobile subscriber identity RAT-related TMSI, setting a new TIN of the user equipment to a packet temporary mobile subscriber identity P-TMSI; or

When the current TIN on the user equipment is RAT-related TMSI, if there is a newly activated service bearer, the new TIN of the user equipment is kept as RAT-related TMSI or a new TIN of the user equipment is Set to the global unique temporary identifier GUTI, if there is no newly activated service bearer, set the new TIN of the user equipment to P-TMSI; or

When the current TIN on the user equipment is GUTI, the new user equipment is

TIN remains unchanged as GUTI; or

If the current TIN of the user equipment is GUTI, if the user equipment saves the valid P-TMSI and the corresponding routing area identifier RAI, the new TIN of the user equipment is set to P-TMSI, if If the user equipment does not save the valid P-TMSI and the corresponding RAI, the new TIN of the user equipment is kept as GUTI.

The method according to claim 1 or 2, wherein, in the case that the current access network is a GSM EDGE radio access network GERAN or a UMTS terrestrial radio access network UTRAN, the setting the user The device's new TIN includes:

Setting a new TIN of the user equipment to GUTI when the current TIN on the user equipment is RAT-related TMSI; or

When the current TIN on the user equipment is RAT-related TMSI, if there is a new activation The service bearer, the new TIN of the user equipment is kept as RAT-related TMSI or the new TIN of the user equipment is set to P-TMSI, if there is no newly activated service, The new TIN of the user device is set to GUTI; or

When the current TIN on the user equipment is P-TMSI, the new TIN of the user equipment is kept as P-TMSI; or

When the current TIN on the user equipment is P-TMSI, if the user equipment saves a valid GUTI, the new TIN of the user equipment is set to GUTI, if the user equipment does not save a valid GUTI , then keep the new TIN of the user device as P-TMSL

The method according to any one of claims 1-3, wherein, if the current access network is E-UTRAN, if the new TIN according to the user equipment is learned, it is required to be initiated. a location update process, the initiating location update process includes: if the new TIN is a P-TMSI, and is required to initiate a location update process, initiating a tracking area location update process in the E-UTRAN; or

If the current access network is a GERAN or a UTRAN, if the location update process is required to be initiated according to the new TIN of the user equipment, the initiating the location update process includes: if the new TIN is a GUTI, A location update procedure needs to be initiated, and a routing area location update procedure is initiated in the GERAN or UTRAN.

The method according to any one of claims 1 to 4, wherein the method further comprises:

If it is known that an attach procedure needs to be initiated based on the new TIN of the user equipment, an attach procedure is initiated.

6. The method of claim 5, wherein

If the current access network is an E-UTRAN, if the new TIN of the user equipment is used to learn that the attach procedure needs to be initiated, the initiating the attaching process includes: if the new TIN is a RAT-related TMSI or At GUTI, if it is known that an attach procedure needs to be initiated, an attach procedure is initiated in the E-UTRAN; or

If the current access network is GERAN or UTRAN, if the new TIN of the user equipment is used to learn that the attach procedure needs to be initiated, the initiating the attaching process includes: if the new TIN is RAT-related TMSI or When the packet temporary mobile subscriber identity P-TMSI is learned, it is known that the attach procedure needs to be initiated, and the attach procedure is initiated in the GERAN or UTRAN.

The method according to any one of claims 1 to 6, wherein the trigger message A reject message sent by the mobile management network element after receiving the request message of the user equipment, or a paging message sent by the access network element.

The method according to claim 7, wherein the rejection message carries a rejection reason, the rejection reason indicates that the identifier of the user equipment is unknown, or indicates an implicit separation, or indicates that the evolved packet system EPS is not activated. Hosted.

The method according to claim 7 or 8, wherein in the case that the current access network is E-UTRAN,

The request message is a tracking area location update request message, and the rejection message is a tracking area rejection message; or

The request message is a service request message, and the reject message is a service rejection message.

10. The method according to claim 7 or 8, wherein, in the case that the current access network is GERAN or UTRAN,

The request message is a routing area location update request message, and the reject message is a routing area reject message; or

The method according to claim 7, wherein the paging message carries user identification information of the user equipment, and a core domain indication in the paging message is set as a packet domain PS.

12. A method for restricting signaling in an idle mode, where the service is restored in an ISR state, and the method includes:

a trigger message sent to the user equipment, so that the user equipment sets a new TIN of the user equipment according to the current access network and the temporary identifier TIN used by the current next update on the user equipment;

Receiving, by the user equipment, a location update request message sent in the case that the location update process needs to be initiated according to the new TIN, and recovering the service of the user equipment.

The method according to claim 12, wherein the trigger message is a reject message sent after receiving the request message of the user equipment, or is a paging message.

The method according to claim 13, wherein the rejection message carries a rejection reason, the rejection reason indicates that the identifier of the user equipment is unknown, or indicates an implicit separation, or indicates that the evolved packet system EPS is not activated. Hosted.

The method according to claim 13, wherein the paging message carries a location The user identification information of the user equipment is described, and the core domain indication in the paging message is set as the packet domain PS.

16. A user equipment, comprising:

a setting unit, configured to: when receiving a trigger message sent by the network side, set a new TIN of the user equipment according to a temporary identifier TIN used by the current access network and the current next update on the user equipment;

a recovery unit, configured to initiate a location update process if it is determined that a location update process needs to be initiated according to the new TIN of the user equipment,

The location update process is used to implement service recovery.

The user equipment according to claim 16, wherein, in a case that the current access network is an evolved UMTS terrestrial radio access network E-UTRAN, the setting unit is specifically configured to be in the user When the current TIN on the device is a temporary mobile subscriber identity RAT-related TMSI related to the radio access technology, the new TIN of the user equipment is set to the packet temporary mobile subscriber identity P-TMSI; or at the user When the current TIN on the device is RAT-related TMSI, if there is a newly activated service bearer, the new TIN of the user equipment is kept as RAT-related TMSI or the new TIN of the user equipment is set to be globally unique Temporarily identifying the GUTI, if there is no newly activated service bearer, setting the new TIN of the user equipment to P-TMSI; or when the current TIN on the user equipment is GUTI, then the user equipment is The new TIN remains unchanged as GUTI; or if the current TIN on the user equipment is GUTI, if the user equipment saves a valid P-TMSI and corresponding The RIA is identified by the zone, and the new TIN of the user equipment is set to P-TMSI. If the user equipment does not save the valid P-TMSI and the corresponding RAI, the new TIN of the user equipment is kept as GUTI.

The user equipment according to claim 16 or 17, wherein, in the case that the current access network is a GSM EDGE radio access network GERAN or a UMTS terrestrial radio access network UTRAN, the setting unit is specific When the current TIN on the user equipment is RAT-related TMSI, the new TIN of the user equipment is set to GUTI; or when the current TIN on the user equipment is RAT-related TMSI, if present The newly activated service bearer, the new TIN of the user equipment is kept as RAT-related TMSI or the new TIN of the user equipment is set to P-TMSI, if there is no newly activated service bearer, The new TIN of the user equipment is set to GUTI; or the current TIN on the user equipment is When P-TMSI, keep the new TIN of the user equipment as P-TMSI; or when the current TIN on the user equipment is P-TMSI, if the user equipment saves a valid GUTI, The new TIN of the user equipment is set to GUTI, and if the user equipment does not save a valid GUTI, the new TIN of the user equipment is kept as P-TMSL

The user equipment according to any one of claims 16 to 18, wherein the recovery unit is specifically configured to: when the current access network is E-UTRAN and the new TIN is P-TMSI Initiating a tracking area location update procedure in the E-UTRAN; or initiating a routing area location update procedure in the GERAN or UTRAN when the current access network is GERAN or UTRAN and the new TIN is GUTI .

The user equipment according to any one of claims 16 to 19, wherein the trigger message is a rejection message sent by the mobility management network element after receiving the request message of the user equipment, or is an access network. The paging message sent by the meta.

The user equipment according to claim 20, wherein the rejection message carries a rejection reason, the rejection reason indicates that the identifier of the user equipment is unknown, or indicates an implicit separation, or indicates that the evolved packet system is not activated. EPS bearer.

The user equipment according to claim 20, wherein the paging message carries user identification information of the user equipment, and the core domain indication in the paging message is set to a packet domain PS.

A mobile management network element device, comprising:

a sending unit, configured to send a trigger message to the user equipment, to enable the user equipment to set a new TIN of the user equipment according to a temporary identifier TIN used by the current access network and the current next update on the user equipment. ;

And a receiving unit, configured to receive a location update request message that is sent by the user equipment, if the user needs to initiate a location update process according to the new TIN, to recover the service of the user equipment.

The mobile management network element device according to claim 23, wherein the trigger message is a reject message sent after receiving the request message of the user equipment, or is a paging message.

The mobile management network element device according to claim 24, wherein the rejection message carries a rejection reason, the rejection reason indicates that the identifier of the user equipment is unknown, or indicates an implicit separation, or indicates that the rejection is not activated. Evolved packet system EPS bearer.

The mobile management network element device according to claim 24, wherein the searching The call message carries user identification information of the user equipment, and the core domain indication in the paging message is set as the packet domain PS.