WO2011153899A1

WO2011153899A1 - Method and system for processing network element failure

Info

Publication number: WO2011153899A1
Application number: PCT/CN2011/074530
Authority: WO
Inventors: 卢飞; 梁爽
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-06-11
Filing date: 2011-05-23
Publication date: 2011-12-15
Also published as: CN102281564A

Abstract

A method and system for processing network element failure are disclosed by the present invention. When it detects that a first mobility management unit connected with a user equipment (UE) restarts or the link is abnormal, a service gateway (S-GW) deactivates idle mode signaling reduction (ISR), and informs a second mobility management unit connected with the UE to deactivate ISR; the second mobility management unit deactivates ISR and informs the UE to deactivate ISR. Or, when it detects that a first mobility management unit connected with an UE restarts or the link is abnormal, a second mobility management unit connected with the UE deactivates ISR, informs an S-GW of the UE to deactivate ISR and the resource between the S-GW and the first mobility management unit, and informs the UE to deactivate ISR. With the present invention, the information asynchrony between the S-GW and mobility management units is avoided, and the information asynchrony between the S-GW and network, which is caused by that the UE can not deactivate ISR, is avoided.

Description

Method and system for processing failure of network element

The present invention relates to the field of communications, and in particular, to a method and system for network element failure processing. Background technique

5 With Worldwide Interoperability for Microwave (WiMax)

Access) technology has sprung up. Third-generation mobile communication systems must maintain their competitiveness in the field of mobile communications, and must improve their network performance and reduce network construction and operating costs. Therefore, the standardization working group of the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) is currently working on the PS Core (Packet Switch Core) and the all-ball mobile communication system wireless access network ( Evolution of UTRAN, Universal Mobile Telecommunication System Radio Access Network. The research topic is called System Architecture Evolution (SAE), which aims to enable EPC (Evolved Packet Core) to provide higher transmission rates, shorter transmission delays, optimized packetization, and support. Evolved UTRAN (E-UTRAN, Evolved UTRAN), UTRAN, WLAN

Mobility management between 15 (WLAN, Wireless Local Area Network) and other non-3GPP access networks.

The architecture of the current SAE is as shown in FIG. 1. The network element included in the evolved radio access network (E-RAN, Evolved Radio Access Network) is an evolved Node B (eNodeB, Evolved NodeB, also referred to as eNB). Providing wireless resources for user access; Packet Data Network (PDN) is a network that provides services for users; EPC provides lower latency and allows more wireless access systems to access, Includes the following network elements:

Mobility Management Entity (MME): Control plane functional entity, a server that temporarily stores user data, responsible for managing and storing user equipment (UE, User) The context of the equipment (such as UE/user identity, mobility management status, user security parameters, etc.), assigns a temporary identifier to the user, and is responsible for authenticating the user when the UE is camped in the tracking area or the network; All non-access stratum messages between the UE and the UE; triggering paging on the SAE. The MME is a mobility management unit of the SAE system. In the Universal Mobile Telecommunications System (UMTS), the mobility management unit is a serving GPRS (General Packet Radio Service) support node (SGSN, Serving GPRS Support Node). ).

The Serving Gateway (S-GW) is a user plane entity that is responsible for user plane data routing processing and terminates downlink data of UEs in idle (ECM_IDLE) state. Manage and store the SAE bearer context of the UE, such as IP bearer service parameters and intranet routing information. The S-GW is the anchor point of the internal user plane of the 3GPP system. A user can only have one S-GW at a time.

The packet data network gateway (P-GW, PDN Gateway) is the gateway responsible for the UE accessing the PDN, assigns the user IP address, and is also the mobility anchor of the 3GPP and non-3GPP access systems. The function of the P-GW also includes the policy implementation. , billing support. Users can access multiple P-GWs at the same time. The Policy and Charging Enforcement Function (PCEF) is also located in the P-GW.

The Policy and Charging Rules Function (PCRF) is responsible for providing policy control and charging rules to the PCEF.

The home subscriber server (HSS) permanently stores the user subscription data. The content stored in the HSS includes the UE's International Mobile Subscriber Identification (IMSI) and the IP address of the P-GW.

Physically, the S-GW and the P-GW may be unified. The EPC system user plane network element includes an S-GW and a P-GW.

When the coverage area where the UE is located changes, for example, from a radio access technology (RAT, Radio) When the coverage area is moved to another RAT coverage area, the UE discovers that it has entered an unregistered area by listening to the broadcast channel. In order to ensure the continuity between the UE and the core network, it needs to be performed under the new RAT coverage area. Registration, therefore, the UE initiates a TAU (Tracking Area Update) or Routing Area Update (RAU) process for accessing the RAT. As shown in FIG. 2, the TAU procedure initiated by the UE registered under the UTRAN coverage area moves to the E-UTRAN coverage area. The RAU procedure initiated by the UE registered under the E-UTRAN coverage area moving to the UTRAN coverage area is similar to FIG. As shown in Figure 2, it mainly includes the following steps:

Step 201: The UE moves to the E-UTRAN coverage area of the MME, sends a tracking area update request to the MME, and requests to register in a new area, where the request message carries the packet temporary mobile subscriber identity (P-TMSI) allocated by the SGSN for the UE. , Packet-Temporary Mobile Subscriber Identity ).

Step 202: The new MME finds the old SGSN according to the P-TMSI identifier, and sends a context request signaling to the old SGSN to perform a context acquisition process.

Step 203: The old SGSN sends the mobility management and bearer information of the user to the new MME, that is, performs a context response.

Step 204: The new MME confirms the context after receiving the context response.

Step 205: The new MME initiates an update bearer request to the S-GW, where the request message carries the source GPRS tunneling protocol-Control plane (GTP-C, GPRS Tunneling Protocol-Control) tunnel identifier and the destination GTP-C tunnel identifier, and the S-GW update 7 The binding relationship.

Step 206: The S-GW sends an update bearer request to the P-GW, and sends the S-GW address information, the tunnel identifier information, and the access technology type to the P-GW.

Step 207: The P-GW updates its own context and returns an update bearer response message to the S-GW. The content of the response message includes the address of the P-GW and the tunnel identifier.

Step 208: The S-GW returns an update bearer response to the new MME, and specifies the destination of the S-GW. The GTP-C tunnel identifier, its own address, and the address and tunnel information of the P-GW are brought to the MME. Step 209: The new MME notifies the change of the HSS registration location by using the location update message. Step 210: The HSS maintains a single registration principle for the UE, and sends location cancellation signaling to the old SGSN to maintain only the registration of the new MME.

Step 211: The old SGSN returns a location cancellation response to the HSS.

Step 212: The HSS confirms the location update of the new MME.

Step 213: If the new MME confirms that the UE is valid in the current tracking area, send a tracking area update accept message to the UE.

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

Based on this location update principle, if the UE moves frequently between the UTRAN coverage area or the E-UTRAN, or the frequent registration area selection due to signal strength and the like in the same coverage area, a large number of TAU or RAU processes are triggered. An empty mouth can cause a heavy burden. Therefore, in the EPS system, in order to reduce air interface signaling between the UE and the core network, the function of Idle (Idle mode Signaling Reduction) is introduced. When this function is activated, UEs having both UTRAN and E-UTRAN access functions can simultaneously register with the MME and the SGSN. Thus, when the UE moves frequently between two different access technologies, the UE does not initiate a TAU or RAU procedure for accessing the RAT, thereby reducing unnecessary air interface signaling transmission.

The UE's process of activating the ISR is also done through the TAU or RAU procedure, but differs in some steps. The difference between the two is explained by taking the TAU process to activate the ISR function as an example. The process of activating the ISR function using the RAU process is similar to this. As shown in Figure 3, it mainly includes the following steps:

Step 301: The UE moves to an E-UTRAN coverage area under the MME, and sends the message to the MME. In addition to carrying the P-TMSI allocated by the UE under the SGSN, the tracking area update request message carries information about whether the UE supports the ISR capability.

Step 302: The new MME finds the old SGSN according to the P-TMSI identifier, and sends a context request signaling to the old SGSN to perform a context acquisition process.

Step 303: The old SGSN sends the mobility management and bearer information of the user to the new MME, and carries the information about whether the ISR capability is supported by the returned context response message.

Step 304: The new MME determines whether to perform ISR activation according to the context information received from the old SGSN. If the ISR is activated, the new MME sends an ISR indication in the context confirmation message replied to the old SGSN to inform the old SGSN to reserve the original UE. Contextual information.

Step 305: The new MME initiates an update bearer request to the S-GW, where the request message carries the source.

GTP-C tunnel identification and destination GTP-C tunnel identification, S-GW update 7 binding relationship. The update bearer request message further includes an indication of activating the ISR, and notifying the S-GW to retain bearer context information owned by the UE under the old SGSN.

Step 306: The S-GW sends an update bearer request to the P-GW because the RAT changes. Step 307, the P-GW updates its own context and returns an update 7-load response information to the S-GW. Step 308: The S-GW returns an update bearer response to the new MME, and brings the destination GTP-C tunnel identifier specified by the S-GW, its own address, and the address and tunnel information of the P-GW to the MME.

Step 309, the new MME notifies the HSS of the change of the location of the HSS by the location update message, and informs the HSS of the information of the ISR activation by the corresponding identifier, then the HSS maintains the dual registration information of the two domains of the E-UTRAN and the UTRAN, and is no longer old. The SGSN sends a location cancellation message.

