WO2011110013A1

WO2011110013A1 - Method, network device and network system for processing failure of mobility management network element

Info

Publication number: WO2011110013A1
Application number: PCT/CN2010/076597
Authority: WO
Inventors: 陈中平; 吴问付
Original assignee: 华为技术有限公司
Priority date: 2010-09-03
Filing date: 2010-09-03
Publication date: 2011-09-15
Also published as: CN102318384A

Abstract

A method for processing a failure of a Mobility Management Network Element (MMNE) includes: determining that a failure occurs in the MMNE; when determining that the values of the bearer attribute parameters of the UE served by the failed MMNE match with the values of the bearer parameters needing to be retained, which are set in a bearer processing policy, in the moment of a failure occurred in the MMNE, retaining the bearers of the UE, wherein the bearer parameters needing to be retained, which are set in the bearer processing policy, in the moment of a failure occurred in the MMNE, correspond to the bearer attribute parameters of the UE. When a failure occurs in a MMNE, using the technical solution provided by the present invention can retain the bearers of the UE, and enables the UE to perform corresponding services.

Description

Method for processing mobility management network element failure, network device and network system

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.

Background technique

In order to meet the challenges of wireless broadband technology and maintain the leading edge of 3GPP networks, a long-term evolution plan (LTE, Long Term Evolution) for mobile communication networks has been established. ₀ Under the guidance of this evolution plan, a new mobile communication network architecture is defined. The architecture is flatter than the current 2G and 3G networks, and only the packet domain (PS) is reserved, so it can be called the Evolved 3 GPP Packet Switched Domain, which can also be called the evolved packet system. 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.

When 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.

Summary of the invention

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. When the mobility management network element fails, the bearer of the UE is reserved, so that the UE can perform corresponding services.

In view of this, the embodiments of the present invention provide:

A method for processing a fault of a mobility management network element, including:

Determining the mobility management network element failure;

Determining the value of the attribute parameter of the bearer of the UE served by the faulty mobility management network element When the value of the bearer parameter to be reserved when the mobility management network element is set in the bearer processing policy is matched, the bearer of the UE is reserved, and the mobility management network element set in the bearer processing policy needs to be reserved when the fault occurs. The parameter of the bearer is a parameter corresponding to the attribute parameter of the bearer of the UE.

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.

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;

And 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 When the value of the bearer parameter to be reserved when the management network element is faulty is matched, 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.

In another embodiment of the present invention, 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. When the mobility management network element fails, 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. DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. One of ordinary skill in the art can also obtain other drawings based on these drawings without undue creative effort.

Figure 1 is a 3GPP network architecture diagram;

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; A method for the MME to restart when the UE accesses the core network through the E-UTRAN; 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;

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.

detailed description

Referring to FIG. 1 , in order to make the technical solutions described in the following embodiments of the present invention more clear, the network architecture to which the embodiments of the present invention are applied is briefly described. As shown in FIG. 1 , 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). 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. It should be noted that the network architecture shown in FIG. 1 is only a network architecture to which the technical solution of the present invention is applicable, and those skilled in the art should understand that the technical solution provided by the present invention can also be applied to other network architectures. , such as non-3GPP network architecture.

Referring to FIG. 2, 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. Specifically, when the UE accesses through the E-UTRAN, 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.

Specifically, 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; When accessing the 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. For details, refer to the detailed description of the subsequent embodiments.

The mobility management network element failure may refer to a mobility management network element restart or other failure.

202. 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.

Specifically, 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.

Specifically, 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.

For example, in the bearer processing policy, 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; In the event of a fault, 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. When the APN is equal to 9, the bearer is deleted, if the bearer of the UE is Sexual parameters, such as QCI equal to 5, AP equal to 9 and APN equal to 13, then retain the bearer and so on. In the embodiment of the present invention, 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:

If 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

If the mobility management NE in the bearer policy parameter fails, the parameters of the bearer to be reserved are

In the case of 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; or

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.

In the prior art, 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. In order to prevent the UE from being unable to perform the service 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. Specifically, 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.

In the embodiment of the present invention, 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.

