WO2011157166A2 - Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité - Google Patents

Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité Download PDF

Info

Publication number
WO2011157166A2
WO2011157166A2 PCT/CN2011/075249 CN2011075249W WO2011157166A2 WO 2011157166 A2 WO2011157166 A2 WO 2011157166A2 CN 2011075249 W CN2011075249 W CN 2011075249W WO 2011157166 A2 WO2011157166 A2 WO 2011157166A2
Authority
WO
WIPO (PCT)
Prior art keywords
network element
management network
mobility management
user equipment
service
Prior art date
Application number
PCT/CN2011/075249
Other languages
English (en)
Chinese (zh)
Other versions
WO2011157166A3 (fr
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 华为技术有限公司
Priority to PCT/CN2011/075249 priority Critical patent/WO2011157166A2/fr
Priority to EP11795132.7A priority patent/EP2706810A4/fr
Priority to CN201180001085XA priority patent/CN102918918A/zh
Publication of WO2011157166A2 publication Critical patent/WO2011157166A2/fr
Publication of WO2011157166A3 publication Critical patent/WO2011157166A3/fr
Priority to US14/085,446 priority patent/US9143997B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/165—Performing reselection for specific purposes for reducing network power consumption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • Embodiments of the present invention relate to the field of mobile communications, and more particularly, to a method of processing service recovery and a mobility management network element. Background technique
  • EPC Evolved Universal Mobile Telecommunication System Territorial Radio Access Network
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • E-UTRAN and EPC form the Evolved Packet System (EPS).
  • EPS Evolved Packet System
  • the user equipment User Equipment, UE
  • GSM Global System for Mobile Communications
  • GSM Enhanced Data Rate for GSM Evolution
  • GSM EDGE Radio Access Network GSM EDGE Radio Access Network, GERAN
  • the Idle mode signaling reduction is a mechanism for reducing signaling interaction provided when the UE in the idle mode reselects the radio access network.
  • the ISR can include two states, an active state and a deactivated state. Take the UE as a re-election between E-UTRAN and UTRAN/GERAN.
  • the UE needs to register with the mobility management network element in the E-UTRAN, that is, the Mobility Management Entity (MME), and the mobility management network element in the UTRAN/GERAN.
  • MME Mobility Management Entity
  • GPRS General Packet Radio Service
  • SGSN Serving GPRS Supporting Node
  • the Serving GateWay keeps the connection information and the connection information of the SGSN, such as the Full Qualified TEID (F-TEID) of the MME/SGSN or IP address of the MME/SGSN;
  • the MME and the SGSN mutually store the connection information, that is, the MME stores the connection information of the SGSN, and the SGSN stores the connection information of the MME.
  • the SGW simultaneously stores the connection information of the MME and the connection information of the SGSN to the SGW, which means that the ISR is activated; the MME and the SGSN mutually save the connection information, and the MME and the SGSN mean ISR activation with each other.
  • the SGW when the SGW receives the downlink user plane or control plane data of the UE, the SGW triggers the corresponding MME and the SGSN to page the UE according to the saved connection information of the MME and the connection information of the SGSN. Because of the JHI, the UE can respond to the paging message of the corresponding network (that is, the called service of the UE is reachable) on the network where the UE resides, regardless of whether the current UE resides in the E-UTRAN or the UTRAN/GERAN.
  • the embodiment of the present invention provides a method for processing service recovery in an ISR activation scenario and a mobile management network element to avoid the problem of service interruption of the user equipment due to a service gateway failure in the ISR activation scenario.
  • a method for processing service recovery in an ISR scenario including: a first mobility management network element associated with an idle mode restriction signaling ISR and a second mobility management network element determining a service gateway failure, the first mobility management The network element and the second mobility management network element save the context of the user equipment of the service gateway service; the first mobility management network element or the second mobility management network element receives a trigger, and performs a process of service recovery of the user equipment.
  • a mobility management network element in an ISR activation scenario including: a determining unit, configured to determine a service gateway fault; and a storage unit, configured to save the service when the determining unit determines that the service gateway is faulty a context of the user equipment of the gateway service; a receiving unit, configured to receive a trigger; and a recovery unit, configured to perform a process of service recovery of the user equipment when the receiving unit receives the trigger.
  • the first mobility management network element and the second mobility management network element associated with the ISR determine that the service gateway is faulty, and the context of the user equipment associated with the service gateway is saved, when the first mobility management network element or the first The second mobility management network element receives other network elements from the network side or the When the user equipment is triggered, the first mobility management network element or the second mobility management network element performs a service recovery process to ensure normal operation of the service.
  • FIG. 1 is a schematic structural diagram of a communication system to which an embodiment of the present invention is applicable.
  • FIG. 2 is a flow chart of a method of handling network device failures in accordance with one embodiment of the present invention.
  • 3 is a schematic flow diagram of a fault handling process in accordance with one embodiment of the present invention.
  • FIG. 4 is a schematic flow chart of a fault handling process in accordance with another embodiment of the present invention.
  • FIG. 5 is a schematic flow chart of a fault handling process in accordance with another embodiment of the present invention.
  • FIG. 6 is a schematic flow chart of a fault handling process in accordance with another embodiment of the present invention.
  • FIG. 7 is a schematic flow chart of a fault handling process in accordance with another embodiment of the present invention.
  • Figure 8 is a schematic block diagram of a mobility management network element in accordance with one embodiment of the present invention.
  • FIG. 9 is a schematic block diagram of a mobility management network element in accordance with another embodiment of the present invention. detailed description
  • FIG. 1 is a schematic structural diagram of a communication system to which an embodiment of the present invention is applicable.
  • the user equipment 101 is accessed through the local wireless access network 102, and the mobility management network element 103 is responsible for functions such as location management, connection management, security authentication, and gateway selection of the mobile user equipment.
  • the service gateway 104 is a local access gateway of the user equipment, and is responsible for access technology related connection management and data forwarding.
  • the packet data network gateway 105 is a gateway for user equipment to access an external data network.
  • the user equipment in the embodiment of the present invention may be: User Equipment (User Equipment); or Mobile Station (Mobile Station).
  • User Equipment User Equipment
  • Mobile Station Mobile Station
  • the radio access network in the embodiment of the present invention may be: an evolved universal mobile communication system, landless An Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN), whose access network element may be an E-UTRAN NodeB (E-UTRAN NodeB); or a global mobile communication GSM/EDGE Radio Access Network (GSM)
  • the access network element may be a base station (Base Transceiver Station, called a BTS); or a Universal Mobile Telecommunication System Territorial Radio Access Network (UTRAN), which accesses the network element It can be a 3G base station (NodeB).
  • the mobility management network element in the embodiment of the present invention may be a mobility management entity (Mobility).
  • MME Management Entity
  • SGSN GPRS Service Support Node
  • the serving gateway in the embodiment of the present invention may be a Serving Gateway (SGW).
  • SGW Serving Gateway
  • the packet data network gateway in the embodiment of the present invention may be a packet data network gateway (Packet
  • PGW Data Network Gateway
  • the first mobility management network element associated with the idle mode restriction signaling ISR and the second mobility management network element determine that the service gateway is faulty, and the first mobility management network element and the second mobility management network element save the service gateway service.
  • the context of the user device is a configurable period of time.
  • the first or the second mobility management network element may determine the service gateway fault, which may include, but is not limited to, the following manners:
  • the mobility management network element receives a path detection (eg, echo request) message sent by the SGW, and the mobility management network element compares the local restart counter included in the path detection message.
  • a path detection eg, echo request
  • the value of the (local Restart Counter) is different from the value of the local restart counter of the locally stored serving gateway (for example, the former is 1 greater than the latter), thereby determining that the serving gateway is restarted; or
  • the mobility management network element sends a path detection (for example, echo request) message to the serving gateway, and does not receive the response message for a long time, and the mobility management network element determines that the service gateway has a non-restart failure.
  • a path detection for example, echo request
  • the mobile management network element receives the notification message sent by the operation and maintenance system, and learns the service network. A non-restart failure or a service gateway restart occurs.
  • the context of the user equipment that saves the service gateway service may include, but is not limited to: the mobility management network element queries the locally stored user equipment context, and if the service gateway recorded in the user equipment context is faulty, The service gateway, the mobility management network element saves the context of the user equipment.
  • the context of the saved user equipment may specifically include: saving a packet data network of the user equipment to a connection context (a PDN connection context or a PDN context table data) and/or a mobility management context ( MM Bearer Context ).
  • the context of the saved user equipment includes the following information: user equipment identification information, for example, an International Mobile Subscriber Identity; and/or an access point name (APN) And/or a bearer ID, where one PDN connection may include one or more bearers, each bearer has a bearer identifier unique to the user granularity; the quality of service (Quality of Service)
  • the information, where the QoS information may specifically include a QoS class identifier (QCI), and/or an allocation/retention priority (ARP).
  • QCI QoS class identifier
  • ARP allocation/retention priority
  • the mobility management network element determines the SGW fault, all the contexts of all the user equipments of the service gateway service may be saved, and the related context of the related user equipment may be saved according to the context preservation policy.
  • the context saving policy may include: a policy of user equipment granularity and/or a policy of context granularity.
  • the policy of user granularity may be the category of the reference user, for example, saving the context of the gold medal user (high priority), or directly setting a part of the user equipment to be saved (for example, some special IMSI). ), - Part of it does not need to be saved.
  • the QoS information of the bearer may be referred to, for example, the context of the specific QCI value or the specific ARP value is saved, and the entire context of the user equipment, or the policy of the context granularity may be saved, or may include only any One of them.
  • the mobility management network element can locally configure the above context saving policy.
  • Local configuration The above context saving policy can be regarded as a common means of configuring according to carrier policies.
  • the foregoing context saving policy information may also be learned from other network elements, for example, PGW or HSS (home subscriber server) / HLR (home location register) Register).
  • PGW packet gateway
  • HSS home subscriber server
  • HLR home location register
  • the embodiment may further include the data packet gateway determining the service gateway failure, and retaining the context of the user equipment served by the serving gateway.
  • the PGW may save all the contexts of all the user equipments of the serving gateway service, and may also save the related context of the related user equipment according to the context saving policy.
  • the above context saving policy information can also be learned from other network elements. For example, MME or SGSN or PCRF (policy and charging rules function).
  • the policies of the mobility management network element and the packet data network gateway configuration are consistent. If they are not consistent, for example, in a roaming scenario, the mobility management network element and the packet data network gateway belong to different operators, then the mobility management network element and the packet data network gateway also need to synchronize the above context preservation results. Specifically, at this time, after detecting, by one of the mobility management network element and the packet data network gateway, the SGW fails, the context of the user equipment served by the serving gateway is saved, and another network element is executed. After the user equipment context saves the process, it notifies the context save result (ie, which contexts are saved), so as to achieve synchronization of the context save result.
  • the present invention recommends that the packet data network gateway perform the user equipment context preservation process and then notify the mobility management network element to save the context of the user equipment that is consistent with itself; or one of the mobility management network element and the packet data network gateway.
  • the mobility management network element Before detecting the SGW failure, for example, when the user equipment creates a packet data network connection procedure, the mobility management network element notifies the packet data network gateway of its learned context preservation policy or is learned by the packet data network gateway to the mobility management network element.
  • the context saves the policy, thereby ensuring that the mobile management network element and the packet data network gateway save the synchronized context after learning of the SGW failure.
  • the mobility management network element or the packet data network gateway saves the context of the user equipment, and further includes starting a timer.
  • the timer may be used to secure the following step 202, that is, when a trigger related to the saved context of the user equipment is received, and when the timer has not timed out, the flow of service recovery is performed.
  • the timer further controls a saving time of the context of the user equipment. If the timer expires, the mobility management network element deletes the context of the saved user equipment.
  • the length of the timer may be equal to a periodic tracking area update timer (hereinafter referred to as a PTAU timer) or a periodic routing area update timer (a periodic routing area update timer).
  • a PTAU timer a periodic tracking area update timer
  • a periodic routing area update timer a periodic routing area update timer
  • the first mobility management network element or the second mobility management network element receives a trigger, and performs the The process of business recovery of user equipment.
  • the receiving, by the first mobility management network element or the second mobility management network element, the triggering comprises: receiving, by the first mobility management network element or the second mobility management network element, a notification message sent by the packet data network gateway or the serving gateway; Or the first mobility management network element receives the notification message sent by the second mobility management network element; or the second mobility management network element receives the notification message sent by the first mobility management network element, or the first The mobility management network element or the second mobility management network element receives the tracking area update request or the routing area update request or the service request message sent by the user equipment.
  • the embodiment of the present invention includes a process of triggering the mobile management network element to perform service recovery by using other types or names of messages/signaling.
  • the process of performing the service recovery of the user equipment specifically includes: performing a network connection re-establishment process; or triggering the user equipment to initiate an attach process.
  • the specific implementation of the performing network connection reestablishment process includes:
  • the first mobility management network element or the second mobility management network element performs a service Gateway migration process.
  • the first mobility management network element or the second mobility management network element receives the tracking area update request or the routing area update request message sent by the user equipment: the first mobility management network element or the first The mobile management network element performs a service gateway migration process.
  • the service gateway migration process specifically includes: the first mobility management network element or the second mobility management network element selects a service gateway; the first mobility management network element or the second mobility management network element selects the The serving gateway sends a create session request message to cause the selected serving gateway to send a modify bearer request message to the packet data network gateway.
  • the first mobility management network element or the second mobility management network element receives the packet data network network. And the notification message sent by the service gateway or the first mobility management network element receives the notification message sent by the second mobility management network element or the second mobility management network element receives the notification message sent by the first mobility management network element or After the mobile management network element or the second mobility management network element receives the service request message sent by the user equipment, the method further includes: the first mobility management network element or the second mobility management network element performing global unique temporary identity re-allocation GUTI or The packet temporary mobile subscriber identity P-TMSI reallocation procedure is such that the user equipment performs a tracking area update or routing area update procedure to activate the ISR.
  • the method further includes: indicating that the user equipment ISR is deactivated, and/ Or instruct the service gateway (ie, the selected service gateway) that the ISR is deactivated.
  • the indicating that the ISR is deactivated may not indicate that the ISR is activated.
  • the first mobility management network element may indicate that the second mobility management network element ISR is deactivated or the second mobility management network element indicates that the first mobility management network element ISR is deactivated.
  • the specific implementation of the triggering the user equipment to initiate an attach process includes: (2.1) receiving, at the first mobility management network element or the second mobility management network element, a notification message sent by a packet data network gateway or a serving gateway. Or the first mobility management network element receives the notification message sent by the second mobility management network element or the second mobility management network element receives the notification message sent by the first mobility management network element: the first mobility management The network element and the second mobility management network element send a paging message carrying the international mobile subscriber identity (IMSI) of the user equipment to the user equipment, so that the user equipment initiates an attach procedure.
  • IMSI international mobile subscriber identity
  • the first mobility management network element or the second mobility management network element receives the service request or the tracking area update request or the routing area update request message sent by the user equipment: the first mobility management network The UE or the second mobility management network element sends a service rejection or tracking area update rejection or routing area update message to the user equipment, so that the user equipment initiates an attach procedure.
  • the first mobility management network element or the second mobility management network element receives the notification message sent by the packet data network gateway or the serving gateway, or the first mobility management network element receives the notification message sent by the second mobility management network element.
  • the second mobility management network element receives the notification message sent by the first mobility management network element, where the notification message carries the international mobile subscriber identity IMSI of the user equipment.
  • the IMSI-enabled notification message is used to instruct the mobility management network element to perform a service recovery process on the user equipment.
  • the notification message may further include a bearer identity and/or an access point name APN and/or a quality of service level identity QCI and/or an allocation hold priority ARP.
  • the bearer identifier and/or the access point name APN and/or the service quality level identifier QCI and/or the allocation hold priority ARP are used to instruct the mobility management network element to perform a service on the bearer/PDN connection of the user equipment. The process of recovery.
  • the first mobility management network element in this embodiment may be an MME or an SGSN, and the corresponding second mobility management network element is an SGSN or MME associated with the ISR.
  • the process of re-establishing the bearer is triggered, so that the re-establishment process can be performed according to the service usage of the user, and the feasibility is compared. Good and have little impact on the system.
  • the first mobility management network element and the second mobility management network element associated with the ISR may determine that the service gateway is faulty, and the context of the user equipment associated with the service gateway is saved, when the first mobility management network element or When the second mobility management network element receives the trigger from the other network element or the user equipment on the network side, the first mobility management network element or the second mobility management network element performs a service recovery process to ensure normal operation of the service. .
  • FIG. 3 is a schematic flow diagram of a fault handling process in accordance with one embodiment of the present invention.
  • the first mobility management network element or the second mobility management network element obtains a process of triggering the service recovery by the gateway device or other mobility management network element associated with the ISR.
  • the UE is used to represent the user equipment
  • the MME and the SGSN represent two mobility management network elements associated with the ISR
  • the SGW represents the service gateway
  • the PGW represents the packet data network gateway.
  • embodiments of the invention are not limited to the particular systems represented by these terms.
  • FIG. 3 is a schematic flow diagram of a fault handling process in accordance with one embodiment of the present invention.
  • the mobility management network element at this time may include a first mobility management network element and a second mobility management network element, where the first mobility management network element and the second mobility management network element are an MME and an SGSN associated with the ISR.
  • the first mobility management network element may be an MME, or may be an SGSN
  • the second management network element is a corresponding SGSN or an MME, which is not specifically limited in this implementation.
  • the packet data network gateway and the mobility management network element determine that the serving gateway is faulty, and the context of the user equipment serving the serving gateway service is saved.
  • the manner of saving the context of the user equipment may be as described in 201 of FIG. 2 .
  • the mobility management network element and the packet data network gateway save the context of the user equipment serving the service gateway service when determining that the service gateway is faulty.
  • the method includes: but is not limited to: the mobile management network element or the packet data network gateway queries the user equipment context of the local storage (temporary storage), and if the service gateway recorded in the user equipment context is the service gateway that is faulty, Then the mobility management network element or the packet data network gateway saves the context of the user equipment.
  • the mobility management network element and the packet data network gateway determine the SGW failure, all the contexts of all the user equipments served by the service gateway may be saved, or the context of the related user equipment may be saved according to the context preservation policy.
  • the mobility management network element or the packet data network gateway also includes starting a timer. The manner in which the mobility management network element and the packet data network gateway learn the context preservation policy and the implementation manner of the timer are described in 201 of FIG. 2 .
  • the PGW receives a downlink data packet related to a context of the saved user equipment. Specifically, the PGW receives the downlink data packet, determines, according to the target IP address information in the downlink data packet, whether a corresponding context is saved, and if yes, that is, locates the context, determining that the user equipment is received and saved Context-sensitive downstream packets, which trigger subsequent steps. Otherwise, the PGW may choose to discard the downlink data packet.
  • the downlink data packet may include a downlink signaling plane message or a downlink user plane packet, which is not limited in this embodiment.
  • the PGW sends a notification message to the MME and the SGSN.
  • Step 303A
  • the PGW (direct) sends a notification message to the MME and the SGSN associated with the ISR; wherein, the PGW needs to obtain the MME and SGSN address information or identification information associated with the ISR from the SGW or other network element, so as to facilitate the The MME and the SGSN send a notification message.
  • the PGW may receive the request message sent by the SGW by using an attach procedure, a tracking location update process, a routing area update process, a PDN connection activation process, or a PDP context activation process.
  • the session request message or the modify bearer request message is used to learn MME/SGSN address information or identification information.
  • the PGW can simultaneously obtain the address information or the identification information of the MME and the SGSN, and the PGW can update the stored MME address information/identification information according to the MME address information/identification information reported by the SGW, and the SGSN reported according to the SGW.
  • the address information/identification information updates its stored SGSN address information/identification information.
  • the PGW receives the downlink data packet, and matches the IP address information in the data packet to the corresponding context, and locates the context to obtain the user equipment information corresponding to the downlink data packet (for example, MME/SGSN address information/identification information (for example, MME/SGSN F-TEID) obtained by IMSI) and (before knowing the SGW failure)ong.
  • MME/SGSN address information/identification information for example, MME/SGSN F-TEID
  • the PGW can learn the data.
  • the bearer information corresponding to the packet for example, the bearer identity and/or the quality of the bearer).
  • the timer that is started in the step 301 does not time out, and the PGW sends a notification message to the MME and the SGSN, where the notification message carries information about the user equipment corresponding to the downlink data packet, where the notification message is in the notification message.
  • the IP layer address may be an IP address of the mobility management network element (the IP address may be included in the MME/SGSN address information that the PGW knows, or the PGW parses or queries according to the MME/SGSN identification information learned by the PGW. of).
  • Step 303A-2 The PGW (directly) receives the response message sent by the MME and the SGSN.
  • the PGW sends a notification message to the SGW.
  • the PGW can send the notification message to the MME and the SGSN through the restarted SGW. If the SGW fails to be a non-restart fault, the PGW can send the foregoing to the MME/SGSN through the candidate SGW. Notification message.
  • the standby SGW can provide services for user equipments in the MME and the SGSN, and belong to the same operator as the restart SGW.
  • the PGW can be configured (for example, the PGW locally configures the connectable SGW master device and the backup device address information); or the candidate SGW address information/identification information corresponding to the SGW can be obtained by querying the DNS; or The candidate SGW address information/identification information is obtained by sending a message carrying the candidate SGW address information/identification information to the SGW.
  • the PGW may track the location update process and route through the attach procedure. The area update process, the PDN connection activation process or the PDP context activation process, etc., obtains the alternative SGW address information/identification information (for example, the IP address of the alternative SGW or the alternative SGW FQDN) by receiving the request message sent by the SGW.
  • the notification message sent by the PGW to the SGW may include the MME and the SGSN address information/identification information associated with the ISR, to instruct the SGW to send a notification message to the corresponding MME and the SGSN.
  • the PGW receives the response message sent by the SGW.
  • the SGW sends a notification message to the MME and the SGSN.
  • the SGW can learn the MME associated with the ISR through the backup system or the local configuration.
  • SGSN address information/identification information can be learned by step 303B-1 (ie, obtained from PGW Knowing the MME and SGSN address information/identification information associated with the ISR, in order to send a notification message to the MME and the SGSN; or, the SGW can connect to the MME pool and the SGSN pool (MME/SGSN Pool) connected thereto
  • MME/SGSN Pool MME/SGSN Pool
  • the notification message is sent to all MMEs/SGSNs of the MME/SGSN pool: when the MME/SGSN in the MME/SGSN pool receives the notification message, if the MME/SGSN receives the notification message If the user equipment context of the user equipment is saved, the process of performing service recovery is triggered; if the user equipment context of the user equipment is not saved in the MME/SGSN that receives the notification message, the MME/SGSN rejects the notification. A message (eg, the MME/SGSN sends a response message carrying a reject reason value to the SGW) or ignores the notification message.
  • the MME/SGSN sends a response message carrying a reject reason value to the SGW
  • the SGW receives the response message sent by the MME and the SGSN.
  • Step 303C
  • the PGW (direct) sends a notification message to the MME/SGSN;
  • step 303A-1 For the MME/SGSN address information/identification information, refer to 303A-1.
  • the PGW can only know (store) the address information/identification information of one of the MME or SGSN. At this time, the PGW may update its stored MME/SGSN address information/identification information according to the MME/SGSN address information/identification information reported by the SGW. In this step, the PGW sends a notification message to the MME/SGSN (that is, the PGW can only send to one of the mobility management network elements), and the implementation of the notification message is described in 303A-1.
  • the PGW receives the response message sent by the MME/SGSN.
  • the MME/SGSN sends a notification message to the SGSN/MME associated with the ISR; wherein, in this step, the step includes the first mobility management network element sending a notification message or a second mobility management network element to the second mobility management network element.
  • a notification message sent to the first mobility management network element ie, the MME sends a notification message to the SGSN associated with the ISR or the SGSN sends a notification message to the MME associated with the ISR.
  • Step 303C-4 The MME/SGSN receives the response message sent by the SGSN/MME. Step 303D:
  • the PGW sends a notification message to the SGW.
  • step 303B-1 For the selection of the SGW and the learning of the alternative SGW address information/identification information, refer to step 303B-1.
  • the notification message sent by the PGW to the SGW may further include an MME/SGSN
  • the address information/identification information is different from the step 303B-1, in which the PGW only knows the address information/identification information of one of the MME or the SGSN, and the notification message sent by the PGW to the SGW in this step only Includes address information/identification information for a mobility management network element.
  • the PGW receives the response message sent by the SGW.
  • the SGW sends a notification message to the MME/SGSN.
  • the SGW can obtain the MME/SGSN address information/identification information through the backup system or the local configuration, or can learn (ie, learn from the PGW) the MME and SGSN address information/identification information associated with the ISR through the step 303D-1, so as to facilitate the
  • the MME/SGSN sends a notification message; or, the SGW may send to one or more MME/SGSNs (eg, all MME/SGSNs in the MME/SGSN Pool) in the MME/SGSN Pool to which it is connected. Notification message.
  • the MME/SGSN in the MME/SGSN pool receives the notification message
  • the MME/SGSN in the MME/SGSN pool receives the notification message
  • the MME/SGSN in the notification message is received
  • the process of performing service recovery is triggered; if the user equipment context of the user equipment is not saved in the MME/SGSN that receives the notification message, the MME/SGSN rejects the notification.
  • a message eg, the MME/SGSN sends a response message carrying a reject cause value to the SGW) or ignores the notification message.
  • the SGW sends a notification message only to the MME or SGSN (only to the MME or SGSN), which does not send the notification message to the MME and the SGSN at the same time; or, only corresponds to the MME Pool or the SGSN Pool.
  • the MME/SGSN sends a notification message, and does not simultaneously send a notification message to the MME/SGSN corresponding to the MME Pool and the SGSN Pool.
  • the SGW receives the response message sent by the MME/SGSN.
  • the MME/SGSN sends a notification message to the SGSN/MME associated with the ISR; wherein, in this step, the step includes the first mobility management network element sending a notification message or a second mobility management network element to the second mobility management network element.
  • a notification message sent to the first mobility management network element ie, the MME sends a notification message to the SGSN associated with the ISR or the SGSN sends a notification message to the MME associated with the ISR.
  • the MME/SGSN receives the response message sent by the SGSN/MME associated with the ISR.
  • the (first or second) mobility management network element may receive a notification sent by the gateway device (ie, SGW or PGW) or other mobile management network element associated with the ISR through this step.
  • the message which triggers the process of performing a business recovery.
  • the MME/SGSN receives the notification message sent by the PGW or the SGW, or the MME/SGSN receives the notification message sent by the SGSN/SGSN to carry the international mobile subscriber identity code IMSI of the user equipment.
  • the IMSI carried in the notification message is used to instruct the mobility management network element to perform a service recovery process on the user equipment.
  • the notification message may also include a bearer identity and/or an access point name APN and/or a service quality level identifier QCI and/or an allocation hold priority ARP.
  • the bearer identifier and/or the access point name APN and/or the service quality level identifier QCI and/or the allocation hold priority ARP are used to indicate that the mobility management network element performs the bearer/PDN connection to the user equipment. The process of business recovery.
  • the MME and the SGSN page the UE.
  • the MME pages the UE by using an E-UTRAN NodeB (ENodeB), which is a packet temporary mobile subscriber identity (SAE-TMSI).
  • ENodeB E-UTRAN NodeB
  • SAE-TMSI packet temporary mobile subscriber identity
  • the SGSN pages the UE by using a base station (Base Transceiver Station, BTS) or a 3G base station (NodeB), and the paging message carries a packet temporary mobile subscriber identity (P-TMSI) .
  • BTS Base Transceiver Station
  • NodeB 3G base station
  • the MME/SGSN learns the corresponding system architecture evolved temporary mobile subscriber identity or the grouped temporary mobile subscriber identity according to the context of the user equipment saved by the IMSI carried in the notification message.
  • both mobile management network elements MME and SGSN need to page the UE to ensure that the UE can receive the paging, so that the UE can be in the UE.
  • the resident network responds to the paging, ensuring that the UE residing in any access network can implement service recovery.
  • the UE performs a service request process.
  • the UE if the UE camps on the E-UTRAN, and receives the paging message in step 304, the UE initiates a service request procedure in the E-UTRAN, for example, including the step of the UE sending a service request (Service Request) message to the MME;
  • the UE camps on the UTRAN, and receives the paging message in step 304, where the UE initiates a service request procedure in the UTRAN, for example, including the step of the UE sending a Service Request message to the SGSN;
  • the receiving step a paging message in 304 the UE sends a paging response message to the SGSN at the GERAN, etc. Steps, responding to paging on the network side.
  • the step 304 and the step 305 may also be collectively referred to as a network-triggered service request (Network Triggered Service Request) procedure.
  • the MME/SGSN performs a service gateway migration (SGW relocation) process.
  • the MME/SGSN is the MME/SGSN that receives the service request (Service Request) or the paging response message in step 305.
  • the step may occur after the MME/SGSN receives the service request or paging response message in step 305.
  • the network connection of the user equipment is reconstructed by performing a service gateway migration process.
  • the service gateway migration process specifically includes:
  • the mobile management network element selects the monthly service gateway
  • the mobile management network element selecting a service gateway includes: if the service gateway failure is a service gateway restart, selecting a restarted service gateway or a new service gateway (for example, an alternate service gateway); Non-restart failure, then a new service gateway (for example, select an alternate service gateway).
  • the mobility management network element sends a create session request message to the selected serving gateway.
  • the mobility management network element may recover all the contexts of the user equipment by using the service gateway migration process, and may also restore part of the context.
  • the MME/SGSN saves the query query according to the bearer identifier and/or the access point name APN and/or the service quality level identifier QCI and/or the allocation hold priority ARP carried in the notification message in step 303.
  • the context of the user equipment reestablishes the corresponding bearer and/or corresponding PDN connection with the same bearer identity and/or access point name APN and/or quality of service level identity QCI and/or assigned hold priority ARP.
  • the selected serving gateway receives a modification bearer response message sent by the packet data network gateway;
  • the mobility management network element receives a create session response message sent by the selected serving gateway.
  • the mobility management network element performs global unique temporary identity re-allocation (GUTI)
  • the process includes the MME sending a global unique temporary identity re-allocation command (GUTI Reallocation Command) message to the UE.
  • GUI Reallocation Command global unique temporary identity re-allocation command
  • the tracking area identifier list that is allocated by the MME does not include the tracking area identifier that is broadcast by the network element of the radio access network, so that the user equipment initiates a tracking area update process (TAU) process.
  • TAU tracking area update process
  • the process includes the SGSN performing a packet temporary mobile user identity relocation command (P-TMSI Reallocation Command) message.
  • P-TMSI Reallocation Command packet temporary mobile user identity relocation command
  • the routing area identifier allocated by the SGSN is different from the tracking area identifier broadcasted by the network element of the radio access network, so that the user equipment initiates a Routing Area Update (RAU) process.
  • RAU Routing Area Update
  • the UE performs a tracking area update process or a tracking area update process.
  • the tracking area update process or the tracking area update process includes the following steps:
  • the UE sends a Tracking Area Update Request (TAU Request)/Routing Area Update Request (RAU Request) message to the MME/SGSN.
  • TAU Request Tracking Area Update Request
  • RAU Request RAU Request
  • the MME/SGSN at this time is the mobility management network element in step 307.
  • the MME/SGSN sends a modify bearer request message to the SGW, indicating that the ISR is deactivated (ie, does not indicate ISR activation);
  • the SGW at this time is the service gateway selected in step 306.
  • the MME/SGSN sends a tracking area update/tracking area update request message to the UE, indicating that the ISR is deactivated (ie, does not indicate ISR activation).
  • the MME/SGSN sends a request message to the SGSN/MME associated with the ISR, indicating that the ISR is deactivated.
  • the step 309 is an optional step, and the request message causes the ISR-related SGSN/MME to delete the context of the saved user equipment. If the request message is not received, the SGSN/MME may wait for the context of the saved user equipment to be deleted after the timer expires in step 301.
  • 309 in Fig. 3 is shown as being executed after 308, the embodiment of the invention is not limited thereto. 309 can also be executed concurrently with 308, or prior to 308.
  • the first mobility management network element and the second mobility management network element associated with the ISR determine that the service gateway fault determines that the service gateway is faulty, and the context of the user equipment served by the serving gateway is saved, when the first mobility management network element Or the second mobility management network element receives other network elements on the network side.
  • the notification message related to the context of the user equipment is sent by, for example, a packet data network gateway or a service gateway or other mobile management network element associated with the ISR
  • the first mobility management network element or the second mobility management network element executes The process of service recovery of the user equipment is performed to ensure the normal operation of the service.
  • FIG. 4 is a schematic flow chart of a fault handling process in accordance with another embodiment of the present invention.
  • the first mobility management network element or the second mobility management network element obtains the process of triggering the service recovery by the gateway device or other mobility management network element associated with the ISR.
  • the PGW receives a downlink data packet related to a context of the saved user equipment. For details, see 302.
  • the PGW sends a notification message to the MME/SGSN.
  • the MME and the SGSN page the UE.
  • the MME is different from the step 304 in that: the MME pages the UE by using an E-UTRAN NodeB (ENodeB), the paging message carries an International Mobile Subscriber Identity (IMSI); and the SGSN passes through the base station (Base The Transceiver Station, called the BTS, or the 3G base station (NodeB) pages the UE, and the paging message carries the International Mobile Subscriber Identity (IMSI).
  • the MME and the SGSN use the IMSI paging UE (that is, the paging message carries the IMSI), and the UE is triggered to perform an attach procedure.
  • both mobile management network elements MME and SGSN need to page the UE to ensure that the UE can receive the page, so that the UE can respond to the paging on the network where it resides, ensuring that it resides in any access.
  • the UE of the network can implement service recovery.
  • the UE performs an attach procedure.
  • the attaching process specifically includes:
  • the UE sends an attach request message to the MME or the SGSN;
  • the UE if the UE camps on the E-UTRAN and receives the paging message in step 404, the UE sends an attach request (Attach Request) to the MME (the MME is not limited to the MME that sends the paging message in step 404). If the UE camps on the UTR AN/GER AN and receives the paging message in step 404, the UE sends an attach request to the SGSN (the SGSN is not limited to the SGSN that sends the paging message in step 404) (Attach Request) ) Message. 405-2: The mobility management network element selects the monthly service gateway;
  • the mobile management network element selecting a service gateway includes: if the service gateway failure is a service gateway restart, selecting a restarted service gateway or a new service gateway (for example, an alternate service gateway); Non-restart failure, then a new service gateway (for example, select an alternate service gateway).
  • the mobility management finder packet data network gateway is further included in the attaching process, and the PGW different from the original service in the step 402 is not limited to be selected at this time.
  • the mobility management network element sends a create session request message to the selected serving gateway.
  • the create session request message sent by the MME/SGSN to the SGW carries the address information/identification information of the selected packet data network gateway.
  • the MME/SGSN indicates that the SGW ISR is deactivated (ie, does not indicate ISR activation) by using the Create Session Request message.
  • the selected serving gateway sends a create session request message to the selected packet data network gateway
  • the selected serving gateway receives a create session response message sent by the selected packet data network gateway;
  • the mobility management network element receives a create session response message sent by the selected serving gateway.
  • the mobility management network element sends an attach accept message to the user equipment.
  • the MME/SGSN indicates that the UE ISR is deactivated by an attach accept message (ie, does not indicate ISR activation).
  • the attaching process may further include: sending, by the MME/SGSN, a location update message to the HLR/HSS, triggering the HLR/HSS to send a cancel location to the first mobility management network element and/or the second mobility management network element. a message, such that the first mobility management network element and/or the second mobility management network element deletes a context of the user equipment.
  • the HLR/HSS sends a cancel location message to the first mobility management network element and the second mobility management network element, to And causing the first mobility management network element and the second mobility management network element to delete the context of the user equipment; or, if the MME/SGSN is the first mobility management network element or the second mobility management network element, the HLR/HSS Sending a cancel location message to the second mobility management network element or the first mobility management network element, so that the second mobility management network element or the first mobility management network element deletes the context of the user equipment, and may further include
  • the MME/SGSN goes The ISR is activated (ie, the F-TEID of the second/first mobility management network element associated with the ISR is deleted).
  • the first mobility management network element and the second mobility management network element associated with the ISR determine that the service gateway fault determines that the service gateway is faulty, and the context of the user equipment served by the serving gateway is saved, when the first mobility management network element Or the second mobility management network element receives a notification message related to the context of the user equipment sent by another network element on the network side (for example, a packet data network gateway or a service gateway or another mobile management network element associated with the ISR), A mobile management network element or a second mobility management network element performs a service recovery process of the user equipment to ensure normal operation of the service.
  • FIG. 5 is a schematic flow chart of a fault handling process in accordance with another embodiment of the present invention.
  • the first mobility management network element and the second mobility management network element associated with the ISR determine that the service gateway failure determines that the service gateway is faulty, and the context of the user equipment that serves the service gateway service is saved, when the first mobility management network
  • the first mobility management network element or the second mobility management network element receives the service request message sent by the user, the first mobility management network element or the second mobility management network element performs a service recovery process of the user equipment to ensure the service Work properly.
  • the UE sends a service request (Service Request) message to the MME or the SGSN. Specifically, if the UE camps on the E-UTRAN, the UE sends a Service Request message to the MME. If the UE resides in the UTRAN, Then the UE sends a Service Request message to the SGSN.
  • Service Request Service Request
  • the MME/SGSN receives the service request message sent by the UE, and confirms whether there is a corresponding context according to the user identification information (for example, S-TMSI, etc.) in the service request message, if yes (ie, locates the context), The process of subsequent service recovery is triggered; otherwise, the MME/SGSN rejects the service request message or discards the service request message.
  • the user identification information for example, S-TMSI, etc.
  • the two mobile management network elements MME and SGSN associated with the ISR in 501 can save the context of the UE, and ensure that the UE resides at any connection.
  • the mobility management network element ie, MME or SGSN
  • corresponding to the UE entering the network may identify the service request message of the UE.
  • the MME/SGSN performs a service gateway migration (SGW relocation) process.
  • SGW relocation The specific implementation manner of the service gateway migration process is described in step 306.
  • the network connection of the user equipment is re-established by performing a service gateway migration process.
  • the MME/SGSN performs global unique temporary identity re-allocation (GUTI) Reallocation) or packet Temporary Mobile User Identity Reassignment (P-TMSI Reallocation) process.
  • GUI global unique temporary identity re-allocation
  • P-TMSI Reallocation packet Temporary Mobile User Identity Reassignment
  • the specific implementation manner of the MME/SGSN performing the globally unique temporary identity re-allocation or the packet temporary mobile user identity re-allocation process is described in step 307.
  • the MME/SGSN performs a global unique temporary identity re-allocation or a packet temporary mobile subscriber identity reallocation process to enable the user equipment to initiate a tracking area update procedure or a tracking area update procedure.
  • the UE performs a tracking area update process or a tracking area update process.
  • the specific implementation manner of the tracking area update process or the tracking area update process is performed by the UE, as described in step 308.
  • the MME/SGSN instructs the selected serving gateway (ie, selected in step 503) and/or the user equipment ISR to be deactivated (ie, does not indicate ISR activation) through the tracking area update procedure or the tracking area update procedure. .
  • Step 506 The MME/SGSN sends a request message to the SGSN/MME associated with the ISR, indicating that the ISR is deactivated.
  • the step 506 is an optional step, and the request message causes the ISR-related SGSN/MME to delete the context of the saved user equipment. If the request message is not received, the SGSN/MME may wait for the context of the saved user equipment to be deleted after the timer expires in step 501.
  • 506 in Fig. 5 is shown to be executed after 505, the embodiment of the present invention is not limited thereto. 506 can also be executed concurrently with 505, or prior to 505.
  • the first mobility management network element and the second mobility management network element associated with the ISR determine that the service gateway fault determines that the service gateway is faulty, and the context of the user equipment served by the serving gateway is saved, when the first mobility management network element
  • the second mobility management network element receives the service request message sent by the user equipment, the first mobility management network element or the second mobility management network element performs a service recovery process of the user equipment to ensure normal service. get on.
  • FIG. 6 is a schematic flow chart of a fault handling process in accordance with another embodiment of the present invention.
  • the first mobility management network element and the second mobility management network element associated with the ISR determine that the service gateway failure determines that the service gateway is faulty, and the context of the user equipment that serves the service gateway service is saved, when the first mobility management network
  • the first mobility management network element or the second mobility management network element performs the service of the user equipment.
  • the recovery process ensures the normal operation of the business.
  • the UE sends a tracking area update request to the MME or the SGSN. Request, TAU Request) / Routing Area Update Request (RAU Request) message.
  • the UE if the UE camps on the E-UTRAN, the UE sends a TAU request message to the MME; if the UE camps on the UTRAN/GERAN, the UE sends a RAU request message to the SGSN.
  • the MME/SGSN receives the TAU/RAU request message sent by the UE, and confirms whether there is a corresponding context according to the user identification information (for example, GUTI, etc.) in the TAU/RAU request message, if yes (ie, locates the context) Then, the flow of subsequent service recovery is triggered; otherwise, the MME/SGSN rejects the TAU/RAU request message or discards the TAU/RAU request message.
  • the user identification information for example, GUTI, etc.
  • the two mobile management network elements MME and SGSN associated with the ISR in 601 can save the context of the UE, and ensure the mobility management network element (ie, the MME or the UE corresponding to the UE that resides in any access network)
  • the SGSN can identify the TAU/RAU request message of the UE.
  • the MME/SGSN performs a service gateway migration process.
  • step 306 The specific implementation manner of the service gateway migration process is described in step 306.
  • the network connection of the user equipment is re-established by performing a service gateway migration process.
  • the MME/SGSN sends a request message to the SGSN/MME associated with the ISR, indicating that the ISR is deactivated.
  • the step 604 is an optional step, and the request message is related to the ISR.
  • the SGSN/MME deletes the context of the saved user equipment. If the request message is not received, the SGSN/MME may wait for the context of the saved user equipment to be deleted after the timer expires in step 601.
  • the MME/SGSN sends a tracking area update/tracking area update request accept message to the UE, indicating that the ISR is deactivated (ie, does not indicate ISR activation).
  • the MME/SGSN indicates that the UE ISR is deactivated, and the method further includes: the MME/SGSN indicating that the serving gateway ISR is deactivated (ie, not ISR activated).
  • the MME/SGSN may indicate in the serving gateway migration process of step 603, for example, indicating that the ISR is deactivated in the MME/SGSN sending a create session request message to the SGW; or, may be indicated in other steps, for example, The MME/SGSN sends an Modify Bearer Request message to the SGW to indicate that the ISR is deactivated.
  • the first mobility management network element and the second mobility management network element associated with the ISR determine that the service gateway fault determines that the service gateway is faulty, and the context of the user equipment served by the serving gateway is saved, when the first mobility management network element
  • the second mobility management network element receives the tracking area update request or the routing area update request message sent by the user equipment, the first mobility management network element or the second mobility management network element performs service recovery of the user equipment. The process ensures the normal operation of the business.
  • the mobility management network element obtains a trigger of the user equipment to reestablish the network connection of the user equipment.
  • the MME/SGSN learns that the SGW is faulty.
  • the UE sends a non-access stratum request message to the MME or the SGSN.
  • the non-access stratum request message may include, but is not limited to, the following message: a Tracking Area Update Request (TAU Request) or a Routing Area Update Request (RAU Request) Monthly Service Request message.
  • TAU Request Tracking Area Update Request
  • RAU Request Routing Area Update Request
  • the MME/SGSN receives the non-access stratum request message sent by the UE, and confirms whether there is a corresponding context according to the user identifier information (such as GUTI or S-TMSI, etc.) in the non-access stratum request message, if any (ie, locating to the context), it is determined that a non-access stratum request message related to the context of the saved user equipment is received, thereby triggering a flow of subsequent service recovery.
  • the user identifier information such as GUTI or S-TMSI, etc.
  • the two mobile management network elements MME and SGSN associated with the ISR in 701 can save the context of the UE, and ensure that the UE resides at any connection.
  • the mobility management network element ie, MME or SGSN
  • corresponding to the UE entering the network may identify the non-access stratum request message of the UE.
  • the MME/SGSN sends a non-access stratum reject message to the UE.
  • the MME/SGSN sends a tracking area update rejection/routing area update rejection/service rejection message to the UE, and triggers the UE to perform an attach procedure.
  • the tracking area update rejection/routing area update rejection/service rejection message may carry an existing cause value, such as #10 (Implicitly detached), or may be a new cause value (for example, SGW Failure). This embodiment does not limit this.
  • the UE performs an attach procedure.
  • step 405. In the attachment process,
  • the UE sends an attach request message to the MME/SGSN (not limited to the MME/SGSN in step 701), And a new PGW (not limited to the served packet data network gateway in step 701) and establishing a network connection for the user equipment.
  • the first mobility management network element and the second mobility management network element associated with the ISR determine that the service gateway fault determines that the service gateway is faulty, and the context of the user equipment served by the serving gateway is saved, when the first mobility management network element
  • the second mobility management network element receives the tracking area update request or the routing area update request or the service request message sent by the user equipment, the first mobility management network element or the second mobility management network element executes the user equipment.
  • the process of business recovery ensures the normal operation of the business.
  • FIG. 8 is a block diagram of a mobility management network element in accordance with an embodiment of the present invention.
  • An example of 80 is the first mobility management network element or the second mobility management network element (e.g., MME or SGSN), and includes a determining unit 81, a storage unit 82, a receiving unit 83, and a restoring unit 84.
  • the determining unit 81, the receiving unit 83, and the restoring unit 84 may be implemented by a processor, and the storage unit 82 may be implemented by a memory.
  • the mobility management network element 80 is associated with another mobility management network element.
  • the determining unit 81 determines that the service gateway is faulty.
  • the storage unit 82 saves the context of the user equipment of the service gateway service when the determining unit 81 determines that the service gateway is faulty.
  • the receiving unit 83 receives the trigger.
  • the recovery unit 84 performs a flow of service recovery of the user equipment when the receiving unit 83 receives the trigger.
  • the service management network element associated with the ISR determines the service gateway failure, and the context of the user equipment associated with the service gateway is saved.
  • the mobile management network element receives the trigger from other network elements or user equipments on the network side, The mobile management network element performs a service recovery process to ensure normal operation of the service.
  • the trigger may be a notification message sent by the packet data network gateway or the serving gateway, or a notification message sent by another mobility management network element, or a tracking area update request sent by the user equipment. Or a routing area update request or a service request message.
  • the receiving unit 83 receives the notification message sent by the packet data network gateway or the serving gateway, or the notification message sent by the another mobility management network element, or receives the tracking area update request sent by the user equipment or Routing area update request or service request message.
  • the recovery unit 84 is specifically configured to perform a network connection re-establishment process, or trigger a user equipment to initiate an attach procedure.
  • the mobile management network element 90 of FIG. 9 further includes a redistribution unit 91, a first indicating unit 92, or a second indicating unit 93.
  • the redistribution unit 91, the first indication unit 92, or the second indication unit 93 may be implemented by a processor.
  • the recovery unit 84 may perform the network. Connection rebuild message. Specifically, the recovery unit 84 sends a paging message to the user equipment, receives a service request procedure sent by the user equipment, and performs a service gateway migration procedure.
  • the restoring unit 84 may perform a network connection re-establishment process. Specifically, the recovery unit 84 performs a service gateway migration process.
  • the redistribution unit 91 may perform a global unique temporary identity re-allocation GUTI or a packet temporary mobile subscriber identity P-TMSI reallocation procedure after the receiving unit 83 receives the service request message sent by the user equipment, so that the user equipment performs the tracking area.
  • the update or routing area update process deactivates the ISR.
  • the restoring unit 84 may perform a network connection re-establishment process. Specifically, the recovery unit 84 performs a service gateway migration process.
  • the first indication unit 92 instructs the user equipment to perform ISR deactivation, and/or instructs the serving gateway to perform ISR deactivation.
  • the recovery unit 84 when performing the service gateway migration process, may select a service gateway and send a create session request message to the selected service gateway to cause the selected service gateway to send a modify bearer request message to the packet data network gateway.
  • the recovery unit 84 may trigger the The user equipment initiates an attach procedure.
  • the recovery unit 84 may trigger the The user equipment initiates an attach procedure.
  • the device sends a paging message carrying the IMSI of the user equipment to the user equipment, so that the user equipment initiates an attach procedure.
  • the recovery unit 84 is touchable.
  • the user equipment initiates an attach procedure.
  • the recovery unit 84 sends a service rejection or tracking area update rejection or routing area update message to the user equipment, so that the user equipment initiates an attach procedure.
  • the notification message received by the receiving unit 84 may carry the international mobile subscriber identity of the user equipment.
  • the notification message may also include a bearer identity, an access point name APN, a quality of service level flag QCI, and/or an allocation hold priority ARP.
  • the second indication unit 93 instructs another mobility management network element to perform ISR deactivation.
  • the various portions of the mobility management network elements 80 and 90 may perform the various processes of the methods of Figures 2-7 above, and are not repeated herein to avoid redundancy.
  • a communication system may include a first mobility management network element and a second mobility management network element associated with the above ISR.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. You can choose some of them according to actual needs or All units are used to achieve the objectives of the solution of this embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

