WO2012041185A1 - Notification capability method and method, system and device for controlling network congestion - Google Patents

Abstract

An embodiment of the present invention relates to the technical field of wireless communication, and in particular to a notification capability method and a method, system and device for controlling network congestion. The invention is used to notify a terminal when said terminal can re-initiate an ATTACH process or a TAU process if a network side rejects an Attach or TAU request made by the terminal. A method for processing network congestion, as put forth in an embodiment of the present invention, comprises: the network side determining the duration of a mobility management back-off timer; and configuring on the terminal the duration of a mobility management back-off timer, once PDN congestion occurs, so as to instruct the terminal to re-initiate the Attach process or TAU process once the mobility management back-off timer expires. The network side can configure the mobility management back-off timer once APN congestion occurs, thereby ensuring that, if a network side rejects an Attach or TAU request made by the terminal, the terminal can re-initiate the ATTACH or TAU process once the mobility management back-off timer expires.

Description

 Method for notifying capability and method, system and device for network congestion control This application claims to be filed on September 28, 2010, the Chinese Patent Office, application number 201010296500.6, the invention name is "a method of notification capability and network congestion control" Method, system and equipment", and the Chinese patent filed on October 22, 2010, the Chinese Patent Office, application number 201010527919.8, the invention titled "a method of notification capability and methods, systems and equipment for network congestion control" Priority of the application, the entire contents of which are incorporated herein by reference. The present invention relates to the field of wireless communication technologies, and in particular, to a method for notifying capability and a method, system and device for network congestion control. Background technique

 In the existing MTC (Machine Type Communication) technology, due to the large number of MTC Devices (machine-type communication devices), it is necessary to consider the network congestion caused by the large amount of signaling and data transmission generated thereby. Therefore, in the 3GPP (3rd Generation Partnership Project), the Congestion Control feature for studying MTC communication is proposed.

 When the APN is congested, the network side rejects the terminal's Attach request or TAU (Tracking Area Update) request.

 Attach process:

 In LTE (Long Term Evolution) / SAE (System Architecture

Evolution, system architecture evolution) In the system, a PDN (Packet Data Network) connection must be established in the Attach process. This requires the terminal to initiate the PDN Connectivity Request process while initiating the Attach process. Existing Attach process The terminal carries the PDN Connectivity Request message in the ESM message container IE of the Attach Request message (EPS session management message container entity; EPS: Evolved Packet System, Evolved Packet System), at which point the PDN Connectivity Request message cannot be carried. APN (Access Point Name), so the network can initiate the PDN Connectivity Request procedure using the terminal's default (default) APN.

 If the terminal wants to provide the APN, you need to set the ESM information transfer flag in the PDN Connectivity Request message, so that the MME (Mobility Management Entity) will initiate the ESM after the Security Context is established. The information request (ESM Information Request) procedure, and the terminal then provides the APN in the ESM Information Response message. If the network allows the APN to be used, the APN is used to initiate the PDN Connectivity Request process.

 TAU process:

 The TAU process is divided into a process of carrying an active flag and a process of not carrying an active flag. If the TAU Request message carries an active flag, the network activates all active bearers of the UE after the TAU process is completed. The process is the same as the Service Request, but starts with the MME establishing the bearer.

 The shortcomings of the prior art are: After the network side rejects the Attach request or the TAU request of the terminal, the terminal does not know when to re-initiate the Attach process or the TAU process. Summary of the invention

 The embodiment of the invention provides a method, a system and a device for network congestion control, which are used to notify the terminal when to initiate an ATTACH process or a TAU process when the network side rejects the attach request or the TAU request of the terminal.

The embodiment of the present invention further provides a method and a device for notifying a capability, to notify the network side terminal whether the Mobility Management back-off timer for determining the time of re-initiating the Attach process or the TAU process is supported. Therefore, the network side can determine whether to configure the mobility management backoff timer according to the capability of the terminal. A method for processing network congestion provided by an embodiment of the present invention includes:

 The network side determines the duration of the mobility management backoff timer Mobility Management back-off timer;

 After the packet data network PDN is congested, the network side configures a duration of the mobility management backoff timer to the terminal, and is used to instruct the terminal to re-initiate the Attach Attach process or the trace region update TAU process after the mobility management backoff timer expires. .

 Another method for handling network congestion provided by the embodiment of the present invention includes:

 After the terminal rejects the attach process or the TAU process on the network side, the terminal starts the mobility management backoff timer according to the mobility management backoff timer configured by the network side;

 The terminal re-initiates the Attach process or the TAU process after the mobility management backoff timer expires.

 A network side device for processing network congestion provided by the embodiment of the present invention includes:

 a timer determining module, configured to determine a duration of the mobility management backoff timer;

 a configuration module, configured to: after the PDN is congested, configure a mobility management backoff timer to the terminal, to indicate that the terminal re-initiates the attach process after the mobility management backoff timer expires or

TAU process.

 A terminal for processing network congestion provided by the embodiment of the present invention includes:

 a startup module, configured to: after the network side rejects the attach process or the TAU process, start the mobility management backoff timer according to the duration of the mobility management backoff timer configured on the network side;

 The processing module is configured to re-initiate the Attach process or the TAU process after the mobility management backoff timer expires.

 A system for processing network congestion provided by an embodiment of the present invention includes:

 The network side device is configured to determine a duration of the mobility management backoff timer, and configure a duration of the mobility management backoff timer to the terminal after the PDN is congested;

a terminal, configured to start a mobility management backoff timer according to a mobility management backoff timer configured by the network side device after the network side device rejects the Attach process or the TAU process, and the mobility management backoff timer expires After that, re-initiate the Attach process or the TAU process. A method for notifying a capability provided by an embodiment of the present invention includes:

 Determining capability information, where the capability information is information indicating whether the terminal supports a mobility management backoff timer;

 The terminal sends the capability information to the network side, and is used to notify the network side to determine, according to the capability information, whether to configure a mobility management backoff timer for the terminal.

 A terminal for notifying the capability provided by the embodiment of the present invention includes:

 An indication information determining module, configured to determine capability information, where the capability information is information used to indicate whether the terminal supports a mobility management backoff timer;

 The indication information sending module is configured to send the capability information to the network side.

 The network side can configure the mobility management backoff timer for the terminal when the APN is congested, so that after the network side rejects the ATTACH request or the TAU request of the terminal, the terminal can re-initiate the ATTACH process or TAU after the mobility management backoff timer expires. The process improves the network efficiency. The terminal can inform the network side whether it supports the mobility management back-off timer. Therefore, the network side can determine whether to configure the mobility management back-off timer according to the capability of the terminal, thereby improving resource utilization. DRAWINGS

 1 is a schematic structural diagram of a system for network congestion control according to an embodiment of the present invention;

 2 is a schematic structural diagram of a network side device for network congestion control according to an embodiment of the present invention; FIG. 3 is a schematic structural diagram of a network congestion control terminal according to an embodiment of the present invention;

 4 is a schematic flowchart of a method for network congestion control according to an embodiment of the present invention;

 FIG. 5 is a schematic flowchart of a second method for network congestion control according to an embodiment of the present invention; FIG.

 6 is a schematic structural diagram of a terminal for notifying a capability according to an embodiment of the present invention;

 FIG. 7 is a schematic flowchart of a method for notifying capability according to an embodiment of the present invention. detailed description

The inventor noticed during the invention: At the SA2#80 meeting, NTT DoCoMo proposed an APN-based congestion control method to avoid and resolve congestion associated with a particular APN. The network starts the mobility management backoff timer according to whether the PGW (PDN Gateway, PDN Gateway) corresponding to the APN is congested, and instructs the MTC Device to initiate the access network or request the connection before the mobility management backoff timer expires. The request, its implementation steps are:

 The MME detects APN-based congestion according to certain criteria, including: a. Per APN (each APN) The maximum number of active EPS Bearers (EPS bearers, EPS: Evolved Packet System, Evolved Packet System);

 b. Per APN's EPS Bearer activation rate;

 c. The MME is unreachable to one or more PDN GWs or receives a congestion indication from these PDN GWs;

 When the APN requested in the attach procedure or the TAU process is in a congested state, the MME should reject the procedure and start the mobility management backoff timer, and indicate that the UE cannot initiate any Mobility Management procedure before the timer expires.

 However, the above content does not have a complete network congestion control scheme, and the inventors have also found that the current R10 previous version of the terminal does not support the mobility management backoff timer, and the network side does not know which terminals support the mobility management backoff timing. Which terminals do not support the mobility management backoff timer.

 The embodiment of the present invention solves the problem of how the terminal supports the mobility management backoff timer, and indicates to the network, after the network receives the indication, configures the duration of the mobility management backoff timer for the terminal, so as to effectively implement the APN-based congestion control mechanism. .

 Based on the above analysis, in the network congestion control scheme invented by the inventor, the network side can configure the mobility management backoff timer for the terminal when the APN is congested, thereby ensuring that the terminal can reject the ATTACH request or the TAU request of the terminal after the network side rejects the terminal. The ATTACH procedure or TAU procedure is re-initiated after the mobility management backoff timer expires.

