WO2011153899A1 - Procédé et système de traitement de défaillance d'élément de réseau - Google Patents

Procédé et système de traitement de défaillance d'élément de réseau Download PDF

Info

Publication number
WO2011153899A1
WO2011153899A1 PCT/CN2011/074530 CN2011074530W WO2011153899A1 WO 2011153899 A1 WO2011153899 A1 WO 2011153899A1 CN 2011074530 W CN2011074530 W CN 2011074530W WO 2011153899 A1 WO2011153899 A1 WO 2011153899A1
Authority
WO
WIPO (PCT)
Prior art keywords
isr
management unit
mobility management
release
request message
Prior art date
Application number
PCT/CN2011/074530
Other languages
English (en)
Chinese (zh)
Inventor
卢飞
梁爽
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011153899A1 publication Critical patent/WO2011153899A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and system for network element failure processing. Background technique
  • Mobility management between 15 WLAN, Wireless Local Area Network
  • other non-3GPP access networks 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 is an evolved Node B (eNodeB, Evolved NodeB, also referred to as eNB).
  • eNodeB Evolved NodeB
  • eNB evolved Node B
  • PDN Packet Data Network
  • EPC provides lower latency and allows more wireless access systems to access, Includes the following network elements:
  • Mobility Management Entity 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). ).
  • GPRS General Packet Radio Service
  • the Serving Gateway 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 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.
  • IMSI International Mobile Subscriber Identification
  • 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.
  • the UE 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 ).
  • P-TMSI 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.
  • GTP-C GPRS tunneling protocol-Control plane
  • GPRS Tunneling Protocol-Control GPRS Tunneling Protocol-Control
  • 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.
  • GUI Globally Unique Temporary Identity
  • 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.
  • 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.
  • 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.
  • the S-GW 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.
  • MME/SGSN mobility management unit
  • 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
  • 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.
  • the present invention provides a method for processing a network element failure, the method comprising:
  • the serving gateway 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;
  • ISR air interface signaling reduction
  • 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
  • the second mobility management unit releases according to the indication in the release bearer request message.
  • the second mobility management unit notifies the UE to release the ISR, specifically:
  • the second mobility management unit 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;
  • the second mobility management unit 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;
  • the S-GW releases the ISR according to the indication in the release session request message.
  • the second mobility management unit notifies the UE to release the ISR, specifically:
  • 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 second mobility management unit 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 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;
  • 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 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 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 UE is configured to complete ISR release according to the notification of the second 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;
  • the S-GW is further configured to release the ISR according to the indication in the release session 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 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic structural diagram of an evolved packet network system in the prior art
  • FIG. 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.
  • FIG. 7 is a flowchart of a method for processing a network element failure according to Embodiment 2 of the present invention.
  • FIG. 8 is a flowchart of a method for processing a network element failure according to Embodiment 3 of the present invention.
  • FIG. 9 is a flowchart of a method for processing a network element failure according to Embodiment 4 of the present invention.
  • FIG. 10 is a flowchart of a method for processing a network element failure according to Embodiment 5 of the present invention.
  • FIG. 11 is a flowchart of a method for processing a network element failure according to Embodiment 6 of the present invention.
  • FIG. 12 is a flowchart of a method for processing a network element failure according to Embodiment 7 of the present invention.
  • FIG. 13 is a flowchart of a method for processing a network element failure according to Embodiment 8 of the present invention.
  • FIG. 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
  • a method for processing failure of a network element provided by the present invention 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.
  • 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.
  • 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.
  • 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.
  • RNCs radio network controllers
  • 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.
  • the first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • 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.
  • 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 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 first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • the processing method is similar to this, and will not be described here.
  • 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.
  • the performing network element failure processing is as shown in FIG. 8, and mainly includes the following steps:
  • 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.
  • RRC Radio Resource Control
  • 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. .
  • 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.
  • the first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • the processing method is similar to this, and will not be described here.
  • 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.
  • the performing network element failure processing is as shown in FIG. 9, and mainly includes the following steps:
  • 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.
  • 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.
  • the first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • the processing method is similar to this, and will not be described here.
  • 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.
  • the performing network element failure processing is as shown in FIG. 10, and mainly includes the following steps:
  • 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.
  • the first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • 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 first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • the processing method is similar to this, and will not be described here.
  • 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.
  • the performing network element failure processing is as shown in FIG. 12, and mainly includes the following steps:
  • 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 first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • the processing method is similar to this, and will not be described here.
  • 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.
  • the performing network element failure processing is as shown in FIG. 13, and mainly includes the following steps:
  • 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 first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • the processing method is similar to this, and will not be described here.
  • 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.
  • 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.
  • 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.
  • 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.
  • step 1414 the RNC forwards the ISR release response message to the SGSN.
  • the first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • the processing method is similar to this, and will not be described here.
  • 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.
  • the first mobility management unit is the MME
  • the second mobility management unit is the SGSN.
  • the processing method is similar to this, and will not be described here.
  • 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.
  • 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 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;
  • the UE is configured to complete the ISR release according to the notification of the second 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 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.