Abstract

L'invention concerne un procédé de traitement de restauration de service et un élément de réseau de gestion de mobilité dans une scène de réduction de signalisation en mode de veille (ISR). Le procédé comprend les étapes suivantes : le premier élément de réseau de gestion de mobilité et le second élément de réseau de gestion de mobilité qui sont associés à l'ISR déterminent qu'une passerelle de desserte est défaillante, ledit premier élément de réseau de gestion de mobilité et ledit second élément de réseau de gestion de mobilité sauvegardent le contexte de l'équipement d'utilisateur dudit service de passerelle de desserte ; ledit premier élément de réseau de gestion de mobilité ou ledit second élément de réseau de gestion de mobilité reçoit un déclencheur et dirige le processus de restauration de service de l'équipement d'utilisateur. Les modes de réalisation de l'invention permettent aux deux éléments de réseau de gestion de mobilité associés à l'ISR de déterminer que la passerelle de desserte est défaillante et de sauvegarder le contexte de l'équipement d'utilisateur associé à la passerelle de desserte, et lorsque l'élément de réseau de gestion de mobilité reçoit le déclencheur d'autres éléments de réseaux ou d'autres équipements d'utilisateur du côté réseau, l'élément de réseau de gestion de mobilité dirige le processus de restauration de service, ce qui garantit le fonctionnement normal du service.
PCT/CN2011/075249 2011-06-03 2011-06-03 Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité WO2011157166A2 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2011/075249 WO2011157166A2 (fr) 2011-06-03 2011-06-03 Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité
EP11795132.7A EP2706810A4 (fr) 2011-06-03 2011-06-03 Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité
CN201180001085XA CN102918918A (zh) 2011-06-03 2011-06-03 业务恢复的处理方法及移动管理网元
US14/085,446 US9143997B2 (en) 2011-06-03 2013-11-20 Service restoration processing method and mobility management network element

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/075249 WO2011157166A2 (fr) 2011-06-03 2011-06-03 Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/085,446 Continuation US9143997B2 (en) 2011-06-03 2013-11-20 Service restoration processing method and mobility management network element