In the solution of the notification capability invented by the inventor, the terminal can inform the network side whether it supports the mobility management backoff timer, so that the network side can determine whether to configure according to the capability of the terminal. Mobility management backoff timer.

 In the following description, the implementation of the cooperation between the network side and the terminal side will be described first. Finally, the implementations from the network side and the terminal side will be described separately, but this does not mean that the two must be implemented together. In fact, when the network When the side is separated from the terminal side, the problems existing on the network side and the terminal side are also solved, but when the two are combined, a better technical effect is obtained.

 The terminal mentioned in the embodiment of the present invention may be another device according to different application environments, for example, a UE (User Equipment) in LTE, and an MS (Mobile Station) in UTRAN or GERAN. .

 The embodiments of the present invention are further described in detail below with reference to the accompanying drawings.

 As shown in FIG. 1, the system for network congestion control in the embodiment of the present invention includes: a network side device 10 and a terminal 20.

 The network side device 10 is configured to determine the duration of the mobility management backoff timer, and configure the duration of the mobility management backoff timer to the terminal 20 after the PDN is congested.

 The duration of the specific mobility management backoff timer can be set as needed, or can be pre-defined in the protocol.

 The terminal 20 is configured to: after the network side device 10 rejects the Attach process or the TAU process, start the mobility management backoff timer according to the mobility management backoff timer configured by the network side device 10, after the mobility management backoff timer expires , Restart the Attach process or the TAU process.

 The network side device 10 does not know whether the terminal 20 supports the mobility management backoff timer. Therefore, the terminal 20 determines and transmits the capability information, where the capability information is used to indicate whether the terminal supports the mobility management backoff timer. information.

 Correspondingly, after receiving the capability information indicating whether the terminal supports the mobility management backoff timer, the network side device 10 determines whether the terminal 20 supports the mobility management backoff timer according to the capability information. After the PDN is congested, if the terminal 20 supports the mobility management backoff timer, the duration of the mobility management backoff timer is configured to the terminal 20. If the terminal 20 does not support the mobility management backoff timer, the mobility is not configured to the terminal 20. The length of time to manage the backoff timer.

If the method of >^ capability information is used on the terminal 20, the network side device 10 does not receive the terminal. The capability information of 20 is considered to be that the terminal 20 does not support the mobility management backoff timer, and does not configure the duration of the mobility management backoff timer to the terminal 20.

 For example, the capability information may be bit information, occupying 1 bit, then "1" may support the mobility management backoff timer, and "0" does not support the mobility management backoff timer. If the terminal 20 supports the mobility management backoff timer, "Γ is transmitted as capability information to the network side device 10; after receiving the "1", the network side device 10 knows that the terminal 20 supports the mobility management backoff timer.

 The capability information may also be the terminal version number information, and the terminal 20 reports its own version number. The network side device 10 may determine whether the terminal 20 supports the mobility management backoff timer according to the version number. If the version number of the terminal 20 is R10, it is determined. The terminal 20 supports the mobility management backoff timer. Specifically, it can be preset that "1" indicates that the version number is R10, and "0" indicates that the version number is not R10. If it is 1, the terminal 20 is determined to support the mobility management backoff timing. If it is 0, it is determined that the terminal 20 does not support the mobility management backoff timer.

 In a specific implementation, when reporting the capability information, the terminal 20 may directly send the capability information to the network side device 10, or may send the capability information in a message.

 For example, if the terminal 20 needs to re-initiate the attach process, the terminal 20 may send an Attach Request message carrying the capability information to the network-side device 10;

 If the terminal 20 needs to re-initiate the TAU procedure, the terminal 20 may send a TAU Request message carrying the capability information to the network side device 10.

 Specifically, if the terminal 20 is applied in an LTE (Long Term Evolution) system, the terminal 20 places the capability information in the terminal network capability information entity UE Network Capability IE of the Attach Request message or the TAU Request message (the terminal network capability information entity). ) in the field.

 For example, if the capability information is bit information, an MMbot indication bit may be added in the UE Network Capability IE field to indicate the capability information of the terminal 20.