Abstract

La présente invention porte sur un procédé et un système de traitement de défaillance d'élément de réseau. Lorsqu'elle détecte qu'une première unité de gestion de mobilité connectée à un équipement utilisateur (UE) redémarre ou que la liaison est anormale, une passerelle de desserte (S-GW) désactive la réduction de signalisation en mode veille (ISR), et indique à une seconde unité de gestion de mobilité connectée à l'UE de désactiver l'ISR ; la seconde unité de gestion de mobilité désactive l'ISR et indique à l'UE de désactiver l'ISR. Ou, lorsqu'elle détecte qu'une première unité de gestion de mobilité connectée à un UE redémarre ou que la liaison est anormale, une seconde unité de gestion de mobilité connectée à l'UE désactive l'ISR, indique à une S-GW de l'UE de désactiver l'ISR et la ressource entre la S-GW et la première unité de gestion de mobilité, et indique à l'UE de désactiver l'ISR. À l'aide de la présente invention, l'asynchronisme d'informations entre la S-GW et des unités de gestion de mobilité est évité, et l'asynchronisme d'informations entre la S-GW et le réseau, qui est dû au fait que l'UE ne peut pas désactiver l'ISR, est évité.
PCT/CN2011/074530 2010-06-11 2011-05-23 Procédé et système de traitement de défaillance d'élément de réseau WO2011153899A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010200737.X 2010-06-11
CN201010200737XA CN102281564A (zh) 2010-06-11 2010-06-11 一种网元失败处理的方法和系统

Publications (1)

Publication Number Publication Date
WO2011153899A1 true WO2011153899A1 (fr) 2011-12-15

Family

ID=45097524

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/074530 WO2011153899A1 (fr) 2010-06-11 2011-05-23 Procédé et système de traitement de défaillance d'élément de réseau

Country Status (2)

