WO2013097503A1

WO2013097503A1 - Congestion control method and device

Info

Publication number: WO2013097503A1
Application number: PCT/CN2012/081968
Authority: WO
Inventors: 王胡成
Original assignee: 电信科学技术研究院
Priority date: 2011-12-30
Filing date: 2012-09-26
Publication date: 2013-07-04
Also published as: CN102413504B; CN102413504A

Abstract

The present invention relates to the technical field of wireless communications. Disclosed are a congestion control method and device, which are used to improve the success rate of a terminal accessing a network. In the present invention, when a congestion state of a current network restores and time corresponding to a mobility management back-off time value stored for congestion control is not reached, a network side device sets the stored mobility management back-off time value to invalid, and then, after receiving a mobility management request sent by the terminal, the network side device does not directly reject the mobility management request according to the mobility management back-off time value, that is to say, when the congestion state of the network restores, the mobility management request sent by the terminal will not be rejected by the network due to congestion control, thereby improving the success rate of the terminal accessing the network.

Description

Congestion control method and device The application is submitted to the Chinese Patent Office on December 30, 2011, the application number is 201110457449.7, and the invention name is

The priority of the Chinese Patent Application for "Congestion Control Method and Apparatus" is hereby incorporated by reference in its entirety. TECHNICAL FIELD The present invention relates to the field of wireless communications, and in particular, to a congestion control method and apparatus. BACKGROUND OF THE INVENTION The existing 3rd Generation Partnership Project (3GPP) protocol proposes an Access Point Name (APN) based APN based Mobility Management control mechanism.

According to the APN-based mobility management congestion control mechanism, the network performs APN-based mobility management congestion control on user equipment (UE) that subscribes to a special APN, and when the UE sends a mobility management (MM) request (request) When the network is connected to the network, the network determines whether to initiate the APN-based mobility management congestion control, and if so, sends the mobile management request rejection message to the UE, and may carry the mobility management backoff timer in the rejection message. The information of the -off timer is that after receiving the information of the mobility management backoff timer, the UE does not initiate an attach procedure other than the emergency service to the network before the mobility management backoff timer expires. At the same time, if the network side maintains the context of the UE, the mobility management backoff time value, that is, the timeout period of the mobility management backoff timer, is saved, and the network rejects the UE before the time corresponding to the mobility management backoff time value arrives. In addition to the emergency request of the emergency business.

The foregoing network determines that the APN-based mobility management congestion control is initiated as follows: The rate of the Mobile Management Non-Access Stratum (NAS) message sent by a group of UEs that have subscribed to the special APN exceeds a certain threshold or Dropped below a certain threshold; and/or, configuration in network management.

The existing 3GPP protocol also proposes a general NAS layer mobility management congestion control (General NAS Mobility Management Congestion Control) mechanism.

The mobility management congestion control of the NAS layer is common. When the UE sends a mobility management request to the network, if the network side has not established an emergency bearer context for the UE, the network determines whether to initiate the movement of the universal NAS layer. Management congestion control, if yes, sending a rejection message of the mobility management request to the UE, and carrying the information of the mobility management backoff timer in the rejection message, after receiving the information of the mobility management backoff timer, the UE starts the local The backoff timer, before the backoff timer expires, the UE cannot initiate any non-emergency service, non-high priority or mobile management request of the called service to the network. At the same time, the network side may save the mobile management The timeout value is the timeout period of the mobility management backoff timer. Before the time corresponding to the mobility management backoff time value arrives, the network rejects the mobility management request of any non-called service sent by the UE; if the network side is already the UE Once the emergency bearer context is established, the network can accept any mobility management request from the UE.

During the operation of the mobility management backoff timer, the UE in the connected state may initiate a Tracking Area Update (TAU) procedure.

The above judgment starts the general NAS layer mobile management congestion control based on the following: The network is in the General Overload Condition.

For a normal UE (ie, a non-high priority user) that does not have an emergency bearer service, if the mobility management backoff timer is running, the UE may initiate a mobility management request for the emergency bearer service, but the mobility management backoff The timer continues to run. The UE may initiate a mobility management request for the emergency bearer service during the operation of the mobility management backoff timer, the purpose of which is to consider that the network may have recovered from the congestion state before the mobility management backoff timer expires, so that the UE may receive the Mobile management request. This mechanism has been introduced in 3GPP TS 24.301.

