WO2011110013A1 - Procédé, dispositif de réseau et système de réseau pour le traitement de défaillance d'élément de réseau de gestion de mobilité - Google Patents

Procédé, dispositif de réseau et système de réseau pour le traitement de défaillance d'élément de réseau de gestion de mobilité Download PDF

Info

Publication number
WO2011110013A1
WO2011110013A1 PCT/CN2010/076597 CN2010076597W WO2011110013A1 WO 2011110013 A1 WO2011110013 A1 WO 2011110013A1 CN 2010076597 W CN2010076597 W CN 2010076597W WO 2011110013 A1 WO2011110013 A1 WO 2011110013A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
network element
mobility management
management network
reserved
Prior art date
Application number
PCT/CN2010/076597
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 华为技术有限公司
Priority to PCT/CN2010/076597 priority Critical patent/WO2011110013A1/fr
Priority to CN2010800019084A priority patent/CN102318384A/zh
Publication of WO2011110013A1 publication Critical patent/WO2011110013A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
    • 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 technologies, and in particular, to a method for processing a fault of a mobility management network element, a network device, and a network system.
  • LTE Long Term Evolution
  • EPS evolved packet system
  • the EPS can provide IP connectivity through the Evolved UMTS Territorial Radio Access Network (E-UTRAN).
  • the core network of EPS mainly includes the Mobile Management Entity (MME) and the Serving Gateway (Serving Gateway). , S-GW), packet data network gateway (P-GW) three logical functions, wherein the MME is responsible for non-access layer (Non Access, NAS) signaling encryption and roaming, tracking and other functions, Assign user temporary IDs, security features, and more.
  • the S-GW is responsible for local mobility anchors and mobility anchors within the 3GPP system, as well as packet routing and forwarding.
  • the P-GW is responsible for UE IP address allocation, accounting, and policy enforcement.
  • the MME fails, for example, the MME restarts (RESTART), the eNodeB and the S-GW notify the MME to restart, and the bearer of the UE served by the MME is released, so that the UE served by the MME cannot perform any service.
  • the MME restarts (RESTART)
  • the eNodeB and the S-GW notify the MME to restart, and the bearer of the UE served by the MME is released, so that the UE served by the MME cannot perform any service.
  • the embodiment of the present invention provides a method for processing a fault of a mobility management entity, a network device, and a network system.
  • the mobility management network element fails, the bearer of the UE is reserved, so that the UE can perform corresponding services.
  • a method for processing a fault of a mobility management network element including:
  • the parameter of the bearer is a parameter corresponding to the attribute parameter of the bearer of the UE.
  • a method for processing a fault of a mobility management network element including:
  • the mobility management network element determines that the value of the attribute parameter of the bearer of the UE matches the value of the bearer parameter to be reserved when the mobility management network element is set in the bearer processing policy, and sends the value to the access network element or the serving gateway. And indicating the information, so that the access network element or the serving gateway reserves the bearer of the UE according to the indication information when the mobility management network element is faulty, and the mobility management network element configured in the bearer processing policy is faulty.
  • the parameter of the bearer to be reserved is a parameter corresponding to the attribute parameter of the bearer of the UE.
  • a method for processing a fault of a mobility management network element including:
  • the priority of the mobility management network element UE determines that all bearers of the UE need to be reserved when the mobility management network element fails;
  • the mobility management network element sends the indication information to the access network element or the serving gateway, so that the access network element or the serving gateway reserves the UE according to the indication information when the mobility management network element fails All bear.
  • a network element device including:
  • a fault determining unit configured to determine whether the mobility management network element is faulty
  • a bearer determining unit configured to determine, when the determination result of the fault determining unit is yes, the value of the attribute parameter of the bearer served by the faulty mobility management network element and the mobility management network element fault set in the bearer processing policy Whether the value of the bearer parameter to be reserved is matched, and the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy is a parameter corresponding to the attribute parameter of the bearer of the UE;
  • a bearer processing unit configured to reserve, when the determination result of the bearer determining unit is yes, retain the bearer of the UE.
  • a mobility management network element including:
  • a determining unit configured to determine whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer that needs to be retained when the mobility management network element is set in the bearer processing policy, and the mobility set in the bearer processing policy
  • the parameters of the bearer to be reserved when the network element fails to be managed and the bearer of the UE
  • the attribute parameter is the corresponding parameter
  • a sending unit configured to send, to the access network element or the serving gateway, the indication information when the determining result of the determining unit is yes, so that the access network element or the serving gateway is configured according to the fault when the mobility management network element fails
  • the indication information retains the bearer of the UE.
  • a mobility management network element including:
  • a determining unit configured to determine, according to a priority of the UE, whether to retain all bearers of the UE when the mobility management network element fails;
  • a sending unit configured to send, to the access network element or the serving gateway, the indication information when the determining result of the determining unit is yes, so that the access network element or the serving gateway is configured according to the fault when the mobility management network element fails
  • the indication information retains all bearers of the UE.
  • a network system comprising: a mobility management network element, an access network element, and a service gateway, where the mobility management network element is configured to determine the value of the attribute parameter of the bearer of the UE and the mobility set in the bearer processing policy
  • the indication information is sent to the access network element or the serving gateway, so that the access network element or the serving gateway fails when the mobility management network element fails.
  • the bearer of the UE is reserved according to the indication information, and the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy is a parameter corresponding to the attribute parameter of the bearer of the UE;
  • the access network element is configured to receive the indication information, and when the mobility management network element is faulty, retain the bearer of the UE according to the indication information;
  • the serving gateway is configured to receive the indication information, and when the mobility management network element fails, retain the bearer of the UE according to the indication information.
  • a network system comprising: a mobility management network element, an access network element, and a service gateway, where the mobility management network element is used for a priority of the UE, and determines that the mobility management network element needs to be reserved when the network element fails All the bearers of the UE are sent; the indication information is sent to the access network element and the serving gateway, so that the access network element or the serving gateway reserves all the UEs according to the indication information when the mobility management network element fails Carry
  • the access network element is configured to receive the indication information, and when the mobility management network element is faulty, retain all bearers of the UE according to the indication information;
  • a service gateway configured to receive the indication information, when the mobility management network element fails, according to The indication information retains all bearers of the UE.
  • a network system comprising: a mobility management network element, an access network element, and a service gateway, where the access network element is configured to determine the faulty mobility management network element when the mobility management network element fails When the value of the attribute parameter of the served UE matches the value of the bearer parameter to be reserved when the mobility management network element is set in the bearer processing policy, the bearer of the UE is reserved; the service gateway is used for When the mobility management network element is faulty, determining the value of the attribute parameter of the bearer of the UE served by the faulty mobility management network element and the bearer to be retained when the mobility management network element is set in the bearer processing policy When the value of the parameter is matched, the bearer of the UE is reserved; where the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy corresponds to the attribute parameter of the bearer of the UE. parameter.
  • An embodiment of the present invention determines whether a bearer needs to be reserved when a mobility management network element fails, by determining whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer that is set in the bearer processing policy, so that when the mobility is changed, When the management network element fails, the UE can also perform services corresponding to the reserved bearers, thereby improving the user experience.
  • the mobility management network element determines whether all the bearers of the UE need to be reserved when the mobility management network element fails according to the priority of a certain UE, and notifies the access network element or the service gateway to enable the connection.
  • the inbound network element or the serving gateway may retain all the bearers of some UEs, so that the high-priority UE can perform services when the mobility management network element fails.
  • Figure 1 is a 3GPP network architecture diagram
  • FIG. 2 is a method for processing a fault of a mobility management network element according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for processing a fault of a mobility management network element according to another embodiment of the present invention
  • FIG. 4 is a flowchart of a method for processing a fault of a mobility management network element according to another embodiment of the present invention
  • FIG. 6 is a flowchart of a method for restarting an SGSN when a UE accesses a core network through a UTRAN according to an embodiment of the present invention
  • FIG. 7 is a structural diagram of a processing network device for a mobility management network element failure according to an embodiment of the present invention.
  • FIG. 8 is a structural diagram of a mobility management network element according to an embodiment of the present invention.
  • FIG. 9 is a structural diagram of another mobility management network element according to an embodiment of the present invention.
  • FIG. 10 is a structural diagram of a network system according to an embodiment of the present invention.
  • FIG. 11 is a structural diagram of another network system according to an embodiment of the present invention.
  • FIG. 12 is a structural diagram of still another network system according to an embodiment of the present invention.
  • the UE can pass the evolved UMTS terrestrial land.
  • the Evolved UMTS Territorial Radio Access Network (E-UTRAN) connects to the core network, and can also connect to the core network through the UMTS Terrestrial Radio Access Network (UTRAN), or through the enhanced data rate GSM evolution.
  • a GSM EDGE Radio Access Network (GERAN) is connected to the core network.
  • the E-UTRAN access network includes an evolved base station eNodeB.
  • the UTRAN or GERAN access network includes a Radio Network Controller (RNC).
  • RNC Radio Network Controller
  • the core network When the UE accesses from the E-UTRAN, the core network includes the MME, the S-GW, and the P-GW; when the UE accesses from the UTRAN or the GERAN, the core network includes a Serving GPRS Support Node (SGSN), S-GW and P-GW; interface connection between network elements in the 3GPP network structure, as shown in Figure 1, here No longer.
  • SGSN Serving GPRS Support Node
  • S-GW Serving GPRS Support Node
  • an embodiment of the present invention provides a method for processing a fault of a mobility management network element.
  • the execution body of each step of the method may be an access network element or an S-GW.
  • the access network element is an eNodeB; when the UE accesses through the UTRAN, the access network element is an RNC.
  • the method describes how to determine whether the access network element or the serving gateway determines whether to retain the bearer or release the bearer when determining the fault of the mobility management network element.
  • the method specifically includes: 201. Determine that the mobility management network element is faulty.
  • the mobility management network element in this embodiment is an MME or an SGSN.
  • the execution subject when the execution subject is an S-GW, it may be determined whether the mobility management network element is faulty by detecting a restart counter in the probe response Echo Response message sent by the mobility management network element;
  • the access network element may determine whether the mobility management network element is faulty by detecting whether the reset message sent by the mobility management network element is received.
  • the mobility management network element failure may refer to a mobility management network element restart or other failure.
  • the bearer of the UE When the value of the attribute parameter of the bearer of the UE served by the mobility management network element that determines the fault is matched with the value of the parameter of the bearer that needs to be reserved when the mobility management network element is set in the bearer processing policy, The bearer of the UE; or the value of the bearer's attribute parameter of the UE served by the faulty mobility management network element and the bearer parameter to be reserved when the mobility management network element is set in the bearer processing policy If the value does not match, the bearer of the UE is released, where the parameter of the bearer to be reserved when the mobility management network element fails in the bearer processing policy is a parameter corresponding to the attribute parameter of the bearer of the UE.
  • the QoS Class Identifier (QCI), the Allocation and Retention Priority (AP), and the access point name (Access) of the bearer of the UE served by the faulty mobility management network element are determined. Whether the value of at least one parameter in the Point Name, APN is matched with the value of the parameter of the bearer to be reserved when the mobility management NE is set in the bearer processing policy.
  • the QCI, the AP, or the APN may be included in the bearer processing policy, for example, the QCI is equal to 5, the AP is greater than or equal to 8 and less than or equal to 10, or the APN is greater than 12; when the mobility management network element fails, the fault is determined.
  • the attribute parameter of the bearer of the served UE of the mobility management network element if the QCI is equal to 5, retains the bearer, and if the AP is equal to 20, the bearer is not retained.
  • At least two of QCI, ARP, and APN may be included, for example, QCI is equal to 5, AP is greater than or equal to 8 and less than or equal to 10, and APN is greater than at least two of 12;
  • QCI is equal to 5
  • AP is greater than or equal to 8 and less than or equal to 10
  • APN is greater than at least two of 12;
  • the attribute parameter of the bearer of the served UE of the mobility management network element of the fault is determined. If the QCI is equal to 5 and the AP is equal to 8, the bearer is reserved, if the attribute parameter of the bearer of the UE, for example, the AP is equal to 9.
  • the parameter of the bearer to be reserved when the mobility management network element fails in the bearer processing policy is a parameter corresponding to the attribute parameter of the bearer of the UE, and specifically:
  • the parameter of the bearer to be reserved when the mobility management network element in the bearer policy parameter is faulty is QCI, compare whether the QCI in the attribute parameter of the bearer of the UE matches; or
  • the mobility management NE in the bearer policy parameter fails, the parameters of the bearer to be reserved are
  • RAP and APN it is compared with whether the RAP and APN in the attribute parameters of the UE bearer match, and so on.
  • the value of the attribute parameter of the bearer of the UE served by the faulty mobility management network element is equal to the value of the parameter of the bearer that needs to be reserved when the mobility management network element is set in the bearer processing policy;
  • the value of the attribute parameter of the bearer of the UE served by the faulty mobility management network element is within the value range of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy.
  • the restart of the mobility management entity will cause the access network element to release the RRC connection with the UE, thereby causing service interruption of the UE being executed. Since the UE cannot sense that the mobility management entity has restarted, a process of re-establishing the connection is initiated to attempt to re-establish a connection with the network side and resume the service, for example, sending a service request Service Request message to the restarted mobility management entity. The restarted mobility management entity returns a reject message to the UE because the UE context has been lost. As a result, the UE cannot perform services for a long time.
  • the method may further include: sending a notification message to the UE when the predetermined condition for releasing the UE connection is satisfied, where the notification message is used to instruct the UE to initiate an attach procedure.
  • the condition for releasing the UE connection may be that the UE is in a static state for a predetermined period of time, for example, the UE is in a static state for a long time (for example, the UE does not perform data transmission for a long time), for example, the UE is in a static state to reach the UE.
  • Inactivity timer The time set by the UE inactivity timer, when the "UE inactivity timer” UE inactivity timer expires, the foregoing notification message is sent, and the specific predetermined duration may be set by the access network element; the UE is caused by the network coverage. Moving outside the jurisdiction of the access network element, the access network element cannot continue to provide services to the UE, and the like.
  • the notification message can be released for the connection.
  • the message is sent (for example, the RRC Connection Release message is released), and the connection release request message carries indication information for instructing the UE to initiate an attach procedure.
  • the UE when determining whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy, it is determined that the mobility management network element is faulty.
  • the bearer that needs to be reserved is determined, so that when the mobility management network element fails, the UE can also perform services corresponding to the reserved bearers, thereby improving the user experience.
  • an embodiment of the present invention provides a method for processing a fault of a mobility management network element, where the mobility management network element determines which bearers of the UE are reserved in the event of a fault, and the method includes:
  • the mobility management network element determines whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy, where the bearer processing policy moves
  • the parameters of the bearer to be reserved when the network element fails to be managed are the parameters corresponding to the attribute parameters of the bearer of the UE.
  • the mobility management network element in this embodiment is an MME or an SGSN.
  • the step may be specifically: determining a value of at least one parameter of the QCI, the allocation and retention priority AP, the access point name APN, and the bearer to be reserved when the mobility management network element is set in the bearer processing policy. Whether the values of the parameters match.
  • the method for determining whether to match may refer to the description in step 202.
  • the mobility management network element accesses the access network element or the service.
  • the gateway sends the indication information, so that the access network element or the serving gateway reserves the bearer of the UE according to the indication information when the mobility management network element fails.
  • the access network element is an eNodeB when the UE accesses through the E-UTRAN.
  • the access network element is an RNC.
  • the solution provided in this embodiment may be performed when a certain bearer of the UE is established, that is, when a certain bearer is established, the value of the currently set bearer attribute parameter and the mobility management set in the bearer processing policy are determined. Whether the value of the bearer parameter to be reserved when the network element is faulty matches, and if so, the access network element or the server gateway is notified to retain the bearer when the mobility management network element fails.
  • the mobility management network element determines that the value of the attribute parameter of the bearer of the UE is equal to the value of the parameter of the bearer that needs to be reserved when the mobility management network element is set in the bearer processing policy; or The mobility management network element determines that the value of the attribute parameter of the bearer of the UE is within the value range of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy. In the embodiment of the present invention, the mobility management network element determines the mobility by determining whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy.
  • the bearer is reserved when the network element is faulty, and the access network element or the serving gateway is notified, so that the access network element or the serving gateway retains part of the bearer of the UE when the mobility management network element fails, instead of all the bearers of the UE. All are released, so that the UE can also perform services corresponding to the reserved bearers, thereby improving the user experience.
  • an embodiment of the present invention provides a method for processing a fault of a mobility management network element, where the method includes:
  • the priority of the mobility management network element UE determines whether all bearers of the UE need to be reserved when the mobility management network element fails.
  • the mobility management network element in this embodiment is an MME or an SGSN.
  • the operator may set some VIP users as high-priority users, and in the case of mobility management failure, all the bearers of the VIP users may be preferentially reserved; for example, a certain data may be set in the subscription data. If a UE is a gold card user, the gold card user is a high priority user, and when the mobility management network element fails, all the bearers of the gold card users may be preferentially reserved.
  • the mobility management network element needs to be reserved, all the bearers of the UE need to be reserved, and send indication information to the access network element or the serving gateway, so that the access network element or the serving gateway is in the mobility.
  • the management network element is faulty, all bearers of the UE are reserved according to the indication information.
  • the access network element is an eNodeB when the UE accesses through the E-UTRAN.
  • the access network element is an RNC.
  • the solution provided by the embodiment may be performed when the bearer of the UE is established, that is, when the bearer is established, the mobility management network element is determined according to the priority of the UE in the subscription information or the priority of the UE in the bearer processing policy. Whether it is necessary to reserve all bearers of the UE when the fault occurs, and if so, notify the access network element or the server gateway to retain all bearers of the UE when the mobility management network element fails.
  • the embodiment of the present invention determines whether the mobility management network element is faulty according to the priority of a certain UE. All the bearers of the UE need to be reserved, and the access network element or the serving gateway is notified, so that the access network element or the serving gateway retains all bearers of some UEs when the mobility management network element fails, instead of all bearers of all UEs. Both are released, which enables high-priority UEs to perform services when the mobility management network element fails.
  • FIG. 5 is a flowchart of a method for processing a fault of a mobility management network element according to an embodiment of the present invention.
  • the scenario described in this embodiment is that the UE accesses through the E-UTRAN, and the UE is in a connected state and is performing a packet service.
  • the S-GW and the eNodeB can continue to reserve bearers, thereby maintaining data transmission.
  • the eNodeB may notify the UE to perform an attach procedure, so that the network can re-establish the context of the UE for the UE, and the method specifically includes:
  • the S-GW and the eNodeB learn that the MME restarts, and determine that the MME restarts.
  • the S-GW may send an Echo Request message to the MME, and the MME returns an Echo Response message to the S-GW, where the message carries a restart count restart counter, when the restart counter is 1, the S-GW determines that the MME restarts; or when the MME restarts
  • the Echo Request message is sent to the S-GW, and the message carries a restart counter.
  • the restart counter is 1, the S-GW determines that the MME restarts.
  • the S-GW may determine the UE affected by the MME restart by: the UE context saved by the S-GW includes the address information of the MME serving the UE (which may be an IP address), and when the MME restarts, S- The GW can determine which UEs the MME restarts to affect by the address information of the restarted MME and the context of each UE.
  • the MME restarts and sends a Reset message to the eNodeB.
  • the eNodeB receives the message and learns that the MME restarts.
  • the eNodeB can determine the UE affected by the MME restart by: when the UE is in the connected state, there is an S1 connection between the eNodeB and the MME serving the UE (ie, a control plane connection between the E-UTRAN and the MME), when the MME When restarting, the S1 connection between the eNodeB and the MME serving the UE is released, so the eNodeB can determine which UEs the MME restarts have an impact on.
  • the eNodeB cannot determine that the MME restart will affect the UE.
  • the S-GW and the eNodeB reserve the bearer of the UE.
  • the specific implementation manner in which the S-GW retains the bearer of the UE includes:
  • the first mode the value of the attribute parameter of the bearer processing policy and the bearer of the UE is determined by the S-GW. Determine which bearers the UE needs to keep. Specifically, the S-GW determines whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy, and if yes, determines to retain the bearer. If the bearer is determined to be released, the specific bearer processing policy may be pre-configured on the S-GW.
  • the bearer processing policy may be one of the following processing modes or a combination of the following processing modes:
  • the above QCI, A P and APN can be regarded as attribute parameters of the bearer.
  • the bearer processing policy may also be other policies formulated by the operator, and does not affect the implementation of the present invention.
  • the MME determines, according to the value of the bearer processing policy and the attribute parameter of the bearer of the UE, which bearer of the UE needs to be reserved when the MME fails. Specifically, the MME determines the value and bearer of the attribute parameter of the bearer of the UE. Whether the value of the bearer parameter to be reserved when the mobility management NE is configured in the processing policy matches, if it matches, it is determined to retain the bearer, otherwise the bearer is determined to be released, and then the S-GW is notified, wherein the bearer processing policy is It can be one of the following processing methods or a combination of the following processing methods:
  • the bearer corresponding to a specific UE is reserved, and other bearers are deleted/released.
  • the above QCI, A P and APN can be regarded as attribute parameters of the bearer.
  • the bearer processing policy may also be other policies formulated by the operator, and does not affect the implementation of the present invention.
  • the MME When a certain bearer is established, the MME sends a Create Session Request to create a session request message to the S-GW.
  • the MME determines that the bearer needs to be reserved according to the bearer processing policy, the MME carries the indication information, where the indication information is used to notify the S. -GW retains the bearer when the MME fails; MME The bearer response message may also be created by sending a Create Bearer Response carrying the indication information to the S-GW, and the S-GW is notified to reserve the bearer when the MME fails.
  • the MME may also send other messages to the S-GW to notify the S-GW of the purpose of retaining the currently established bearer.
  • the S-GW After receiving the indication information, the S-GW confirms that the bearer is retained when the MME fails, and saves the indication information. In this way, the S-GW in this step can determine which bearers of the UE need to be reserved according to the saved indication information.
  • the third mode The MME determines whether to retain all the bearers of the UE when the MME is faulty, that is, the MME determines whether to retain all the UEs when the MME fails, according to the priority of the UE in the subscription information or the priority of the UE in the bearer processing policy. Bearer, then notify the S-GW.
  • the UE when the UE is a high-priority user, it is determined that all the bearers of the UE are reserved when the MME is faulty, and when the UE is a low-priority user, it is determined that all bearers of the UE are released when the MME is faulty.
  • the MME sends a Create Session Request Create Session Request message to the S-GW.
  • the message carries the indication information, where the indication information indicates that the MME is reserved when the MME fails. All bearers of the UE.
  • the S-GW confirms that all the bearers of the UE are reserved when the MME fails, and saves the indication information, so that the S-GW in this step can determine, according to the indication information, that all bearers of the UE are reserved.
  • the specific implementation manner in which the eNodeB retains the bearer of the UE includes:
  • the eNodeB determines the bearer that the UE needs to keep according to the value of the bearer processing policy and the attribute parameter of the bearer of the UE. Specifically, the eNodeB determines whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer that needs to be reserved when the mobility management network element is set in the bearer processing policy, and if yes, determines to retain the bearer, otherwise Make sure to release the bearer.
  • the specific bearer processing policy may be pre-configured on the eNodeB or obtained from the MME. Specifically, the bearer processing policy may be one of the following processing manners or a combination of the following processing manners:
  • the above QCI, AP and APN can be regarded as attribute parameters of the bearer.
  • the bearer processing policy may also be other policies formulated by the operator, and does not affect the implementation of the present invention. If the bearer processing policy is obtained from the MME, the eNodeB can obtain the bearer processing policy from the MME in the following manner: When the eNodeB is initialized, the MME sends a bearer processing policy to the eNodeB, for example, the MME sends an SI SETUP RESPONSE message to the eNodeB, where The bearer processing policy may of course adopt other message sending bearer processing policies, which does not affect the implementation of the present invention.
  • the MME determines, according to the value of the bearer processing policy and the attribute parameter of the bearer of the UE, which bearer of the UE needs to be reserved when the MME fails. Specifically, the MME determines the value of the attribute parameter of the UE and the bearer processing. Whether the value of the bearer parameter to be reserved when the mobility management NE is set in the policy matches, if it matches, it is determined to retain the bearer, otherwise the bearer is determined to be released, and then the eNodeB is notified, where the bearer processing policy can be One way is the same and will not be described here.
  • the MME sends a bearer setup request message corresponding to the currently established bearer to the eNodeB.
  • the message carries the indication information, where the indication information indicates When the MME fails, the currently established bearer is reserved.
  • the eNodeB confirms that the bearer is reserved when the MME fails, and saves the indication information. In this way, the eNodeB in this step can determine which 7 of the UEs need to be reserved according to the saved indication information.
  • the third mode The MME determines whether to retain all the bearers of the UE when the MME is faulty, that is, the MME determines whether to retain all the UEs when the MME fails, according to the priority of the UE in the subscription information or the priority of the UE in the bearer processing policy. Host, then notify the eNodeB.
  • the MME sends a context request message to the eNodeB, where the context request message carries indication information, where the indication information indicates that when the mobility management entity fails, all bearers of the UE are reserved.
  • the eNodeB confirms that all the bearers of the UE are reserved when the MME fails, and saves the indication information. In this step, the eNodeB can determine, according to the indication information, that all bearers of the UE are reserved.
  • both the eNodeB and the S-GW may retain part of the bearer of the UE. It is assumed that the voice bearer is currently reserved. If the eNodeB and the S-GW are currently transmitting voice data, the eNodeB and the S-GW may maintain the voice bearer. Transmitting voice data does not cause interruption of the transmission of current voice data. If the eNodeB and the S-GW do not currently transmit voice data, since the voice bearer is reserved, The user equipment can re-initiate the call and other operations, and the eNodeB and the S-GW can transmit the voice data on the reserved voice bearer.
  • the eNodeB when the condition for the scheduled release of the UE is met, sends an RRC Connection Release message to the UE, where the message carries an indication message '&> indicating that the UE initiates the attach procedure.
  • the condition for releasing the UE connection may be that the UE is in a static state for a predetermined period of time, for example, the UE is in a static state for a long time (for example, the UE does not perform data transmission for a long time), and the time in the quiescent state reaches "UE inactivity timer".
  • the time when the UE inactivity timer is set, the RRC Connection Release message is sent, and the specific predetermined duration may be set by the eNodeB; or the predetermined release UE is carried by the eNodeB.
  • the eNodeB cannot continue to provide services for the UE. For example, the UE moves outside the eNodeB jurisdiction due to network coverage, which causes the eNoedB to continue to provide services for the UE.
  • the RRC Connection Release message in this step may directly notify the UE to initiate an attach procedure, for example, adding a value “Attach required” to the original release reason “Release Cause” in the message, the “Attach required”
  • the indication information is used to indicate that the UE initiates the attach procedure.
  • the message is sent to the MME to restart the MME, and the UE is triggered to initiate the attach procedure.
  • the message carries the MME restart indication "MME Restart Indication".
  • the "MME Restart Indication” is the indication information for instructing the UE to initiate the attach procedure; or the message notifying the UE that the context is lost, triggering the UE to initiate the attach procedure, for example, carrying the cell context invalidation in the message "UE Context Invalid ", then the "UE Context Invalid” is indication information indicating that the UE initiates an attach procedure.
  • the eNodeB when the predetermined condition for releasing the UE connection is met, the eNodeB sends an RRC Connection Release message to the UE, promptly notifying the UE to initiate an attach procedure, so that the UE avoids sending unnecessary re-establishment connection signaling, such as a service request Service Request message, etc. In this way, the interruption time of the UE service can be reduced, and the unnecessary re-establishment of the connection process can also be saved.
  • the UE after receiving the RRC Connection Release message, the UE initiates an attach procedure according to the indication information used in the message to instruct the UE to initiate an attach procedure.
  • the value added in the "Release Cause” can be released according to the reason in the message - "Attach” Required", directly initiates the attach process; or, according to the cell "MME Restart Indication” in the message, learns that the MME that has been registered has been restarted, initiates an attach procedure; or, according to the message "UE Context Invalid” in the message, learns the UE's The context is not available, the attach process is initiated.
  • the bearer of the UE served by the MME is reserved, and the UE is enabled to perform the related service.
  • the subsequent eNodeB sends the RRC Connection Release message to the UE
  • the connection release request is carried in the connection release request to indicate that the UE initiates the attach procedure.
  • the UE initiates an attach procedure according to the indication information, so that the network side re-establishes the context for the UE, so that the UE can avoid sending unnecessary re-establishment connection signaling, such as a service request Service Request message, etc., which can reduce the interruption of the UE service. Time, while also saving unnecessary re-establishment of the connection process.
  • FIG. 6 is a diagram showing another method for processing a mobility management network element restart according to an embodiment of the present invention.
  • the scenario described in this embodiment is that the UE accesses through the UTRAN, and the UE is in a connected state and is performing packet service.
  • the S-GW and the RNC can continue to reserve bearers, thereby maintaining data transmission.
  • the RNC may notify the UE to perform an attach process, so that the network can re-establish the context of the UE for the UE, and the method specifically includes:
  • the S-GW and the RNC learn that the SGSN restarts, and determine the UE affected by the SGSN restart. Specifically, the S-GW may send an Echo request message to the SGSN, and the SGSN returns an Echo Response message to the S-GW, where the message carries a restart counter restart counter.
  • the restart counter is 1, the S-GW determines that the SGSN is restarted; or when the SGSN restarts The Echo Request message is sent to the S-GW, and the message carries a restart counter.
  • the restart counter is 1, the S-GW determines that the SGSN is restarted.
  • the S-GW can determine the UE affected by the SGSN restart by: S-GW, when the SGSN is restarted, the S-GW can determine the SGSN restart by using the address information of the restarted SGSN and the context of each UE.
  • the UE has an impact.
  • the SGSN restarts and sends a Reset message to the RNC.
  • the RNC receives the message and learns that the SGSN is restarted.
  • the RNC may determine the UE affected by the SGSN restart by: when the UE is in the connected state, there is an Iu-PS connection between the RNC and the SGSN serving the UE (ie, a control plane connection between the UTRAN and the SGSN), when the SGSN When restarting, the Iu-PS connection is released, so the RNC can determine which UEs the SGSN restarts will affect.
  • the S-GW and the RNC reserve the bearer of the UE.
  • the specific implementation manner in which the S-GW retains the bearer of the UE includes:
  • the second mode The SGSN determines, according to the value of the bearer processing policy and the attribute parameter of the bearer of the UE, which bearer of the UE needs to be reserved when the SGSN is faulty. Specifically, the SGSN determines the value and bearer of the attribute parameter of the bearer of the UE. Whether the value of the bearer parameter to be reserved when the mobility management NE is set in the processing policy matches. If the match is matched, the bearer is determined to be reserved. Otherwise, the bearer is determined to be released, and then the S-GW is notified. Specifically, the bearer processing is performed.
  • the policy is the same as the bearer processing policy in the second mode in the foregoing embodiment, and details are not described herein again.
  • the SGSN when the bearer is established, the SGSN sends a Create Session Request to create a session request message to the S-GW.
  • the SGSN determines that the bearer needs to be reserved according to the bearer processing policy, the SGSN carries the indication information, where the indication information is used for the notification.
  • the S-GW retains the bearer when the SGSN fails.
  • the SGSN may also create a bearer response message by sending a Create Bearer Response carrying the indication information to the S-GW, and notify the S-GW to reserve the bearer when the SGSN fails.
  • the SGSN may also send other messages to the S-GW to notify the S-GW of the purpose of retaining the currently established bearer.
  • the S-GW After receiving the indication information, the S-GW confirms that the bearer is reserved when the SGSN fails, and saves the indication information. In this way, the S-GW in this step can determine which bearers of the UE need to be reserved according to the saved indication information.
  • the third mode The SGSN determines whether to retain all the bearers of the UE when the SGSN is faulty, that is, the SGSN determines whether to retain all the UEs when the SGSN fails, according to the priority of the UE in the subscription information or the priority of the UE in the bearer processing policy. Bearer, then notify the S-GW.
  • the UE when the UE is a high-priority user, it is determined that all bearers of the UE are reserved when the SGSN is faulty, and when the UE is a low-priority user, it is determined that all bearers of the UE are released when the SGSN is faulty.
  • the SGSN when the bearer is set up, the SGSN sends a Create Session Request Create Session Request message to the S-GW.
  • the message When it is determined that all the bearers of the UE are reserved, the message carries the indication information, where the indication information indicates that the SGSN is reserved when the SGSN is faulty. All bearers of the UE.
  • the S-GW After receiving the indication information, the S-GW confirms that all the bearers of the UE are reserved when the SGSN is faulty, and saves the indication information. Therefore, the S-GW in this step may determine, according to the indication information, that all the bearers of the UE are reserved.
  • the specific implementation manner in which the RNC retains the bearer of the UE includes:
  • the first mode The RNC determines the bearer that the UE needs to keep according to the value of the bearer processing policy and the attribute parameter of the bearer of the UE.
  • the specific bearer processing policy may be pre-configured on the RNC. Or it is obtained from the SGSN.
  • the specific processing policy is the same as the one described in the first mode of the specific implementation manner of the eNodeB in the step 502 of the foregoing embodiment, and is not described here.
  • the RNC may obtain the bearer processing policy from the SGSN in the following manner:
  • the SGSN sends a bearer processing policy to the RNC.
  • the SGSN sends an Iu SETUP RESPONSE message to the RNC, where
  • the bearer processing policy may of course adopt other message sending bearer processing policies, which does not affect the implementation of the present invention.
  • the second mode the SGSN determines, according to the value of the bearer processing policy and the Attribute parameter of the bearer of the UE, which bearers of the UE need to be reserved when the SGSN fails. Specifically, the bearer processing policy and the RNC retain the UE in step 502 in the foregoing embodiment.
  • the bearer processing policy described in the second mode is the same as the specific implementation of the bearer, and is not mentioned here.
  • the SGSN when a certain bearer is established, the SGSN sends a bearer setup request message corresponding to the currently established bearer to the RNC.
  • the message When the SGSN determines that the bearer needs to be reserved according to the bearer processing policy, the message carries the indication information, where the indication information is Indicates that when the SGSN fails, the currently established bearer is reserved.
  • the RNC After receiving the indication information, the RNC confirms that the bearer is reserved when the SGSN fails, and saves the indication information.
  • this step may be according to the indication information stored RNC, the UE determines what needs to retain 7
  • the third mode The SGSN determines whether to retain all the bearers of the UE when the SGSN is faulty, that is, the SGSN determines whether to retain all the UEs when the SGSN fails according to the priority of the UE in the subscription information or the priority of the UE in the bearer processing policy. Bear, then notify the RNC.
  • the SGSN when the bearer is set up, the SGSN sends a context request message to the RNC, where the context request message carries indication information, where the indication information indicates that when the mobility management entity fails, all bearers of the UE are reserved.
  • the RNC After receiving the indication information, the RNC confirms that all the bearers of the UE are reserved when the SGSN is faulty, and saves the indication information. In this step, the RNC may determine, according to the indication information, that all bearers of the UE are reserved.
  • both the RNC and the S-GW may reserve part of the bearer of the UE, assuming that the voice bearer is currently reserved. If the RNC and the S-GW are currently transmitting voice data, the RNC and the S-GW may maintain the voice bearer. Transmitting voice data does not cause interruption of the transmission of the current voice data. If the RNC and the S-GW do not currently transmit voice data, the terminal may re-establish the voice bearer. Initiating a call or the like, the RNC and the S-GW can transmit voice data on the reserved voice bearer.
  • the RNC sends an RRC Connection Release message to the UE, where the message carries an indication message for instructing the UE to initiate an attach procedure, and the step is satisfied that the condition for releasing the UE connection is satisfied.
  • the RNC sends the RRC to the UE.
  • the Connection Release message notifies the UE to initiate an attach procedure, so that the UE avoids sending unnecessary re-establishment connection signaling, such as a service request Service Request message, etc., so that the UE service interruption time can be reduced, and unnecessary re-saving can be saved.
  • unnecessary re-establishment connection signaling such as a service request Service Request message, etc.
  • the UE After receiving the RRC Connection Release message, the UE initiates an attach procedure according to the indication information used in the message to instruct the UE to initiate an attach procedure.
  • the bearer of the UE served by the SGSN is reserved, and the UE is enabled to perform the related service.
  • the connection release request carries the connection initiation procedure.
  • the UE initiates an attach procedure according to the indication information, so that the network side re-establishes the context for the UE, so that the UE can avoid sending unnecessary re-establishment connection signaling, such as a service request Service Request message, etc., which can reduce the interruption of the UE service. Time, while also saving unnecessary re-establishment of the connection process.
  • an embodiment of the present invention provides a network device, where the network device may be an access network element or an S-GW, and the network device specifically includes:
  • the fault determining unit 701 is configured to determine whether the mobility management network element is faulty.
  • the mobility management network element may be specifically determined by detecting a restart counter in the Echo Response message sent by the mobility management network element. If the network device is the access network element, the device may determine whether the mobility management network element is faulty by detecting whether the reset message sent by the mobility management network element is received. For details, refer to the corresponding part of the method embodiment. description.
  • the bearer determining unit 702 is configured to: when the determining result of the fault determining unit 701 is YES, determine the value of the attribute parameter of the bearer of the UE served by the faulty mobility management network element and the mobility management network set in the bearer processing policy Whether the value of the bearer parameter to be reserved in the case of a meta-failure is matched. Specifically, the value of at least one parameter in the QCI, AP, and APN carried by the UE and the bearer processing policy may be determined. The value of the parameter of the bearer that needs to be reserved when the mobility management network element is faulty is matched. For the specific description of the bearer processing policy, refer to the corresponding description in the foregoing two method embodiments, which is not mentioned here.
  • the bearer processing unit 703 is configured to: when the determination result of the bearer determining unit 702 is YES, retain the bearer of the UE; when the determining result of the bearer determining unit 702 is NO, release the bearer of the UE.
  • the bearer processing unit 703 is further configured to release the bearer of the reserved UE when the condition for releasing the UE connection is satisfied, to notify the UE to initiate the attach procedure, when the condition for releasing the UE connection is satisfied, the network device further includes The sending unit 704 is configured to send, to the UE, a notification message, when the condition that the predetermined release UE connection is met, the notification message is used to instruct the UE to initiate an attach procedure.
  • the condition that the UE is in the quiescent state is that the time is up to a predetermined duration, or the access network element cannot continue to provide services for the UE.
  • the notification message sent to the UE may be carried to indicate that the UE initiates the attachment.
  • a release request message indicating the flow of the process.
  • the mobility management network element when the mobility management network element is faulty, it is determined whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer that needs to be reserved when the mobility management network element is set in the bearer processing policy.
  • an embodiment of the present invention provides a mobility management network element, where the mobility management network element can be an SGSN or an MME, and specifically includes:
  • the determining unit 801 is configured to determine whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy. Specifically, determining the bearer of the UE Whether the value of at least one parameter of the QCI, the allocation and retention priority AP, and the access point name APN matches the value of the bearer parameter to be reserved when the mobility management network element is set in the bearer processing policy; For details of the processing strategy, refer to the corresponding description in the foregoing two method embodiments, which is not mentioned here.
  • the sending unit 802 is configured to: when the determining result of the determining unit 801 is yes, send the indication information to the access network element or the serving gateway, so that the access network element or the serving gateway is faulty in the mobility management network element.
  • the bearer of the UE is reserved according to the indication information.
  • the indication information may not be sent to the access network element or the serving gateway, and the access network element or the serving gateway may be sent to indicate that the UE is deleted when the mobility management network element fails.
  • the determining unit 801 is configured to determine whether the value of the attribute parameter of the UE is equal to the bearer to be reserved when the mobility management network element is set in the bearer processing policy. The value of the parameter; or
  • the determining unit 801 is configured to determine whether the value of the attribute parameter of the bearer of the UE is within a value range of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy
  • the mobility management network element determines the mobility by determining whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy.
  • the management network element fails, the bearer that needs to be reserved is determined, and the access network element and the service gateway are notified, instead, all the bearers of the UE are released when the mobility management gateway is faulty, so that when the mobility management network element fails,
  • the UE can also perform services corresponding to the reserved bearers, thereby improving the user experience.
  • an embodiment of the present invention provides a mobility management network element, where the mobility management network element can be an SGSN or an MME, and specifically includes:
  • the determining unit 901 is configured to determine, according to the priority of the UE, whether to reserve all the bearers of the UE when the mobility management network element is faulty, and specifically, according to the priority of the UE in the subscription information or the UE in the bearer processing policy. Priority, determining whether it is necessary to retain all the UEs when the mobility management network element fails;
  • the sending unit 902 is configured to: when the determining result of the determining unit 901 is yes, send the indication information to the access network element or the serving gateway, so that the access network element or the serving gateway is configured according to the fault when the mobility management network element fails.
  • the indication information retains all bearers of the UE.
  • the determining result of the determining unit 901 is NO, the information may not be sent to the access network element or the serving gateway, and the indication may be sent to the access network element or the serving gateway to delete all bearers of the UE when the mobility management network element fails. information.
  • the mobility management network element determines, according to the priority of a certain UE, whether to retain all bearers of the UE when the mobility management network element is faulty, and notifies the access network element or the serving gateway to enable the access network element.
  • the serving gateway reserves all the bearers of some UEs when the mobility management network element fails, instead of releasing all the bearers of all UEs, so that the high priority UEs can be
  • the mobility management network element can also perform services when it fails.
  • an embodiment of the present invention provides a network system, where the network system includes: an access network element 1001, a mobility management network element 1002, and a serving gateway S-GW 1003;
  • the mobility management network element 1002 is configured to determine, when the value of the attribute parameter of the bearer of the UE matches the value of the bearer parameter to be reserved when the mobility management network element is set in the bearer processing policy, to the access network element. Or the serving gateway sends the indication information, so that the access network element or the serving gateway retains the bearer of the UE according to the indication information when the mobility management network element is faulty; wherein the mobility management network element may be an MME or an SGSN;
  • the access network element 1001 is configured to receive the indication information, and when the mobility management network element is faulty, retain the bearer of the UE according to the indication information; where, when the mobility management network element is the MME, the access network element is The eNodeB, when the mobility management network element is the SGSN, the access network element is the RNC.
  • the serving gateway 1003 is configured to receive the indication information, and when the mobility management network element fails, retain the bearer of the UE according to the indication information.
  • the mobility management network element determines the mobility by determining whether the value of the attribute parameter of the bearer of the UE matches the value of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy.
  • the management network element fails, the bearer that needs to be reserved is determined, and the access network element or the serving gateway is notified, so that the access network element or the serving gateway retains part of the UE's bearer when the mobility management network element fails, instead of all the UEs.
  • the bearer is released, so that when the mobility management network element fails, the UE can also perform services corresponding to the reserved bearers, thereby improving the user experience.
  • an embodiment of the present invention provides a network system, where the network system includes: an access network element
  • the mobility management network element 1102 is configured to use the priority of the UE to determine that all the bearers of the UE need to be reserved when the mobility management network element fails; and send indication information to the access network element and the serving gateway, so that the access network When the mobility management network element is faulty, the UE or the serving gateway retains all bearers of the UE according to the indication information; wherein, the mobility management network element may be an MME or an SGSN;
  • the access network element 1101 is configured to receive the indication information.
  • the mobility management network element fails, all the bearers of the UE are reserved according to the indication information.
  • the mobility management network element is the MME
  • the access network element is an eNodeB.
  • the mobility management network element is an SGSN
  • the access network element is an RNC.
  • the service gateway 1103 is configured to receive the indication information, when the mobility management network element fails, according to The indication information retains all bearers of the UE.
  • an embodiment of the present invention provides a network system, where the network system includes: an access network element 1201, a mobility management network element 1202, and a serving gateway S-GW 1203, where
  • the access network element 1201 is configured to: when the mobility management network element 1202 fails, determine the value of the attribute parameter of the UE served by the faulty mobility management network element 1202 and the mobility management set in the bearer processing policy. When the value of the bearer parameter to be reserved when the network element is faulty matches, the bearer of the UE is reserved;
  • the service gateway 1203 is configured to determine, when the mobility management network element 1203 fails, the value of the attribute parameter of the UE served by the faulty mobility management network element and the mobility management network element fault set in the bearer processing policy.
  • the bearer parameter to be reserved is matched, the bearer of the UE is reserved; wherein the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy is the same as the attribute parameter of the bearer of the UE Corresponding parameters.
  • the UE according to the priority of a certain UE, it is determined whether all bearers of the UE need to be reserved when the mobility management network element is faulty, and the access network element or the serving gateway is notified, so that the access network element or the serving gateway is moving.
  • the mobility management network element fails, the UE will retain all the bearers of the UE, instead of releasing all the bearers of all the UEs. This allows the high-priority UE to perform services when the mobility management NE fails.