Country Link
CN (1) CN102281564A (fr)
WO (1) WO2011153899A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103563429A (zh) * 2012-12-31 2014-02-05 华为技术有限公司 一种防止sgw与网络节点间信息不一致的方法、装置和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1620032A (zh) * 2003-11-19 2005-05-25 华为技术有限公司 一种实现多媒体广播/组播业务去激活的方法
CN101459905A (zh) * 2008-06-27 2009-06-17 中兴通讯股份有限公司 Isr去激活方法及isr去激活指示装置
CN101572877A (zh) * 2008-04-28 2009-11-04 大唐移动通信设备有限公司 实现去激活空闲状态信令优化功能的方法与装置
CN101583118A (zh) * 2008-07-01 2009-11-18 中兴通讯股份有限公司 Isr去激活方法及移动性管理单元

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101448294B (zh) * 2008-01-21 2011-05-04 华为技术有限公司 网络资源释放处理的方法及设备
CN101552980B (zh) * 2008-03-31 2011-02-09 华为技术有限公司 网络侧分离ue时的处理方法、移动性管理装置及网络系统
CN101572943B (zh) * 2008-04-28 2011-07-20 电信科学技术研究院 Mme释放isr情况下空闲态ue上下文的方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1620032A (zh) * 2003-11-19 2005-05-25 华为技术有限公司 一种实现多媒体广播/组播业务去激活的方法
CN101572877A (zh) * 2008-04-28 2009-11-04 大唐移动通信设备有限公司 实现去激活空闲状态信令优化功能的方法与装置
CN101459905A (zh) * 2008-06-27 2009-06-17 中兴通讯股份有限公司 Isr去激活方法及isr去激活指示装置
CN101583118A (zh) * 2008-07-01 2009-11-18 中兴通讯股份有限公司 Isr去激活方法及移动性管理单元

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE.: "MME/SGSN Restart.", GPP TSG CT4 MEETING #49BIS.C4-101670, 2 July 2010 (2010-07-02) *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103563429A (zh) * 2012-12-31 2014-02-05 华为技术有限公司 一种防止sgw与网络节点间信息不一致的方法、装置和系统

Also Published As

Publication number Publication date
CN102281564A (zh) 2011-12-14

Similar Documents

Publication Publication Date Title
US11665668B2 (en) Offset of international mobile subscriber identity
JP7366356B2 (ja) ワイヤレスネットワークによるワイヤレスデバイスのページング
US9143990B2 (en) Method and device for handling failure of mobility management device in ISR activated scenario
EP2582191B1 (fr) Procédé de communication mobile, système de communication mobile et entité d'accès
DK2702793T3 (en) Improvements to completed mobile calls
EP2291014B1 (fr) Procédé et terminal correspondant pour une mise à jour de relation d'association
WO2011153750A1 (fr) Procédé et système de synchronisation de données d'utilisateur
US20110110308A1 (en) Method for detaching network, a method for deactivating isr and an indicating device thereof
WO2009132567A1 (fr) Procédé, système et dispositif de déconnexion cachée
KR20140097324A (ko) 무선 통신 시스템에서 nas 시그널링 요청 처리 방법 및 장치
WO2009094871A1 (fr) Procédé pour purger des données de la mémoire tampon d'une passerelle de desserte
WO2009097814A1 (fr) Procédé et système de réalisation d'appel dans le domaine à commutation de circuits, et procédé de réalisation de service
WO2009097772A1 (fr) Procédé de commande, système de communication et dispositif correspondant pour une libération de ressource
WO2009117879A1 (fr) Procédé pour indiquer la gestion de support de la passerelle de desserte
US20140348071A1 (en) Bearer processing method and mobile management device
WO2009124488A1 (fr) Procédé, système et dispositif servant à acquérir des informations de services d’urgence
WO2012122910A1 (fr) Procédé et système de communication à double canal
WO2011107041A2 (fr) Procédé et système de traitement de service csfb, entité de gestion de mobilité et équipement utilisateur
WO2014201630A1 (fr) Procédé, dispositif et système de traitement de mise à jour de position de rattachement
WO2015123871A1 (fr) Procédé et dispositif pour traiter une défaillance de réseau
WO2011063762A1 (fr) Procédé, équipement réseau et équipement utilisateur assurant une connexion de service
WO2010054544A1 (fr) Procédé de radiomessagerie dans un système évolué de domaine paquet de communication mobile
EP2296333A1 (fr) Procédé de désactivation d'isr et unité de gestion de mobilité
WO2017125026A1 (fr) Procédé, dispositif et système de mise en œuvre de surveillance d'évènements mtc, et support de stockage
WO2009076814A1 (fr) Procédé et dispositif de mise à jour de règle pcc

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11791890

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11791890

Country of ref document: EP

Kind code of ref document: A1