The corresponding identification information described above is currently indicated as a dual registration by the existing location update type message unit.

Step 310: The HSS determines whether the UE activates the ISR. If the HSS does not maintain dual registration for the UE, the location cancellation signaling is sent to the SGSN. If the ISR is activated, the HSS keeps the registration of the two PS domains for the UE, and therefore does not go to the old The SGSN sends location cancellation signaling. Belonging to the process The latter case.

Step 311: If the SGSN receives the location cancellation signaling, the SGSN returns a location cancellation response to the HSS. Corresponding to the latter case in step 310, the SGSN does not need to return to the location to cancel the port.

Step 312, the HSS confirms the location update of the new MME.

Step 313: If the new MME confirms that the UE is valid in the current tracking area, send a tracking area update accept message to the UE, where the MME informs the UE that the ISR function is activated by the indication.

Step 314: If the new MME allocates a new GUTI identifier to the UE through the TAU procedure, the UE returns a tracking area update complete message to confirm to the MME.

When the ISR is activated, the S-GW retains the bearer information of the two access networks at the same time. Therefore, when the MME or the SGSN fails for some reason and causes a restart, the S-GW can simultaneously release the resources of the connected MME and the SGSN; The -GW can also release only the resources connected to the restarting node, while maintaining resources with the normally available nodes, thereby ensuring a good user experience. However, there is no processing mechanism in the prior art for the ISR user's mobility management unit (MME/SGSN) to restart the resource process, which easily leads to the ISR deactivation between the S-GW and the mobility management unit (MME/SGSN). The information is not synchronized, and it is easy for the UE to release the ISR and the information between the UE and the network is not synchronized. Summary of the invention

In view of this, the main purpose of the present invention is to provide a method and system for network element failure processing, to avoid information synchronization between the S-GW and the mobility management unit, and UE and network caused by the UE not releasing the ISR. The information between them is not synchronized.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

The present invention provides a method for processing a network element failure, the method comprising:

The serving gateway (S-GW) detects the first mobility management unit connected to the user equipment (UE) Release the air interface signaling reduction (ISR) when the restart or the link is abnormal, and notify the second mobility management unit connected to the UE to release the ISR;

The second mobility management unit completes the ISR release and notifies the UE to release the ISR.

The method further includes:

The S-GW sends a release bearer request message to the second mobility management unit that is connected to the UE, where the message carries a cause value of the first mobility management unit restarting or the link is abnormal, and the cause value is used to indicate the second mobile The management unit releases the ISR;

Correspondingly, the second mobility management unit releases according to the indication in the release bearer request message.

ISR.

The second mobility management unit notifies the UE to release the ISR, specifically:

When the UE is in the connected state under the second mobility management unit, the second mobility management unit notifies the UE to release the ISR by using an ISR release request message;

When the UE is in an idle state under the second mobility management unit, the second mobility management unit notifies the UE to release the ISR through a paging message, or first converts the UE into a connection state, and then notifies the UE to release by using an ISR release request message. ISR.

The present invention also provides a method for processing a network element failure, the method comprising:

The second mobility management unit connected to the UE detects that the first mobility management unit restarts or the link is abnormal, releases the ISR, notifies the S-GW of the UE to release the ISR and resources between the first mobility management unit, and notify the The UE releases the ISR.

The method further includes: the second mobility management unit sends a release session request message to the S-GW of the UE, where the message carries a cause value of the first mobility management unit restarting or the link is abnormal, and the cause value is used to Instructing the S-GW to release the ISR;

Correspondingly, the S-GW releases the ISR according to the indication in the release session request message.

The second mobility management when the UE is in a connected state under the second mobility management unit The unit notifies the UE to release the ISR through the ISR release request message;

The present invention further provides a system for network element failure processing, the system comprising: an S-GW, a first mobility management unit, a second mobility management unit, and a UE, wherein the first mobility management unit and the second mobility management The unit provides mobility management services for the UE;

The S-GW is configured to release an ISR when detecting that the first mobility management unit connected to the UE is restarted or the link is abnormal, and notify the second mobility management unit connected to the UE to release the ISR;

The second mobility management unit is configured to complete the ISR release according to the notification of the first mobility management unit, and notify the UE to release the ISR;

The UE is configured to complete ISR release according to the notification of the second mobility management unit.

The S-GW is further configured to send a release bearer request message to the second mobility management unit that is connected to the UE, where the message carries a cause value of the first mobility management unit restarting or the link is abnormal, and the cause value is used. Instructing the second mobility management unit to release the ISR;

Correspondingly, the second mobility management unit is further configured to release the ISR according to the indication in the release bearer request message.