Abstract

La présente invention concerne un procédé pour le traitement de défaillance d'élément de réseau de gestion de mobilité (MMNE) comprenant: la détermination de la survenance d'une défaillance dans l'élément de réseau de gestion de mobilité ; lorsque l'on détermine que les valeurs des paramètres d'attributs de support de l'équipement utilisateur desservi par l'élément de réseau de gestion de mobilité défaillant correspondent aux valeurs des paramètres de support nécessitant le maintien, qui sont établis dans les règles de traitement de support, à l'instant de la survenance de la défaillance dans l'élément de réseau de gestion de mobilité, le maintien des supports de l'équipement utilisateur, les paramètres de support nécessitant le maintien, qui sont établis dans les règles de traitement de support, à l'instant de la survenance de la défaillance dans l'élément de réseau de gestion de mobilité correspondant aux paramètres d'attributs de support de l'équipement utilisateur. Lorsqu'une défaillance se produit dans l'élément de réseau de gestion de mobilité, la solution technique fournie par la présente invention permet le maintien des supports de l'équipement utilisateur, et permet la réalisation de services correspondant par l'équipement utilisateur.
PCT/CN2010/076597 2010-09-03 2010-09-03 Procédé, dispositif de réseau et système de réseau pour le traitement de défaillance d'élément de réseau de gestion de mobilité WO2011110013A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2010/076597 WO2011110013A1 (fr) 2010-09-03 2010-09-03 Procédé, dispositif de réseau et système de réseau pour le traitement de défaillance d'élément de réseau de gestion de mobilité
CN2010800019084A CN102318384A (zh) 2010-09-03 2010-09-03 移动性管理网元故障的处理方法、网络设备及网络系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/076597 WO2011110013A1 (fr) 2010-09-03 2010-09-03 Procédé, dispositif de réseau et système de réseau pour le traitement de défaillance d'élément de réseau de gestion de mobilité