Publications (2)

Publication Number Publication Date
WO2011157166A2 true WO2011157166A2 (fr) 2011-12-22
WO2011157166A3 WO2011157166A3 (fr) 2012-05-03

Family

ID=45348631

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/075249 WO2011157166A2 (fr) 2011-06-03 2011-06-03 Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité

Country Status (4)

Country Link
US (1) US9143997B2 (fr)
EP (1) EP2706810A4 (fr)
CN (1) CN102918918A (fr)
WO (1) WO2011157166A2 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014187478A1 (fr) * 2013-05-22 2014-11-27 Nokia Solutions And Networks Oy Pistage de dérangements dans un système de télécommunications
US9532331B2 (en) * 2012-10-12 2016-12-27 Cisco Technology, Inc. System and method for reducing paging in UTRAN/GERAN/E-UTRAN networks when idle signaling reduction is active
CN108307540A (zh) * 2016-09-22 2018-07-20 普天信息技术有限公司 一种服务网关重启后用户设备业务的快速恢复方法
CN110944331A (zh) * 2017-04-28 2020-03-31 Oppo广东移动通信有限公司 获取上下文配置信息的方法、终端设备和接入网设备
CN111246527A (zh) * 2015-08-17 2020-06-05 华为技术有限公司 一种更新用户面网关的方法及装置
CN113891385A (zh) * 2021-10-29 2022-01-04 中国联合网络通信集团有限公司 网络设备的链路状态的检测方法、装置及设备

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2706810A4 (fr) * 2011-06-03 2014-11-12 Huawei Tech Co Ltd Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité
EP2742705B1 (fr) * 2011-08-12 2018-10-10 LG Electronics Inc. Procédé permettant de traiter des données associées à une réduction de la signalisation dans un système de communication sans fil
US9820327B2 (en) * 2012-10-15 2017-11-14 Nokia Technologies Oy Re-attaching to the network after reception of a service reject at a user equipment in response to a service request
CN103338525B (zh) * 2013-06-26 2017-12-29 华为技术有限公司 一种网络连接重建方法、相关设备及系统
CN104661205B (zh) * 2013-11-22 2019-12-03 中兴通讯股份有限公司 一种网关更新信息通知方法及控制器
KR102412234B1 (ko) * 2014-05-08 2022-06-23 인터디지탈 패튼 홀딩스, 인크 Ｕｅ를 전용 코어 네트워크 노드에 리디렉트하기 위한 방법들 및 이동성 관리 엔티티(ｍｍｅ)
RU2666633C2 (ru) 2014-06-30 2018-09-11 Хуавэй Текнолоджиз Ко., Лтд. Способ повторного установления pdn-соединения, центральный сервер сброса, элемент сети управления мобильностью и шлюз передачи данных
US10085196B1 (en) * 2014-07-03 2018-09-25 Sprint Communications Company L.P. Wireless communication control based on border gateway protocol
US10637834B2 (en) * 2015-07-12 2020-04-28 Qualcomm Incorporated Network architecture and security with simplified mobility procedure
PT3509337T (pt) * 2015-08-14 2021-08-02 Ericsson Telefon Ab L M Nó e método para gestão de uma ligação de rede de dados em pacotes
WO2017169281A1 (fr) * 2016-03-29 2017-10-05 株式会社Ｎｔｔドコモ Procédé de mise à jour de listes d'identités de zones de suivi
CN109997379B (zh) * 2016-11-07 2021-11-30 Lg电子株式会社 用于管理会话的方法
CN111386742B (zh) 2018-10-17 2023-09-29 联发科技（新加坡）私人有限公司 改进全球唯一临时标识分配的方法及用户设备
US20220019380A1 (en) * 2018-11-19 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Methods providing network service restoration context and related service instance sets and storage resource nodes
CN112532403B (zh) * 2019-09-17 2023-08-08 中盈优创资讯科技有限公司 网元适配的驱动服务装置、网元适配方法及系统
US11563627B2 (en) * 2019-11-08 2023-01-24 Verizon Patent And Licensing Inc. Remote probing for failover
CN112954664B (zh) * 2019-12-10 2022-07-12 华为技术有限公司 一种数据处理方法、装置及系统
CN111417163B (zh) * 2020-03-27 2022-05-20 Oppo广东移动通信有限公司 一种ip地址恢复方法及终端、存储介质
CN115150857A (zh) * 2021-03-31 2022-10-04 华为技术有限公司 网关故障恢复方法、系统及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070165573A1 (en) * 2006-01-19 2007-07-19 Hannu Hietalahti Mobility Management with Controlled Use of New Reject Causes
CN101448294B (zh) * 2008-01-21 2011-05-04 华为技术有限公司 网络资源释放处理的方法及设备
CN101541097B (zh) * 2008-03-19 2013-04-17 华为技术有限公司 恢复承载的方法、装置及系统
US8477724B2 (en) * 2010-01-11 2013-07-02 Research In Motion Limited System and method for enabling session context continuity of local service availability in local cellular coverage
WO2011134108A1 (fr) * 2010-04-27 2011-11-03 Nokia Siemens Networks Oy Procédé de détermination d'une défaillance de liaison radio associée au transfert intercellulaire d'un équipement utilisateur entre un nœud d'accès émetteur et un nœud d'accès récepteur, nœud d'accès pour la détermination d'une défaillance de liaison radio associée au transfert intercellulaire d'un équipement utilisateur entre un nœud d'accès émetteur et un nœud d'accès récepteur, et équipement utilisateur
EP2706810A4 (fr) * 2011-06-03 2014-11-12 Huawei Tech Co Ltd Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None
See also references of EP2706810A4

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9532331B2 (en) * 2012-10-12 2016-12-27 Cisco Technology, Inc. System and method for reducing paging in UTRAN/GERAN/E-UTRAN networks when idle signaling reduction is active
WO2014187478A1 (fr) * 2013-05-22 2014-11-27 Nokia Solutions And Networks Oy Pistage de dérangements dans un système de télécommunications
US10140169B2 (en) 2013-05-22 2018-11-27 Nokia Solutions And Networks Oy Fault tracking in a telecommunications system
CN111246527A (zh) * 2015-08-17 2020-06-05 华为技术有限公司 一种更新用户面网关的方法及装置
CN111246527B (zh) * 2015-08-17 2023-11-17 华为技术有限公司 一种更新用户面网关的方法及装置
CN108307540A (zh) * 2016-09-22 2018-07-20 普天信息技术有限公司 一种服务网关重启后用户设备业务的快速恢复方法
CN110944331A (zh) * 2017-04-28 2020-03-31 Oppo广东移动通信有限公司 获取上下文配置信息的方法、终端设备和接入网设备
CN113891385A (zh) * 2021-10-29 2022-01-04 中国联合网络通信集团有限公司 网络设备的链路状态的检测方法、装置及设备
CN113891385B (zh) * 2021-10-29 2023-10-31 中国联合网络通信集团有限公司 网络设备的链路状态的检测方法、装置及设备