A schematic diagram of the UE Network Capability IE field can be found in the protocol 3GPP TS 24.301 Non-Access-Stratum (NAS, Non-Access Stratum) rotocol for Evolved Packet System (EPS). The MMbot (Mobility Management back-off timer) indicator can occupy one or more spares in a graph (specifically, the bit size occupied by the capability information is determined), and the location in the figure can be as needed. Make settings. For example, in the 7th row and the 5th column. See Table 1 for details.

 Mobility Management back-off timer (MMbot) capability (octet 7, bit 5)

 (Mobility management backoff timer capability (7th byte, 5th bit)

0 MMbot not supported (mobility management backoff timer not supported)

1 MMbot supported (supports mobility management backoff timer)

 Table 1 User terminal network capability information

 For example, if the capability information is the terminal version number information, a "V" indication bit may be added in the UE Network Capability IE field to indicate the terminal version number information. A schematic diagram of the UE Network Capability IE field can be found in the protocol 3GPP TS 24.301 Non-Access-Stratum protocol for Evolved Packet System.

 The "V" indicator bit can occupy one or more spares in a picture (determined by the bits occupied by the capability information), and the position in the figure can be set as needed. For example, in the fifth column. See Table 2 for details.

 UE Version (octet 7, bit 5)

 (UE version (7th byte, 5th bit))

 0 not RlO UE (0 non-version 10 UE)

 1 R10 UE (1 version 10 UE)

 Table 2 User terminal network capability information

If the terminal 20 is applied to a UTRAN (UMTS Terrestrial Radio Access Network, UMTS: Universal Mobile Telecommunications System, Universal Mobile Telecommunications System) or GERAN (GSM/EDGE Radio Access Network, GSM/EDGE Radio Access Network; GSM: Global System for Mobile Communications; Global Mobile Telecommunications System; EDGE: Enhanced Data Rates for GSM Evolution, GSM Evolution Enhanced Data Rate), terminal 20 places capability information in Attach Request The mobile station network capability information entity in the MS Network Capability IE field of the message or TAU Request message.

 For example, if the capability information is bit information, an MMbot indication bit may be added in the MS Network Capability IE field to indicate the capability information of the terminal 20.

 A schematic diagram of the MS Network Capability IE field can be found in the protocol 3GPP TS 24.008 Mobile radio interface Layer 3 specification: Core network protocols (Mobile Network Layer 3 Interface Specification: Core Network Protocol).

 See Table 3 for details.

 MMbot capability (Mobility Management Backoff Timer Capability) This information field indicates if the MS supports the Mobility Management back-off timer (This information field indicates whether the MS supports the mobility management backoff timer)

0 Mobility Management back-off timer not supported

 1 Mobility Management back-off timer supported

 Table 3 Mobile Network Capability Information Entity

 For example, if the capability information is the terminal version number information, a "V" indication bit may be added in the MS Network Capability IE field to indicate the terminal version number information.

 A schematic diagram of the MS Network Capability IE field can be found in the protocol 3GPP TS 24.008 Mobile radio interface Layer 3 specification: Core network protocols.

 See Table 4 for details.

 MS Version capability

 (mobile station version capability)

 This information field indicates MS Edition information

 (This information field indicates MS version information)

 0 not R10 UE

 1 R10 UE

Table 4 Mobile station network capability information entity It should be noted that, the reporting capability information in the embodiment of the present invention is not limited to the foregoing manners of using the Attach Request message and the TAU Request message, and other manners capable of reporting capability information are applicable to the embodiments of the present invention.

 The advantage of reporting the Attach Request message and the TAU Request message is: When the request is initiated, the capability information can be immediately reported to the network measuring device 10, so that the duration of the mobility management backoff timer can be configured to the terminal 20 immediately after the PDN is congested. This saves time and resources.

 The network side device 10 may directly send the duration of the mobility management backoff timer to the terminal 20, or may send the duration of the mobility management backoff timer to the terminal 20 by using a message.

 For example, the network side device 10 needs to reject the request of the terminal 20 after the PDN is congested, so the duration of the mobility management backoff timer can be carried in the reject message.

 Specifically, if the terminal 20 needs to re-initiate the Attach process, the network side device 10 sends an Attach Reject message carrying the mobility management backoff timer to the terminal 20; if the terminal 20 needs to re-initiate the TAU process, the network side device 10 sends a TAU Reject message carrying the duration of the mobility management backoff timer to the terminal 20.

 It should be noted that, the duration of configuring the mobility management backoff timer in the embodiment of the present invention is not limited to the foregoing manners of using the Attach ejectt message and the TAU Reject message, and the manner in which the mobility management backoff timer can be configured is applicable. In the embodiment of the invention.

 The advantage of configuring the mobility management backoff timer by the Attach Reject message and the TAU Reject message is that the terminal 20 can receive the mobility management configured by the network side device 10 while determining that the network side device 10 rejects the Attach process or the TAU process. The duration of the backoff timer can be started immediately by the mobility management backoff timer, thereby ensuring that the duration of the mobility management backoff timer is configured to the terminal 20 at the fastest speed, saving time and resources.

After re-initiating the Attach process or the TAU process, if the PDN congestion is not released, and the duration of the mobility management backoff timer does not change, the network side device 10 may directly send a reject message, and then the terminal 20 restarts the timer; if mobility When the duration of the management backoff timer changes, the network side device 10 can send a reject message carrying the changed duration, and the terminal 20 starts the timer according to the new duration. The network side device in the embodiment of the present invention may be a base station (such as a macro base station, an evolved base station, a home base station, etc.), or may be an RN (relay) device, an MME, or other network side devices.

 Based on the same inventive concept, an embodiment of the present invention further provides a network side device for network congestion control, a network congestion control terminal, and a network congestion control method, and a network side device, a terminal, and a method for solving a problem and a network The systems of congestion control are similar. Therefore, the implementation of network-side devices, terminals, and methods can be referred to the implementation of the system.

 As shown in FIG. 2, the network side device of the network congestion control according to the embodiment of the present invention includes: a timer determining module 100 and a configuration module 110.

 The timer determining module 100 is configured to determine a duration of the mobility management backoff timer.

 The configuration module 110 is configured to configure a mobility management backoff timer to the terminal after the PDN is congested, and is used to instruct the terminal to re-initiate the attach process or the TAU process after the mobility management backoff timer expires.

 After the PDN is congested, the configuration module 110 receives the capability information indicating whether the terminal supports the mobility management backoff timer, and determines that the terminal supports the mobility management backoff timer according to the capability information, and configures the mobility management backoff timer to the terminal. The length of time.

 If the terminal needs to re-initiate the attach process, the configuration module 110 may send an Attach Reject message carrying the duration of the mobility management back-off timer to the terminal;

 If the terminal needs to re-initiate the TAU procedure, the configuration module 110 may send a TAU Reject message carrying the duration of the mobility management backoff timer to the terminal.

 As shown in FIG. 3, the terminal for network congestion control in the embodiment of the present invention includes: a startup module 200 and a processing module 210.

 The startup module 200 is configured to receive a duration of the mobility management backoff timer configured on the network side. After the network side rejects the Attach process or the TAU process, the mobility management backoff timer is started according to the mobility management timeout timer configured on the network side.

 The processing module 210 is configured to re-initiate the attach process or the TAU process after the mobility management backoff timer expires.

The terminal of the network congestion control in the embodiment of the present invention may further include: indication information The determination module 220 and the indication information transmitting module 230.

 The indication information determining module 220 is configured to determine capability information, where the capability information is information used to indicate whether the terminal supports the mobility management backoff timer.

 The indication information sending module 230 is configured to send the capability information determined by the indication information determining module 220 to the network side.

 If the terminal needs to re-initiate the attach process, the indication information sending module 230 may send an Attach Request message carrying the capability information to the network side;

 If the terminal needs to re-initiate the TAU procedure, the indication information sending module 230 may send a TAU Request message carrying the capability information to the network side.

 Further, if the terminal application is in the LTE system, the indication information sending module 230 may set the capability information in the UE Network Capability IE field of the Attach Request message or the TAU Request message;

 If the terminal application indicates that the information transmitting module 230 can be in the UTRAN or GERAN, the capability information is placed in the MS Network Capability IE field of the Attach Request message or the TAU Request message.

 As shown in FIG. 4, the method for network congestion control according to the first embodiment of the present invention includes the following steps: Step 401: The network side determines the duration of the mobility management backoff timer.

 The duration of the specific mobility management backoff timer can be set as needed, or can be pre-defined in the protocol.

 Step 402: After the PDN is congested, the network side configures a duration of the mobility management backoff timer to the terminal, and is used to instruct the terminal to re-initiate the attach process or the TAU process after the mobility management backoff timer expires.

Since the network side does not know whether the terminal supports the mobility management backoff timer, a preferred method is that the terminal sends capability information, and after receiving the capability information indicating whether the terminal supports the mobility management backoff timer, the network side according to the capability The information determines whether the terminal supports the mobility management backoff timer. After the PDN is congested, if the terminal supports the mobility management backoff timer, the terminal 20 is configured with the mobility management backoff timer. If the terminal does not support the mobility management backoff timer, The duration of the mobility management backoff timer is not configured to the terminal.

 If the capability information of the terminal is used, the network side does not receive the capability information of the terminal. It can be considered that the terminal does not support the mobility management backoff timer and does not configure the mobility management backoff timer for the terminal.

 The network side may directly send the duration of the mobility management backoff timer to the terminal, or may send the duration of the mobility management backoff timer to the terminal by using a message.

 For example, the network side needs to reject the request of the terminal after the PDN is congested, so the duration of the mobility management backoff timer can be carried in the reject message.

 Specifically, if the terminal needs to re-initiate the attach process, the network side sends an Attach reject Reject message carrying the duration of the mobility management back-off timer to the terminal;

 If the terminal needs to re-initiate the TAU procedure, the network side sends a TAU Rej ect message carrying the duration of the mobility management back-off timer to the terminal.

 It should be noted that, the duration of configuring the mobility management backoff timer in the embodiment of the present invention is not limited to the foregoing manners of using the Attach Reject message and the TAU Reject message, and the manner in which the mobility management backoff timer can be configured is applicable. In the embodiment of the invention.

 After re-initiating the Attach process or the TAU process, if the PDN congestion is not released, and the duration of the mobility management backoff timer does not change, the network side may directly send a reject message, and then the terminal restarts the timer; if the mobility management backoff timing If the duration of the device changes, the network side device may send a reject message carrying the changed duration, and the terminal starts the timer according to the new duration.

 The executor of the network side of the embodiment of the present invention may be a base station (such as a macro base station, an evolved base station, a home base station, etc.), or may be an RN device, an MME, or other network side devices.

 As shown in FIG. 5, the method for controlling network congestion control in the second embodiment of the present invention includes the following steps: Step 501: After the network side rejects the Attach process or the TAU process, the terminal manages the duration of the backoff timer according to the mobility configured on the network side. Start the mobility management backoff timer.

Step 502: After the mobility management backoff timer expires, the terminal re-initiates the Attach process or the TAU process. Since the network side does not know whether the terminal supports the mobility management backoff timer, a preferred method is that the terminal transmits capability information. Specifically, before step 501, the method further includes:

 Step a500: The terminal determines capability information, where the capability information is information used to indicate whether the terminal supports the mobility management backoff timer.

 Step b500: The terminal sends the capability information to the network side, and is used to notify the network side to determine, according to the capability information, whether the mobility management backoff timer is configured for the terminal.

 For example, the capability information is bit information, occupying 1 bit, then "1" can support the mobility management backoff timer, and "0" does not support the mobility management backoff timer. If the terminal supports the mobility management backoff timer, "Γ is sent as capability information to the network side.

 The capability information may also be the terminal version number information, and the terminal reports its own version number. The network side device can determine whether the terminal supports the mobility management backoff timer according to the version number. If the version number of the terminal is R10, it is determined that the terminal supports mobility. Manage the backoff timer; otherwise, determine that the terminal does not support the mobility management backoff timer.

 Specifically, it may be preset that "1" indicates that the version number is R10, and "0" indicates that the version number is not R10. If it is 1, it is determined that the terminal 20 supports the mobility management backoff timer. If it is 0, it is determined that the terminal 20 does not support. Mobility management backoff timer.

 In a specific implementation, when the terminal reports the capability information, the terminal may directly send the capability information to the network side, or may send the capability information in the message.

 For example, if the terminal needs to re-initiate the attach process, the terminal may send an Attach Request message carrying the capability information to the network side;

 If the terminal needs to re-initiate the TAU process, the terminal may send a TAU Request message carrying the capability information to the network side.

 Specifically, if the terminal is used in the LTE system, the terminal places the capability information in the UE Network Capability IE field of the Attach Request Information message or the TAU Request message.

If the terminal is applied in UTRAN or GERAN, the terminal places the capability information in the mobile station network capability information entity MS Network of the Attach Request message or the TAU Request message. Capability in the IE field.

 It should be noted that the reporting capability information in the embodiment of the present invention is not limited to the foregoing manners of using the Attach Request message and the TAU Request message, and other manners capable of reporting capability information are applicable to the embodiments of the present invention.

 The advantage of reporting the Attach Request message and the TAU Request message is that the capability information can be reported to the network test immediately after the request is initiated, so that the duration of the mobility management backoff timer can be configured to the terminal 20 immediately after the PDN is congested, thereby saving Time and resources.

 4 and 5 can be combined to form a new network congestion control method, that is, steps a500 and b501 are performed first, then steps 401 and 402 are performed, and steps 501 and 502 are finally executed.

 As shown in FIG. 6, the terminal for notifying the capability in the embodiment of the present invention includes: an indication information determining module 300 and an indication information sending module 310.

 The functions of the indication information determining module 300 and the indication information sending module 310 are the same as those of the indication information determining module 220 and the indication information sending module 230 in FIG. 3, and are not described herein again.

 As shown in FIG. 7, the method for notifying capability in the embodiment of the present invention includes the following steps:

 Step 701: The terminal determines capability information, where the capability information is information used to indicate whether the terminal supports the mobility management backoff timer.

 Step 702: The terminal sends the capability information to the network side, and is used to notify the network side to determine, according to the capability information, whether the mobility management backoff timer is configured for the terminal.

 The steps 701 and 702 are the same as the steps a500 and b500 in FIG. 5, and are not described here.

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 take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code. The present invention has been 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 flowchart illustrations and/or FIG. 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.

 Although the preferred embodiment of the invention has been described, it will be apparent to those skilled in the < Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and modifications

 The network side can configure the mobility management backoff timer for the terminal when the APN is congested, so that after the network side rejects the ATTACH request or the TAU request of the terminal, the terminal can re-initiate the ATTACH process or TAU after the mobility management backoff timer expires. Process, improving network efficiency.

 The terminal can inform the network side whether it supports the mobility management back-off timer, so that the network side can determine whether to configure the mobility management back-off timer according to the capability of the terminal, thereby improving resource utilization.

Obviously, those skilled in the art can make various modifications and variations to the present invention without departing from the invention. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Claims

Rights request

A method for processing network congestion, the method comprising:

 The network side determines the duration of the mobility management backoff timer Mobility Management back-off timer;

 After the packet data network PDN is congested, the network side configures a duration of the mobility management backoff timer to the terminal, and is used to instruct the terminal to re-initiate the Attach Attach process or the trace region update TAU process after the mobility management backoff timer expires. .

 The method according to claim 1, wherein the network side, before the PDN is congested, and before configuring the mobility management backoff timer to the terminal, further includes:

 The network side receives capability information indicating whether the terminal supports the mobility management backoff timer, and determines, according to the capability information, that the terminal supports the mobility management backoff timer.

 The method according to claim 1 or 2, wherein the length of the mobility management backoff timer is configured by the network side terminal, including:

 If the terminal needs to re-initiate the attach process, the network side sends an Attach reject Reject message carrying the mobility management back-off timer to the terminal;

 If the terminal needs to re-initiate the TAU procedure, the network side sends a TAU Reject message carrying the duration of the mobility management backoff timer to the terminal.

 A method for processing network congestion, the method comprising:

 After the terminal refuses the attach process or the TAU process on the network side, the terminal starts the mobility management backoff timer according to the duration of the mobility management backoff timer configured on the network side;

 After the mobility management backoff timer expires, the terminal re-initiates the attach process or the TAU process.

 The method according to claim 4, wherein the terminal further includes: determining, by the terminal, the terminal according to the mobility management backhaul timer configured by the network side before starting the mobility management backoff timer. Capability information;

The capability information is used to indicate whether the terminal supports the mobility management backoff timer. Information.

 The method according to claim 5, wherein the capability information is bit information or terminal version number information.

 The method according to claim 6, wherein the transmitting capability information of the terminal comprises: if the terminal needs to re-initiate an attach procedure, the terminal sends an Attach Request message carrying capability information to the network side. ;

 If the terminal needs to re-initiate the TAU process, the terminal sends a TAU Request message carrying the capability information to the network side.

 The method according to claim 7, wherein if the terminal is used in a Long Term Evolution (LTE) system, the terminal places capability information in a terminal network capability information entity UE Network of an Attach Request message or a TAU Request message. Capability in the IE field;

 If the terminal is applied in a universal mobile communication system terrestrial radio access network UTRAN or a GSM/EDGE radio access network GERAN, the terminal places the capability information in the mobile station network capability information entity MS of the Attach Request message or the TAU Request message. In the Network Capability IE field.

 A network side device for processing network congestion, wherein the network side device comprises: a timer determining module, configured to determine a duration of the mobility management backoff timer;

 The configuration module is configured to configure a mobility management backoff timer to the terminal after the PDN is congested, and is used to instruct the terminal to re-initiate the attach process or the TAU process after the mobility management backoff timer expires.

 The network side device according to claim 9, wherein the configuration module is further configured to:

 After the PDN is congested, before configuring the mobility management backoff timer to the terminal, the capability information indicating whether the terminal supports the mobility management backoff timer is received, and determining, according to the capability information, the terminal supports mobility management. Backoff timer.

The network side device according to claim 9 or 10, wherein the configuration module is specifically configured to: If the terminal needs to re-initiate the Attach process, send an Attach Reject message carrying the duration of the mobility management back-off timer to the terminal;

 If the terminal needs to re-initiate the TAU procedure, the terminal sends a TAU Reject message carrying the duration of the mobility management backoff timer.

 12. A terminal for handling network congestion, characterized in that the terminal comprises:

 a startup module, configured to: after the network side rejects the attach process or the TAU process, start the mobility management backoff timer according to the duration of the mobility management backoff timer configured on the network side;

 The processing module is configured to re-initiate the Attach process or the TAU process after the mobility management backoff timer expires.

 The terminal according to claim 12, wherein the terminal further comprises: an indication information determining module, configured to determine capability information, wherein the capability information is used to indicate whether the terminal supports a mobility management backoff timer Information;

 And an indication information sending module, configured to send the capability information to the network side.

 The terminal according to claim 13, wherein the indication information sending module is specifically configured to:

 If the terminal needs to re-initiate the attach process, send an Attach Request message carrying the capability information to the network side;

 If the terminal needs to re-initiate the TAU procedure, the TAU Request message carrying the capability information is sent to the network side.

 The terminal according to claim 14, wherein the indication information sending module is specifically configured to:

 If the terminal is used in the LTE system, the capability information is placed in the UE Network Capability IE field of the Attach Request message or the TAU Request message;

 If the terminal is applied in UTRAN or GERAN, the capability information is placed in the MS Network Capability IE field of the Attach Request message or the TAU Request message.

 16. A system for handling network congestion, characterized in that the system comprises:

The network side device is configured to determine the duration of the mobility management backoff timer. After the PDN is congested, The duration of configuring the mobility management backoff timer to the terminal;

 a terminal, configured to start a mobility management backoff timer according to a mobility management backoff timer configured by the network side device after the network side device rejects the Attach process or the TAU process, and the mobility management backoff timer expires After that, re-initiate the Attach process or the TAU process.

 17. A method of notifying capability, the method comprising:

 Determining capability information, where the capability information is information indicating whether the terminal supports a mobility management backoff timer;

 The terminal sends the capability information to the network side, and is used to notify the network side to determine, according to the capability information, whether to configure a mobility management backoff timer for the terminal.

 The method of claim 17, wherein the transmitting, by the terminal, the capability information to the network side includes:

 If the terminal needs to re-initiate the attach process, the terminal sends an Attach Request message carrying the capability information to the network side;

 If the terminal needs to re-initiate the TAU procedure, the terminal sends a TAU Request message carrying the capability information to the network side.

 The method according to claim 18, wherein, if the terminal is used in an LTE system, the terminal places capability information in a UE Network Capability IE field of an Attach Request message or a TAU Request message;

 If the terminal is used in UTRAN or GERAN, the terminal places the capability information in the MS Network Capability IE field of the Attach Request message or the TAU Request message.

 20. A terminal capable of notifying, wherein the terminal comprises:

 An indication information determining module, configured to determine capability information, where the capability information is information used to indicate whether the terminal supports a mobility management backoff timer;

 The indication information sending module is configured to send the capability information to the network side.

 The terminal according to claim 20, wherein the indication information sending module is specifically configured to:

If the terminal needs to re-initiate the Attach process, send a carrying capability letter to the network side. Attach Request message;

 If the terminal needs to re-initiate the TAU procedure, the TAU Request message carrying the capability information is sent to the network side.

 The terminal according to claim 21, wherein the indication information sending module is specifically configured to:

 If the terminal is used in the LTE system, the capability information is placed in the UE Network Capability IE field of the Attach Request message or the TAU Request message;

 If the terminal is applied in UTRAN or GERAN, the capability information is placed in the MS Network Capability IE field of the Attach Request message or the TAU Request message.