Referring to FIG. 3, 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:

301: 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 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.

302. 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, 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. When the UE accesses through the 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. Whether 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.

Referring to FIG. 4, an embodiment of the present invention provides a method for processing a fault of a mobility management network element, where the method includes:

401. 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.

In the embodiment of the present invention, 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.

402. When 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. When the management network element is faulty, all bearers of the UE are reserved according to the indication information.

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. When the MME restarts, the S-GW and the eNodeB can continue to reserve bearers, thereby maintaining data transmission. Further, when the RRC connection is released, 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:

501. The S-GW and the eNodeB learn that the MME restarts, and determine that the MME restarts.

UE.

Specifically, 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. When 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. When the UE is in the idle state, since there is no S1 connection between the eNodeB and the UE, the eNodeB cannot determine that the MME restart will affect the UE.

502. 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:

1) Keep QCI as a specific value bearer, and other bearers delete/release;

2) Retain QICs that belong to a specific value range, and other bearers are deleted/released;

3) Keep A P as a specific value bearer, and other bearers delete/release;

4) Reserved A P belongs to a bearer within a certain value range, and other bearers are deleted/released;

5) Retain the bearer corresponding to a specific APN, and delete/release other bearers;

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:

1) Keep QCI as a specific value bearer, and other bearers delete/release;

3) Keep A P as a specific value bearer, and other bearers delete/release;

6) The bearer corresponding to a specific UE is reserved, and other bearers are deleted/released.

When a certain bearer is established, the MME sends a Create Session Request to create a session request message to the S-GW. When 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. Of course, 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. 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.

For example, 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.

Specifically, when the bearer is set up, the MME sends a Create Session Request Create Session Request message to the S-GW. 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 MME is reserved when the MME fails. All bearers of the UE. After receiving the indication information, 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 first mode: 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:

1) Keep QCI as a specific value bearer, and other bearers delete/release;

2) Retain QICs belonging to a certain value range, other bearers delete/release; 3) Retain A P as a specific value bearer, and other bearers delete/release;

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 second mode: 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.

Specifically, when a certain bearer is established, the MME sends a bearer setup request message corresponding to the currently established bearer to the eNodeB. When the MME determines that the bearer needs to be reserved according to the bearer processing policy, the message carries the indication information, where the indication information indicates When the MME fails, the currently established bearer is reserved. After receiving the indication information, 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.

Specifically, when the bearer is set up, 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. After receiving the indication information, 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.

In this step, 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.

503. Optionally, when the condition for the scheduled release of the UE is met, the eNodeB 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.

Specifically, 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. Alternatively, the message is sent to the MME to restart the MME, and the UE is triggered to initiate the attach procedure. For example, 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.

In this step, 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.

504. Optionally, 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.

Specifically, 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.

In the embodiment of the present invention, when the MME is restarted, the bearer of the UE served by the MME is reserved, and the UE is enabled to perform the related service. When 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. In the indication information, 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. When the SGSN is restarted, the S-GW and the RNC can continue to reserve bearers, thereby maintaining data transmission. Further, when the RRC connection is released, 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:

601. 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. When 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. When 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.

602. 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 first way is the same as the description below in step 502 of the previous embodiment, and will not be described here. 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.

Specifically, when the bearer is established, the SGSN sends a Create Session Request to create a session request message to the S-GW. When 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. Of course, 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. 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.

For example, 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.

Specifically, when the bearer is set up, the SGSN sends a Create Session Request Create Session Request message to the S-GW. 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. 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.

If the bearer processing policy is obtained from the SGSN, the RNC may obtain the bearer processing policy from the SGSN in the following manner: When the RNC is initialized, the SGSN sends a bearer processing policy to the RNC. For example, 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.

Specifically, when a certain bearer is established, the SGSN sends a bearer setup request message corresponding to the currently established bearer to the RNC. 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. After receiving the indication information, the RNC confirms that the bearer is reserved when the SGSN fails, and saves the indication information. Thus, this step may be according to the indication information stored RNC, the UE determines what needs to retain ₇ | uploaded.

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.

Specifically, 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. 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.