Publications (1)

Publication Number Publication Date
WO2011110013A1 true WO2011110013A1 (fr) 2011-09-15

Family

ID=44562842

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076597 WO2011110013A1 (fr) 2010-09-03 2010-09-03 Procédé, dispositif de réseau et système de réseau pour le traitement de défaillance d'élément de réseau de gestion de mobilité

Country Status (2)

Country Link
CN (1) CN102318384A (fr)
WO (1) WO2011110013A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106465448A (zh) * 2015-03-27 2017-02-22 华为技术有限公司 数据传输方法、接入网设备和通信系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101541097A (zh) * 2008-03-19 2009-09-23 华为技术有限公司 恢复承载的方法、装置及系统
CN101540989A (zh) * 2008-03-21 2009-09-23 华为技术有限公司 设备重启后的数据恢复方法、设备和系统
CN101646270A (zh) * 2008-08-06 2010-02-10 华为技术有限公司 保持业务连续的方法、系统、移动性管理实体和存储设备
WO2010016518A1 (fr) * 2008-08-08 2010-02-11 株式会社エヌ・ティ・ティ・ドコモ Procédé de communication mobile, dispositif de réseau et station de commutation

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8264956B2 (en) * 2009-02-27 2012-09-11 Cisco Technology, Inc. Service redundancy in wireless networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101541097A (zh) * 2008-03-19 2009-09-23 华为技术有限公司 恢复承载的方法、装置及系统
CN101540989A (zh) * 2008-03-21 2009-09-23 华为技术有限公司 设备重启后的数据恢复方法、设备和系统
CN101646270A (zh) * 2008-08-06 2010-02-10 华为技术有限公司 保持业务连续的方法、系统、移动性管理实体和存储设备
WO2010016518A1 (fr) * 2008-08-08 2010-02-11 株式会社エヌ・ティ・ティ・ドコモ Procédé de communication mobile, dispositif de réseau et station de commutation

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106465448A (zh) * 2015-03-27 2017-02-22 华为技术有限公司 数据传输方法、接入网设备和通信系统
EP3277051A4 (fr) * 2015-03-27 2018-03-21 Huawei Technologies Co., Ltd. Procédé de transmission de données, dispositif de réseau d'accès et système de communication
US10477610B2 (en) 2015-03-27 2019-11-12 Huawei Technologies Co., Ltd. Data transmission method, access network device, and communication system