However, if the mobility management request initiated by the UE is a service request (service request), a TAU, or a Routing Area Update (RAU) request, the NAS layer of the network cannot determine whether the mobility management request is for the emergency bearer service. Therefore, the network may still reject the mobility management request, making the mechanism impossible.

In the process of implementing the present invention, the inventors have found that the following technical problems exist in the prior art:

The congestion control method proposed by the 3GPP, by sending a mobility management backoff timer, prevents the terminal from initiating a mobility management request in the case of network congestion, and saves the mobility management backoff time value on the network side, and rejects the mobility management request initiated by the subsequent UE. . However, this method may bring the following problems: If the network has recovered from the congestion state before the time corresponding to the mobility management backoff time value arrives, the mobile management request initiated by the terminal will still be rejected by the network, thereby making the terminal unable to access normally. The internet. SUMMARY OF THE INVENTION The embodiments of the present invention provide a congestion control method and device, which are used to improve the success rate of a terminal accessing a network.

A congestion control method, the method comprising:

The network side device sets the mobility management backoff time value to be invalid after determining that the current network congestion state is restored and the time corresponding to the saved mobility management backoff time value for congestion control is not reached;

After receiving the mobility management request sent by the terminal, the network side device determines whether to accept the mobility management request according to the current network condition.

A congestion control device, the device comprising:

a first setting unit, configured to determine, in the congestion state of the current network, the saved and saved for congestion control After the time corresponding to the management backoff time value has not arrived, the mobile management backoff time value is set to be invalid; the control unit is configured to: after receiving the mobility management request sent by the terminal, determine whether to accept the mobile according to the current network condition. Manage requests.

In this solution, when the congestion status of the current network is restored and the time corresponding to the saved mobility management backoff time value for congestion control is not reached, the saved mobility management backoff time value is set to be invalid, and then received. After the mobility management request sent by the terminal, the mobile management request is no longer directly rejected according to the mobility management backoff time value, that is, when the network congestion state is restored, the mobility management request sent by the terminal is not rejected by the network due to congestion control, thereby improving The success rate of the terminal accessing the network. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic flow chart of a method for providing an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of a device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS In order to improve the success rate of a terminal accessing a network, the embodiment of the present invention provides a congestion control method. In this method, a network management device recovers from a current network congestion state and saves a mobility management backoff time for congestion control. When the time corresponding to the value does not arrive, the saved mobility management backoff time value is set to be invalid. Thereafter, after receiving the mobility management request sent by the terminal, the mobility management request is no longer directly rejected according to the mobility management backoff time value.

Referring to FIG. 1 , a congestion control method provided by an embodiment of the present invention includes the following steps:

Step 10: After determining that the current network congestion state is restored and the saved time corresponding to the mobility management backoff time value for congestion control is not reached, the network management device sets the mobility management backoff time value to be invalid.

Step 11: After receiving the mobility management request sent by the terminal, the network side device determines whether to accept the mobility management request according to the current network condition.

Specifically, when the terminal is a non-owned UE that is not attached to the network, and the congestion control initiated by the network-side device for the terminal is based on the mobile management congestion control of the APN subscribed by the terminal, in step 10, determining the current Whether the congestion status of the network is restored, the specific implementation can be as follows:

The network side device determines, according to the current network condition, whether a condition for starting the mobility management congestion control based on the APN of the terminal subscription is met, and if not, determining that the mobility management signaling of the terminal that has subscribed to the APN is on the network side. No congestion occurs, and congestion state recovery is determined. If yes, it is determined that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side, and it is determined that the congestion state is not restored. Here, the condition for starting the mobility management congestion control of the APN based on the subscription of the terminal is: the rate of the mobility management non-access stratum (NAS) message sent by the group of UEs that have subscribed to the special APN exceeds a certain threshold or is lowered. Below a certain threshold; and / or, in network management Configuration.