In this step, 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.

603. Optionally, when the condition for the scheduled release of the UE connection is met, 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. When 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. The process of establishing a connection.

For the specific implementation of the step, refer to the related description of step 503, and no further description is provided herein. 604. Optionally, 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.

For the specific implementation of the step, refer to the related description of step 504, and no further description is provided herein. In the embodiment of the present invention, when the SGSN is restarted, the bearer of the UE served by the SGSN is reserved, and the UE is enabled to perform the related service. When the subsequent RNC sends the RRC Connection Release message to the UE, the connection release request carries the connection initiation procedure. In the indication information, 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.

Referring to FIG. 7, 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. When the network device is an S-GW, 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.

In the embodiment of the present invention, 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. It is determined whether the bearer is reserved when the mobility management network element fails, instead of deleting all the bearers of the UE, so that when the mobility management network element fails, the UE can also perform services corresponding to the reserved bearers, thereby improving The user's experience; further, when the predetermined condition for releasing the UE connection is met, sending a notification 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. 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.

Referring to FIG. 8, 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. When the determining result of the determining unit 801 is NO, 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 indication information carried.

In another embodiment of the present invention, 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

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. When 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.

Referring to FIG. 9, 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. When 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.

In the embodiment of the present invention, 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. Or 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.

Referring to FIG. 10, 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.

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. When 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.

Referring to FIG. 11, an embodiment of the present invention provides a network system, where the network system includes: an access network element

1101, a mobility management network element 1102 and a service gateway S-GW 1103;

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. When the mobility management network element fails, all the bearers of the UE are reserved according to the indication information. When the mobility management network element is the MME, the access network element is an eNodeB. When 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.

Referring to FIG. 12, 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. When the value of 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.

In the embodiment of the present invention, 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. When 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.

A person skilled in the art can understand that all or part of the steps of implementing the foregoing embodiments may be performed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, such as a read only memory. Disk or disc, etc.

The method, the network device, and the network system for processing the fault of the mobility management network element provided by the embodiment of the present invention are described in detail. The principles and implementation manners of the present invention are described in the following. The description is only for helping to understand the method of the present invention and its core idea; at the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in specific embodiments and application scopes. The contents of this specification are not to be construed as limiting the invention.

Claims

Rights request

A method for processing a fault of a mobility management network element, comprising:

Determining that the mobility management network element is faulty;

Determining, when the value of the attribute parameter of the bearer of the UE served by the mobility management network element of the fault is matched with 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 of the UE, 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.

2. The method of claim 1 wherein

The value of the attribute parameter of the bearer of the UE served by the mobility management network element that is determined by 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 is specifically:

Determining the value of at least one parameter of the quality of service type identifier QCI, the allocation and retention priority AP, the access point name APN, and the mobility management set in the bearer processing policy of the bearer of the UE served by the faulty mobility management network element The values of the parameters of the bearer to be reserved when the NE fails are matched.

The method according to claim 1, wherein the determining 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 The value matching of the parameters of the bearer to be reserved in the case of a meta-fault includes:

Determining, by the value of the parameter of the bearer of the UE that is served by the mobility management network element of the fault, and 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;

Or,

Determining the value of the attribute parameter of the bearer of the UE served by the mobility management network element of the fault 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 method according to claim 1, wherein after the bearer of the UE is reserved, the method further includes:

And when the condition for releasing the UE connection is met, sending a notification message to the UE, where the notification message is used to indicate that the UE initiates an attach procedure.

5. The method of claim 4, wherein The condition for the predetermined release of the UE connection is that the time when the UE is in a quiescent state reaches a predetermined duration, or the access network element cannot continue to provide services for the UE.

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. Instructing 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, where the mobility management network element set in the bearer processing policy The parameters of the bearer to be reserved in the event of a fault are corresponding to the attribute parameters of the bearer of the UE.

7. The method of claim 6 wherein:

The mobility management network element determines that 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 is specifically:

Determining the value of at least one parameter of the quality of service type identifier QCI, the allocation and retention priority AP, and the access point name APN of the bearer of the UE and the parameters of the bearer to be reserved when the mobility management network element is set in the bearer processing policy The value matches.

The method according to claim 6, wherein the mobility management network element determines the value of the attribute parameter of the bearer of the UE and the bearer to be reserved when the mobility management network element is set in the bearer processing policy Match the values of the parameters, including:

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 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.

The method according to any one of claims 6 to 8, wherein the mobility management network element determines the value of the attribute parameter of the bearer of the UE and the fault of the mobility management network element set in the bearer processing policy The value of the parameter to be reserved is matched, and the indication information is sent to the access NE or the serving gateway, including:

When the mobility management network element establishes the mobility of the UE, the mobility management network element determines the value of the attribute parameter of the established UE and the mobility management network element set in the bearer processing policy. Whether the values of the bearer parameters to be reserved in the fault match, and if they match, the access network element or The service gateway sends an indication message.

11. The method of claim 7 wherein:

The priority of the mobility management network element UE determines that all the bearers of the UE need to be reserved when the mobility management network element fails:

The mobility management network element needs to reserve all the bearers of the UE when the mobility management network element fails, according to the priority of the UE in the subscription information or the priority of the UE in the bearer processing policy.

12. A network element device, comprising:

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 set in the bearer processing policy Whether the value of the bearer parameter to be reserved when the management network element is faulty 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 the same as the attribute parameter of the bearer of the UE. Corresponding parameters;

a bearer processing unit, configured to: when the determination result of the bearer determining unit is yes, retain the

UE's 7|

13. The device according to claim 12, further comprising:

And a sending unit, configured to send a notification message to the UE when the condition for the scheduled release of the UE is met, where the notification message is used to indicate that the UE initiates an attach procedure.

14. A mobility management network element, comprising:

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 parameter of the bearer that needs to be reserved when the network element fails to be managed is a parameter corresponding to the attribute parameter of the bearer of the UE; a sending unit, configured to send, to the access network element or the serving gateway, 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.

15. The mobility management network element of claim 14 wherein:

The determining unit is configured to determine whether the value of the attribute parameter of the bearer of the UE is equal to the value of the parameter of the bearer to be reserved when the mobility management network element is set in the bearer processing policy; or the determining unit, Whether 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.

16. A mobility management network element, comprising:

a sending unit, configured to send, to the access network element or the serving gateway, 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.

17. The mobility management network element of claim 16 wherein:

The determining unit is configured to determine, according to the priority of the UE in the subscription information or the priority of the UE in the bearer processing policy, whether to retain all the bearers of the UE when the mobility management network element fails.

A network system, comprising: a mobility management network element, an access network element, and a service gateway, where

a mobility management network element, 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 reserves the bearer of the UE according to the indication information when the mobility management network element fails, and the mobility management set in the bearer processing policy The parameter of the bearer to be reserved when the network element fails is the parameter corresponding to the attribute parameter of the bearer of the UE;

a service gateway, configured to receive the indication information, when the mobility management network element fails, according to The indication information retains a bearer of the UE.

a mobility management network element, configured for a priority of the UE, determining to retain all bearers of the UE when the mobility management network element fails; sending indication information to the access network element and the serving gateway, so that the When the mobility management network element fails, the ingress network element or the serving gateway reserves all the bearers of the UE according to the indication information, and the parameters of the bearer to be reserved when the mobility management network element is set in the bearer processing policy a parameter corresponding to an attribute parameter of the bearer of the UE;

The serving gateway is configured to receive the indication information, and when the mobility management network element fails, retain all bearers of the UE according to the indication information.

An access network element, configured to determine, when the mobility management network element fails, the value of the attribute parameter of the UE served by the faulty mobility management network element and the mobility management network set in the bearer processing policy The bearer of the bearer is reserved when the value of the bearer parameter to be reserved in the case of the meta-failure is reserved; the serving gateway is configured to determine, when the mobility management network element fails, determine the service provided by the faulty mobility management network element 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, the bearer of the UE is reserved; where the bearer processing policy is set The parameters of the bearer to be reserved when the mobility management network element fails are the parameters corresponding to the attribute parameters of the bearer of the UE.