Also Published As

Publication number Publication date
CN102318384A (zh) 2012-01-11

Similar Documents

Publication Publication Date Title
US11889465B2 (en) Paging cause value
RU2749750C1 (ru) Управление разрывом услуги для беспроводного устройства
US20220022089A1 (en) Service instance indication for resource creation
KR20190021461A (ko) 무선 통신 시스템에서의 등록 해제 방법 및 이를 위한 장치
JP7188462B2 (ja) Ｕｅの方法及びｕｅ
US20110182244A1 (en) Method for supporting context management by home node-b
WO2012138760A1 (fr) Décharge de trafic ip sélectionné et accès ip local
US20120100823A1 (en) Method, system, network side device, and ue of managing csg membership
WO2012097706A1 (fr) Procédé et système de modification de support
WO2011153750A1 (fr) Procédé et système de synchronisation de données d'utilisateur
WO2014000219A1 (fr) Procédé de rapport d'état de congestion et dispositif de réseau d'accès
WO2009089790A1 (fr) Procédé pour l'acquisition du type d'un service support et pour la commutation entre réseaux supports pour des terminaux
WO2011026407A1 (fr) Procédé et système de prise en charge de mobilité de connexion d'accès par protocole internet local
US9629179B2 (en) Method and device for processing local access connection
TW201513701A (zh) 在通信網路中用於緊急處理的方法及裝置
WO2012130018A1 (fr) Procédé et système pour la prise en charge de mobilité de connexion de déchargement ip
WO2009076814A1 (fr) Procédé et dispositif de mise à jour de règle pcc
WO2012103773A1 (fr) Procédé de régulation de surcharge et système de système de relais
WO2012146093A1 (fr) Procédé et système destinés à réaliser un traitement de service
WO2011085623A1 (fr) Procédé et système permettant à une passerelle d'accès local d'obtenir des informations d'appel d'un terminal
WO2011035719A1 (fr) Procédé et système pour libérer des connexions locales
WO2011032522A1 (fr) Système et procédé de mise en œuvre d'accès local
WO2011110013A1 (fr) Procédé, dispositif de réseau et système de réseau pour le traitement de défaillance d'élément de réseau de gestion de mobilité
WO2011035671A1 (fr) Système et procédé pour libérer une connexion d'accès de protocole internet (ip) locale
WO2011006395A1 (fr) Procédé de synchronisation et système de gestion de défaut partiel

Legal Events

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

Ref document number: 201080001908.4

Country of ref document: CN

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

Ref document number: 10847271

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: 10847271

Country of ref document: EP

Kind code of ref document: A1