When the network-side device initiates the APN-based mobility management congestion control for the terminal, the network-side device may set the value of the first congestion control startup identifier corresponding to the APN, so that the first congestion control startup identifier indicates that the terminal is subscribed to the APN. Mobile management signaling is congested on the network side;

Correspondingly, the mobility management backoff time value is set to be invalid, and the specific implementation may be as follows: The network side device modifies the value of the first congestion control startup identifier, so that the first congestion control startup identifier indicates the mobility management of the terminal that has subscribed to the APN. Signaling does not occur on the network side.

Specifically, when the terminal is a terminal that is not attached to the network, and the congestion control initiated by the network-side device for the terminal is a general mobility management congestion control, in step 10, it is determined whether the current network congestion state is restored, and the specific implementation may be 3⁄4 mouth:

The network side device determines, according to the current network condition, whether the condition for starting the universal mobility management congestion control is met, and if not, determining that the network side device is not overloaded, and determining that the network congestion state is restored, if satisfied, Then, it is determined that the network side device is overloaded, and it is determined that the network congestion state is not restored. Here, the condition for starting the general mobility management congestion control is: The network managed by the network side device is in a general overload condition (General Overload Condition).

When the network side device starts the general mobility management congestion control for the terminal, the network side device may set the second congestion control startup identifier corresponding to the network side device, so that the second congestion control startup identifier indicates that the network side device is overloaded;

Correspondingly, the mobility management backoff time value is set to be invalid. The specific implementation may be as follows: The network side device modifies the value of the second congestion control startup identifier, so that the second congestion control startup identifier indicates that the network side device has not been overloaded.

Specifically, when the terminal is attached to the network (attached UE), and the congestion control initiated by the network side device for the terminal is general mobility management congestion control, in step 10, it is determined whether the current network congestion state is restored. The specific implementation can be as follows:

The network side device determines, according to the current network condition, whether the condition for starting the universal mobility management congestion control is met, and if not, determining that the network side device is not overloaded, and determining that the network congestion state is restored, if satisfied, Then, it is determined that the network side device is overloaded, and it is determined that the network congestion state is not restored.

Correspondingly, the mobility management backoff time value is set to be invalid, and the specific implementation may be as follows: If it is determined that the congestion state of the network managed by the network side device is restored, the network side device modifies the value of the second congestion control startup identifier to The second congestion control activation flag indicates that the network side device is not overloaded. Specifically, in the terminal that is not attached to the network, in step 11, determining whether to accept the mobility management request according to the current network status, the specific implementation may be as follows:

If the current second congestion control activation indicator indicates that the network side device is overloaded, the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the mobility management request, and if yes, starts Universal mobility management congestion control;

If the current second congestion control initiation identifier indicates that the network side device does not overload, and the first congestion control activation identifier corresponding to the one or more APNs that the terminal subscribes to indicates that the mobility management signaling of the terminal that has subscribed to the corresponding APN is If congestion occurs on the network side, the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached. If not, the mobile management request is rejected. If yes, the mobility management congestion control based on the one or more APNs is started. ;

If the current second congestion control initiation identifier indicates that the network side device is not overloaded, and the first congestion control startup identifier corresponding to all APNs subscribed by the terminal indicates that the mobility management signaling of the terminal that has subscribed to the corresponding APN is on the network side. If congestion does not occur, the network side device accepts the mobility management request.

Specifically, in the terminal attached to the network, in step 11, determining whether to accept the mobile management request according to the current network status, the specific implementation may be as follows:

If the current second congestion control activation indicator indicates that the network side device does not have an overload, the network side device accepts the mobility management request.

Further, after the step 11, the network side device determines that the current network is in the congestion state again, and may perform one of the following two operations:

First, if the time corresponding to the mobility management backoff time value does not arrive, the network side device sets the mobility management backoff time value to be valid. Specifically, if the mobility management signaling of the terminal that has subscribed to the APN is on the network side again If the congestion occurs, the first congestion control activation identifier corresponding to the APN is modified, so that the first congestion control startup identifier indicates that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side; if the network side device occurs again If the overload occurs, the second congestion control activation identifier corresponding to the network side device is modified, so that the second congestion control startup identifier indicates that the network side device is overloaded; and subsequently determining whether to accept the reception according to the mobility management backoff time value according to the prior art. The mobile management request sent by the terminal;

Second, if the time corresponding to the mobility management backoff time value has arrived or passed, the network side device starts the congestion control for the terminal again.

In the present invention, the first congestion control initiation identifier of the APN is used to indicate whether the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side; the second congestion control startup identifier of the network side device is used to indicate The Whether the network side device is overloaded. The initial value of the first congestion control initiation identifier needs to indicate that the mobility management signaling of the terminal that has subscribed to the APN does not have congestion on the network side, and the initial value of the second congestion control startup identifier needs to indicate that the network side device does not have an overload.

In the present invention, the network side device may be any device capable of performing congestion control such as an MME (Mobility Management Entity).

In the present invention, for a non-owned UE, the mobility management request is an attach request, and for the attached UE, the mobility management request is a request other than the attach request.

The present invention will be described below in conjunction with specific embodiments:

Embodiment 1:

This embodiment is directed to a non attached UE, which is specifically as follows:

Step 1, after receiving the attach request sent by the terminal, the MME determines that the condition of starting the mobility management congestion control of the APN based on the terminal subscription is met, and determines that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side. ;

Step 2: The MME sends a reject message rejecting the attach request to the terminal, where the reject message carries the information of the mobility management backoff timer; and the mobile management backoff time value is the timeout period of the mobility management backoff timer; and the APN is set. The value of the corresponding first congestion control initiation identifier is 1, to indicate that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side;

Step 3: After determining, according to the current network condition, that the MME does not meet the preset condition for starting the mobility management congestion control of the terminal-based APN, and the time corresponding to the saved mobility management backoff time value has not arrived, modify the first corresponding to the APN. The value of the congestion control startup identifier is 0, so that the mobility management signaling of the terminal that has subscribed to the APN does not cause congestion on the network side.

Step 4: After receiving the attach request sent by the terminal, the MME determines whether to accept the attach request according to the following method:

Method 1: If the current second congestion control initiation identifier indicates that the MME is overloaded, the MME determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the attach request, and if yes, initiates a general mobility Manage congestion control;

If the current second congestion control initiation identifier indicates that the MME does not have an overload, and the first congestion control initiation identifier corresponding to the one or more APNs that the terminal subscribes to indicates that the mobility management signaling of the terminal that has subscribed to the corresponding APN occurs on the network side. Congested, the MME determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the attach request, and if so, initiates mobility management congestion control based on the one or more APNs;

If the current second congestion control initiation identifier indicates that the MME does not have an overload, and the first congestion control initiation identifier corresponding to all APNs subscribed by the terminal indicates that the mobility management signaling of the terminal that has subscribed to the corresponding APN does not occur on the network side. Then, the MME accepts the attach request. Step 5: After the MME determines that the condition for starting the mobility management congestion control of the APN based on the terminal subscription is met again, if the time corresponding to the saved mobility management backoff time value does not arrive, the first congestion control corresponding to the APN is performed. The startup identifier is modified to 1 to indicate that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side, and then the attachment request sent by the terminal is received, and the attachment request is directly rejected according to the mobility management backoff time value. ; If the time corresponding to the saved mobility management backoff time value has arrived or passed, go to step 2.

Embodiment 2:

This embodiment is directed to a non attached UE, as follows:

Step 1: After receiving the attach request sent by the terminal, determining that the pre-set condition for starting the general mobility management congestion control is met, determining that the network managed by the terminal is in a congested state;

Step 2: Send a reject message rejecting the attach request to the terminal, where the reject message carries the information of the mobility management backoff timer; and save the mobility management backoff time value, that is, the timeout period of the mobility management backoff timer; The corresponding second congestion control startup identifier has a value of 1 to indicate that the fault occurs.

Step 3: After determining that the preset general mobility management congestion control condition is not met according to the current network condition, and the time corresponding to the saved mobility management backoff time value has not arrived, modifying the second congestion control startup identifier corresponding to the 拥The value of 0 is to indicate that the ΜΜΕ has not been overloaded;