Also Published As

Publication number Publication date
WO2011157166A3 (fr) 2012-05-03
CN102918918A (zh) 2013-02-06
EP2706810A2 (fr) 2014-03-12
EP2706810A4 (fr) 2014-11-12
US20140078890A1 (en) 2014-03-20
US9143997B2 (en) 2015-09-22

Similar Documents

Publication Publication Date Title
WO2011157166A2 (fr) Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité
RU2749750C1 (ru) Управление разрывом услуги для беспроводного устройства
US10666555B2 (en) Method and apparatus for relocating and restoring connections through a failed serving gateway and traffic offloading
US11089542B2 (en) Terminal apparatus, base station apparatus, mobility management entity (MME), and communication control method
US9930611B2 (en) Network selection method and core network device
KR101802005B1 (ko) 장애가 생긴 서빙 게이트웨이를 통한 접속의 재배치 및 복구 및 트래픽 오프로딩을 위한 방법 및 장치
US11083043B2 (en) Method and system for user equipment (UE) registration
DK2702793T3 (en) Improvements to completed mobile calls
US9143990B2 (en) Method and device for handling failure of mobility management device in ISR activated scenario
US8855045B2 (en) Method and system for controlling establishment of local IP access
JP6368859B2 (ja) Ｐｄｎ接続再確立方法、リセット中央サーバ、モビリティ管理ネットワーク要素、およびデータゲートウェイ
US8582503B2 (en) Method for indicating the bearer management of a serving gateway
WO2009140919A1 (fr) Procédé, dispositif et système de tolérance aux accidents basée sur des passerelles de paquets sans fil
US10652946B2 (en) Method and nodes for handling bearers
WO2013139235A1 (fr) Procédé et dispositif de radiomessagerie
WO2012071695A1 (fr) Procédé, système et dispositif associé de traitement de panne de nœud
US20220345997A1 (en) User equipment and core network apparatus
US20220295279A1 (en) User equipment, intra-core network apparatus, and communication control method
US20220256450A1 (en) User equipment, intra-core network apparatus, and communication control method
WO2013104111A1 (fr) Procédé pour le rétablissement d'un service et élément de réseau de gestion de la mobilité
WO2017028637A1 (fr) Procédé et dispositif de traitement destinés à la récupération de passerelle
US20190335413A1 (en) Terminal apparatus, core network apparatus, and communication control method
WO2012103773A1 (fr) Procédé de régulation de surcharge et système de système de relais
WO2016019559A1 (fr) Appareil, système, et procédé d'identification d'équipement d'utilisateur de réseau partagé
WO2010048881A1 (fr) Procédé, appareil et système pour une connexion de service d'utilisateur pendant une panne de réseau

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180001085.X

Country of ref document: CN

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

Ref document number: 11795132

Country of ref document: EP

Kind code of ref document: A2

ENP Entry into the national phase

Ref document number: 2013/1961

Country of ref document: KE

WWE Wipo information: entry into national phase

Ref document number: 2011795132

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE