WO2012041197A1

WO2012041197A1 - Method and network side device for handling mobility management process

Info

Publication number: WO2012041197A1
Application number: PCT/CN2011/080154
Authority: WO
Inventors: 艾明; 邓强
Original assignee: 电信科学技术研究院
Priority date: 2010-09-30
Filing date: 2011-09-26
Publication date: 2012-04-05
Also published as: CN102448042B; CN102448042A

Abstract

A method and a network side device for handling a mobility management process. The method comprises: during the mobility management process of a user equipment (UE), and on the basis of whether or not different access point names (APN) have a congestion control mechanism activated, the network side transmitting to the UE a mobility management accept message; the network side attaching a mobility management back-off timer to the mobility management accept message. The present invention reduces the consumption of resources of the UE and of the network side, thereby achieving an improved control over network congestion.

Description

The invention relates to a method for processing a mobility management process and a network side device. The application is submitted to the Chinese Patent Office on September 30, 2010, and the application number is 201010503865.1, and the invention name is "a method for rejecting the mobility management process and a network side device. The priority of the Chinese Patent Application, the entire contents of which is incorporated herein by reference. Technical field

The present invention relates to the field of wireless communication technologies, and in particular, to a method for processing a mobility management process and a network side device. Background technique

APN (Access Point Name) is an important parameter used by a network entity in a mobile communication network to select a gateway node of a PDN (Packet Date Network). Different nodes correspond to different gateway nodes. A connection between the corresponding gateway nodes establishes a connection to the UI.

For different application scenarios, the network entity is an MME (Mobility Management Entity) or an SGSN (Serving GPRS Support Node), and the gateway node is a PGW (Packet Data Network Gateway) or a GGSN. (Gateway GPRS Support Node, Gateway GPRS Support Node).

For EPS (Evolved Packet System), consider the number of UEs accessing the same gateway node and the number of initiators that are initiated. If the signaling volume is too large, congestion will be caused to the gateway node. In order to perform congestion control on the gateway node, the MME is introduced to perform an APN-based congestion control mechanism. details as follows:

The MME determines whether each APN is congested according to a specific rule. If the APN is congested and congestion control is required, the existing standard defines the APN as the APN for enabling the congestion control mechanism, and the MME determines whether the congestion occurs in each APN, which may be from the PGW. The instructions are known, and can also be judged according to their own rules. In the attaching ATTACH process or the TA ² J process of the UE, if the APN that the UE subscribes to activates the congestion control mechanism, the ATTACH request and the TAU (Tracking Area Update procedures) request message are rejected, and the mobility management backoff is carried. The duration information of the timer.

After rejecting the ATTACH or TAU request, the MME should retain the subscription data of the UE for a period of time. The main purpose is to refuse to interact with the HSS (Home Subscriber Server, the home subscriber server), and reject the UE from the UE when the APN is still congested. Follow-up request.

The MME receives the PDN connection request sent by the UE, and the PDN connection request may or may not carry the APN. If the APN is not carried, the MME needs to obtain the subscription data of the UE from the HSS. At this time, the MME will learn which APNs the UE has subscribed to, and obtain the default APN of the UE from the subscription data of the UE as the APN requested by the UE. When the APN requested by the UE turns on the congestion control mechanism, the MME rejects the PDW connection request corresponding to the APN requested by the UE. For the PDW that is congested, the MME may also carry the session backoff timer to the UE by rejecting the PDN connection request message. When the MME rejects the connection request of the priority service/emergency call service, the MME shall not instruct the UE to start the session backoff timer.

After receiving the mobility management backoff timer information sent by the MME, the UE starts the mobility management backoff timer, and the UE should not initiate any mobility management process before the mobility management backoff timer expires. .

After receiving the session management backoff timer sent by the MME, the UE starts the session management backoff timer of the APN, before the session management backoff timer expires:

1) If the APN is rejected in the PDN connection request message, the UE cannot initiate any session management process of the APN, and the UE may initiate a session management process to other APNs that it subscribes to;

2) If the rejecting PDN connection request message does not include the APN, the UE cannot initiate a session management process that does not include any APN, and the UE may initiate a session management process corresponding to the specific APN, and the specific APN refers to the UE signing the APN except the default APN;

3) Cell/Tracking Area TA/PLMN (Public Land Mobile Network) / RA (Routing Area) change does not stop the session management backoff timer;

4) Even if the session management backoff timer is running, the UE is allowed to initiate to priority service/emergency call Called the session management process of the business. ³

For the scenario where the network entity MME rejects the attach/TAU request of the UE and carries the mobility backoff timer, how the network processes the EPS bearer information, the prior art does not provide a clear solution. Summary of the invention

The present invention provides a processing method and apparatus for a mobility management process for optimizing a processing method of an existing mobility management process.

A method of processing a mobility management process, including:

In the mobility management process of the user equipment UE, the network side sends a mobility management accept message to the UE according to whether the access point name APN enables the congestion control mechanism;

The network side carries a mobility management backoff timer in the mobility management accept message. A mobility management process backoff method includes:

The user equipment UE receives the mobility management acceptance carried by the network side and carries the mobility management backoff timer in the mobility management process; %, package,;

The UE starts a mobility management backoff timer, and only initiates a mobility management process related to the priority service or the emergency call service before the mobility management timer expires;

The UE determines that the duration of the mobility management backoff timer is greater than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the value of the mobility management backoff timer is not less than The periodic tracking timer is started.

A processing network side device for a mobility management process, comprising:

a message sending unit, configured to send, in a mobility management process of the user equipment UE, a mobility management accept message to the UE according to whether a different access point name APN enables a congestion control mechanism;

And a timer carrying unit, configured to carry a mobility management backoff timer in the sent mobility management accept message.

A user equipment UE that implements a mobility management process backoff includes:

Receiving a message receiving unit, configured to receive, in the mobility management process, a mobility management accept message that is sent by the network side and carries a mobility management backoff timer; a first timer starting unit, configured to start a dynamic management backoff timer, and only initiate a mobility management process related to a priority service or an emergency call service before the mobility management timer expires; a second timer starting unit The duration of the mobility management backoff timer is greater than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the value of the mobility management backoff timer is not less than The periodic tracking timer is started.

The processing method of the mobility management process and the network side device, the mobility management process backoff method and the user equipment provided by the present invention have the following beneficial effects: the mobility transmitted to the UE by whether the APN is enabled with the information of the congestion control mechanism. The management acceptance message carries the mobility management backoff timer, which can further save resources of the UE and the network side, and has better effect on network congestion control. DRAWINGS

1 is a flowchart of a method for processing a mobility management process according to an embodiment of the present invention; FIG. 2 is a flowchart of a mobility management backoff method according to an embodiment of the present invention;

3 is a structural diagram of a network side device for processing a mobility management process according to an embodiment of the present invention; and FIG. 4 is a structural diagram of a user equipment UE for implementing a mobility management process backoff according to an embodiment of the present invention. detailed description

The inventors of the present invention have found that the existing mobility management processing method has the following technical drawbacks: For each APN that the UE may activate, the UE should support an independent session backoff management timer. If the UE establishes a connection to the APN, the APN is considered to be activated. In the APN-based congestion control mechanism in the prior art, although the network entity MME can send the mobility management backoff timer duration information to the UE, it is limited to carrying the mobility management in the reject attachment request message and the reject TAU request message. The duration information of the backoff timer has certain limitations. After the UE receives the duration information of the mobility management timer initiated by the MME and starts the mobility management timer in the TAU process, the UE should have a longer length of the mobility management timer than the periodic tracking area update timer. How to deal with it, there is no clear solution in the prior art. In view of the above technical defects, the embodiment of the present invention proposes to move Processing method and a network-side device mobility management, and mobility management during ⁵ move back-off method and a user equipment. The method for processing the mobility management process, the network side device, the mobility management process backoff method, and the user equipment provided by the present invention will be described in more detail below with reference to the accompanying drawings and embodiments.

In the 3GPP (3rd Generation Partnership Project) machine-to-machine communication specification development process, the APN-based congestion control mechanism is discussed, and it is decided that this mechanism can also be used for APN congestion caused by common UEs. However, for the rejection scenarios and methods, there is currently no complete, accurate, and specific representation of the behavior of the network and the UE, and there are some unresolved issues.

The present invention provides a method for processing a mobility management process. As shown in FIG. 1, the method includes: Step S10: In the mobility management process of the UE, the network side sends a mobility to the UE according to whether a different APN starts a congestion control mechanism. Sex management acceptance message;

Step S20: When the network side sends a mobility management accept message to the UE, the mobility management accept message sent by the network carries a mobility management backoff timer.

The method proposed by the present invention makes the refusal mobility management process not only limited to the implementation of rejecting the attach or location update process, but also rejects the mobility management process by receiving the message through the mobility management according to whether the APN is enabled to open the congestion control mechanism, thereby avoiding serious Network congestion, saving network resources and better congestion control.

The present invention provides a mobility management process backoff method, as shown in FIG. 2, including:

Step SOI, the UE receives the mobility management acceptance of the mobility management backoff timer sent by the network side in the mobility management process; %, packet,;

Step S02: The UE starts a mobility management backoff timer, and only initiates a mobility management process related to a priority service or an emergency call service before the mobility management timer expires;

Step S03: The UE determines that the mobility management backoff timer is longer than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the duration of the mobility management backoff timer is not less than The value is used to start the periodic tracking timer.

The above method proposed by the present invention can be applied to a GPRS (General Packet Radio Service) system or an EPS system. The preferred embodiment of the technical solution of the present invention is given below by taking an application to the EPS system as an example and combining with a specific mobility management process. In this embodiment, the mobility management process of the UE is an attach procedure ATTACH, and the mobility management accept message is an attach accept message.

Preferably, the network side sends the mobility management accept message to the UE according to whether the different APNs enable the congestion control mechanism, and the method includes: the first network entity determines an APN that the UE requests to connect in the attaching process; and the first network entity connects according to the request. Whether the APN turns on the congestion control mechanism and sends an attach accept message to the UE.

When applied to the EPS system, the first network entity is an MME.

In this embodiment, the MME determines the APN that the UE requests to connect in the attaching process, and the method includes: determining that the APN is the APN requesting the connection when the message sent by the UE in the attaching process, and determining that the UE is attached. When the APN is not carried in the message sent by the process, the default APN in the subscription data is determined to be the APN to be connected according to the subscription data of the UE obtained from the HSS.

In this embodiment, when the MME determines that the APN requesting the connection to open the congestion control mechanism, the MME sends an attach accept message carrying the mobility management backoff timer, and also sends a connection reject message to the UE, and carries the connection reject message in the connection reject message. The session management backoff timer of the APN requesting the connection.

Preferably, the MME determines that the APN requesting the connection starts the congestion control mechanism, and attempts to establish an attach accept message carrying the mobility management backoff timer to the UE after the connection to the APN is successfully established, and also sends an activation to the UE. The EPS bears the context request message, and carries the session management backoff timer of the APN in the activated EPS bearer context request message.

The method flow of rejecting the mobility management process in the embodiment of the present invention includes:

Step S101: The UE sends an attach request ATTACH REQUEST message. According to the prior art, in the ATTACH REQUEST message, the UE is also requested to request a PDN CONNECTIVITY REQEUST message to the APN connection, and the message may not include any APN. In step S102, the network performs the attach process according to the existing process. Identity request request procedure, authentication/security authentication AUTHENTICAITON/SECURITY procedure, password selection request/response CIPERE OPTION REQUEST/RESPONESE procedure. In the password selection request/response process, the UE may indicate an APN to the MME; Step S103, if the current MME does not have a valid context, then the subscription data of the UE needs to be obtained from the HSS. At this point, you will know which defects the UE has signed. If the UE indicates the APN in the foregoing step, it indicates that the UE will establish a connection to the APN. If the APN is not indicated, the MME obtains the default APN of the UE from the subscription data of the UE as the target APN to be established in the ATTACH process. Thereby determining that the UE requests to establish a connected APN.

Step S104: The MME checks whether there is an APN-enabled congestion control mechanism in the APN requested by the UE. The open congestion control mechanism referred to in this document is the same as the standard definition mentioned in the background technology. If no APN is enabled to enable congestion control, the current normal process is performed. If there is an APN to enable congestion control, perform S105 or S106;

Step S105: According to the existing ATTACH procedure, the MME still attempts to establish a connection to the requested APN. If the connection is successful, step S109 is performed. If not successful, performing S107 or S108, preferably, if the MME knows that the UE supports the mobility management backoff timer and/or the session management backoff timer function, step S108 is performed;

Step S106, directly performing step S107 or S108 without attempting to connect with the requested APN. Preferably, if the MME knows that the UE supports the mobility management backoff timer and/or the session management backoff timer function, executing S108;

Step S107: The MME directly sends an attach reject ATTACH REJECT message to the UE, where the mobility management backoff timer is carried in the ATTACH REJECT message. According to the existing method, the ATTACH REJECT message and the request PDN reject message REQUEST PDN REJECT MESSAGE are simultaneously sent to the UE, and the MME also needs to carry the session management timer in the REQUEST PDN REJECT message;

Step S107-UE, for the UE, the UE considers that it does not have an ATTACH to the network. If the UE cannot understand the received mobility management backoff timer and session management timer, then the behavior of the UE will cause the behavior described in the prior art. If the UE can receive the understanding of the mobility management backoff timer and the session management timer, the UE cannot initiate an ATTACH request until the mobility management backoff timer expires. After the mobility management backoff timer expires, the ATTACH request is re-initiated. Before the session management timer expires, the connection request process to the previously determined APN cannot be initiated, but can be initiated. Attach request to other APNs. ⁸

Step S108: The ATTACH ACCEPT message is directly sent to the UE, and the mobility management backoff timer is carried in the ATTACH ACCEPT message. According to the existing method, the ATTACH ACCEPT message and the REQUEST PDN REJECT message are simultaneously sent to the UE, and the MME also needs to carry the session management timer in the REQUEST PDN REJECT message;

Step S108: The UE returns an ATTACH COMPLETE message to the MME after receiving the ATTACH ACCEPT message. The UE learns through the received REQUEST PDN REJECT message that the network has not established an APN connection to the UE for the request. After receiving the mobility management backoff timer and the session management timer, the UE cannot initiate a mobility management process such as TAU before the mobility management backoff timer expires. Before the session management timer expires, the UE cannot initiate the determination request. APN connection process. After both timers have timed out, if the UE has not established any APN connection, it needs to initiate the process of establishing a connection with the APN immediately.

Step S109: The ATTACH ACCEPT message is directly sent to the UE, and the mobility management backoff timer is carried in the ATTACH ACCEPT message. According to the existing method, the network sends the ATTACH ACCEPT message and the active default EPS context request ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to the UE at the same time. In this case, the MME also needs to carry the session management timer in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.

Step S109-UE, after receiving the ATTACH ACCEPT message, the UE returns an ATTACH COMPLETE message to the network. If the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message can be accepted, the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is returned to the network, which indicates that the APN is established. Connection. At this time, before the mobility management backoff timer expires, the UE cannot initiate a mobility management process such as TAU. Before the session management timer expires, the ESM process related to the connection of the APN that determines the request cannot be initiated, such as dedicated bearer activation. , carrying resource modification, etc. If it is unacceptable, it returns to activate the default EPS bearer context to reject the ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message to the network, and thereafter the UE behavior is performed according to step S108-UE.

Example 2 The embodiment according to the present embodiment the mobility management message is accepted ⁹ elimination location updating accept message, a location update procedure may involve the SGW (Serving Gateway, Serving Gateway) changes or does not change the scene, the present embodiment will not change SGW, When the network entity (MME/SGSN) that the network side communicates with the UE changes or does not change, a specific implementation manner is given.

For a scenario in which the network entity on the network side does not change, the network side sends a mobility management accept message to the UE according to whether the APN has enabled the congestion control mechanism, and the method includes: the first network entity determines that the SGW does not occur during the location update process of the UE. When the change is made, the APN that has established a connection with the UE before the location update is determined; when the first network entity determines that the APN with the UE has established a connection has an APN-enabled congestion control mechanism, the location update accept message is sent to the UE.

For the scenario in which the network entity on the network side changes, the network side sends the mobility management accept message to the UE according to whether the APN is enabled with the congestion control mechanism, and the method includes: before the location update process, determining, by the second network entity, the location update The UE is configured to acquire the bearer information of the UE from the first network entity when the UE is connected to the first network entity, and the second network entity determines, according to the acquired bearer information of the UE, The UE has established a connected APN; the second network entity determines that the APN has a congestion control mechanism in the APN that has established a connection with the UE, and sends a location update accept message to the UE.

Preferably, the second network entity determines that there is an APN-enabled congestion control mechanism in the APN in which the UE has established a connection, and sends a location update accept message to the UE, where: the second network entity determines that the APN that has established the connection with the UE is enabled to be congested. Controlling the APN of the mechanism, and indicating that the determined APN is congested by the SGW; the SGW does not need to send a modify bearer request message to the indicated APN that is congested according to the APN that is congested by the second network entity. Returning, to the second network entity, a first modified bearer response message, and returning a second modified bearer response message to the second network entity, where the second modified bearer response message is sent to the second network entity. The response message carries a reject reason code indicating that the APN is sent to the congestion-generating message; the second network entity deletes the bearer of the rejected APN and the rejected APN according to the received second modified bearer response message. Connecting; the second network entity determines to delete all the connections in the connection between the UE and the APN, and sends the location to the UE. Rejection message, and the message carries the rejected cell mobility The backoff timer is managed. Otherwise, the location update accept message carrying the mobility management backoff timer is sent to the UE.

Preferably, when the network side sends the location update reject message to the UE, the reason that the location update update message is carried in the location update reject message is that the allocating of the activated APN is congested. When the network side sends the location update accept message to the UE by deleting the connection between the UE and the APN, the network side implements the APN by the network side and the UE side by using the evolved packet system EPS bearer status in the location update accept message. The synchronization of the bearer. The network side specifically deletes the bearer of the APN and the connection to the APN through an actively initiated request de-connection process. After the network side sends the location update reject message, the network side further includes: the network side actively initiating a detach process to the UE.

The network side maintains the mobile reachable timer of the UE. The Mobile Reachable timer is started when the UE enters the IDLE state (ie, the idle state). When the UE and the network side establish a NAS (Non-Access Stratum, non-access stratum) When the signaling connection (the UE enters the connected state), the network side stops the Mobile Reachable timer.

When the periodic cell update timing timer of the UE times out, it is necessary to initiate a periodic location update process. The periodic location update timer is started after the UE enters the idle state, and stops when the UE and the network establish a signaling connection.

When the embodiment of the present invention is applied to the GPRS system, the location update process is specifically a routing area update process, the network entity is an SGSN, and the periodic location update timer is an RAU timer. When applied to the EPS system, the location update process is tracking. To the update process, the periodic location update timer is a TAU timer, and the network entity is the MME.

The following takes the EPS system as an example to describe the process of rejecting the mobility management process in the embodiment of the present invention. The embodiment is applied to the scenario where the SGW is unchanged, and specifically includes:

Step S201: The UE sends a tracking area update request TAU REQUEST message to the MME. According to the prior art, during the TAU request process, the MME activates all the established connection with the APN of the possible UE.

In step S202, the MME that receives the TAU request may be the MME that the UE is connected to before, or may be the new MME. If it is a new MME, step S205 is performed, if the MME does not change, the MME Determining that the SGW is not relocated (ie, the SGW does not need to be changed to ¹ ), the MME determines whether there is an APN in the APN that establishes a connection with the UE before the cell update, and the MME needs to perform step S203. If not, the current MME needs to perform the step S203. There is process processing;

Step S203: The MME sends a tracking area update accepting a TAU ACCEPT message to the UE, and carries a mobility management backoff timer to the UE in the TAU ACCEPT message.

The MME carries the mobility management backoff timer in the TAU ACCEPT message, specifically the mobility management backoff timer identifier and the duration thereof. In this step, the MME determines the mobility management backoff timer carried in the mobility management accept message. When the duration is greater than the duration of the mobile reachable timer of the UE maintained by the network side, the mobility reachable timer of the UE is restarted according to a value that is not less than the duration of the mobility management backoff timer.

Preferably, the MME further carries a periodic TAU timer and a duration thereof in the TAUACCEPT message, and the duration of the periodic TAU timer is not less than the duration of the mobility management backoff timer; the MME is not less than the period. The value of the duration of the sexual location update timer is restarted, and the mobility reachability timer of the UE is restarted.

Step S204: After receiving the TAU ACCEPT message carrying the mobility management backoff timer, the UE needs to start the mobility management backoff timer, and cannot initiate any mobility management process before the mobility management backoff timer expires. Only initiate mobility management processes related to priority services or emergency call services.

The UE determines that the duration of the mobility management backoff timer is greater than the duration of the periodic tracking area update timer, and when the periodic tracking timer needs to be started, the value of the mobility management backoff timer is not less than The periodic tracking timer is started.

Preferably, if the UE determines that the tracking area update accept message further carries a periodic tracking update timer and its duration, the periodic tracking area update timer duration in the tracking area update accept message is used to initiate periodic tracking. Zone update timer.

Step S205: The MME needs to acquire the bearer information of the UE from the old MME, and interacts with the SGW according to the EPS bearer related information of the UE from the old MME. At this time, the new MME needs to establish a connection with the UE before the tracking area update according to the bearer information of the UE. The APN, and determine which of these APNs APN ^{12 has} enabled congestion control mechanisms.

For example, the APA, the APNB, and the APNC are connected to the UE before the tracking area is updated. The MME determines that the congestion control mechanism is enabled on the APNB. The MME needs to perform the following processing: for the connection with the APNA and the APNC, according to the existing process. That is, the MME sends a modify bearer request Modify Bearer Request message to the SGW for the APNA and the APNC respectively. For the APNB, the MME needs to add a congestion indication to the Modify Bearer Request Modify Bearer Request message sent to the SGW, and the APN indication of the congestion control is turned on to the SGW.

Step S206: After receiving the Modify Bearer Request message, the SGW continues the subsequent process if there is no congestion indication. If there is a congestion indication, the APN (PGW corresponding to the APN) is subsequently processed according to whether to send the modified bearer Modify Bearer Request. If the Modify Bearer Request is required to be sent to the APN, the SGW directly sends a Modify Bearer Reponse (with Reject CAUSE CODE, or new source code) message carrying the reject reason code to the MME. If the Modify Bearer Request is not sent to the PGW, the SGW sends the Modify Bearer Reponse directly to the MME, indicating success.

Step S207: The new MME needs to perform different processing according to the content in the Modify Bearer Reponse message:

If the received Reason Bearer Reponse message carries a reject reason code, the new MME needs to delete the bearer of the rejected APN and the connection to the rejected APN. The specific deletion method can be processed according to the existing method. For example, it is performed by initiating a delete session request Delete Session Request message. At this time, although the PGW is already in a congested state, if a request such as deleting a bearer, deleting a session, or deleting a PDN connection is received, these deletion requests should not be rejected and should be handled according to the normal procedure.

If the MME finds that all connections in the connection established before the location update between the UE and the APN need to be deleted, it indicates that the TAU request needs to be rejected. At this step, step S208 is performed, and if at least one connection is not deleted, the TAU request may be accepted. , execute S209.

Step S208: The MME sends a TAU REJECT message to the UE, and the specific processing procedure is as follows:

The MME sends a TAU REJECT message to the UE, and carries a mobility management backoff timer to the UE in the TAU REJECT message. And use a new reason value to illustrate the network because of all the UE's Live PDN connection congestion occurs, can not establish a connection to carry all PDN υή ^3.

After receiving the TAU REJECT message carrying the mobility management backoff timer, the UE needs to start the mobility management backoff timer, which cannot initiate any mobility management procedure before the mobility management backoff timer expires. According to the new cause value, before the mobility management backoff timer expires, the UE can perform a connection establishment procedure to the APNs other than the APNA, the APNB, and the APNC, for example, the UE initiates a request to the APND connection.

After the mobility management backoff timer expires, if the UE has not established any APN connection, the UE needs to perform an attach ATTACH procedure, or a UE REQUEST CONNECTIVITY procedure to establish a default APN bearer. At this point, you can establish a connection to APNA, APNB, and APNC.

The step is 209, the MME sends a TAU ACCEPT message to the UE. The specific treatment is as follows:

The MME sends a TAU ACCEPT message to the UE, and carries a mobility management backoff timer to the UE in the TAU ACCEPT message.

Step S210: After receiving the TAU ACCEPT message carrying the mobility management backoff timer, the UE needs to start the mobility management backoff timer, and cannot initiate any mobility management process before the mobility management backoff timer expires. Only initiate mobility management processes related to priority services or emergency call services.

Determining, by the UE, that the mobility management backoff timer is longer than a periodic tracking area update timer The duration is such that when the periodic tracking timing needs to be started, the periodic tracking timer is started according to a value that is not less than the duration of the mobility management backoff timer.

Example 3

In the embodiment of the present invention, when the mobility management accept message is a location update accept message, the location update process may involve a scenario in which the SGW changes or does not change. In this embodiment, the SGW changes, and the network side communicates with the UE. A specific implementation is given when the network entity (MME/SGSN) changes or does not change.

In this embodiment, the network side sends a mobility management accept message to the UE according to whether the APN is enabled to perform the congestion control mechanism, and the method includes: determining, by the network side, that the serving gateway SGW changes in the location update process of the UE, before the location update and the UE Whether the APN has opened the congestion control mechanism in the connected APN, and sends a location update accept message to the UE.

When the SGW changes, the network entity that receives the cell update request sent by the UE may also not change, that is, the first network entity is connected before the UE cell update, and the network side that performs the location update process of the UE is the first network entity or the first The network entity that performs the foregoing denial mobility management process is the first network entity, and the scenario where the network entity changes, that is, the network side that performs the location update process of the UE is the second And the network entity further includes: the second network entity acquiring the bearer information of the UE from the first network entity, so as to be able to determine that the UE has established a connected APN.

In this embodiment, the network side sends a location update accept message to the UE according to whether the APN is enabled in the APN that has been connected to the UE before the location update, and the network side includes: the network side establishes a connection with the UE before determining the location update. In the APN, when the APN has enabled the congestion control mechanism, the bearer of the APN and the connection to the APN are deleted; when the network side determines that all the connections in the connection between the UE and the APN are deleted, the location update rejection message is sent to the UE, and Carrying a mobility management backoff timer in the location update reject message, otherwise, sending a mobility management backoff timer to the UE The location update accepts the message. ¹⁵

Preferably, when the network side sends the location update reject message to the UE, the reason that the location update update message is carried in the location update reject message is that the allocating of the activated APN is congested. When the network side deletes the connection between the UE and the APN to send the location update accept message to the UE, the network side also synchronizes the APN bearer between the network side and the UE side by using the EPS bearer status in the location update accept message. The network side deletes the bearer of the APN and the connection to the APN by using an actively initiated request de-connection process. After the network side sends the location update reject message, the network side further includes: the network side actively initiating a detach process to the UE.

Similarly, when the embodiment of the present invention is applied to the GPRS system, the location update process is specifically a routing area update process, the network entity is an SGSN, and the periodic location update timer is an RAU timer; when applied to the EPS system, the location update process is performed. To track the update process, the periodic location update timer is a TAU timer and the network entity is the MME.

The following is an example of the process of processing the mobility management process in the embodiment of the present invention. The embodiment is applied to the scenario in which the SGW changes.

Step S301, the UE sends a tracking area update request TAU REQUEST message to the MME. According to the prior art, during the TAU request process, the MME activates all the established connection between the UE and the APN.

Step S302: If the MME of the TAU request sent by the UE is changed, the context is requested by the context request/response CONTEXT REQUEST/RESPONSE process between the new and old MMEs, so that the new MME obtains the bearer information of the UE from the old MME. The MME receiving the TAU request, because it is determined that the SAW has changed, the MME needs to initiate a connection to the new SGW and the update process of the bearer. First, the MME needs to check whether there is an APN open congestion control mechanism in the APN that establishes a connection with the UE before the location update. If yes, the MME needs to perform step S303, otherwise it processes according to the existing process.

Step S303, this step illustrates how the MME reestablishes the connection and bearer update procedure to the SGW according to the APN-based congestion control when the SGW changes, and assumes that the UE has established three APN connections before initiating the current TAU: to the APNA, the APNB, and APNC connection. In the first case, the AP3 is currently connected to the UE. At least one APN does not have congestion control enabled. For example, the MME determines that the APNB has enabled the congestion control mechanism, and the congestion control mechanism is not enabled for the APNA and the APNC.

The MME performs the process of reestablishing the connection to the new SGW and the bearer update process for the APNA and the APNC that have not enabled the congestion control mechanism, that is, the MME sends a Create Session Request to the new SGW.

The MME is configured to prevent the APNB that is determined to be congested from being further congested by the APNB that has started the congestion control mechanism. The MME cannot perform the connection reestablishment and the bearer update process to the new SGW according to the existing procedure. In this embodiment, the MME needs to delete the connection to the APNB. Preferably, the MME uses the existing procedure "UE or MME requested PDN disconnection", that is, the MME actively initiates a request PDN connection process to delete the connection to the APNB.

Further, the MME uses the EPS STATUS IE in the existing TAU ACCEPT message to implement synchronization of the bearer information between the network side and the UE side, that is, in the EPS STATUS IE, does not include any bearer information connected to the APNB. Subsequent steps 304 and S305 are performed.

Case 2, that is, in the APN that previously established a connection with the UE, all APNs have a congestion control mechanism enabled. For example, at this time, the MME has started an APN-based congestion control mechanism for APNA, APNB, and APNC.

At this time, since the MME has already changed the SGW, the connection re-establishment and bearer update process to the new SGW cannot be performed according to the existing process, and all connections with the APN need to be deleted at this time. Preferably, the MME uses the existing procedure "UE or MME requested PDN disconnection", that is, the actively initiated request PDN de-connection process to delete the connection with the APNA, the APNB, and the APNC. Further, the MME may also initiate a de-attach DETACH procedure to detach the UE from the network. Subsequent steps S306 and S307 are performed.

Step S304: The MME sends a tracking area update accepting a TAU ACCEPT message to the UE, and carries a mobility management backoff timer in the TAU ACCEPT message.

The MME carries the mobility management backoff timer in the TAU ACCEPT message, specifically carrying the mobility management backoff timer identifier and the duration thereof. In this step, the MME determines that the mobility management accepts the cancellation. If the rf ⁷ length of the mobility management backoff timer carried in the information is greater than the duration of the mobility reachable timer of the UE maintained by the network side, the value of the duration of the mobility management backoff timer is not less than Restarting the mobility reachable timer of the UE

Step S305, the same step S210.

Step S305B: The UE returns a TAU COMPLETE message to the network according to the existing procedure.

Step S306, the MME sends a tracking area update reject TAU REJECT message to the UE, and carries a mobility management backoff timer to the UE in the TAU REJECT message. And a new cause value indicates that the network is unable to establish a bearer for all PDN connections for the UE because of congestion of all activated PDN connections of the UE.

Step S307: After receiving the TAU REJECT message carrying the mobility management backoff timer, the UE needs to start the timer, and cannot initiate any mobility management process before the timer expires. According to the new cause value, before the timer expires, the UE can perform a connection establishment procedure to the APN outside the APNA, APNB, and APNC connections, for example, initiating a UE requesting a connection request to the APN, requesting to establish a connection to the APND.

After the mobility management backoff timer expires, if the UE has not established a connection to any APN, the UE needs to perform an attach ATTACH procedure, or the UE requests to connect to the UE REQUEST CONNECTIVITY process to establish a connection to the default APN, which can be established to the APNA, APNB, APNC connection.

For the GPRS system, the method of rejecting mobility management and the method of retreating the mobility management process are the same as the above process.

Example 4

In this embodiment, the mobility management process of the UE is a detachment process initiated by the UE, and the mobility management accept message is a detachment accept message, and the network side starts the congestion control mechanism according to different APNs. Q

And sending, by the UE, the mobility management accept message, if the network side determines that the APN that is currently connected to the UE has an APN-enabled congestion control mechanism, and sends a detachment accept message carrying the mobility management evasion timer to the UE.

Specifically, for the APN subscribed by the UE, if the UE establishes a connection to the APN through the gateway node corresponding to the APN, it is determined that the APN is an activated APN.

Taking the EPS system as an example, the following steps are specifically included:

Step S401, the UE sends a detach request DETACH REQUEST message to the MME;

Step S402, the MME determines that the APN-enabled congestion control mechanism is established in the APN that is currently connected to the UE, and the MME carries the mobility management backoff timer in the detachment-receiving DETACH ACCEPT message sent to the UE.

Step S403: After discovering the mobility management backoff timer in the received DETACH ACCEPT message, the UE starts the mobility management backoff timer, and does not initiate an attach request message to the following APN before the mobility management backoff timer expires. : The APN activated in the APN that the UE subscribes to when the UE sends the detach request message.

For the GPRS system, the method for handling mobility management and the method for backoff of the mobility management process are the same as the above process, and the network entities on different network sides are SGSNs.

Example 5

In this embodiment, based on the foregoing embodiment, the method for rejecting the mobility management process is specifically: the network side decides to detach the UE from the network, and determines that the APN currently connected to the UE has an APN enabled. In the congestion control mechanism, the network side actively initiates a detach request to the UE, and carries a mobility management backoff timer in the detach request. In this embodiment, the UE receives the detach request message initiated by the network side to initiate the mobility management backoff timer; the UE starts the mobility management backoff timer, and stops before the mobility management backoff timer expires. An attach request to the APN activated by the UE when the detach request message is received.

For the EPS system, the following steps are specifically included:

Step S501: The MME determines to send the UE from the network to the DETACH. Before sending the DETACH REQUEST message to the UE, the MME determines that the APN that is currently connected with the UE has the APN enabled to be congested. The MME carries the mobility management backoff timer in the DE'iACH REQUEST message sent to the UE.

Step S502: After receiving the DETACH REQUEST, the UE sends a DETACH ACCPET message to the network according to a normal process. After the UE current DETACH REQUEST message includes the mobility management backoff timer, the mobility management backoff timer is started, and any APN activated on the UE when the DOTACH request message is received is not initiated before the mobility management backoff timer expires. ATTACH request message.

Example 6

In the service request process of the UE ( SERVICE REQUEST PROCEDURE ), the mobility management entity in the network also needs to perform the modification and update process of the bearer connection established by the UE to the APN.

Step S601: The UE sends a SERVICE REQUEST request message to the network.

Step S602, after the MME receives the message, the interaction between the mobility management node, the SGW, and the PGW may be updated by referring to the methods in steps S205 to S207 in Embodiment 2 to connect the PDN connection and the bearer at the MME. The specific process will not be described again.

After the update is completed, if the MME finds that all connections in the connection established between the UE and the APN need to be deleted, it indicates that the SERVICE REQUEST request needs to be rejected. At this step, step S603 is performed, and if at least one connection is not deleted, the MME can accept the connection. SERVICE REQUEST request, execute

S604.

Step 603: The network sends a SERVICE REJECT message to the UE, and carries a corresponding reason code. And carry the label and duration of the mobility management backoff timer.

Step 604, the process ends normally. In the existing method, if the network can establish a bearer, the corresponding response message is not sent to the UE, and the UE determines that the SERIVCE request process is successful according to the bearer establishment result.

The mobility management entity referred to herein refers to the MME and GPRS systems in the EPS system.

SGSN.

In the foregoing embodiment of the present invention, when the UE receives the TAU accept message, the timer is started. The mechanism is as follows: when the UE receives the attachment acceptance cancellation, the duration of the mobility management backoff timer is determined to be greater than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the mobility is not less than The duration of the grace management backoff timer is used to start the periodic tracking timer.

According to another embodiment of the present invention, a network side device that rejects the mobility management process is provided. As shown in FIG. 3, the method includes: a message sending unit 10, configured to use different APNs in the mobility management process of the UE. Whether the congestion control mechanism is enabled, and the mobility management accept message is sent to the UE; the timer carrying unit 20 is configured to carry the mobility management backoff timer in the sent mobility management accept message.

Preferably, the message sending unit 10 specifically includes any one or more of the following units: a first message sending unit, configured to send, in the attaching process of the UE, to the UE according to whether a different APN starts a congestion control mechanism And a second message sending unit, configured to: in the location update process of the UE, send a location update accept message to the UE according to whether a different APN starts a congestion control mechanism; and a third message sending unit, configured to De-attaching the process initiated by the UE, and sending a detach accept message to the UE according to whether the APN is enabled with a congestion control mechanism;

The timer carrying unit 20 includes any one or more of the following units: a first timer carrying unit, configured to carry a mobility management backoff timer in the attach accept message sent by the first message sending unit; a second timer carrying unit, configured to carry a mobility management backoff timer in the location update accept message sent by the second message sending unit, and a third timer carrying unit, configured to remove the detachment sent by the third message sending unit The acceptance message carries a mobility management backoff timer.

Preferably, the message sending unit 10 includes a first message sending unit, the timer carrying unit includes a first timer carrying unit, and the first message sending unit specifically includes: a first APN determining unit, configured to determine a UE The APN is requested to be connected in the attaching process. The first triggering unit is configured to send an attach accept message to the UE according to whether the APN that is requested to be connected is enabled, and trigger the first timer carrying unit to carry in the attach accept message. Mobility management backoff timer.

Preferably, the first APN determining unit is configured to send an attach accept message to the UE when the APN of the request connection is determined to be in a congestion control mechanism, where the network side device further includes: a fourth timer The bearer unit is configured to send a connection rejection message to the UE, and carry the session management backoff timer of the APN in the connection reject message.

Preferably, the first APN determining unit is specifically configured to determine the APN-enabled congestion control mechanism, and after attempting to establish a connection to the APN, send an attach accept message to the UE, where the network side device further includes: And a timer carrying unit, configured to send an activated evolved packet system EPS bearer context request message to the UE, and carry the session management backoff timer of the APN in the activated EPS bearer context request message.

Preferably, the message sending unit includes a second message sending unit, the timer carrying unit includes a second timer carrying unit, and the second message sending unit specifically includes: a second APN determining unit, configured to determine a location update The network-side device that is connected to the UE is not changed, and when the serving gateway SGW does not change during the location update process of the UE, the APN that has established a connection with the UE before the location update is determined; the second triggering unit is configured to determine When the APN has established a connection control mechanism with the APN, the UE sends a location update accept message to the UE, and triggers the second timer carrying unit to carry the mobility management backoff timer in the location update accept message.

Preferably, the message sending unit includes a second message sending unit, the timer carrying unit includes a second timer carrying unit, and the second message sending unit specifically includes: a bearer information acquiring unit, configured to determine a location update The network side device connected to the UE is changed, and the bearer information of the UE is obtained from the previous network side device when the SGW is not changed in the location update process of the UE; the third APN determining unit is configured to be configured according to the obtained The bearer information of the UE is used to determine an APN that has established a connection with the UE before the location update. The third triggering unit is configured to: when the APN with the UE that has established a connection with the APN has a congestion control mechanism, send a location update to the UE. Receiving the message, and triggering the second timer carrying unit to carry the mobility management backoff timer in the location update accept message.

Preferably, the third triggering unit specifically includes: a congestion indication unit, configured to determine an APN in which the congestion control mechanism is enabled in the APN in which the UE has established a connection, and instruct the SGW that the determined APN is congested, and the SGW is configured according to the SGW. The APN that is congested by the second network entity returns to the second network entity when the modified bearer request message is not sent to the indicated APN that is congested. Modify Bearer Response message back to the first, the need to refer to ² fe when congestion occurs in transmission APN bearer modification request message, the second return modify bearer response message to the second network entity, the second modified bearer response message carries represents Rejecting the rejection reason code of the APN sending message to the congestion; the first APN deleting unit is configured to delete the bearer of the rejected APN and the connection to the rejected APN according to the received second modified bearer response message; a message form determining unit, configured to send a location update reject message to the UE when the connection between the UE and the APN is deleted, and carry a mobility management backoff timer in the cell reject message, otherwise, to the UE And sending a location update accept message and triggering the second timer carrying unit to carry the mobility management backoff timer in the location update accept message.

Preferably, the message sending unit includes a second message sending unit, the timer carrying unit includes a second timer carrying unit, and the second message sending unit specifically includes: a fourth APN determining unit, configured to determine When the serving gateway SGW changes during the location update process of the UE, the APN that has established a connection with the UE before the location update is determined; and the fourth triggering unit is configured to send a location update to the UE according to whether the APN has enabled the congestion control mechanism before the location update. Accept the message.

Preferably, the fourth trigger determining unit specifically includes: a second APN deleting unit, configured to delete the bearer of the APN and the APN when the APN is enabled to connect to the APN before the location update is established. a second message form determining unit, configured to send a location update reject message to the UE when the connection between the UE and the APN connection is deleted, and carry the mobility management backoff timer in the location update reject message Otherwise, the location update accept message is sent to the UE and the second timer carrying unit is triggered to carry the mobility management backoff timer in the location update accept message.

Preferably, when the first message form determining or the second message form determining unit is specifically configured to send the location update reject message to the UE, the reason that the location update update reject message carries the indication that the UE location update is rejected is that all activated APNs are congested. .

Preferably, the first message form determining or the second message form determining unit is specifically configured to: when the connection of the part of the connection between the UE and the APN is deleted, send the location update accept message to the UE, and further pass the evolution in the location update accept message. The packet system EPS bearer status implements the APN on the network side and the UE side. The synchronization of the bearer. ^{twenty three}

Preferably, the first APN deleting unit or the second APN deleting unit is specifically configured to delete the bearer of the APN and the connection to the APN by using an actively initiated request de-connection process.

Preferably, the timer carries the mobility management back-off timer in the mobility management accept message, which is specifically carrying the mobility management back-off timer identifier and the duration thereof, and the network-side device further includes: a first mobile reachable timer a startup unit, configured to determine, when the mobility management backoff timer carried in the mobility management accept message is longer than the mobile reachable timer duration of the UE maintained by the network side, according to not less than the mobility The value of the duration of the backoff timer is managed, and the mobility reachable timer of the UE is restarted.

Preferably, the message sending unit includes a second message sending unit, and the timer carrying unit includes a second timer carrying unit, and further includes: a sixth timer carrying unit, configured to carry the periodic position in the location update accept message Updating a timer and a duration thereof, the duration of the periodic location update timer being greater than a duration of the mobility management backoff timer; and a second mobile reachable timer starting unit, configured to update according to not less than the periodic location The value of the duration of the timer restarts the mobility reachable timer of the UE.

Preferably, the message sending unit includes a third message sending unit, the timer carrying unit includes a third timer carrying unit, and the third message sending unit is specifically configured to determine that the APN currently establishing a connection with the UE has an APN. When the congestion control mechanism is enabled, the detachment accept message is sent to the UE, and the third timer carrying unit is triggered to carry the mobility management backoff timer in the sent detachment accept message.

Preferably, the network side device further includes: an active detaching unit 30, configured to determine to detach the UE from the network, and determine that an APN open congestion control mechanism is currently established in the APN that establishes a connection with the UE, and initiates The detach request is sent to the UE, and the mobility management backoff timer is carried in the detach request.

Preferably, the network side device further includes: a third APN deleting unit, configured to perform, during a service request process of the UE, when performing a modification and update process of the bearer that the UE has established the connection to the APN, determining that the UE has already Establish an APN in the connected APN to enable the congestion control mechanism, and delete the The bearer of the APN and the connection to the APN; the seventh-party: the bearer carrying unit, configured to send a service reject message to the UE when deleting all the connections in the connection between the UE and the APN, and in the service reject message Carry the mobility management backoff timer.

Preferably, the network side device is an MME in an SGSN or an EPS system in a GPRS system. The user equipment UE that implements the mobility management process backoff according to the embodiment of the present invention, as shown in FIG. 4, includes: an accepting message receiving unit 401, configured to receive mobile mobility management sent by the network side in the mobility management process. Mobility management acceptance message of the backoff timer; first timer starting unit

402, configured to start a mobility management backoff timer, and only initiate a mobility management process related to a priority service or an emergency call service before the mobility management timer expires; a second timer starting unit

403. The duration of the mobility management backoff timer is greater than the duration of the periodic location update timer. When the periodic tracking timer needs to be started, the value of the mobility management backoff timer is not less than , to start the periodic tracking timer.

Preferably, the mobility management process is a location update process, the mobility management accept message is a location update accept message, and the second timer initiating unit 403 is specifically configured to determine that the location update accept message further carries When the periodic location update timer and its duration are used, the periodic location update timer is started according to the duration of the periodic location update timer in the location update accept message.

Preferably, the mobility management process is a detachment process initiated by the UE, and the mobility management accept message is a detach accept message, and the first timer starting unit 402 is specifically configured to time out the timeout in the mobility management backoff timer. Before, the attach request of the APN activated by the UE when the detach request is sent is stopped.

Preferably, the method further includes: a request message receiving unit 404, configured to receive a detach request message carrying a mobility management backoff timer that is actively sent by the network side, where the first timer starting unit 402 is specifically configured to start the mobile The sex management backoff timer stops, before the timeout of the mobility management backoff timer, the attach request of the APN activated by the UE when the detach request message is received.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be applied to one or more of the packages Computer/storage media (including but not limited to disk storage, containing computer usable program code,

A form of a computer program product implemented on a CD-ROM (Compact Disc Read-Only Memory, optical storage, etc.).

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowcharts and/or block diagrams, and combinations of flow and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the preferred embodiment of the invention has been described, the subject matter Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and modifications The spirit and scope of the Ming. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

A method for processing a mobility management process, comprising:

The network side carries a mobility management backoff timer in the mobility management accept message.

2. The method of claim 1 wherein:

The mobility management process of the UE is an attach procedure, and the mobility management accept message is an attach accept message; or

The mobility management process of the UE is a location update process, and the mobility management accept message is a location update accept message; or

The mobility management process of the UE is a detach procedure initiated by the UE, and the mobility management accept message is a detach accept message.

The method of claim 2, wherein, when the mobility management accept message is an attach accept message, the network side sends the mobility management accept message to the UE according to whether the different APNs enable the congestion control mechanism, including:

Determining, by the first network entity, an APN that the UE requests to connect during the attaching process;

And the first network entity sends an attach accept message to the UE according to whether the APN starts a congestion control mechanism.

The method according to claim 3, wherein the first network entity sends an attach accept message to the UE according to whether the APN starts the congestion control mechanism, and the method includes:

And determining, when the APN starts the congestion control mechanism, sending an attach accept message to the UE, and further including:

Sending a connection reject message to the UE, and carrying the session management backoff timer of the APN in the connection reject message.

5. The method of claim 3, wherein the first network entity is according to the

Whether the APN starts the congestion control mechanism and sends an attach accept message to the UE, which specifically includes: After the APN is enabled to enable the congestion control mechanism, and the connection is successfully established, the connection accept message is sent to the UE, and the method further includes:

Sending an evolved packet system EPS bearer context request message to the UE, and carrying the session management backoff timer of the APN in the active EPS bearer context request message.

The method according to claim 2, wherein, when the mobility management accept message is a location update accept message, the network side sends a mobility management accept message to the UE according to whether the APN starts the congestion control mechanism, including :

Determining, by the first network entity, that the APN has established a connection with the UE before the location update, when the serving gateway SGW has not changed during the location update process of the UE;

When the first network entity determines that the APN with the UE has established a connection has an APN open congestion control mechanism, it sends a location update accept message to the UE.

The second network entity acquires, according to the location update process of the UE, the bearer information of the UE from the first network entity when the UE is connected to the first network entity and the SGW is not changed before the location update;

Determining, by the second network entity, the APN that has established a connection with the UE before the location update according to the acquired bearer information of the UE;

When the second network entity determines that the APN with the UE has established a connection has an APN open congestion control mechanism, it sends a location update accept message to the UE.

The method of claim 7, wherein the second network entity determines that the APN with the UE has established a connection has an APN-enabled congestion control mechanism, and sends a location update acceptance message to the UE, including:

The second network entity determines an APN in which the congestion control mechanism is enabled in the APN to which the UE has established a connection, and instructs the SGW that the APN that has established a connection with the UE is congested;

The SGW is not required according to the APN that is indicated by the second network entity and is congested. And when the modified bearer request message is sent to the indicated APN that is congested, the first modified bearer response message is returned to the second network entity, and when the modified bearer request message needs to be sent to the indicated APN that is congested, the second network entity is returned. The second modified bearer response message, where the second modified bearer response message carries a reject reason code indicating that the APN sending the message to the congestion is rejected;

The second network entity deletes the 7-load of the rejected APN and the connection to the rejected APN according to the received second modified bearer response message;

When the second network entity determines that all the connections in the connection between the UE and the APN are deleted, the location update reject message is sent to the UE, and the mobility management backoff timer is carried in the cell reject message, otherwise, the location is sent to the UE. Update acceptance message.

The network side determines whether there is an APN open congestion control mechanism in the APN that has established a connection with the UE before the location update in the location update process of the UE, and sends a location update accept message to the UE.

The method according to claim 9, wherein the network side sends a location update accept message to the UE according to whether the APN is enabled in the APN that has established a connection with the UE before the location update, and the method includes:

When the network side determines that the APN has established a congestion control mechanism in the APN that has established a connection with the UE before the location update, the 7-bit of the APN and the connection to the APN are deleted;

When the network side determines that all the connections in the connection between the UE and the APN are deleted, the location update reject message is sent to the UE, and the mobility management backoff timer is carried in the location update reject message, otherwise, the location update is sent to the UE. Accept the message.

The method according to claim 8 or 10, wherein, when the network side sends a location update reject message to the UE, the reason for carrying the location update update rejection message in the location update reject message is all activations. The APN is congested.

12. The method according to claim 8 or 10, wherein the network side is deleted When the connection between the part of the connection between the UE and the APN is sent to the UE, the synchronization of the APN bearer is performed on the network side and the UE side by using the evolved packet system EPS bearer status in the location update accept message.

The method according to claim 8 or 10, wherein the network side deletes the bearer of the APN and the connection to the APN by using an active initiated request to connect procedure.

The method according to claim 8 or 10, wherein, after the sending, by the network side, the update message, the method further includes:

The network side actively initiates a detach process to the UE.

The method according to any one of claims 6 to 10, wherein the network side carries a mobility management backoff timer in the mobility management accept message, specifically carrying the mobility management backoff timer identifier and its duration The method further includes: determining, by the network side, a duration of the mobility management backoff timer carried in the mobility management accept message, which is greater than a duration of the mobile reachable timer of the UE maintained by the network side, according to not less than The value of the duration of the mobility management backoff timer is started, and the mobility reachability timer of the UE is started.

The method according to claim 15, wherein when the mobility management process is a location update process, and the mobility management accept message is a location update accept message, the method further includes:

The network side further includes a periodic location update timer and a duration thereof, where the duration of the periodic location update timer is greater than the duration of the mobility management backoff timer; Not less than the value of the duration of the periodic location update timer, and the mobility reachability timer of the UE is started.

The method according to claim 2, wherein the mobility management process of the UE is a detachment process initiated by the UE, the mobility management accept message is a detach accept message, and the network side starts congestion according to different APNs. The control mechanism sends a mobility management accept message to the UE, including:

When the network side determines that the APN that is currently connected to the UE has an APN open congestion control mechanism, it sends a detach accept message to the UE.

18. The method of claim 1, further comprising:

The network side decides to detach the UE from the network, and determines the APN currently establishing a connection with the UE. When the APN has enabled the congestion control mechanism, the network side actively initiates a detach request to the UE, and carries a mobility management backoff timer in the detach request.

19. The method of claim 1, further comprising:

During the service request process of the UE, the network side needs to perform the process of modifying and updating the bearer that the UE has established the connection to the APN, determining the APN of the APN that is connected to the UE, and deleting the APN. Carrying and connecting to the APN;

When the network side determines that all the connections in the connection between the UE and the APN are deleted, the service reject message is sent to the UE, and the mobility management backoff timer is carried in the service reject message.

20. The method of claim 1, wherein the method is applied to a general packet radio service GPRS system or an evolved packet service EPS system.

21. A mobility management process backoff method, characterized in that:

The method of claim 21, wherein the mobility management process is a location update process, and the mobility management accept message is a location update accept message, further comprising:

The UE determines that the location update accept message further carries a periodic location update timer and its duration, and starts the periodic location update timer according to the duration of the periodic location update timer in the location update accept message.

The method according to claim 21, wherein the mobility management process is a detachment process initiated by the UE, the mobility management accept message is a detach accept message, and the UE is in the mobility management Before the backoff timer expires, the attachment request of the APN activated by the UE when the detach request is sent is stopped.

24. The method of claim 21, further comprising:

Receiving, by the UE, a detach request message that is sent by the network side and carrying a mobility management backoff timer; the UE starts the mobility management backoff timer, and stops starting to receive before the mobile management backoff timer expires The attachment request of the APN activated by the UE when the request message is attached.

A network-side device that rejects the mobility management process, comprising: a message sending unit, configured to: in a mobility management process of the user equipment UE, whether a congestion control mechanism is enabled according to different access point names APN, Sending a mobility management accept message to the UE;

The network side device according to claim 25, wherein the message sending unit comprises any one or more of the following units:

a first message sending unit, configured to send, in the attaching process of the UE, an attach accept message to the UE according to whether a different APN turns on a congestion control mechanism,

a second message sending unit, configured to send, in the location update process of the UE, a location update accept message to the UE according to whether a different APN starts a congestion control mechanism;

a third message sending unit, configured to send, in the detaching process initiated by the UE, a detaching accept message to the UE according to whether a different APN turns on a congestion control mechanism;

The timer carrying unit specifically includes any one or more of the following units:

a first timer carrying unit, configured to carry a mobility management backoff timer in the attach accept message sent by the first message sending unit;

a second timer carrying unit, configured to carry a mobility management backoff timer in the location update accept message sent by the second message sending unit;

The third timer carrying unit is configured to carry a mobility management backoff timer in the detach accept message sent by the third message sending unit.

The network side device according to claim 26, wherein the message sending unit includes a first message sending unit, the timer carrying unit includes a first timer carrying unit, and the first message sending unit Specifically include: a first APN determining unit, configured to determine an APN that the ui ² requests to connect in the attaching process, where the first triggering unit is configured to send an attach accept message to the UE according to whether the APN connected to the request is enabled to perform a congestion control mechanism, and trigger the first A timer carrying unit carries a mobility management backoff timer in the attach accept message.

The network side device according to claim 27, wherein the first APN determining unit is configured to: when determining that the APN requesting the connection to open the congestion control mechanism, send an attach accept message to the UE, where the network side The device also includes:

And a fourth timer carrying unit, configured to send a connection reject message to the UE, and carry the session management backoff timer of the APN in the connection reject message.

The network side device according to claim 27, wherein the first APN determining unit is specifically configured to determine that the APN opens a congestion control mechanism, and attempts to establish a connection to the APN, to the UE. Sending an attach accept message, the network side device further includes:

And a fifth timer carrying unit, configured to send an activating an evolved packet system EPS bearer context request message to the UE, and carry the session management backoff timer of the APN in the activated EPS bearer context request message.

The network side device according to claim 26, wherein the message sending unit includes a second message sending unit, the timer carrying unit includes a second timer carrying unit, and the second message sending unit Specifically include:

a second APN determining unit, configured to determine that the network side device connected by the UE before the location update is unchanged, and that the serving gateway SGW does not change during the location update process of the UE, determining that the UE has established a connection before the location update APN;

a second triggering unit, configured to send a location update accept message to the UE, and trigger a second timer carrying unit to be in the location update accept message, when the APN open congestion control mechanism is established in the APN that is connected to the UE. Carry the mobility management backoff timer.

The network side device according to claim 26, wherein the message sending unit includes a second message sending unit, the timer carrying unit includes a second timer carrying unit, and the second message sending unit Specifically include: a bearer information acquiring unit, configured to determine that the network side device connected to the UE is changed before the bit update, and acquires the bearer information of the UE from the previous network side device when the SGW is not changed in the location update process of the UE;

a third APN determining unit, configured to determine, according to the acquired bearer information of the UE, an APN that has established a connection with the UE before the location update;

a third triggering unit, configured to send a location update accept message to the UE, and trigger the second timer carrying unit to be in the location update accept message, when the APN with the UE that has established the connection has an APN-enabled congestion control mechanism Carry the mobility management backoff timer.

The network side device according to claim 31, wherein the third triggering unit specifically includes:

a congestion indication unit, configured to determine an APN in which the congestion control mechanism is enabled in the APN in which the UE has established a connection, and instructs the SGW that the determined APN is congested, and the SGW is congested according to the indication indicated by the second network entity. The APN, when it is not required to send the modify bearer request message to the indicated APN that is congested, return a first modified bearer response message to the second network entity, and when the modified bearer request message needs to be sent to the indicated APN that is congested, The second network entity returns a second modified bearer response message, where the second modified bearer response message carries a reject reason code indicating that the APN sending the message to the congestion is rejected;

a first APN deleting unit, configured to delete the 7-load of the rejected APN and the connection to the rejected APN according to the received second modified bearer response message;

a first message form determining unit, configured to: when a connection between the UE and the APN is deleted, send a location update reject message to the UE, and carry a mobility management backoff timer in the cell reject message, otherwise, The UE sends a location update accept message and triggers the second timer carrying unit to carry the mobility management backoff timer in the location update accept message.

a fourth APN determining unit, configured to determine a serving gateway SGW in a location update process of the UE When a change occurs, determine the APN that is connected to the UE ³ fc before the location update;

The fourth triggering unit is configured to send a location update accept message to the UE according to whether the APN has started the congestion control mechanism before the location update.

The network side device according to claim 33, wherein the fourth trigger determining unit specifically includes:

a second APN deleting unit, configured to determine, when the APN has a congestion control mechanism in the APN that has established a connection with the UE before the location update, deleting the bearer of the APN and the connection to the APN;

a second message form determining unit, configured to send a location update reject message to the UE when the connection between the UE and the APN is deleted, and carry the mobility management backoff timer in the location update reject message, otherwise, Sending a location update accept message to the UE and triggering the second timer carrying unit to carry the mobility management backoff timer in the location update accept message.

The network side device according to claim 32 or claim 34, wherein the first message form determining or the second message form determining unit is specifically configured to: when the location update reject message is sent to the UE, update the reject message at the location The reason for carrying the rejection of the UE location update is that all activated APNs are congested.

The network side device according to claim 32 or claim 34, wherein the first message form determining or the second message form determining unit is specifically configured to send a location to the UE by deleting a part of the connection between the UE and the APN. When the update accept message is sent, the synchronization of the APN bearer between the network side and the UE side is also implemented by the evolved packet system EPS bearer status in the location update accept message.

The network side device according to claim 32 or claim 34, wherein the first APN deleting unit or the second APN deleting unit is specifically configured to delete the ASN of the ASN and the The APN connection.

The network side device according to any one of claims 30 to 34, wherein the timer carries a mobility management backoff timer in the mobility management accept message, specifically carrying a mobility management backoff timer identifier. And the duration thereof, the network side device further includes:

a first mobile reachable timer starting unit, configured to determine a duration of the mobility management backoff timer carried in the mobility management accept message, which is greater than a mobile reachable timing of the UE maintained by the network side When the duration is longer, the mobility reachability timer of the UE is restarted according to a value that is not less than the duration of the mobility pipe if backoff timer.

The network side device according to claim 38, wherein the message sending unit includes a second message sending unit, the timer carrying unit includes a second timer carrying unit, and further includes: a sixth timer carrying unit And the duration of the periodic location update timer is greater than the duration of the mobility management backoff timer;

And a second mobile reachable timer starting unit, configured to restart the mobility reachable timer of the UE according to a value that is not less than a duration of the periodic location update timer.

The network side device according to claim 26, wherein the message sending unit includes a third message sending unit, the timer carrying unit includes a third timer carrying unit, and the third message sending unit Specifically, when the APN that is currently connected to the UE has an APN-enabled congestion control mechanism, the eNB sends a detachment accept message to the UE, and triggers the third timer carrying unit to carry the mobility management in the sent detachment accept message. Backoff timer.

The network side device according to claim 25, further comprising:

An active detachment unit is configured to determine to detach the UE from the network, and determine that an APN-enabled congestion control mechanism is currently established in the APN that establishes a connection with the UE, and initiates a detach request to the UE, and de-attaches the eNB. The request carries a mobility management backoff timer.

The network side device according to claim 25, further comprising:

The third APN deleting unit is configured to: when performing the tampering and updating process of the connection that the UE has established to the APN, in the service request process of the UE, determine that the congestion control mechanism is enabled in the APN that has established the connection with the UE. APN, and deleting the bearer of the APN and the connection to the APN; the seventh timer carrying unit is configured to send a service reject message to the UE when the connection between the UE and the APN is deleted, and The mobility rejection message carries the mobility management backoff timer.

The network side device according to claim 25, wherein the network side device is a serving GPRS support node SGSN or an evolved packet service EPS in a general packet radio service GPRS system. Mobility Management Entity MME in the system. ³⁶

A user equipment (UE) that implements a mobility management process backoff, and includes: an accepting message receiving unit, configured to receive mobility management of a mobility management backoff timer sent by a network side in a mobility management process Accept the message;

a first timer starting unit, configured to start a mobility management backoff timer, and only initiate a mobility management process related to a priority service or an emergency call service before the mobility management timer expires; a second timer starting unit The duration of the mobility management backoff timer is greater than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the value of the mobility management backoff timer is not less than The periodic tracking timer is started.

The UE according to claim 44, wherein the mobility management process is a location update process, the mobility management accept message is a location update accept message, and the second timer start unit is specifically configured to: When it is determined that the location update accept message further carries a periodic location update timer and its duration, the periodic location update timer is started according to the duration of the periodic location update timer in the location update accept message.

The UE according to claim 44, wherein the mobility management process is a detachment process initiated by the UE, and the mobility management accept message is a detach accept message, the first timer start unit, specifically And stopping to initiate an attach request of the APN activated by the UE when the detach request is sent before the mobility management backoff timer expires.

The UE according to claim 44, further comprising:

a request message receiving unit, configured to receive a detach request message that is sent by the network side and carries a mobility management backoff timer;

The first timer starting unit is specifically configured to start the mobility management backoff timer, and stop initiating the APN activated by the UE when receiving the detach request message before the mobility management backoff timer expires. Attach request.