Step 4: After receiving the attach request sent by the terminal, determine whether to accept the attach request according to the foregoing method 1;

Step 5: After determining that the pre-set condition of the general mobility management congestion control is met again, if the time corresponding to the saved mobility management backoff time value has not arrived, the second congestion control startup identifier corresponding to the UI is modified to 1 . In order to indicate that the ΜΜΕ has an overload, and then receives the attach request sent by the terminal, the acknowledgment request is directly rejected according to the mobility management backoff time value; if the saved mobility management backoff time value has not arrived or passed, then the step is 2.

Embodiment 3:

This embodiment is directed to the attached UE, as follows:

Step 1: After receiving the MM request sent by the terminal, determining that the pre-set condition for starting the universal mobile management congestion control is met, determining that the network managed by the MME is in a congested state;

Step 2: The MME sends a reject message rejecting the MM request to the terminal, where the reject message carries the information of the mobility management backoff timer; and the mobile management backoff time value is the timeout period of the mobility management backoff timer; and the MME is set. The value of the corresponding second congestion control initiation identifier is 1 to indicate that the MME is overloaded. Step 3: The MME determines, according to the current network status, that the preset mobility management congestion control condition is not met and the saved mobility management After the time corresponding to the backoff time value is not reached, the value of the second congestion control start identifier corresponding to the MME is changed to 0, indicating that the MME does not have an overload;

Step 4: After receiving the MM request sent by the terminal, the MME determines, according to the method 2, whether to accept the mobile tube. Request

Method 2: If the current second congestion control initiation identifier indicates that the MME is overloaded, the MME determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the MM request, and if yes, initiates general mobility management. Congestion control

If the current second congestion control initiation flag indicates that the MME has not experienced an overload, the MM request is accepted. Step 5: After the MME determines that the condition for starting the general mobility management congestion control is met again, if the time corresponding to the saved mobility management backoff time value does not arrive, the second congestion control startup identifier corresponding to the MME is modified to 1 . In order to indicate that the MME is overloaded, and then receives an attach request sent by the terminal, the attach request is directly rejected according to the mobility management backoff time value; if the saved mobility management backoff time value has not arrived or passed, then the step is 2.

Referring to FIG. 2, an embodiment of the present invention provides a congestion control device, where the device includes:

The first setting unit 20 is configured to set the mobility management backoff time value to be invalid after determining that the current network congestion state is restored and the time corresponding to the saved mobility management backoff time value for congestion control is not reached;

The control unit 21 is configured to determine, after receiving the mobility management request sent by the terminal, whether to accept the mobility management request according to the current network condition.

Further, the first setting unit 20 is configured to:

When the terminal is a terminal that is not attached to the network, and the congestion control initiated for the terminal is based on the mobile management congestion control of the access point name APN signed by the terminal, it is determined according to the current network condition whether the preset is satisfied. Starting the condition of the mobility management congestion control based on the APN, if not, determining that the mobility management signaling of the terminal that has subscribed to the APN does not cause congestion on the network side, and determining that the congestion state is restored, and if yes, determining that the contract is signed. The mobility management signaling of the terminal of the APN is congested on the network side, and it is determined that the congestion state is not restored.

Further, the device further includes:

a second setting unit 22, configured to: when the APN-based mobility management congestion control is initiated for the terminal, set a value of the first congestion control startup identifier corresponding to the APN, so that the first congestion control startup identifier indicates that the first congestion control startup identifier is The mobility management signaling of the terminal of the APN is congested on the network side;

The first setting unit 20 is configured to:

The value of the first congestion control initiation identifier is modified such that the first congestion control initiation identifier indicates that the mobility management signaling of the terminal that has subscribed to the APN does not cause congestion on the network side.

Further, the first setting unit 20 is configured to:

When the terminal is a terminal that is not attached to the network, and the congestion control initiated for the terminal is a general mobility management congestion control, it is determined according to the current network condition whether the preset universal mobility management congestion control is met. If the condition is not met, it is determined that the network side device is not overloaded, and the network congestion state is determined to be restored. If yes, it is determined that the network side device is overloaded, and the network congestion state is determined to be unrecovered. Further, the device further includes:

The third setting unit 23 is configured to: when the universal mobility management congestion control is started for the terminal, set a second congestion control startup identifier corresponding to the device, so that the second congestion control startup identifier indicates that the device is overloaded;

The first setting unit 20 is configured to:

The value of the second congestion control initiation identifier is modified such that the second congestion control activation identifier indicates that the device has not been overloaded.

Further, the first setting unit 20 is configured to:

When the terminal is a terminal that has been attached to the network, and the congestion control initiated for the terminal is a general mobility management congestion control, it is determined according to the current network condition whether the preset universal mobility management congestion control is met. If the condition is not met, it is determined that the network side device is not overloaded, and the network congestion state is determined to be restored. If yes, it is determined that the network side device is overloaded, and the network congestion state is determined to be unrecovered.

Further, the device further includes:

The fourth setting unit 24 is configured to: when the universal mobility management congestion control is started for the terminal, set a second congestion control startup identifier corresponding to the device, so that the second congestion control startup identifier indicates that the device is overloaded;

The first setting unit 20 is configured to:

Further, the control unit 21 is configured to:

If the current second congestion control activation indicator indicates that the network side device is overloaded, the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the mobility management request, and if yes, starts Universal mobility management congestion control; If the current second congestion control activation indicator indicates that the network side device does not have an overload, the network side device accepts the mobility management request.

Further, the device further includes:

The recovery unit 25 is configured to: after determining that the current network enters the congestion state again, set the mobility management backoff time value to be valid; and determine, according to the mobility management backoff time value, whether to accept the received mobility management request sent by the terminal. Or,

The congestion control is initiated again for the terminal.

An embodiment of the present invention further provides a mobility management entity (MME), where the MME includes the congestion control device. In summary, the beneficial effects of the present invention include:

In the solution provided by the embodiment of the present invention, the network side device sets the saved mobility management backoff time value to be invalid when the current network congestion state is restored and the time corresponding to the saved mobility management backoff time value for congestion control is not reached. After receiving the mobility management request sent by the terminal, the mobility management request is no longer directly rejected according to the mobility management backoff time value, that is, when the network congestion state is restored, the mobility management request sent by the terminal is not controlled by the network due to congestion. And refuse, thereby improving the success rate of the terminal accessing the network.

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 present invention can be embodied in the form of a computer program product embodied on one or more computer-usable storage interfaces (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing 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 process 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 are provided for implementing one or more processes and/or block diagrams in the flowchart The steps of the function specified in the box or in multiple boxes.

Although the preferred embodiment of the invention has been described, it will be apparent to those of ordinary skill in the art that <RTIgt; Therefore, the appended claims are intended to be construed as including the preferred embodiments and the modifications

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

Claims

A congestion control method, the method comprising:

2. The method according to claim 1, wherein the terminal is a terminal that is not attached to the network, and the congestion control initiated by the network side device for the terminal is an access point name APN based on the terminal subscription. When the mobility management congestion control is performed, the determining the congestion state recovery of the current network includes:

The network side device determines, according to the current network condition, whether a condition for starting the mobility management congestion control based on the APN is met, and if not, determining that the mobility management signaling of the terminal that has subscribed to the APN does not occur on the network side. Congestion, and determining congestion state recovery. If yes, it is determined that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side, and it is determined that the congestion state is not restored.

The method of claim 2, wherein when the network side device initiates the APN-based mobility management congestion control for the terminal, the method further includes: the network side device setting the first congestion control startup identifier corresponding to the APN Taking the value, and indicating that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side by using the first congestion control startup identifier;

And the setting, by the network side device, the value of the first congestion control startup identifier, and the first congestion control startup identifier indicates that the terminal that has subscribed to the APN is The mobility management signaling does not cause congestion on the network side.

The method according to claim 1, wherein when the terminal is a terminal that is not attached to the network, and the congestion control initiated by the network side device for the terminal is general mobility management congestion control, Determining the current state of congestion recovery for the network includes:

The method of claim 4, wherein when the network side device starts the universal mobility management congestion control for the terminal, the method further includes: the network side device setting the second congestion control startup identifier corresponding to the network side device, And indicating that the network side device is overloaded by the second congestion control startup identifier;

And the setting, by the network side device, the value of the second congestion control startup identifier, and the second congestion control startup identifier indicates that the network side device is not overloaded.

6. The method according to claim 1, wherein the terminal is a terminal that has been attached to a network, and When the congestion control initiated by the network side device for the terminal is a general mobility management congestion control, the determining the congestion state recovery of the current network includes:

The method of claim 6, wherein when the network side device initiates the universal mobility management congestion control for the terminal, the method further includes: the network side device setting the second congestion control startup identifier corresponding to the network side device, And indicating that the network side device is overloaded by the second congestion control startup identifier;

The setting the mobility management backoff time value to be invalid includes:

If it is determined that the congestion state of the network managed by the network side device is restored, the network side device modifies the value of the second congestion control startup identifier, and the second congestion control startup identifier indicates that the network side device management does not have an overload.

The method according to claim 3 or 5, wherein the determining whether to accept the mobility management request according to the current network condition comprises:

The method according to claim 7, wherein the determining whether to accept the mobility management request according to the current network condition comprises:

The method according to claim 1, wherein after determining whether to accept the mobility management request according to the current network condition, the method further includes: The network side device determines that the current network enters the congestion state again, sets the mobility management backoff time value to be valid, and determines whether to accept the received mobility management request sent by the terminal according to the mobility management backoff time value; or

The network side device initiates congestion control for the terminal again.

11. A congestion control device, the device comprising:

a first setting unit, configured to set the mobility management backoff time value to be invalid after determining that the current network congestion state is restored and the time corresponding to the saved mobility management backoff time value for congestion control is not reached;

The control unit is configured to determine, according to the current network condition, whether to accept the mobility management request after receiving the mobility management request sent by the terminal.

The device according to claim 11, wherein the first setting unit determines the congestion state recovery of the current network, and specifically includes:

The device of claim 12, further comprising:

a second setting unit, configured to: when the APN-based mobility management congestion control is initiated for the terminal, set a value of the first congestion control startup identifier corresponding to the APN, and indicate that the APN is signed by the first congestion control startup identifier The mobility management signaling of the terminal is congested on the network side;

The first setting unit is configured to:

The value of the first congestion control initiation identifier is modified, and the mobility management signaling indicating that the terminal that has subscribed to the APN is not congested on the network side by using the first congestion control activation identifier.

When the terminal is a terminal that is not attached to the network, and the congestion control initiated for the terminal is a general mobility management congestion control, it is determined according to the current network condition whether the preset universal mobility management congestion control is met. If the condition is not met, it is determined that the network side device is not overloaded, and the network congestion state is determined to be restored. If yes, it is determined that the network side device is overloaded, and the network congestion state is determined to be unrecovered.

The device according to claim 14, wherein the device further comprises:

a third setting unit, configured to: when a universal mobility management congestion control is initiated for the terminal, set a second congestion control startup identifier corresponding to the device, and indicate that the device is overloaded by the second congestion control startup identifier;

The first setting unit is configured to: The value of the second congestion control startup identifier is modified, and the second congestion control startup identifier indicates that the device is not overloaded.

The device according to claim 16, wherein the device further comprises:

a fourth setting unit, configured to: when a universal mobility management congestion control is initiated for the terminal, set a second congestion control startup identifier corresponding to the device, and indicate that the device is overloaded by the second congestion control startup identifier;

The first setting unit is configured to:

The value of the second congestion control startup identifier is modified, and the second congestion control startup identifier indicates that the device is not overloaded.

The device according to claim 13 or 15, wherein the control unit is configured to:

The device according to claim 17, wherein the control unit is configured to:

The device of claim 11, wherein the device further comprises: a recovery unit, configured to: after determining that the current network enters the congestion state again, setting the mobility management backoff time value to be valid; determining, according to the mobility management backoff time value, whether to accept the received mobility management request sent by the terminal; or,

The congestion control is initiated again for the terminal.

A mobility management entity, characterized in that it comprises a congestion control device according to any of claims 11-20.