The second mobility management unit is further configured to: when the UE is in a connected state under the second mobility management unit, notify the UE to release the ISR by using an ISR release request message; when the UE is idle under the second mobility management unit In the state, the UE is notified by the paging message to release the ISR, or the UE is first converted into a connected state, and then the UE is notified to release the ISR through an ISR release request message.

The second mobility management unit is configured to detect that the first mobility management unit connected to the UE is heavy The ISR is released when the link is not normal, and the S-GW of the UE is notified to release the ISR and the resource with the first mobility management unit, and the UE is notified to release the ISR.

The S-GW, configured to release, according to the notification of the second mobility management unit, the ISR and the resource between the S-GW and the first mobility management unit;

The second mobility management unit is further configured to send a release session request message to the S-GW of the UE, where the message carries a cause value of the first mobility management unit restarting or the link is abnormal, and the cause value is used to indicate The S-GW releases the ISR;

Correspondingly, the S-GW is further configured to release the ISR according to the indication in the release session request message.

The method and system for processing a network element failure according to the present invention, when the S-GW detects that the first mobility management unit connected to the UE is restarted or the link is abnormal, the SSR releases the ISR, and notifies the UE of the second mobility management. The unit releases the ISR; the second mobility management unit completes the ISR release and notifies the UE to release the ISR. Alternatively, the second mobility management unit connected by the UE detects that the first mobility management unit restarts or releases the ISR when the link is abnormal, notifies the S-GW of the UE to release the ISR and the resources between the first mobility management unit, and notify The UE releases the ISR. Through the invention, the information between the S-GW and the mobility management unit is not synchronized, and the information between the UE and the network caused by the UE cannot release the ISR is not synchronized. DRAWINGS

1 is a schematic structural diagram of an evolved packet network system in the prior art;

2 is a signaling flowchart of performing normal tracking area update in the prior art; 3 is a signaling flowchart of activating an ISR function by a tracking area update process in the prior art; FIG. 4 is a flowchart 1 of a method for processing a network element failure according to the present invention;

FIG. 5 is a second flowchart of a method for processing a network element failure according to the present invention; FIG.

6 is a flowchart of a method for processing a network element failure according to Embodiment 1 of the present invention;

7 is a flowchart of a method for processing a network element failure according to Embodiment 2 of the present invention;

8 is a flowchart of a method for processing a network element failure according to Embodiment 3 of the present invention;

9 is a flowchart of a method for processing a network element failure according to Embodiment 4 of the present invention;

10 is a flowchart of a method for processing a network element failure according to Embodiment 5 of the present invention;

11 is a flowchart of a method for processing a network element failure according to Embodiment 6 of the present invention;

12 is a flowchart of a method for processing a network element failure according to Embodiment 7 of the present invention;

13 is a flowchart of a method for processing a network element failure according to Embodiment 8 of the present invention;

14 is a flowchart of a method for processing a network element failure according to Embodiment 9 of the present invention;

FIG. 15 is a flowchart of a method for processing a network element failure according to Embodiment 10 of the present invention. detailed description

The technical solutions of the present invention are further elaborated below in conjunction with the accompanying drawings and specific embodiments. To avoid ISR deactivation, the information between the S-GW and the mobility management unit is not synchronized, and the information between the UE and the network caused by the UE cannot release the ISR is not synchronized. A method for processing failure of a network element provided by the present invention, as shown in FIG. 4, mainly includes the following steps:

Step 401: The S-GW detects that the first mobility management unit connected to the UE is restarted or the link is abnormal.

Step 402: The S-GW releases the ISR, and notifies the second mobility management unit connected to the UE to release.

ISR.

Step 403: The second mobility management unit completes the ISR release, and notifies the UE to release the ISR. The S-GW may send a release bearer request message to the second mobility management unit that is connected to the UE, where the message carries the cause value of the first mobility management unit restarting or the link is abnormal. The value is used to instruct the second mobility management unit to release the ISR; then, correspondingly, the second mobility management unit releases the ISR according to the indication in the release bearer request message.

The present invention also provides another method for network element failure processing, as shown in FIG. 5, which mainly includes the following steps:

Step 501: The second mobility management unit connected to the UE detects that the first mobility management unit is restarted or the link is abnormal.

Step 502: The second mobility management unit releases the ISR.

Step 503: The second mobility management unit notifies the S-GW of the UE to release the ISR and the resource between the first mobile management unit, and notify the UE to release the ISR.

The second mobility management unit may send a release session request message to the S-GW of the UE, where the message carries a cause value of the first mobility management unit restarting or the link is abnormal, and the cause value is used to indicate that the S-GW releases the ISR. Then, correspondingly, the S-GW releases the ISR according to the indication in the release session request message.

It should be noted that the foregoing mobility management unit includes an MME and an SGSN. If one of the MME and the SGSN is used as the first mobility management unit, the other is described as the second mobile line.

The application scenario of the first embodiment of the present invention is as follows: The UE is in an idle state in both the MME and the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 4, the performing network element failure processing is as shown in FIG. 6, and mainly includes the following steps:

Step 601, the MME restarts or the MME link is interrupted.

Step 602: The S-GW detects that the MME restarts or the MME link is interrupted.

Step 603: The S-GW sends a release bearer request message to the SGSN, where the request message carries a cause value of the MME restart or the link interruption, and is used to instruct the SGSN to release the ISR.

Step 604, after receiving the release bearer request message from the S-GW, the SGSN according to the message The indication releases the ISR and returns a release bearer response message to the S-GW.

Step 605: The SGSN sends a paging message to all radio network controllers (RNCs) in the routing area (RA, Routing Area) where the UE is located, because the UE is in an idle state in the SGSN. The cause value of the MME restart or link interruption is used to indicate that the UE releases the ISR.

Step 606: The RNC forwards the paging message.

Step 607: After receiving the paging message, the UE releases the ISR according to the indication in the message, and initiates a service request process in the SGSN network, so that the UE is converted into a connected state.

It should be noted that, in this embodiment, the first mobility management unit is the MME, and the second mobility management unit is the SGSN. For the case where the first mobility management unit is the SGSN and the second mobility management unit is the MME, The processing method is similar to this, and will not be described here.

The application scenario of the second embodiment of the present invention is as follows: The UE is in an idle state in both the MME and the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 4, the performing network element failure processing is as shown in FIG. 7, and mainly includes the following steps:

Step 701: The MME restarts or the MME link is interrupted.

Step 702: The S-GW detects that the MME restarts or the MME link is interrupted.

Step 703: The S-GW sends a release bearer request message to the SGSN, where the request message carries a cause value of the MME restart or the link interruption, and is used to instruct the SGSN to release the ISR.

Step 704: After receiving the release bearer request message from the S-GW, the SGSN releases the ISR according to the indication in the message, and returns a release bearer response message to the S-GW.

Step 705: Because the UE is in an idle state in the SGSN, the SGSN sends a paging message to all RNCs in the RA where the UE is located.

Step 706, the RNC forwards the paging message.

Step 707: After receiving the paging message, the UE initiates a service request process in the SGSN network, so that the UE is converted into a connected state. Step 708: The SGSN sends an ISR release request message to the RNC where the UE is located.

Step 709: The RNC forwards the ISR release request message.

Step 710: After receiving the ISR release request message, the UE releases the ISR, and returns an ISR release response message to the RNC.

Step 711: The RNC forwards an ISR release response message to the SGSN.

The application scenario of the third embodiment of the present invention is as follows: The UE is in a connected state under the MME, and is in an idle state in the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 4, the performing network element failure processing is as shown in FIG. 8, and mainly includes the following steps:

In step 801, the MME restarts or the MME link is interrupted.

Step 802: The S-GW detects that the MME restarts or the MME link is interrupted.

Step 803: The eNodeB detects that the MME restarts or the MME link is interrupted.

Step 804: The eNodeB sends a radio resource control (RRC, Radio Resource Control) connection release request message to the UE.

Step 805: The UE returns an RRC connection release response message to the eNodeB.

Step 806: The S-GW sends a release bearer request message to the SGSN, where the request message carries a cause value of the MME restart or the link interruption, and is used to instruct the SGSN to release the ISR.

Step 807: After receiving the release bearer request message from the S-GW, the SGSN releases the ISR according to the indication in the message, and returns a release bearer response message to the S-GW.

Step 808: The UE is in an idle state in the SGSN, so the SGSN sends a paging message to all the RNCs in the RA where the UE is located, where the paging message carries the cause value of the MME restart or the link interruption, and is used to indicate that the UE releases the ISR. .

In step 809, the RNC forwards the paging message. Step 810: After receiving the paging message, the UE releases the ISR according to the indication in the message, and initiates a service request procedure in the SGSN network, so that the UE is converted into a connected state.

It should be noted that, in this embodiment, the first mobility management unit is the MME, and the second mobility management unit is the SGSN. For the case where the first mobility management unit is the SGSN and the second mobility management unit is the MME, The processing method is similar to this, and will not be described here. In addition, the start of step 804 in Fig. 8 and the start of step 806 are performed without prioritization.

The application scenario of the fourth embodiment of the present invention is as follows: The UE is in a connected state under the MME, is in an idle state in the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 4, the performing network element failure processing is as shown in FIG. 9, and mainly includes the following steps:

In step 901, the MME restarts or the MME link is interrupted.

Step 902: The S-GW detects that the MME restarts or the MME link is interrupted.

Step 903: The eNodeB detects that the MME restarts or the MME link is interrupted.

Step 904: The eNodeB sends an RRC connection release request message to the UE.

Step 905: The UE returns an RRC Connection Release Response message to the eNodeB.

Step 906: The S-GW sends a release bearer request message to the SGSN, where the request message carries

The cause value of the MME restart or link interruption is used to instruct the SGSN to release the ISR.

Step 907: After receiving the release bearer request message from the S-GW, the SGSN releases the ISR according to the indication in the message, and returns a release bearer response message to the S-GW.

Step 908: Because the UE is in an idle state in the SGSN, the SGSN sends a paging message to all RNCs in the RA where the UE is located.

Step 909, the RNC forwards the paging message.

Step 910: After receiving the paging message, the UE initiates a service request process in the SGSN network, so that the UE is converted into a connection state.

Step 911: The SGSN sends an ISR release request message to the RNC where the UE is located.

In step 912, the RNC forwards the ISR release request message. Step 913: The UE releases the ISR after receiving the ISR release request message, and returns an ISR release response message to the RNC.

Step 914: The RNC forwards an ISR release response message to the SGSN.

It should be noted that, in this embodiment, the first mobility management unit is the MME, and the second mobility management unit is the SGSN. For the case where the first mobility management unit is the SGSN and the second mobility management unit is the MME, The processing method is similar to this, and will not be described here. In addition, the start of execution of step 904 in Fig. 9 and the start of step 906 are performed without prioritization.

The application scenario of the fifth embodiment of the present invention is as follows: The UE is in an idle state under the MME, is in a connected state under the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 4, the performing network element failure processing is as shown in FIG. 10, and mainly includes the following steps:

In step 1001, the MME restarts or the MME link is interrupted.

Step 1002: The S-GW detects that the MME restarts or the MME link is interrupted.

Step 1003: The S-GW sends a release bearer request message to the SGSN, where the request message carries the cause value of the MME restart or the link interruption, and is used to instruct the SGSN to release the ISR.

Step 1004: After receiving the release bearer request message from the S-GW, the SGSN releases the ISR according to the indication in the message, and returns a release bearer response message to the S-GW.

Step 1005: Because the UE is in the connected state in the SGSN, the SGSN sends an ISR release request message to the RNC where the UE is located.

Step 1006: The RNC forwards the ISR release request message.

Step 1007: After receiving the ISR release request message, the UE releases the ISR and returns an ISR release response message to the RNC.

Step 1008: The RNC forwards an ISR release response message to the SGSN.

It should be noted that, in this embodiment, the first mobility management unit is the MME, and the second mobility management unit is the SGSN. For the case where the first mobility management unit is the SGSN and the second mobility management unit is the MME, The processing method is similar to this, and will not be described here. The application scenario of the sixth embodiment of the present invention is as follows: The UE is in an idle state in both the MME and the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 5, the performing network element failure processing is as shown in FIG. 11, and mainly includes the following steps:

Step 1101, the MME restarts or the MME link is interrupted.

Step 1102: The SGSN detects that the MME restarts or the MME link is interrupted.

Step 1103: The SGSN sends a release session request message to the S-GW, where the request message carries the cause value of the MME restart or the link interruption, and is used to instruct the S-GW to release the ISR.

Step 1104: After receiving the release session request message from the SGSN, the S-GW releases the ISR according to the indication in the message, and returns a release session response message to the SGSN.

Step 1105: The UE is in an idle state in the SGSN, so the SGSN sends a paging message to all the RNCs in the RA where the UE is located, where the paging message carries the cause value of the MME restart or the link interruption, and is used to indicate that the UE releases the ISR. .

Step 1106, the RNC forwards the paging message.

Step 1107: After receiving the paging message, the UE releases the ISR according to the indication in the message, and initiates a service request process in the SGSN network, so that the UE is converted into a connected state.

The application scenario of the seventh embodiment of the present invention is as follows: The UE is in an idle state in both the MME and the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 5, the performing network element failure processing is as shown in FIG. 12, and mainly includes the following steps:

In step 1201, the MME restarts or the MME link is interrupted.

Step 1202: The SGSN detects that the MME restarts or the MME link is interrupted.

Step 1203: The SGSN sends a release session request message to the S-GW, where the request message carries a cause value of the MME restart or the link interruption, and is used to instruct the S-GW to release the ISR. Step 1204: After receiving the release session request message from the SGSN, the S-GW releases the ISR according to the indication in the message, and returns a release session response message to the SGSN.

Step 1205: Since the UE is in an idle state in the SGSN, the SGSN sends a paging message to all RNCs in the RA where the UE is located.

Step 1206, the RNC forwards the paging message.

Step 1207: After receiving the paging message, the UE initiates a service request process in the SGSN network, so that the UE is converted into a connection state.

Step 1208: The SGSN sends an ISR release request message to the RNC where the UE is located.

Step 1209: The RNC forwards the ISR release request message.

Step 1210: After receiving the ISR release request message, the UE releases the ISR and returns an ISR release response message to the RNC.

Step 1211: The RNC forwards an ISR release response message to the SGSN.

The application scenario of the ninth embodiment of the present invention is as follows: The UE is in a connected state under the MME, is in an idle state under the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 5, the performing network element failure processing is as shown in FIG. 13, and mainly includes the following steps:

In step 1301, the MME restarts or the MME link is interrupted.

Step 1302: The SGSN detects that the MME restarts or the MME link is interrupted.

Step 1303: The eNodeB detects that the MME restarts or the MME link is interrupted.

Step 1304: The eNodeB sends an RRC Connection Release Request message to the UE.

Step 1305: The UE returns an RRC Connection Release Response message to the eNodeB.

Step 1306: The SGSN sends a release session request message to the S-GW, where the request message carries a cause value of the MME restart or the link interruption, and is used to instruct the S-GW to release the ISR. Step 1307: After receiving the release session request message from the SGSN, the S-GW releases the ISR according to the indication in the message, and returns a release session response message to the SGSN.

Step 1308: The UE is in an idle state in the SGSN, so the SGSN sends a paging message to all the RNCs in the RA where the UE is located, where the paging message carries the cause value of the MME restart or the link interruption, and is used to indicate that the UE releases the ISR. .

Step 1309, the RNC forwards the paging message.

Step 1310: After receiving the paging message, the UE releases the ISR according to the indication in the message, and

The service request process is initiated in the SGSN network, so that the UE is converted into a connected state.

The application scenario of the ninth embodiment of the present invention is as follows: The UE is in a connected state under the MME, is in an idle state in the SGSN, and the MME fails to restart. Then, according to the method shown in FIG. 5, the performing network element failure processing is as shown in FIG. 14, and mainly includes the following steps:

Step 1401, the MME restarts or the MME link is interrupted.

Step 1402: The SGSN detects that the MME restarts or the MME link is interrupted.

Step 1403: The eNodeB detects that the MME restarts or the MME link is interrupted.

Step 1404: The eNodeB sends an RRC Connection Release Request message to the UE.

Step 1405: The UE returns an RRC Connection Release Response message to the eNodeB.

Step 1406: The SGSN sends a release session request message to the S-GW, where the request message carries the cause value of the MME restart or the link interruption, and is used to instruct the S-GW to release the ISR.

Step 1407: After receiving the release session request message from the SGSN, the S-GW releases the ISR according to the indication in the message, and returns a release session response message to the SGSN.

Step 1408: The SGSN sends a paging message to all RNCs in the RA where the UE is located, because the UE is in an idle state in the SGSN. In step 1409, the RNC forwards the paging message.

Step 1410: After receiving the paging message, the UE releases the ISR according to the indication in the message, and initiates a service request process in the SGSN network, so that the UE is converted into a connected state.

Step 1411: The SGSN sends an ISR release request message to the RNC where the UE is located.

In step 1412, the RNC forwards the ISR release request message.

Step 1413: After receiving the ISR release request message, the UE releases the ISR and returns an ISR release response message to the RNC.

In step 1414, the RNC forwards the ISR release response message to the SGSN.

The application scenario of the tenth embodiment of the present invention is as follows: The UE is in an idle state under the MME, is in a connected state under the SGSN, and the MME is restarted and failed. Then, according to the method shown in FIG. 5, the performing network element failure processing is as shown in FIG. 15, and mainly includes the following steps:

Step 1501, the MME restarts or the MME link is interrupted.

Step 1502: The S-GW detects that the MME restarts or the MME link is interrupted.

Step 1503: The SGSN sends a release session request message to the S-GW, where the request message carries a cause value of the MME restart or the link interruption, and is used to instruct the S-GW to release the ISR.

Step 1504: After receiving the release session request message from the SGSN, the S-GW releases the ISR according to the indication in the message, and returns a release bearer response message to the SGSN.

Step 1505: Because the UE is in the connected state in the SGSN, the SGSN sends an ISR release request message to the RNC where the UE is located.

Step 1506: The RNC forwards the ISR release request message.

Step 1507: After receiving the ISR release request message, the UE releases the ISR and returns an ISR release response message to the RNC. Step 1508: The RNC forwards an ISR release response message to the SGSN.

Corresponding to the method for processing the failure of the network element shown in FIG. 4, the present invention further provides a system for processing a network element failure, comprising: an S-GW, a first mobility management unit, a second mobility management unit, and a UE, where a mobility management unit and a second mobility management unit provide mobility management services for the UE;

The S-GW is configured to release the ISR when the first mobility management unit connected to the UE is detected to be restarted or the link is abnormal, and notify the second mobility management unit connected to the UE to release the ISR.

a second mobility management unit, configured to complete the ISR release according to the notification of the first mobility management unit, and notify the UE to release the ISR;

The UE is configured to complete the ISR release according to the notification of the second mobility management unit.

Preferably, the S-GW is further configured to: send a release bearer request message to the second mobility management unit that is connected to the UE, where the message carries a cause value of the first mobility management unit restarting or the link is abnormal, and the cause value is used. Instructing the second mobility management unit to release the ISR; correspondingly, the second mobility management unit is further configured to release the ISR according to the indication in the release bearer request message.

Preferably, the second mobility management unit is further configured to: when the UE is in the connected state under the second mobility management unit, notify the UE to release the ISR through the ISR release request message; when the UE is in the idle state under the second mobility management unit The UE is notified by the paging message to release the ISR, or the UE is first converted into a connected state, and then the UE is notified to release the ISR through an ISR release request message.

The present invention further provides another system for deactivating an ISR, including: an S-GW, a first mobility management unit, a second mobility management unit, and a UE, where a mobility management unit and a second mobility management unit provide a mobility management service for the UE; a second mobility management unit, configured to detect, after detecting that the first mobility management unit connected to the UE is restarted or When the link is abnormal, the ISR is released, and the S-GW of the UE is notified to release the ISR and the resource between the ISR and the first mobility management unit, and notify the UE to release the ISR.

An S-GW, configured to release, according to the notification of the second mobility management unit, the ISR and resources between the S-GW and the first mobility management unit;

Preferably, the second mobility management unit is further configured to: send a release session request message to the S-GW of the UE, where the message carries a cause value of the first mobility management unit restarting or the link is abnormal, and the cause value is used to indicate The S-GW releases the ISR; correspondingly, the S-GW is further configured to release the ISR according to the indication in the release session request message.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for processing failure of a network element, characterized in that the method comprises:

The serving gateway (S-GW) releases the air interface signaling reduction (ISR) when detecting that the first mobility management unit connected to the user equipment (UE) is restarted or the link is abnormal, and notifies the second mobility management unit connected to the UE. Release the ISR;

2. The method for processing a network element failure according to claim 1, wherein the method further comprises:

ISR.

The method for processing a network element failure according to claim 1 or 2, wherein the second mobility management unit notifies the UE to release the ISR, specifically:

5. The method for processing a network element failure according to claim 4, wherein the method is The step includes: the second mobility management unit sends a release session request message to the S-GW of the UE, where the message carries a cause value of the first mobility management unit restarting or the link is abnormal, and the cause value is used to indicate S -GW releases the ISR;

The method for processing a network element failure according to claim 4 or 5, wherein the second mobility management unit notifies the UE to release the ISR, specifically:

A system for failing processing of a network element, the system comprising: an S-GW, a first mobility management unit, a second mobility management unit, and a UE, wherein the first mobility management unit and the second mobile The management unit provides mobility management services for the UE;

The system for processing a network element failure according to claim 7, wherein the S-GW is further configured to: send a release bearer request message to the second mobility management unit that is connected to the UE, where the message carries the first a cause value of the mobile management unit restarting or the link is abnormal, and the cause value is used to instruct the second mobility management unit to release the ISR;

The system for processing a network element failure according to claim 7 or 8, wherein the second mobility management unit is further configured to: when the UE is in a connected state under the second mobility management unit, pass the ISR. The release request message notifies the UE to release the ISR; when the UE is in the idle state under the second mobility management unit, the UE is notified by the paging message to release the ISR, or the UE is first converted into the connection state, and then the UE is notified by the ISR release request message. Release the ISR.

The second mobility management unit is configured to release an ISR when detecting that the first mobility management unit connected to the UE is restarted or the link is abnormal, and notify the S-GW of the UE to release the ISR and the first mobility management unit Resources, and notify the UE to release the ISR;

The system for processing a network element failure according to claim 10, wherein the second mobility management unit is further configured to send a release session request message to the S-GW of the UE, where the message carries the first mobile The cause value of the management unit restarting or the link is abnormal, and the reason value is used to indicate that the S-GW releases the ISR;

The system for processing a network element failure according to claim 10 or 11, wherein the second mobility management unit is further configured to: when the UE is in a connected state under the second mobility management unit, pass the ISR. The release request message notifies the UE to release the ISR; when the UE is in the idle state under the second mobility management unit, the UE is notified by the paging message to release the ISR, or the UE is first converted into the connection state, and then the UE is notified by the ISR release request message. Release the ISR.