CN109309946B

CN109309946B - Congestion control method, equipment and system

Info

Publication number: CN109309946B
Application number: CN201811202716.4A
Authority: CN
Inventors: 舒林; 弗兰克·马德曼; 张万强; 朱奋勤
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2012-09-29
Filing date: 2012-09-29
Publication date: 2021-04-20
Anticipated expiration: 2032-09-29
Also published as: WO2014047950A1; CN109219082A; CN104054377B; CN104054377A; CN109219082B; CN109309946A

Abstract

The embodiment of the invention provides a congestion control method, equipment and a system, which relate to the field of communication and can solve the problem that a network rejects an access request with a normal priority of UE when the congestion or overload control is carried out on the access request with a low priority of the UE. The method comprises the following steps: a mobile management network element receives a first request sent by UE, wherein the first request comprises first priority indication information, and the first priority indication information is used for identifying the priority of the first request; and determining whether to carry out congestion or overload control on the first request according to the receiving time of the first request, the first priority indication information and the time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information.

Description

Congestion control method, equipment and system

Technical Field

The present invention relates to the field of communications, and in particular, to a method, device, and system for congestion control.

Background

A large number of User Equipments (UEs) are commonly used for a Machine Type Communication (MTC) application. When a large number of UEs access the network, the network (which may be a mobility management network element and/or a gateway device) may suffer from congestion and overload, and in order to ensure that the network operates normally, congestion or overload control is performed, for example: when the UE accesses the network, the network may reject the access request of the UE. The current method comprises the following steps: when the network rejects the access request of the UE, a time indication message (back-off timer) may be saved, and the network rejects the access request from the UE within a time range indicated by the time indication message. When the network rejects the access request of the UE, the time indication information is provided for the UE, and the UE does not access the network within the time range indicated by the time indication information.

Compared with the mobile phone UE, the UE for MTC application mainly transmits service data when accessing the network, and has more tolerance in terms of access delay, so that the UE can be configured as a low priority UE, and when the UE is configured as a low priority UE, the access request message includes the low priority indication information, so that the network can recognize that the access request is of a low priority. If the network performs congestion or overload control, low priority access requests are first congestion or overload controlled before normal priority access requests are congestion or overload controlled.

However, currently, when the network only performs congestion or overload control on the low-priority access request, and a UE supporting dual-priority (both low-priority and normal-priority) sends the low-priority access request to the network, the network rejects the low-priority access request of the UE and stores a time indication message; the UE supporting dual priority may send the normal priority access request to the network within the time range indicated by the time indication information, and at this time, the network will reject the normal priority access request of the UE.

Disclosure of Invention

Embodiments of the present invention provide a method, a device, and a system for congestion control, which can solve the problem that a network rejects an access request with a normal priority of a UE when congestion or overload control is performed on an access request with a low priority of the UE.

In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:

in one aspect, an embodiment of the present invention provides a method for congestion control, where the method includes:

a mobility management network element receives a first request sent by User Equipment (UE), where the first request includes first priority indication information, and the first priority indication information is used to identify a priority of the first request;

and determining whether to carry out congestion or overload control on the first request according to the receiving time of the first request, the first priority indication information, the time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information.

In a first possible implementation manner of the first aspect, when the receiving time is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is lower than or equal to a priority indicated by the second priority indication information, it is determined to perform congestion or overload control on the first request.

In a second possible implementation manner of the first aspect, when the receiving time is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is higher than a priority indicated by the second priority indication information, it is determined to perform congestion or overload control on the first request; alternatively, the first and second electrodes may be,

and when the receiving moment is out of the time range indicated by the time indication information, determining to carry out congestion or overload control on the first request.

In a third possible implementation manner of the first aspect, when the receiving time is within a time range indicated by the time indication information and a priority indicated by the first priority indication information is higher than a priority indicated by the second priority indication information, it is determined that congestion or overload control is not performed on the first request; alternatively, the first and second electrodes may be,

when the receiving time is out of the time range indicated by the time indication information, determining not to carry out congestion or overload control on the first request.

With reference to the second possible implementation manner of the first aspect, in a fourth possible implementation manner, the method further includes:

and modifying the time indication information into newly specified time indication information, and modifying the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

In a fifth possible implementation manner of the first aspect, the method further includes: and the mobility management network element initially sets the time indication information and the second priority indication information.

With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, the method may be: after rejecting the second request of the UE, the time indication information and the second priority indication information are initially set, so that the priority indicated by the second priority indication information is the same as the priority of the second request.

With reference to the first aspect and the six possible implementation manners of the first aspect, in a seventh possible implementation manner, the first request is a mobility management request; or, the first request is a session management request, and the time indication information is time indication information corresponding to the UE and an Access Point Name (APN) selected by the UE.

With reference to the first aspect and the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner, the time indication information corresponding to the UE and the second priority indication information are stored in the mobility management element.

In a second aspect, an embodiment of the present invention provides a method for congestion control, where the method further includes:

when a low-priority access request of User Equipment (UE) is subjected to congestion or overload control, a mobile management network element receives a first request with normal priority sent by the UE;

according to the first request, the mobile management network element sends a session management message to the gateway equipment;

the session management message comprises identification information used for indicating that the UE is allocated with a bearer when a low-priority access request of the UE is subjected to congestion or overload control; so that the gateway device maintains, in the context of the bearer allocated for the UE, identification information indicating that the bearer is an allocated bearer when a low priority access request of the UE is subject to congestion or overload control.

In a first possible implementation manner of the second aspect, the identification information for indicating that the bearer is the bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control is saved in the generated charging data record of the bearer.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the receiving, by the mobility management network element, the first access request with a normal priority sent by the UE includes: and after the mobile management network element informs a wireless access network of performing extended access control (EAB) on the low-priority access request of the UE, the mobile management network element receives the first access request sent by the UE.

In a third possible implementation manner of the second aspect, the time of receiving the first request is within a time range indicated by the saved time indication information corresponding to the UE, and the priority of the first request of the UE is higher than the priority indicated by the priority indication information corresponding to the time indication information.

In a third aspect, an embodiment of the present invention provides a method for congestion control, where the method includes:

user Equipment (UE) determines that an access request with low priority is subjected to congestion or overload control;

the UE sends a first request to a mobile management network element, wherein the first request comprises indication information of requesting access when an access request with low priority is subjected to congestion or overload control; and the mobile management network element and the gateway equipment allocate the bearer for the UE, and store the identification information for identifying the bearer as the bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control in the context of the bearer.

In a first possible implementation manner of the third aspect, the first request further includes: priority indication information for identifying a priority of the first request; wherein the priority of the first request is a normal priority.

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, the determining that the access request with the low priority is subject to congestion or overload control includes:

the sent access request with low priority is rejected by the mobility management element, the mobility management element carries time indication information aiming at the UE in an access request response message, the UE starts a timer according to the time indication information, and the access request with low priority cannot be sent during the running period of the timer; or

Receiving indication information for enabling EAB for the low priority access request from a wireless communication network; or

The method includes that a sent low-priority Radio Resource Control (RRC) connection request message is rejected by a wireless communication network, the wireless communication network carries time indication information aiming at the UE in an RRC connection response message, the UE starts a timer according to the time indication information, and the UE cannot send the low-priority RRC connection request when the timer runs.

In a fourth aspect, an embodiment of the present invention provides a method for congestion control, where the method includes:

the method comprises the steps that gateway equipment receives a session management message sent by a mobile management network element, wherein the session management message comprises identification information used for indicating that load bearing is allocated to UE when a low-priority access request of the UE is subjected to congestion or overload control;

allocating a bearer for the UE and saving, in the context of the bearer, identification information indicating that the bearer is the bearer allocated when a low priority access request of the UE is subject to congestion or overload control;

and sending a session management response message to the mobile management network element, wherein the session management response message carries indication information of the bearer allocated to the UE.

In a first possible implementation manner of the fourth aspect, the method further includes: and storing identification information for indicating that the bearer is the bearer allocated to the UE when the low-priority access request of the UE is subjected to congestion or overload control in the generated charging data record of the bearer.

In a fifth aspect, an embodiment of the present invention provides a mobility management network element, where the mobility management network element includes:

a receiving unit, configured to receive a first request sent by a user equipment UE, where the first request includes first priority indication information; wherein the first priority indication information is used for identifying the priority of the first request;

and the processing unit is used for determining whether to carry out congestion or overload control on the first request according to the receiving time of the first request received by the receiving unit, the first priority indication information and the time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information.

In a first possible implementation manner of the fifth aspect, the processing unit is specifically configured to, when a receiving time at which the receiving unit receives the first request is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is lower than or equal to a priority indicated by the second priority indication information; determining to perform congestion or overload control on the first request.

In a second possible implementation manner of the fifth aspect, the processing unit is specifically configured to, when a receiving time at which the receiving unit receives the first request is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is higher than a priority indicated by the second priority indication information; determining to perform congestion or overload control on the first request; alternatively, the first and second electrodes may be,

when the receiving time when the receiving unit receives the first request is out of the time range indicated by the time indication information, determining to carry out congestion or overload control on the first request.

In a third possible implementation manner of the fifth aspect, the processing unit is specifically configured to, when a receiving time at which the receiving unit receives the first request is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is higher than a priority indicated by the second priority indication information; determining not to congestion or overload control the first request; alternatively, the first and second electrodes may be,

when the receiving time when the receiving unit receives the first request is out of the time range indicated by the time indication information, determining not to perform congestion or overload control on the first request.

With reference to the second possible implementation manner of the fifth aspect, in a fourth possible implementation manner, the processing unit is further configured to modify the time indication information to be newly specified time indication information, and modify the second priority indication information so that a priority indicated by the second priority indication information is the same as a priority indicated by the first priority indication information.

In a fifth possible implementation manner of the fifth aspect, the processing unit is further configured to initially set the time indication information and the second priority indication information.

With reference to the fifth possible implementation manner of the fifth aspect, in a sixth possible implementation manner, the processing unit is specifically configured to, after rejecting the second request of the UE, initially set the time indication information and the second priority indication information, so that a priority indicated by the second priority indication information is the same as a priority of the second request.

With reference to the fifth aspect and the above six possible implementation manners of the fifth aspect, in a seventh possible implementation manner, the mobility management network element further includes:

a storage unit, configured to store the time indication information and the second priority indication information corresponding to the UE.

In a sixth aspect, an embodiment of the present invention provides a mobility management network element, where the mobility management network element includes:

the device comprises a receiving unit, a judging unit and a judging unit, wherein the receiving unit is used for receiving a first request with normal priority sent by User Equipment (UE) when a low-priority access request of the UE is subjected to congestion or overload control;

a generating unit, configured to generate a session management message according to the first request received by the receiving unit, where the session management message includes identification information used to indicate that a bearer is allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control;

a sending unit configured to send the session management message generated by the generating unit to the gateway device; so that the gateway device maintains, in the context of the bearer allocated for the UE, identification information indicating that the bearer is an allocated bearer when a low priority access request of the UE is subject to congestion or overload control.

In a first possible implementation manner of the sixth aspect, the mobility management network element further includes a processing unit, configured to save, in the generated charging data record of the bearer, identification information indicating that the bearer is a bearer allocated when a low-priority access request of the UE is subjected to congestion or overload control.

With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner, the receiving unit is specifically configured to, when the low-priority access request of the UE is subjected to congestion or overload control, notify, by the mobility management network element, a radio access network to perform extended access control EAB for the low-priority access request of the UE, and then receive the first request sent by the UE.

In a third possible implementation manner of the sixth aspect, the receiving unit is specifically configured to, when a low-priority access request of the UE is subjected to congestion or overload control, receive the first request when the time of receiving the first request is within a time range indicated by saved time indication information corresponding to the UE, and a priority of the first request of the UE is higher than a priority indicated by priority indication information corresponding to the time indication information.

In a seventh aspect, an embodiment of the present invention provides a UE, where the UE includes:

a processing unit for determining that a low priority access request is subject to congestion or overload control;

a generating unit, configured to generate a first request when the processing unit determines that the low-priority access request is subjected to congestion or overload control, where the first request includes indication information that the low-priority access request is subjected to congestion or overload control and requests to access;

a sending unit, configured to send the first request generated by the generating unit to a mobility management network element; and the mobile management network element and the gateway equipment allocate the bearer for the UE, and store the identification information for identifying the bearer as the bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control in the context of the bearer.

In a first possible implementation manner of the seventh aspect, the first request generated by the generating unit further includes priority indication information, where the priority indication information is used to identify a priority of the first request; wherein the priority of the first request is a normal priority.

With reference to the seventh aspect or the first possible implementation manner of the seventh aspect, in a second possible implementation manner, the processing unit is specifically configured to reject, by the mobility management element, the low-priority access request sent by the UE, where the mobility management element carries time indication information for the UE in an access request response message, the UE starts a timer according to the time indication information, and during the running period of the timer, the low-priority access request cannot be sent; or

The sent RRC connection request message with low priority is rejected by a wireless communication network, the wireless communication network carries time indication information aiming at the UE in an RRC connection response message, the UE starts a timer according to the time indication information, and the UE cannot send the RRC connection request with low priority when the timer runs;

determining that the low priority access request is subject to congestion or overload control.

In an eighth aspect, an embodiment of the present invention provides a gateway device, where the gateway device includes:

a receiving unit, configured to receive a session management message sent by a mobility management network element, where the session management message includes identification information used to indicate that a bearer is allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control;

a processing unit, configured to allocate a bearer for the UE according to the session management message received by the receiving unit, and store, in a context of the bearer, identification information used for indicating that the bearer is allocated when a low-priority access request of the UE is subjected to congestion or overload control;

a generating unit, configured to generate a session management response message according to a processing result of the processing unit, where the session management response message carries indication information that the bearer has been allocated to the UE;

a sending unit, configured to send the first response message generated by the generating unit to the mobility management network element.

In a first possible implementation manner of the eighth aspect, the processing unit is further configured to save, in the generated charging data record of the bearer, identification information indicating that the bearer is the bearer allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control.

In a ninth aspect, an embodiment of the present invention provides a mobility management network element, where the mobility management network element includes:

a receiving module, configured to receive a first request sent by a user equipment UE, where the first request includes first priority indication information; wherein the first priority indication information is used for identifying the priority of the first request;

and the processor is used for determining whether to carry out congestion or overload control on the first request according to the receiving time when the receiving module receives the first request, the first priority indication information, the time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information.

In a first possible implementation manner of the ninth aspect, the processor is specifically configured to, when a receiving time at which the receiving module receives the first request is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is lower than or equal to a priority indicated by the second priority indication information; determining to perform congestion or overload control on the first request.

In a second possible implementation manner of the ninth aspect, the processor is specifically configured to, when a receiving time when the receiving module receives the first request is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is higher than a priority indicated by the second priority indication information; determining to perform congestion or overload control on the first request; alternatively, the first and second electrodes may be,

when the receiving time when the receiving module receives the first request is out of the time range indicated by the time indication information, determining to perform congestion or overload control on the first request.

In a third possible implementation manner of the ninth aspect, the processor is specifically configured to, when a receiving time when the receiving module receives the first request is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is higher than a priority indicated by the second priority indication information; determining not to congestion or overload control the first request; alternatively, the first and second electrodes may be,

when the receiving time when the receiving module receives the first request is out of the time range indicated by the time indication information, determining not to perform congestion or overload control on the first request.

With reference to the second possible implementation manner of the ninth aspect, in a fourth possible implementation manner, the processor is further configured to modify the time indication information to be newly specified time indication information, and modify the second priority indication information so that a priority indicated by the second priority indication information is the same as a priority indicated by the first priority indication information.

In a fifth possible implementation manner of the ninth aspect, the processor is further configured to initially set the time indication information and the second priority indication information.

With reference to the fifth possible implementation manner of the ninth aspect, in a sixth possible implementation manner, the processor is specifically configured to, after rejecting the second request of the UE, initially set the time indication information and the second priority indication information, so that a priority indicated by the second priority indication information is the same as a priority of the second request.

With reference to the ninth aspect and the first six possible implementation manners of the ninth aspect, in a seventh possible implementation manner, the mobility management network element further includes:

a register for storing the time indication information corresponding to the UE and the second priority indication information.

In a tenth aspect, an embodiment of the present invention provides a mobility management network element, where the mobility management network element includes:

the device comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for receiving a first access request with normal priority sent by User Equipment (UE) when a low-priority access request of the UE is subjected to congestion or overload control;

a processor, configured to generate a session management message according to the first request received by the receiving module, where the session management message includes identification information used to indicate that a bearer is allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control;

a sending module, configured to send the session management message generated by the processor to the gateway device; so that the gateway device maintains, in the context of the bearer allocated for the UE, identification information indicating that the bearer is an allocated bearer when a low priority access request of the UE is subject to congestion or overload control.

In a first possible implementation manner of the tenth aspect, the processor is further configured to save, in the generated charging data record of the bearer, identification information indicating that the bearer is a bearer allocated when a low-priority access request of the UE is subjected to congestion or overload control.

With reference to the tenth aspect or the first possible implementation manner of the tenth aspect, in a second possible implementation manner, the receiving module is specifically configured to, when a low-priority access request of a user equipment UE is subjected to congestion or overload control, notify, by the mobility management network element, a radio access network to perform extended access control EAB on the low-priority access request of the UE, and then receive the first request sent by the UE.

In a third possible implementation manner of the tenth aspect, the receiving module is specifically configured to, when a low-priority access request of the UE is subjected to congestion or overload control, receive the first request at a time within a time range indicated by saved time indication information corresponding to the UE, where a priority of the first request of the UE is higher than a priority indicated by priority indication information corresponding to the time indication information.

In an eleventh aspect, an embodiment of the present invention provides a UE, where the UE includes:

the processor is used for determining that the access request with low priority is subjected to congestion or overload control and generating a first request, wherein the first request comprises indication information of requesting access when the access request with low priority is subjected to congestion or overload control;

a sending module, configured to send the first request generated by the processor to a mobility management network element; and the mobile management network element and the gateway equipment allocate the bearer for the User Equipment (UE), and the identification information for identifying the bearer as the bearer allocated when the access request with the low priority of the UE is subjected to congestion or overload control is stored in the context of the bearer.

In a first possible implementation manner of the eleventh aspect, the first request generated by the processor further includes: priority indication information for identifying a priority of the first request; wherein the priority of the first request is a normal priority.

With reference to the eleventh aspect or the first possible implementation manner of the eleventh aspect, in a second possible implementation manner, the processor is specifically configured to be rejected by the mobility management element according to the sent low-priority access request, where the mobility management element carries time indication information for the UE in an access request response message, the UE starts a timer according to the time indication information, and during the running period of the timer, the low-priority access request cannot be sent; or

and determining that the access request with the low priority is subjected to congestion or overload control, and generating a first request, wherein the first request comprises indication information of requesting access when the access request with the low priority is subjected to congestion or overload control.

In a twelfth aspect, an embodiment of the present invention provides a gateway device, where the gateway device includes:

a receiving module, configured to receive a session management message sent by a mobility management network element, where the session management message includes identification information used to indicate that a bearer is allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control;

a processor, configured to allocate the bearer for the UE according to the session management message received by the receiving module, and store, in the context of the bearer, identification information indicating that the bearer is allocated when a low-priority access request of the UE is subjected to congestion or overload control; generating a session management response message, wherein the session management response message carries indication information of the bearer allocated to the UE;

a sending module, configured to send the first response message generated by the processor to the mobility management network element.

In a first possible implementation manner of the twelfth aspect, the processor is further configured to save, in the generated charging data record of the bearer, identification information indicating that the bearer is the bearer allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control.

In a thirteenth aspect, an embodiment of the present invention provides a system for congestion control, where the system includes: a mobility management network element of any possible implementation of the fifth aspect or the fifth aspect, or a mobility management network element of any possible implementation of the ninth aspect or the ninth aspect.

In a fourteenth aspect, an embodiment of the present invention provides a system for congestion control, where the system includes: a mobility management network element of any one of the possible implementations of the sixth aspect or the sixth aspect, a UE of any one of the possible implementations of the seventh aspect or the seventh aspect, a gateway device of any one of the possible implementations of the eighth aspect or the eighth aspect; or

A mobility management network element of any possible implementation of the tenth aspect or the tenth aspect, a UE of any possible implementation of the eleventh aspect or the eleventh aspect, a gateway device of any possible implementation of the twelfth aspect or the twelfth aspect.

The embodiment of the invention provides a method, equipment and a system for controlling congestion, wherein a mobile management network element can judge whether to control the congestion or overload of a request of UE according to a certain condition when the first request of the UE, time indication information corresponding to the UE and second priority indication information corresponding to the time indication information meet the certain condition; otherwise, rejecting the request of the UE. Therefore, the problem that the mobile management network element rejects the normal access request supporting the UE with double priorities when the network only carries out congestion or overload control on the access request with low priority can be solved. In addition, when the mobility management network element determines that the UE initiates the access request with normal priority when the access request with low priority is subjected to congestion or overload control, the session management message is sent to the gateway device, so that the gateway device allocates a bearer for the access request of the UE.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a flowchart illustrating a method for congestion control according to an embodiment of the present invention;

fig. 2 is a detailed flowchart of a method for congestion control according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating another congestion control method according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a method for congestion control according to another embodiment of the present invention;

fig. 5 is a block diagram illustrating a structure of a mobility management element according to an embodiment of the present invention;

fig. 6 is a block diagram schematically illustrating a structure of a mobility management element according to an embodiment of the present invention;

fig. 7 is a schematic block diagram of a mobility management element according to another embodiment of the present invention;

fig. 8 is a block diagram illustrating a structure of a user equipment according to another embodiment of the present invention;

fig. 9 is a block diagram schematically illustrating a structure of a user equipment according to another embodiment of the present invention;

fig. 10 is a schematic block diagram of a gateway device according to another embodiment of the present invention;

fig. 11 is a block diagram illustrating a structure of a mobility management element according to an embodiment of the present invention;

fig. 12 is a block diagram schematically illustrating a structure of a mobility management element according to an embodiment of the present invention;

fig. 13 is a schematic block diagram of a mobility management element according to another embodiment of the present invention;

fig. 14 is a block diagram schematically illustrating a structure of a ue according to another embodiment of the present invention;

fig. 15 is a block diagram illustrating a structure of a gateway device according to another embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

An embodiment of the present invention provides a method for congestion control, as shown in fig. 1, the method includes the following steps:

s101, a mobile management network element receives a first request sent by UE, wherein the first request comprises first priority indication information; wherein the first priority indication information is used to identify the priority of the first request.

In embodiments of the invention, the UE may be configured to support dual priority, i.e. low priority and normal priority network access. The UE may also be configured to support only low priority access network access.

In all embodiments of the present invention, the first request sent by the UE is embodied by a first request message, and when the mobility management element receives the first request message, where the first request message includes first priority indication information, the mobility management element processes the first request corresponding to the first request message.

For example, the first priority indication Information may be encapsulated in a Device Properties Information Element (Device Properties Information Element), where the first request message includes the Device Properties Information Element. For example: when the corresponding flag in the device attribute cell is set to "MS configured for NAS signaling low priority", the priority of the first request of the UE is low priority; when the corresponding flag in the device attribute cell is set to ' MS not configured for NAS signaling low priority ' in the MS not configured for NAS signaling low priority ', the UE indicates that the priority of the first request is a normal priority. In addition, the priority of the first request of the UE when the first priority indication information does not include the device attribute information element is a normal priority, or the priority of the first request of the UE when the first priority includes the device attribute information element but the device attribute information element does not have an identification bit for identifying the priority of the request is a normal priority.

The first request may be a mobility management request, and the corresponding first request message is a mobility management request message, and in the case of the mobility management request message, the first request may be: an Attach Request (Attach Request) message, a Routing Area Update Request (Routing Area Update Request) message, a Tracking Area Update Request (Tracking Area Update Request) message, a Service Request (Service Request) message, an extended Service Request (extended Service Request) message, and the like.

S102, the mobile management network element determines whether to carry out congestion or overload control on the first request according to the receiving time of the first request, the first priority indication information, the time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information.

The mobility management element may store the time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information in a context of the UE stored by the mobility management element or a table for storing time indication information; embodiments of the invention are not limited in this regard and may be stored in any memory.

Before the UE sends the first request, if congestion or overload control is performed on the UE and the request of the UE is rejected, the mobility management element may store, in a context of the UE that is stored by the mobility management element, time indication information corresponding to the UE and second priority indication information corresponding to the time indication information, where the time indication information is a duration or a time. Specifically, the time indication information is a time length, and the time indication information may be a timer. In addition, the mobility management element may further store the time indication information and the second priority indication information corresponding to the time indication information in a table for storing time indication information. Such time indication information may be referred to as mobility management time indication information in an embodiment of the present invention.

Before the UE sends the first request, the mobility management element performs congestion or overload control on the UE, which includes the following two cases.

In case one, when the mobility management element does not store the time indication information corresponding to the UE, the mobility management element receives a first request of the UE, and the mobility management element determines to perform congestion or overload control on the mobility management request of the UE, so that the mobility management element may store the time indication information corresponding to the UE and second priority indication information corresponding to the time indication information in a context of the UE stored by the mobility management element, where a priority indicated by the second priority indication information corresponding to the time indication information is a priority of the first request of the UE;

in case two, the mobility management element determines to perform congestion or overload control on the first request with low priority or normal priority according to the current network congestion or overload condition, and the mobility management element stores time indication information corresponding to the UE and priority indication information corresponding to the time indication information in the context of the UE stored by the mobility management element, wherein if the mobility management element determines to perform congestion or overload control on the first request with low priority, the priority indicated by the second priority indication information corresponding to the time indication information is low priority; and if the mobile management network element determines to perform congestion or overload control on the mobile management request with the normal priority, the priority indicated by the second priority indication information corresponding to the time indication information is the normal priority.

In the invention, when the mobility management network element performs congestion or overload control on the access request of the UE, the mobility management network element rejects the access request of the UE or discards the access request of the UE. When the mobile management network element does not carry out congestion or overload control on the access request of the UE, the mobile management network element receives the access request of the UE

Illustratively, the time indication information is specified by the mobility management element when the mobility management element performs congestion or overload control on the request of the UE. Specifically, the mobility management element specifies a time range or a time point identified by the time indication information.

When the mobility management network element performs congestion or overload control on the request of the UE and the request is a normal priority request, the second priority indication information indicates a normal priority. Specifically, the flag bit corresponding to the second priority indication information may be set to "the mobile station is not configured as a non-access stratum signaling low priority"; or

When the mobility management network element performs congestion or overload control on the request of the UE and the request is a low-priority request, the second priority indication information indicates low priority. Specifically, the flag bit corresponding to the second priority indication information may be set to "mobile station configured as non-access stratum signaling low priority".

In this embodiment of the present invention, the second priority indication information corresponding to the time indication information may be used to indicate that the time indication information is stored by the mobility management element performing congestion or overload control on the request of the priority identified by the second priority indication information. Thus, the second priority indication information may identify a reason why the time information is saved.

For example, an identification bit may be used to identify the second priority indication information, and specifically, the identification bit may be set to "mobile station configured as non-access stratum signaling low priority", which indicates that the time indication information is saved due to congestion or overload control on a low priority request; the flag may also be set to "mobile station not configured for non-access stratum signaling low priority" indicating that the time indication information is maintained due to normal priority requests for congestion or overload control.

In this embodiment of the present invention, the second priority indication information corresponding to the time indication information may also be reason indication information that the time indication information is stored, where the reason indication information is used to indicate that the time indication information is stored by a mobility management network element performing congestion or overload control on a request with the second priority being the priority indicated by the reason indication information.

For example, the mobility management element may use an identification bit to indicate the reason indication information corresponding to the Time indication information, and when the identification bit is set to "Time stored to low priority request", it indicates that the Time indication information is stored because the mobility management element performs congestion or overload control on a low priority request, in this case, the priority indicated by the second priority indication information corresponding to the Time indication information is low priority; when the flag is set to "Time is stored due to normal priority access request", it indicates that the Time indication information is stored due to congestion or overload control performed by the mobility management element on a normal priority request, and in this case, the priority indicated by the second priority indication information corresponding to the Time indication information is the normal priority.

In the embodiment of the present invention, the above-described expression is not limited, and other expressions may be used.

In addition, after the mobility management element receives the first request, the mobility management element may identify the priority of the first request of the UE through the first priority indication information, where the first priority is a low priority or a normal priority.

The following cases are described below to respectively describe whether to perform the congestion or overload control on the current request of the UE.

In the first case:

when the moment when the mobile management network element receives the first request is in the time range indicated by the time indication information and the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information, determining to perform congestion or overload control on the first request.

In all embodiments of the present invention, when the time indication information is a timer, if the time when the mobility management network element receives the first request is not expired by the timer, it indicates that the time when the first request is received is within the time range indicated by the time indication information. When the time indication information is time, if the time of receiving the first request is before the time indicated by the time indication information, the time of receiving the first request is within the time range indicated by the time indication information.

Optionally, when the mobility management element determines to perform congestion or overload control on the first request of the UE according to the load condition of the mobility management element and a congestion or overload control policy of the mobility management element, the mobility management element may reject the first request of the UE through the first request response, and specifically, may send a first request response message to the mobility management element to reject the first request of the UE.

For example, the condition that the mobility management element determines to perform congestion or overload control on the first request of the UE may be that the mobility management element determines to perform congestion control on the first request of the UE according to a congestion or overload condition or a congestion or overload control policy of a current network. For example, the mobility management element only performs congestion or overload control on a low-priority request, but the network congestion or overload condition is further aggravated, the mobility management element determines that congestion or overload control is also performed on a normal-priority request; that is to say, when the moment when the mobility management element receives the first request of the UE is within the time range of the time indication information of the UE stored by the mobility management element, and the second priority indication information corresponding to the time indication information is the low priority, and the priority indicated by the first priority indication information carried in the first request sent by the UE is the normal priority, in this case, the mobility management element can still perform congestion or overload control on the first request of the normal priority of the UE.

The first request response message may be a mobility management request response message, and when the first request response message is a mobility management request response message, the first request response message may be: an Attach Reject (Attach Reject) message, a Routing Area Update Reject (Routing Area Update Reject) message, a Tracking Area Update Reject (Tracking Area Update Reject) message, a Service Request Reject (Service Request Reject) message, and the like.

Further, the mobility management element modifies the time indication information into newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

For example, if there is time indication information corresponding to the UE and second priority indication information corresponding to the time indication information in the mobility management element, for example, the priority indicated by the second priority indication information is, for example, low priority, and the time when the mobility management element receives the first request is within the time range indicated by the time indication information, and the priority indicated by the first priority indication information is, for example, normal priority, that is, the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information. At this time, if the mobility management element determines to perform congestion or overload control on the first request of the UE according to the network condition, the mobility management element rejects the first request of the UE, modifies the time indication information into newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

The second priority indication information may further indicate, by an identification bit, reason indication information corresponding to the newly specified time indication information, where the identification bit is set to "time saved due to a low-priority access request" before modification, that is, the identification bit indicates a low priority; the flag bit is set to "time saved for normal priority access request" after modification, i.e., the flag bit indicates normal priority.

In this embodiment of the present invention, the first request to the UE is rejected, the mobility management network element modifies the time indication information to be newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information. However, the embodiment of the present invention is not limited thereto, and may also be another implementation method: that is, the mobility management element deletes the stored time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information, and the mobility management element stores the newly specified time indication information and the second priority indication information corresponding to the newly specified time indication information, and the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

The second priority indication information may further indicate the reason indication information corresponding to the time indication information through an identification bit, for example, if the priority of the first request of the UE is a low priority, the identification bit may be set to "time saved due to a low priority access request", that is, the identification bit indicates a low priority; if the first request of the UE is of normal priority, the flag may be set to "time saved due to the access request of normal priority", that is, the flag indicates normal priority.

In the second case:

and when the moment when the mobile management network element receives the first request is out of the time range indicated by the time indication information, determining to carry out congestion or overload control on the first request.

Optionally, when the mobility management element determines that the first request of the UE is congestion or overload controlled according to the load condition of the mobility management element and a congestion or overload control policy of the mobility management element, the mobility management element rejects the first request of the UE through the first request response message.

For example, if time indication information corresponding to the UE and second priority indication information corresponding to the time indication information exist in the mobility management element; and the moment when the mobile management network element receives the first request is out of the time range indicated by the time indication information; at this time, if the mobility management element determines to perform congestion or overload control on the first request of the UE according to the network condition, the mobility management element rejects the first request of the UE, modifies the time indication information into newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

It should be noted here that, in the second case, the second priority indication information may be a low priority or a normal priority, and the first priority indication information carried in the first request may be a low priority or a normal priority.

In the third case:

when the moment when the mobility management network element receives the first request is in the time range indicated by the time indication information and the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information, determining not to perform congestion or overload control on the first request, and the mobility management network element accepts the first request.

Optionally, when the mobility management element determines not to perform congestion or overload control on the first request of the UE according to the load condition of the mobility management element and a congestion or overload control policy of the mobility management element, the mobility management element may receive the first request of the UE through the first request response, specifically, the mobility management element may receive the first request of the UE through sending the first request response message.

For example, the case that the mobility management element determines not to perform congestion or overload control on the first request of the UE may be that the mobility management element determines not to perform congestion control on the first request of the UE according to a congestion or overload condition or a congestion or overload control policy of a current network. For example, the mobility management element only performs congestion or overload control on the low-priority request, but the network congestion or overload condition is not further aggravated, and then the mobility management element still performs congestion or overload control on the low-priority request; that is to say, when the moment when the mobility management element receives the first request of the UE is within the time range of the time indication information of the UE stored by the mobility management element, and the second priority indication information corresponding to the time indication information is a low priority, and the priority indicated by the first priority indication information carried in the first request sent by the UE is a normal priority, that is, the priority indicated by the first priority indication information carried in the first request of the UE is higher than the priority indicated by the second priority indication information corresponding to the time indication information, in this case, the mobility management element may not perform congestion or overload control on the first request of the normal priority of the UE.

Further, the method further comprises: accepting a first request by the UE.

And when the first request is a mobility management request, the mobility management network element performs subsequent flow processing of the corresponding mobility management request according to the type of the mobility management request message of the UE. For example, when the mobility management request message corresponding to the request is an attach request message, the mobility management network element performs authentication, location update, bearer establishment, and the like of the UE. And after the flow corresponding to the mobile management request is completed, the mobile management network element sends a mobile management request response message to the UE, wherein the mobile management request response message indicates that the request of the UE is accepted. The mobility management Request response message may be an Attach Accept/Reject (Attach Accept/Reject) message, a Routing Area Update Accept/Reject (Routing Area Update Accept/Reject) message, a Tracking Area Update Accept/Reject (Tracking Area Update Accept/Reject) message, a Service Request Accept/Reject (Service Request Accept/Reject) message, or the like.

In a fourth case:

Optionally, when the mobility management element determines not to perform congestion or overload control on the first request of the UE according to the load condition of the mobility management element and a congestion or overload control policy of the mobility management element, the mobility management element may receive the first request of the UE through the first request response message.

For example, the case that the mobility management element determines not to perform congestion or overload control on the first request of the UE may be that the mobility management element determines not to perform congestion control on the first request of the UE according to a congestion or overload condition or a congestion or overload control policy of a current network. For example, the mobility management element first performs congestion or overload control on a low-priority or normal-priority request, but the network congestion or overload condition is not further aggravated, if the time when the mobility management element receives the first request of the UE is outside the time range of the time indication information of the UE stored by the mobility management element; that is, when the time when the mobility management element receives the first request of the UE is outside the time range of the time indication information of the UE stored by the mobility management element, the mobility management element may not perform congestion or overload control on the first request of the normal priority of the UE.

Further, the method further comprises: accepting a first request by the UE.

In the fifth case: when the receiving time is in the time range indicated by the time indication information and the priority indicated by the first priority indication information is lower than or equal to the priority indicated by the second priority indication information, determining to perform congestion or overload control on the first request.

For example, if the mobility management element has time indication information corresponding to the UE and second priority indication information corresponding to the time indication information, for example, a normal priority; and the moment when the mobility management network element receives the first request is within the time range indicated by the time indication information, and the first priority carried in the first request is the priority indicated by the indication information and is low, that is, the priority indicated by the first priority indication information is lower than the priority indicated by the second priority indication information. At this point, the mobility management element rejects the first request of the UE.

For another example, if the mobility management element has time indication information corresponding to the UE and second priority indication information corresponding to the time indication information, for example, a normal priority; and the moment when the mobility management network element receives the first request is within the time range indicated by the time indication information, and the first priority indication information carried in the first request indicates a normal priority, that is, the priority indicated by the first priority indication information is equal to the priority indicated by the second priority indication information. At this point, the mobility management element rejects the first request of the UE.

For another example, if the mobility management element has time indication information corresponding to the UE and second priority indication information corresponding to the time indication information, for example, the time indication information is low priority; and the moment when the mobility management network element receives the first request is within the time range indicated by the time indication information, and the first priority carried in the first request is low priority, that is, the priority indicated by the first priority indication information is equal to the priority indicated by the second priority indication information. At this point, the mobility management element rejects the first request of the UE.

It should be noted that, in the embodiment of the present invention, the priority indicated by the first priority indication information is equal to the priority indicated by the second priority indication information, which indicates that the priority indicated by the first priority indication information is the same as the priority indicated by the second priority indication information.

In the sixth case:

and the mobility management network element initially sets the time indication information and the second priority indication information.

If the time indication information corresponding to the UE does not exist, and the second priority indication information corresponding to the time indication information does not exist; then, when performing congestion or overload control on the second request of the UE, the mobility management network element initially sets the time indication information and the second priority indication information, that is, stores the time indication information and the second priority indication information in the context of the UE or in a table for storing time indication information.

It should be noted that the second request may also be the first request.

Optionally, after rejecting the second request of the UE, the mobility management network element initially sets the time indication information and the second priority indication information, so that the priority indicated by the second priority indication information is the same as the priority of the second request.

For example, the mobility management element has not previously set the time indication information for the UE and the second priority indication information corresponding to the time indication information, and after receiving a second request sent by the UE, the mobility management element initially sets the time indication information and the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority of the second request because the congestion or overload control is performed on the UE to reject the second request of the UE. The time indication information and the second priority indication information of the initial setting may be stored in a context of the UE or a table for storing time indication information.

And when the mobility management network element performs congestion or overload control on the second request of the UE, the mobility management network element specifies the time indication information. Specifically, the mobility management element specifies a time range or a time point identified by the time indication information.

When the mobility management network element performs congestion or overload control on the second request of the UE and the priority indicated by the second priority indication information included in the second request is a normal priority, the mobility management network element initially sets the time indication information and the second priority indication information. For the second priority indication information, specifically, the flag bit for identifying the second priority indication information may be set to "the mobile station is not configured as a non-access stratum signaling low priority"; or

When the mobility management network element performs congestion or overload control on the second request of the UE and the priority indicated by the second priority indication information included in the second request is low priority, the mobility management network element initially sets the time indication information and the second priority indication information. For the second priority indication information, specifically, the identification bit identifying the second priority indication information may be set to "mobile station configured as non-access stratum signaling low priority".

The following describes a method for performing congestion or overload control in a mobility management process by using an example, as shown in fig. 2, which includes the following steps:

a. a mobility management network element receives a mobility management request sent by UE, wherein the mobility management request comprises first priority indication information; wherein the first priority indication information is used to identify a priority of the mobility management request.

b. The mobility management network element identifies the priority of the mobility management request through the first priority indication information; if the priority is low, performing the process in the step c-g; if the priority is normal, the process in step h-is performed.

c. And the mobile management network element inquires whether time indication information corresponding to the UE exists.

If there is time indication information corresponding to the UE and the time when the mobility management request of the UE is received is within the time range indicated by the time indication information (i.e., the time indication information is valid), performing the operation in step d; if the time indication information corresponding to the UE exists, but the time when the mobile management request of the UE is received is not in the time range indicated by the time indication information; or the time indication information does not exist, the operation in the step e is carried out.

d. And the mobility management network element refuses the mobility management request of the UE.

When the time indication information corresponding to the UE exists, the mobility management element may further obtain second priority indication information corresponding to the time indication information; at this time, the mobility management element rejects the mobility management request of the UE regardless of whether the priority indicated by the second priority indication information is a normal priority or a low priority, that is, the priority indicated by the second priority indication information is higher than or equal to the priority indicated by the first priority indication information. Therefore, it may not be necessary to know the priority indication information corresponding to the time indication information in this step.

e. The mobility management element determines whether to congestion or overload control the low priority mobility management requests.

If the mobile management network element carries out congestion or overload control on the mobile management request with low priority, executing the operation in the step f; if the mobility management element does not perform congestion or overload control on the low-priority mobility management request, the operation in step g is performed.

f. The mobility management network element rejects the low priority mobility management request of the UE.

If the mobility management element does not have the time indication information corresponding to the UE in step c, the mobility management element stores a designated time indication information and second priority indication information corresponding to the time indication information, where the priority indicated by the second priority indication information is a low priority.

If the time indication information corresponding to the UE exists in the mobility management element in step c, but the time when the mobility management request of the UE is received is not within the time range indicated by the time indication information, the mobility management element modifies the time indication information corresponding to the UE into newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

g. And the mobility management network element receives the mobility management request of the UE.

h. And the mobile management network element acquires whether time indication information corresponding to the UE exists or not.

When the time indication information corresponding to the UE exists, the mobility management element may further obtain the indication information of the second priority corresponding to the time indication information.

And if the moment when the mobility management network element receives the mobility management request of the UE is in the time range indicated by the time indication information and the acquired priority indicated by the second priority indication information corresponding to the time indication information is the normal priority, performing the operation in the step i.

If the moment when the mobility management network element receives the mobility management request of the UE is in the time range indicated by the time indication information, and the priority indicated by the second priority indication information corresponding to the time indication information is low priority; or

The moment when the mobility management network element receives the mobility management request of the UE is outside the time range indicated by the time indication information, and the priority indicated by the second priority indication information corresponding to the time indication information is the normal priority; or

The moment when the mobility management network element receives the mobility management request of the UE is outside the time range indicated by the time indication information, and the priority indicated by the second priority indication information corresponding to the time indication information is low priority;

the step in step j is performed.

And if the time indication information corresponding to the UE does not exist, performing the step in the step j.

i. And the mobility management network element refuses the mobility management request of the UE.

j. The mobility management element determines whether to congestion or overload control the normal priority mobility management requests.

If the mobility management network element performs congestion or overload control on the mobility management request with the normal priority, executing the operation in the step k; if the mobility management network element does not perform congestion or overload control on the mobility management request with normal priority, the operation in step l is performed.

k. And the mobility management network element performs congestion or overload control on the mobility management request with the normal priority of the UE.

If the mobility management element does not have the time indication information corresponding to the UE in step h, the mobility management element stores a designated time indication information and second priority indication information corresponding to the time indication information, and at this time, the priority indicated by the second priority indication information is the normal priority.

If the time indication information corresponding to the UE exists in the mobility management network element in the step h, the moment when the mobility management request of the UE is received is out of the time range indicated by the time indication information; the mobility management network element modifies the time indication information corresponding to the UE into newly specified time indication information, and modifies the modified priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information, and the modified priority indicated by the second priority indication information is a normal priority.

If the mobility management network element has the time indication information corresponding to the UE in the step h, but the time when the mobility management request of the UE is received is within the time range indicated by the time indication information, and the priority indicated by the second priority indication information is a low priority; the mobility management network element modifies the time indication information corresponding to the UE to update to the newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information, and the modified priority indicated by the second priority indication information is the normal priority.

And l, the mobile management network element receives the mobile management request with the normal priority of the UE.

The embodiment of the invention provides a congestion control method.A mobile management network element can judge whether to carry out congestion or overload control on a request of UE according to a certain condition when meeting a certain condition according to a first request of the UE, time indication information corresponding to the UE and second priority indication information corresponding to the time indication information; otherwise, rejecting the request of the UE. Therefore, the problem that the mobile management network element rejects the normal access request supporting the UE with double priorities when the network only carries out congestion or overload control on the access request with low priority can be solved; in addition, the mobility management network element determines whether to reject the access request from the UE according to the stored time indication information and the priority indication information corresponding to the time indication information, and does not need to determine whether to reject the access request from the UE according to the current congestion/control strategy for each access request, so that the processing efficiency of the mobility management network element is improved.

Another embodiment of the present invention provides a method for congestion control, as shown in fig. 3, the method includes the following steps:

s301, a mobile management network element receives a first request sent by UE, wherein the first request comprises first priority indication information; wherein the first priority indication information is used to identify the priority of the first request.

The first request may be a session management request, the corresponding first request message is a session management request message, and when the first request message is a session management request message, the first request may be: a Packet Data Network connection establishment Request (Packet Data Network connection Request) message, an Activate Packet Data Protocol Context Request (active Packet Data Protocol Context Request) message, a Bearer Resource Modification Request (Bearer Resource Modification Request) message, a Modify Packet Data Protocol Context Request (Modification Packet Data Protocol Context Request) message, and the like.

S302, the mobility management network element determines whether to perform congestion or overload control on the first request according to the receiving time of the first request, the first priority indication information, the time indication information corresponding to the UE and the APN selected by the UE, and the second priority indication information corresponding to the time indication information.

And the mobile management network element determines the UE to request to access the selected APN according to the parameters carried in the first request. Since the UE may initiate a request to select a different APN and congestion or overload conditions between APNs may be different, the mobility management element performs congestion or overload control of APN granularity based on the APN selected by the UE request.

The mobility management network element determines the APN selected by the first request according to the parameter in the first request, and may save the time indication information corresponding to the UE and the APN selected by the UE and the second priority indication information corresponding to the time indication information in the context of the UE saved by the mobility management network element or in a table for saving time indication information; embodiments of the invention are not limited in this regard and may be stored in any memory.

In this embodiment of the present invention, the mobility management network element determines, according to the parameter in the first request, the APN selected by the request, where the implementation manner includes, but is not limited to: the first request comprises the information of the selected APN, and the mobile management network element determines the APN selected by the first request of the UE according to the information of the selected APN in the first request, the subscription data of the UE and the like; or the first request does not include the information of the selected APN, and the mobile management network element determines the APN selected by the first request of the UE according to the subscription data of the UE and the like.

In the embodiment of the present invention, the APN selected by the UE represents an APN selected by an access request of the UE, and an APN pointed by the UE represents an APN selected by an access request of the UE.

Before the UE sends the first request, if congestion or overload control is performed on the request of the UE directed to the APN and the request of the UE is rejected, the mobility management element may store, in a context of the UE that is stored in the mobility management element, one piece of time indication information corresponding to the UE and the APN selected by the UE and second priority indication information corresponding to the time indication information, where the time indication information is duration or time. In addition, the mobility management element may store the time indication information and second priority indication information corresponding to the time indication information in a table for storing time indication information. Such time indication information may be referred to as session management time indication information in embodiments of the present invention.

In addition, before the mobility management element sends the first request, the mobility management element determines to perform congestion or overload control on the first request with low priority or normal priority directed to the APN according to the current network congestion or overload condition or the congestion or overload condition of the APN. The mobility management network element stores time indication information corresponding to the UE and the APN and priority indication information corresponding to the time indication information in the context of the UE stored by the mobility management network element, wherein if the mobility management network element determines to perform congestion or overload control on a first request pointing to a low priority of the APN, the priority indicated by second priority indication information corresponding to the time indication information is the low priority; and if the mobile management network element determines to perform congestion or overload control on the first request pointing to the normal priority of the APN, the priority indicated by the second priority indication information corresponding to the time indication information is the normal priority.

In the first case:

Optionally, when the mobility management element determines to perform congestion or overload control on the first request of the UE according to the load condition of the mobility management element, the congestion or overload control policy of the mobility management element, the load condition of the gateway device corresponding to the APN selected by the UE for the current request, and the like, the mobility management element may reject the first request of the UE through the first request response, and specifically, may send a first request response message to the mobility management element to reject the first request of the UE.

The first request response message may be a session management request response message, and when the first request response message is a session management request response message, the first request response message may be: a Packet Data network connection setup Reject (PDN Connectivity Reject) message, an Active PDP Context Reject (Active PDP Context Reject), a Bearer Resource Modification Reject (Bearer Resource Modification Reject) message, a modified Packet Data Protocol Context Reject (modified Packet Data Protocol Context Reject) message, etc.

For example, if there are time indication information corresponding to the UE and the APN selected by the UE in the mobility management element, and second priority indication information corresponding to the time indication information, for example, the priority indicated by the second priority indication information is low priority, and the time when the mobility management element receives the first request is within the time range indicated by the time indication information, and the priority indicated by the first priority indication information is, for example, normal priority, that is, the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information. At this time, if the mobility management element determines to perform congestion or overload control on the first request of the UE according to the network condition, the mobility management element rejects the first request of the UE, modifies the time indication information into newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

The second priority indication information may further indicate the reason indication information corresponding to the newly specified time indication information through an identification bit, for example, the identification bit is modified to "time saved due to an access request with normal priority", that is, the identification bit indicates normal priority after modification.

In this embodiment of the present invention, the first request to the UE is rejected, the mobility management network element modifies the time indication information to be newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information. However, the embodiment of the present invention is not limited thereto, and may also be another implementation method: that is, the mobility management element deletes the stored time indication information corresponding to the UE and the APN selected by the UE and the second priority indication information corresponding to the time indication information, and the mobility management element stores the newly specified time indication information and the second priority indication information corresponding to the time indication information, and the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

In the second case:

Optionally, when the mobility management element determines to perform congestion or overload control on the first request of the UE, the mobility management element rejects the first request of the UE through the first request response message.

In the third case:

when the moment when the mobile management network element receives the first request is in the time range indicated by the time indication information and the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information, determining not to carry out congestion or overload control on the first request.

Optionally, if the mobility management network element determines not to perform congestion or overload control on the current request of the UE, the method further includes: accepting a first request by the UE.

And when the first request is a session management request, the mobile management network element performs subsequent process processing of the corresponding session management request according to the type of the current session management request of the UE. For example: when the session management Request message corresponding to the Request is a packet data network connection establishment Request (PDN Connectivity Request) message, the subsequent procedure includes: a Create Session (Create Session) flow, a Bearer Setup (Bearer Setup) flow, and the like. And after the flow corresponding to the session management request is completed, the mobile management network element sends a session management request response message to the UE, wherein the session management request response message indicates that the request of the UE is accepted. The session management request response message may be a Packet Data network connection setup response (PDN Connectivity Accept/Reject) message, an Active PDP Context response (Active PDP Context/Reject) message, a Bearer Resource Modification response (Bearer Resource Modification Accept/Reject) message, a modified Packet Data Protocol Context response (modified Packet Data Protocol Context/Reject) message, or the like.

In a fourth case:

For example, the case that the mobility management network element determines not to perform congestion or overload control on the UE and the first request of the APN to which the UE points may be that the mobility management network element determines not to perform congestion control on the first request of the UE according to a load condition of the mobility management network element, a congestion or overload control policy of the mobility management network element, a load condition of a gateway device corresponding to an APN selected by the first request of the UE, and the like. For example, the mobility management element first performs congestion or overload control on a low-priority or normal-priority request, but the network congestion or overload condition is not further aggravated, if the time when the mobility management element receives the first request of the UE is outside the time range of the time indication information of the UE stored by the mobility management element; that is, when the time when the mobility management element receives the first request of the UE is outside the time range of the time indication information of the UE stored by the mobility management element, the mobility management element may not perform congestion or overload control on the first request of the normal priority of the UE.

Further, the method further comprises: accepting a first request by the UE.

For example, if there are time indication information corresponding to the UE and the APN selected by the UE and second priority indication information corresponding to the time indication information in the mobility management element, for example, the time indication information is a low priority; and the moment when the mobility management network element receives the first request is within the time range indicated by the time indication information, and the first priority indication information carried in the first request indicates low priority, that is, the priority indicated by the first priority indication information is equal to the priority indicated by the second priority indication information. At this point, the mobility management element rejects the first request of the UE.

For another example, if there are time indication information corresponding to the UE and the APN selected by the UE and second priority indication information corresponding to the time indication information in the mobility management element, for example, the time indication information is a normal priority; and the moment when the mobility management network element receives the first request is within the time range indicated by the time indication information, and the first priority indication information carried in the first request indicates low priority, that is, the priority indicated by the first priority indication information is lower than the priority indicated by the second priority indication information. At this point, the mobility management element rejects the first request of the UE.

For another example, if there are time indication information corresponding to the UE and the APN selected by the UE in the mobility management element, and a second priority indication information indication corresponding to the time indication information, for example, a normal priority; and the moment when the mobility management network element receives the first request is within the time range indicated by the time indication information, and the first priority carried in the first request is the normal priority, that is, the priority indicated by the first priority indication information is equal to the priority indicated by the second priority indication information. At this point, the mobility management element rejects the first request of the UE.

In the sixth case:

If the time indication information corresponding to the UE and the APN selected by the UE does not exist, the second priority indication information corresponding to the time indication information exists; then, when performing congestion or overload control on the second request of the UE, the mobility management network element initially sets the time indication information and the second priority indication information, that is, stores the time indication information and the second priority indication information in the context of the UE or in a table for storing time indication information.

It should be noted that the second request may also be the first request.

Optionally, after rejecting the second request of the UE and the APN to which the UE points, the mobility management network element initially sets the time indication information and the second priority indication information, so that the priority indicated by the second priority indication information is the same as the priority of the second request.

For example, the mobility management element has not previously set time indication information for the UE and an APN selected by the UE and the second priority indication information corresponding to the time indication information, and after receiving a second request message sent by the UE, the mobility management element initially sets the time indication information and the second priority indication information so that a priority indicated by the second priority indication information is the same as a priority of the second request since congestion or overload control is performed on the UE to reject the second request of the UE. The time indication information and the second priority indication information of the initial setting may be stored in a context of the UE or a table for storing time indication information.

The embodiment of the invention provides a congestion control method.A mobile management network element can judge whether to carry out congestion or overload control on a first request of UE according to the first request of the UE, time indication information corresponding to the UE and second priority indication information corresponding to the time indication information when certain conditions are met; otherwise, the request of the UE is refused. Therefore, the problem that the mobile management network element rejects the normal access request supporting the UE with double priorities when the network only carries out congestion or overload control on the access request with low priority can be solved; in addition, the mobility management network element determines whether to reject the access request from the UE according to the stored time indication information and the priority indication information corresponding to the time indication information, and does not need to determine whether to reject the access request from the UE according to the current congestion/control strategy for each access request, so that the processing efficiency of the mobility management network element is improved.

Yet another embodiment of the present invention provides a method for congestion control, as shown in fig. 4, the method includes the following steps:

s401, when the low priority access request of the UE is subjected to congestion or overload control, the mobile management network element receives a first request with normal priority sent by the UE.

Optionally, the first request includes: priority indication information for identifying a priority of the first request; wherein the priority of the first request is a normal priority.

Further, the method for acquiring the normal priority access request initiated by the UE when the low priority access request is subjected to congestion or overload control by the mobility management network element includes the following steps:

the first method comprises the following steps: and the mobile management network element receives the first request sent by the UE and comprises indication information of requesting access of the UE under the condition that the access request with low priority is subjected to congestion or overload control.

Wherein determining, by the UE, that the low-priority access request is subject to congestion or overload control before sending the first request comprises:

1) the access request with low priority sent by the UE is rejected by a mobile management network element, the mobile management network element carries time indication information aiming at the UE in an access request response message, the UE starts a timer according to the time indication information, and the UE cannot send the access request with low priority during the running period of the timer.

2) And the UE receives indication information for enabling the EAB to the Access request with low priority from a Radio Access Network (RAN for short).

3) The RRC connection request message with low priority sent by the UE is rejected by the wireless communication network, the wireless communication network carries time indication information aiming at the UE in the RRC connection response message, the UE starts a timer according to the time indication information, and the UE cannot send the RRC access request with low priority when the timer runs.

In the above case, the UE may determine that its low priority access requests are subject to congestion or overload control.

For example, in the first request, a certain Information Element (Information Element) may be used to identify that the UE is an indication that access is requested if a low priority access request is subject to congestion or overload control. For example, a flag bit in the information element may be set to "Request access while low priority access Request is under congestion or overload control" ("Request access while high priority access Request"), which identifies that the UE requests access while low priority access Request is under congestion or overload control.

In addition, the mobility management network element may further include priority indication information in the first request sent by the UE, where the priority indication information is used to identify the priority of the first request; wherein the priority of the first request is a normal priority.

And the second method comprises the following steps: the moment when the mobile management network element receives the first request sent by the UE is within a time range indicated by the stored time indication information corresponding to the UE or the UE and the APN selected by the UE; and the priority of the first request is higher than the priority indicated by the priority indication information corresponding to the time indication information.

For example, when the first request is a mobility management request message, the mobility management element recognizes that the priority of the request of the UE is, for example, a normal priority, and obtains whether it stores time indication information corresponding to the UE and priority indication information corresponding to the time indication information. If time indication information corresponding to the UE exists and priority indication information corresponding to the time indication information exists; and when the moment when the mobility management network element receives the first request sent by the UE is within the time range indicated by the time indication information and the priority (normal priority) of the first request is higher than the priority (low priority) indicated by the priority indication information corresponding to the time indication information, the mobility management network element may determine that the UE is an access request of normal priority initiated when the access request of low priority is subjected to congestion or overload control.

For another example: when the first request is a session management request message, the mobility management network element identifies that the priority of the first request of the UE is, for example, a normal priority, and determines the APN selected by the access request of the UE this time according to the parameters in the first request. And acquiring whether time indication information corresponding to the UE and the APN selected by the UE is stored or not, and priority indication information corresponding to the time indication information. If time indication information corresponding to the UE and the APN selected by the UE exists, and a priority indication message corresponding to the time indication information; and when the moment when the mobility management network element receives the first request sent by the UE is within the time range indicated by the time indication information and the priority (normal priority) of the first request is higher than the priority (low priority) indicated by the priority indication information corresponding to the time indication information, the mobility management network element may determine that the UE is an access request of normal priority initiated when the access request of low priority is subjected to congestion or overload control.

Wherein, according to the above two embodiments, when the access request of the UE is subjected to congestion or overload control; or, when the access request directed to the APN by the UE is subject to congestion or overload control; the mobility management network element rejects the access request of the UE, and stores time indication information corresponding to the UE and the priority indication information corresponding to the time indication information, or stores time indication information corresponding to the UE and an APN selected by the UE and the priority indication information corresponding to the time indication information.

And the third is that: and after informing the RAN of EAB on the low-priority access request of the UE, the mobile management network element receives a first request with the priority of normal priority sent by the UE.

In this embodiment of the present invention, the first request may be a mobility management request, and the corresponding first request message may be a mobility management request message; the first request may also be a session management request, and the corresponding first request message may be a session management request message.

By way of example, the first Request may be an attach Request, a PDN Connectivity Request or an active PDP Context Request.

S402, according to the first request, the mobile management network element sends a session management message to the gateway device, wherein the session management message comprises identification information used for indicating that the UE is allocated with a bearer when the low-priority access request of the UE is subjected to congestion or overload control.

Illustratively, when the mobility management element determines, according to the first request, that the UE is initiating an access request with a normal priority when the access request with a low priority is subjected to congestion or overload control, the mobility management element sends a session management message to a gateway device corresponding to an APN selected by the access request of the UE, where the session management message includes identification information for indicating that a bearer is allocated to the UE when the access request with a low priority of the UE is subjected to congestion or overload control.

The Session management message may be a Create PDP Context Request (Create PDP Context Request) message or a Create Session Request (Create Session Request) message. For example, an information element in the session management message may be used to identify the identity information of the assigned bearer when a low priority access request of the UE is subject to congestion or overload control. Optionally, when a flag bit in the information element is set to "Create bearer low restriction priority" for an access request with low priority under congestion or overload control, the flag bit indicates that the UE allocates a bearer when the access request with low priority is under congestion or overload control.

For the second method, the third method, that is, when the mobility management element determines that the UE is the access request with the normal priority initiated when the access request with the low priority is subjected to congestion or overload control through the second method or the third method, the mobility management element further stores information of a bearer to be established of the UE, where the information of the bearer includes: bearer identification, indication information that the UE requests access when the low priority access request is subject to congestion or overload control.

S403, the gateway device allocates a bearer for the UE, and stores, in the context of the bearer, identification information indicating that the bearer is the bearer allocated when a low-priority access request of the UE is subjected to congestion or overload control.

The identification information can identify that the bearer is the bearer allocated for the UE when the access request with low priority is subjected to congestion or overload control.

S404, the gateway device sends a session management response message to the mobile management network element, wherein the session management response message carries indication information of the allocated load for the UE.

For example, the Session management Response message sent by the gateway device to the mobility management element may be a Create PDP Context Response (Create PDP Context Response) message, a Create Session Response (Create Session Response) message, or the like.

Further, after receiving the session management response message, the mobility management network element stores, in the context of the bearer, identification information indicating that the bearer is a bearer allocated when a low-priority access request of the UE is subjected to congestion or overload control.

In the embodiment of the present invention, further, when the mobility management element and the gateway device maintain, in the context of respective bearers, identification information indicating that the bearer is a bearer allocated when the low priority access request of the UE is subjected to congestion or overload control, the mobility management element and the gateway device may maintain, in generating a Charging Data Record (CDR) about this bearer, identification information indicating that the bearer is a bearer allocated for the UE when the low priority access request of the UE is subjected to congestion or overload control, so that the CDR may be indicated by the identification information as the CDR of the bearer allocated by the UE when the low priority access request of the UE is subjected to congestion or overload control.

For example, an information element in the CDR may be used to identify information identifying that the UE allocates a bearer when a low priority access request is subject to congestion or overload control. Optionally, a flag bit in the information element may be set to "allocate a bearer when the low-priority access request is subjected to congestion or overload control", and the flag bit indicates that the UE allocates a bearer when the low-priority access request is subjected to congestion or overload control.

In the embodiment of the present invention, the Bearer may refer to an evolved packet system Bearer (EPS Bearer), a packet data network connection (PDN connection), a packet data protocol Context (PDP Context), and the like.

In addition, the mobility management network element may respond to the first request of the UE, specifically, send a first request response message, where the first request response message indicates that the access request of the UE is accepted.

For example, the first request response may be Attach Accept (Attach Accept), PDN connection establishment Accept (PDN Connectivity Accept), activate PDP Context Accept (Active PDP Context Accept), or the like.

It should be noted that the congestion or overload control method according to all embodiments of the present invention can be applied to various wireless communication networks. For example: universal Mobile Telecommunications System (UMTS), terrestrial Radio Access Network (E-UTRAN), UMTS Terrestrial Radio Access Network (UTRAN), Global System for Mobile Communications (GSM) for improving Data rate, Enhanced Data for GSM Evolution (EDGE) Radio Access Network (GERAN), non-third Generation partnership Project (3 GPP) Network, and the like.

The Mobility Management element may be a Mobility Management Entity (MME), a Serving General Packet Radio Service (GPRS) support Node (SGSN), or the like.

The Gateway device may be a Serving Gateway (S-GW), a Packet Data Network Gateway (P-GW), a Gateway General Packet Radio Service (GPRS) support Node (GGSN), or the like.

A User Equipment (UE) may be any one of the following, and the UE may be static or mobile. The stationary UE may be a Terminal (Terminal), a Mobile Station (Mobile Station), a Subscriber Unit (Subscriber Unit), or a Station (Station). Mobile UEs may include Cellular phones (Cellular phones), Personal Digital Assistants (PDAs), Wireless modems (modems), Wireless communication devices, handheld devices (handhelds), Laptop computers (Laptop computers), Cordless phones (hardless phones), or Wireless Local Loop (WLL) stations, among others. The UEs may be distributed throughout the wireless network.

The embodiment of the invention provides a congestion control method, wherein a mobile management network element comprises identification information for indicating that a bearer is allocated to UE when a low-priority access request of the UE is subjected to congestion or overload control to gateway equipment according to a first request of a normal priority sent by the UE, so that the gateway equipment allocates the bearer to the UE, the identification information for indicating that the bearer is allocated when the low-priority access request of the UE is subjected to the congestion or overload control is stored in the context of the bearer, and the mobile management network element also stores the identification information in the context of the bearer after the gateway equipment allocates the bearer. In addition, the mobility management network element and the gateway device may store, in the CDR of the bearer, identification information indicating that the bearer is a bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control, so that a network operator may further perform individual charging for the bearer and may also perform good management for the UE supporting dual-priority.

The embodiment of the invention provides a congestion control system, which comprises a mobile management network element.

Based on the system, the embodiment of the present invention provides a mobility management element, where the mobility management element 10 corresponds to the mobility management element in the congestion control method provided in the first two embodiments of the foregoing method, and therefore, a detailed description of each unit may be a description of the foregoing steps, which is not described herein again. As shown in fig. 5, the mobility management element 10 includes:

a receiving unit 101, configured to receive a first request sent by a UE, where the first request includes first priority indication information; wherein the first priority indication information is used to identify the priority of the first request.

The first priority indication information may be encapsulated in a device attribute information element, wherein the device attribute information element is included in the first request. For example: when the corresponding identification bit in the device attribute cell is set to 'the mobile station is configured as a non-access stratum signaling low priority', the priority of the first request is indicated as a low priority; and when the corresponding identification bit in the equipment attribute cell is set as 'the mobile station is not configured to be the non-access stratum signaling low priority', indicating that the priority of the first request is the normal priority.

A processing unit 102, configured to determine whether to perform congestion or overload control on the first request according to the receiving time and the first priority indication information when the receiving unit 101 receives the first request, and according to the time indication information corresponding to the UE and second priority indication information corresponding to the time indication information.

The mobility management element may query, in a context of the UE stored therein or in a table for storing time indication information, whether there is time indication information corresponding to the APN selected by the UE or the UE and the UE, and the second priority indication information corresponding to the time indication information; however, the embodiments of the present invention are not limited thereto, and may be stored in any storage unit.

Before the UE sends the first request, if congestion or overload control is performed on the UE and the request of the UE is rejected, the mobility management element may store, in a context of the UE that is stored by the mobility management element, time indication information corresponding to the UE or the UE and an APN selected by the UE and second priority indication information corresponding to the time indication information, where the time indication information is duration or time. In addition, the mobility management element may further store the time indication information and second priority indication information corresponding to the time indication information in a table for storing the time indication information. Such time indication information may be referred to as mobility management time indication information in an embodiment of the present invention.

It should be noted that the first request may be a mobile management request or a session management request; when the first request is a mobility management request message, the time indication information and the first time indication information correspond to the UE; when the first request is a session management request, the time indication information and the first time indication information correspond to the UE and an APN selected by the UE.

Optionally, the processing unit 102 is specifically configured to, if the time when the receiving unit 101 receives the first request is within the time range indicated by the time indication information, and the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information; determining to perform congestion or overload control on the first request.

Optionally, the processing unit 102 is specifically configured to, if the time when the receiving unit 101 receives the first request is outside the time range indicated by the time indication information; determining to perform congestion or overload control on the first request.

In this case, the processing unit 102 is further configured to modify the time indication information into newly specified time indication information, and modify the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

For example, if time indication information corresponding to the UE or the APN selected by the UE exists in the mobility management element, and the priority indicated by the second priority indication information corresponding to the time indication information is, for example, a low priority; in this case, if the processing unit 102 learns that the time of the first request received by the receiving unit 101 is within the time range indicated by the time indication information and the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information, at this time, if the processing unit 102 determines to perform congestion or overload control on the first request of the UE according to the network condition, the processing unit rejects the first request of the UE, modifies the time indication information into newly specified time indication information, and modifies the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

Optionally, the processing unit 102 is specifically configured to, when the receiving time of the first request by the receiving unit is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is higher than a priority indicated by the second priority indication information; determining not to congestion or overload control the first request.

The processing unit 102 is specifically configured to determine not to perform congestion or overload control on the first request when the receiving time at which the receiving unit 101 receives the first request is outside the time range indicated by the time indication information.

Further, the processing unit 102 may be further configured to accept the first request of the UE through the first request response.

Optionally, the processing unit 102 is specifically configured to, when the time when the receiving unit 101 receives the first request is within the time range indicated by the time indication information, and the priority indicated by the first priority indication information is lower than or equal to the priority indicated by the second priority indication information; then it is determined to congestion or overload control the first request.

For example, if time indication information corresponding to the UE or the UE and the APN selected by the UE exists in the mobility management element, and second priority indication information corresponding to the time indication information, for example, a normal priority is present; if the processing unit 102 learns that the time when the receiving unit 101 receives the first request is within the time range indicated by the time indication information and the first priority indication information carried in the first request indicates low priority, that is, the priority indicated by the first priority indication information is lower than or equal to the priority indicated by the second priority indication information, the first request of the UE is rejected.

Optionally, the processing unit 102 is further configured to initially set the time indication information and the second priority indication information.

If the time indication information corresponding to the UE does not exist, and the second priority indication information corresponding to the time indication information does not exist; then, when performing congestion or overload control on the second request of the UE, the processing unit 102 initially sets the time indication information and the second priority indication information.

It should be noted that the second request may be the first request.

Further, the processing unit 102 is specifically configured to, after rejecting the second request of the UE, initially set the time indication information and the second priority indication information, so that a priority indicated by the second priority indication information is the same as a priority of the second request.

For example, the processing unit 102 has not previously set the time indication information selected for the UE or the UE and the second priority indication information corresponding to the time indication information, and after the receiving unit 101 receives the second request message sent by the UE, the processing unit 102 initially sets the time indication information and the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority of the second request since the second request of the UE is rejected due to congestion or overload control performed on the UE. The time indication information and the second priority indication information of the initial setting may be stored in a context of the UE or a table for storing time indication information.

Furthermore, as shown in fig. 6, the mobility management element 10 further includes:

a storage unit 103, configured to store the UE and the second priority indication information.

The embodiment of the invention provides a mobile management network element, which can judge whether to carry out congestion or overload control on the request of the UE according to the network condition when a certain condition is met according to the received first request of the UE, the time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information; otherwise, rejecting the request of the UE. Therefore, the problem that the mobile management network element rejects the normal access request supporting the UE with double priorities when the network only carries out congestion or overload control on the access request with low priority can be solved; in addition, the mobility management network element determines whether to reject the access request from the UE according to the stored time indication information and the priority indication information corresponding to the time indication information, and does not need to determine whether to reject the access request from the UE according to the current congestion/control strategy for each access request, so that the processing efficiency of the mobility management network element is improved.

Another embodiment of the present invention provides a system for congestion control, where the system includes a mobility management element, a UE, and a gateway device.

Based on the system, the embodiment of the present invention provides another mobility management element 20, where the mobility management element 20 corresponds to the mobility management element in the congestion control method provided in the third embodiment of the foregoing method, and therefore, a detailed description of each unit may be a description of the foregoing step, which is not described herein again. The mobility management element 20, as shown in fig. 7, includes:

a receiving unit 201, configured to receive a first request with a normal priority sent by a UE when a low priority access request of the UE is subjected to congestion or overload control.

A generating unit 202, configured to generate a session management message according to the first request received by the receiving unit 201, where the session management message includes identification information used to indicate that a bearer is allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control.

The generating unit 202 may determine that the UE is an access request of normal priority initiated when the access request of low priority is subjected to congestion or overload control according to indication information that the access request of low priority is subjected to congestion or overload control in the first request received by the receiving unit 201.

Wherein the UE determining that the low priority access request is subject to congestion or overload control may include:

1) the access request with low priority sent by the UE is rejected by a mobile management network element, the mobile management network element carries time indication information aiming at the UE in an access request response message, the UE starts a timer according to the time indication information, and the access request with low priority cannot be sent during the running period of the timer.

2) The UE receives indication information for enabling EAB for the low priority access request from the wireless communication network. For example, the RAN may carry EAB enabled indication information in a broadcast message sent by the RAN, and the UE obtains the EAB enabled indication information by receiving the broadcast message.

3) The RRC connection request message with low priority sent by the UE is rejected by a wireless communication network, the wireless communication network carries time indication information aiming at the UE in an RRC connection response message, the UE starts a timer according to the time indication information, and the UE cannot send the RRC connection request with low priority when the timer runs.

Optionally, the receiving unit 201 is specifically configured to, when the low-priority access request of the UE is subjected to congestion or overload control, receive the first request sent by the UE after the mobility management element notifies a radio access network to perform EAB for the low-priority access request of the UE.

In this case, the generating unit 202 may determine, according to the information of the receiving unit 201, that the UE is a normal-priority access request initiated when a low-priority access request is subjected to congestion or overload control.

Optionally, the receiving unit 201 is specifically configured to, when the low-priority access request of the UE is subjected to congestion or overload control, receive the first request when the time of receiving the first request is within a time range indicated by the saved time indication information corresponding to the UE, and a priority of the first request of the UE is higher than a priority indicated by the priority indication information corresponding to the time indication information.

A sending unit 203, configured to send the session management message generated by the generating unit 202 to the gateway device; so that the gateway device maintains, in the context of the bearer allocated for the UE, identification information indicating that the bearer is an allocated bearer when a low priority access request of the UE is subject to congestion or overload control.

Further, as shown in fig. 8, the mobility management element further includes a processing unit 204, configured to store, in the generated charging data record of the bearer, identification information indicating that the bearer is the bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control.

Wherein the processing unit 204 is further configured to, after the gateway device allocates the bearer, store, in the context of the bearer, identification information indicating that the bearer is an assigned bearer when a low-priority access request of the UE is subjected to congestion or overload control.

Furthermore, when the processing unit 204 is further configured to, when it is determined that the UE is an access request of a normal priority initiated when the access request of a low priority is subjected to congestion or overload control, not directly obtain from the first request, the processing unit 204 is further configured to, before the gateway device allocates the bearer, save information of the bearer ready to be established for the UE, where the information of the bearer includes: the bearer identification and the indication information that the UE requests access when the access request with low priority is subjected to congestion or overload control.

Further, the processing unit 204 is further configured to store, in the generated CDR of the bearer, identification information indicating that the bearer is a bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control, so that the CDR can be indicated by the identification information as the CDR of the bearer allocated by the UE when the low-priority access request is subjected to congestion or overload control.

The embodiment of the invention provides a mobile management network element, which comprises identification information used for indicating that a bearer is allocated to UE when a low-priority access request of the UE is subjected to congestion or overload control, so that the gateway equipment allocates the bearer to the UE, the identification information used for indicating that the bearer is allocated when the low-priority access request of the UE is subjected to the congestion or overload control is stored in the context of the bearer, and the mobile management network element also stores the identification information in the context of the bearer after the gateway equipment allocates the bearer. In addition, the mobility management network element and the gateway device may store, in the CDR of the bearer, identification information indicating that the bearer is a bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control, so that a network operator may further perform individual charging for the bearer and may also perform good management for the UE supporting dual-priority.

Based on the system for congestion control provided in the above further embodiment, an embodiment of the present invention provides another UE 30, where the UE 30 corresponds to the UE in the method for congestion control provided in the third embodiment of the foregoing method, and therefore, specific descriptions of each unit may be descriptions of the above steps, which are not repeated herein. As shown in fig. 9, the UE 30 includes:

a processing unit 301 for determining that a low priority access request is subject to congestion or overload control.

Optionally, the processing unit 301 is specifically configured to reject the low-priority access request sent by the mobility management element, where the mobility management element carries time indication information for the UE in an access request response message, the UE starts a timer according to the time indication information, and during the running period of the timer, the low-priority access request cannot be sent; or

Receiving indication information for enabling extended access control (EAB) for the low priority access request from a wireless communication network; or

The sent Radio Resource Control (RRC) connection request message with low priority is rejected by a wireless communication network, the wireless communication network carries time indication information aiming at the UE in an RRC connection response message, the UE starts a timer according to the time indication information, and the UE cannot send the RRC connection request with low priority when the timer runs;

A generating unit 302, configured to generate a first request when the processing unit 301 determines that the access request with low priority is subjected to congestion or overload control, where the first request includes indication information that the access request with low priority is subjected to congestion or overload control.

In this embodiment of the present invention, the first request may be a mobility management request or a session management request.

Further, the first request generated by the generating unit 302 further includes: priority indication information for identifying a priority of the first request; wherein the priority of the first request is a normal priority.

A sending unit 303, configured to send the first request generated by the generating unit 302 to a mobility management network element; and the mobile management network element and the gateway equipment allocate the bearer for the UE, and store the identification information for identifying the bearer as the bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control in the context of the bearer.

The embodiment of the invention provides UE (user equipment), wherein the UE sends a first request carrying indication information of requesting access when an access request with low priority is subjected to congestion or overload control to a mobile management network element, so that the mobile management network element and gateway equipment allocate a bearer for the UE, and the identification information of the allocated bearer when the access request with low priority is subjected to congestion or overload control is stored in the context of the bearer.

Based on the system for congestion control provided in the above further embodiment, an embodiment of the present invention provides another gateway device 40, where the gateway device 40 corresponds to the gateway device in the method for congestion control provided in the third embodiment of the foregoing method, and therefore, a detailed description of each unit may be a description of the foregoing step, which is not described herein again. As shown in fig. 10, the gateway apparatus 40 includes:

a receiving unit 401, configured to receive a session management message sent by a mobility management network element, where the session management message includes identification information used to indicate that a bearer is allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control.

And the gateway equipment corresponds to the access point name APN selected by the UE access request.

A processing unit 402, configured to allocate the bearer for the UE according to the session management message received by the receiving unit 401, and store, in the context of the bearer, identification information used for indicating that the bearer is allocated when a low-priority access request of the UE is subjected to congestion or overload control.

A generating unit 403, configured to generate a session management response message according to the processing result of the processing unit 402, where the session management response message carries indication information that a bearer has been allocated for the UE.

A sending unit 404, configured to send the first response message generated by the generating unit 403 to the mobility management network element.

Further, the processing unit 402 is further configured to store, in the generated CDR of the bearer, identification information indicating that the bearer is a bearer allocated for the UE when a low-priority access request of the UE is subjected to congestion or overload control.

And indicating that the CDR is the CDR of the bearer allocated to the UE when the access request with low priority is subjected to congestion or overload control through the identification information.

For example, an information element in the CDR may be used to identify information identifying the bearer allocated when a low priority access request is subject to congestion or overload control. Optionally, when a flag bit in the information element is set to "allocate a bearer when the low-priority access request is subjected to congestion or overload control", the flag bit is used to identify the CDR that the UE allocates a bearer when the low-priority access request is subjected to congestion or overload control.

The embodiment of the invention provides gateway equipment, which allocates a bearer for an access request of UE when receiving a session management message which is sent by a mobile management network element and comprises identification information used for indicating that the bearer is allocated for the UE when a low-priority access request of the UE is subjected to congestion or overload control, and stores the identification information used for indicating that the bearer is allocated when the access request of the UE at low priority is subjected to congestion or overload control in the context of the bearer. In addition, the CDR of the bearer stores identification information for indicating that the bearer is allocated for the UE when the access request of the low priority is subjected to congestion or overload control, so that a network operator can further perform separate charging on the bearer, and the CDR of the bearer can also count and obtain the access information of the user equipment when the access request of the low priority is subjected to congestion or overload control, so that the UE supporting double priorities can be well managed.

Based on the system, the embodiment of the present invention provides a mobility management element 50, where the mobility management element 50 corresponds to the mobility management element in the congestion control method provided in the first two embodiments of the foregoing method, and therefore, the detailed description of each module may be a description of the foregoing step, which is not described herein again. As shown in fig. 11, the mobility management element 50 includes:

a receiving module 501, configured to receive a first request sent by a UE, where the first request includes first priority indication information; wherein the first priority indication information is used to identify the priority of the first request.

The first priority indication information may be encapsulated in a device attribute information element, wherein the device attribute information element is included in the first request. For example: when the corresponding identification bit in the device attribute cell is set to 'the mobile station is configured as a non-access stratum signaling low priority', the priority of the first request is indicated as a low priority; and when the corresponding identification bit in the equipment attribute cell is set to be 'the mobile station is not configured to be the non-access stratum signaling low priority', indicating that the priority of the first request is the normal priority.

A processor 502, configured to determine whether to perform congestion or overload control on the first request of the UE according to the receiving time of the first request and the first priority indication information received by the receiving module 501, as well as time indication information corresponding to the UE and second priority indication information corresponding to the time indication information.

The mobility management element may query, in a context of the UE stored therein or in a table for storing time indication information, whether there is time indication information corresponding to the APN selected by the UE or the UE and the UE, and the second priority indication information corresponding to the time indication information; embodiments of the invention are not limited in this regard and may be stored in any memory.

It should be noted that the first request may be a mobile management request or a session management request; when the first request is a mobility management request, the time indication information and the first time indication information correspond to the UE; when the first request is a session management request, the time indication information and the first time indication information correspond to the UE and an APN selected by the UE.

Optionally, the processor 502 is specifically configured to, if the time when the receiving module 501 receives the first request is within the time range indicated by the time indication information, and the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information; determining to perform congestion or overload control on the first request.

Optionally, the processor 502 is specifically configured to, if the time when the receiving module 501 receives the first request is outside the time range indicated by the time indication information; determining to perform congestion or overload control on the first request.

In this case, the processor 502 is further configured to modify the time indication information into newly specified time indication information, and modify the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

For example, if time indication information corresponding to the UE or the APN selected by the UE exists in the mobility management element, and the priority indicated by the second priority indication information corresponding to the time indication information is, for example, a low priority; in this case, if the processor 502 knows that the time of the first request received by the receiving module 501 is within the time range indicated by the time indication information, and the priority indicated by the first priority indication information is higher than the priority indicated by the second priority indication information, at this time, if the processor 502 determines to perform congestion or overload control on the first request of the UE according to the network condition, the first request of the UE is rejected, the time indication information is modified to be newly specified time indication information, and the second priority indication information is modified, so that the priority indicated by the second priority indication information is the same as the priority indicated by the first priority indication information.

Optionally, the processor 502 is configured to, when the receiving time of the first request received by the receiving module 501 is within a time range indicated by the time indication information, and a priority indicated by the first priority indication information is higher than a priority indicated by the second priority indication information; determining not to congestion or overload control the first request.

The processor 502 is specifically configured to determine not to perform congestion or overload control on the first request when the receiving time at which the receiving module 501 receives the first request is outside the time range indicated by the time indication information.

Further, the processor 502 may be further configured to accept the first request of the UE through the first request response.

Optionally, the processor 502 is specifically configured to, when the time when the receiving module 501 receives the first request is within the time range indicated by the time indication information, and the priority indicated by the first priority indication information is lower than or equal to the priority indicated by the second priority indication information; then it is determined to congestion or overload control the first request.

For example, if time indication information corresponding to the UE or the UE and the APN selected by the UE exists in the mobility management element, and second priority indication information corresponding to the time indication information, for example, a normal priority is present; if the processor 502 learns that the time when the receiving module 501 receives the first request is within the time range indicated by the time indication information and the first priority indication information carried in the first request indicates low priority, that is, the priority indicated by the first priority indication information is lower than or equal to the priority indicated by the second priority indication information, the first request of the UE is rejected.

Optionally, the processor 502 is further configured to initially set the time indication information and the second priority indication information.

If the time indication information corresponding to the UE does not exist, and the second priority indication information corresponding to the time indication information does not exist; then, when performing congestion or overload control on the second request of the UE, the processor 502 initially sets the time indication information and the second priority indication information.

It should be noted that the second request may be the first request.

Further, the processor 502 is specifically configured to, after rejecting the second request of the UE, initially set the time indication information and the second priority indication information, so that a priority indicated by the second priority indication information is the same as a priority of the second request.

For example, the processor 502 has not previously set the time indication information selected for the UE or the UE and the second priority indication information corresponding to the time indication information, and after the receiving module 501 receives the second request message sent by the UE, and rejects the second request of the UE due to congestion or overload control performed on the UE, the processor 502 initially sets the time indication information and the second priority indication information so that the priority indicated by the second priority indication information is the same as the priority of the second request. The time indication information and the second priority indication information of the initial setting may be stored in a context of the UE or a table for storing time indication information.

In addition, as shown in fig. 12, the mobility management element 50 further includes:

a register 503, configured to store the information corresponding to the UE and the second priority indication information.

The embodiment of the invention provides a mobile management network element, which can judge whether to carry out congestion or overload control on the current request of the UE according to the network condition when meeting a certain condition according to the received first request of the UE, the time indication information corresponding to the UE and the second priority indication information corresponding to the time indication information; otherwise, the request of the UE is refused. Therefore, the problem that the mobile management network element rejects the normal access request supporting the UE with double priorities when the network only carries out congestion or overload control on the access request with low priority can be solved; in addition, the mobility management network element determines whether to reject the access request of this time from the UE according to the stored time indication information and the priority indication information corresponding to the time indication information, and does not need to determine whether to reject the access request of this time from the UE according to the current congestion/control policy for each access request, thereby improving the processing efficiency of the mobility management network element.

Yet another embodiment of the present invention provides a system for congestion control, which includes a mobility management element, a UE, and a gateway device.

Based on the system, the embodiment of the present invention provides another mobility management element 60, where the mobility management element 60 corresponds to the mobility management element in the congestion control method provided in the third embodiment of the foregoing method, and therefore, the detailed description of each module may be a description of the foregoing step, which is not described herein again. The mobility management element 60, as shown in fig. 13, includes:

a receiving module 601, configured to receive a first request with a normal priority sent by a UE when a low-priority access request of the UE is subjected to congestion or overload control.

In this embodiment of the present invention, the first request may be a mobile management request or a session management request

A processor 602, configured to generate a session management message according to the first request received by the receiving module 601, where the session management message includes identification information used to indicate that a bearer is allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control.

Optionally, the processor 602 may determine that the UE is an access request of a normal priority initiated when the access request of a low priority is subjected to congestion or overload control according to indication information that the first request received by the receiving module 601 includes access request when the access request of a low priority is subjected to congestion or overload control.

Optionally, the receiving module 601 is specifically configured to, when the low-priority access request of the UE is subjected to congestion or overload control, receive the first request sent by the UE after the mobility management element notifies a radio access network to perform EAB for the low-priority access request of the UE.

In this case, the processor 602 may determine, according to the information of the receiving module 601, that the UE is a normal-priority access request initiated when a low-priority access request is subjected to congestion or overload control.

Optionally, the receiving module 601 is specifically configured to, when the low-priority access request of the UE is subjected to congestion or overload control, receive the first request when the time of receiving the first request is within a time range indicated by the stored time indication information corresponding to the UE, and a priority of the first request of the UE is higher than a priority indicated by the priority indication information corresponding to the time indication information.

A sending module 60, configured to send the session management message generated by the processor 602 to the gateway device; so that the gateway device maintains, in the context of the bearer allocated for the UE, identification information indicating that the bearer is an allocated bearer when a low priority access request of the UE is subject to congestion or overload control.

Further, the processor 602 is further configured to maintain, in the generated charging data record of the bearer, identification information indicating that the bearer is a bearer allocated when a low-priority access request of the UE is subjected to congestion or overload control.

Wherein the processor 602 is further configured to, after the gateway device allocates the bearer, save, in the context of the bearer, identification information indicating that the bearer is an assigned bearer when a low-priority access request of the UE is subjected to congestion or overload control.

Further, the processor 602 is configured to, when it is determined that the UE is not directly obtained from the first request when the low-priority access request is subjected to congestion or overload control, before the gateway device allocates the bearer, save information of the bearer of the UE to be established, where the information of the bearer includes: the bearer identification and the indication information that the UE requests access when the access request with low priority is subjected to congestion or overload control.

Further, the processor 602 is further configured to store, in the generated CDR of the bearer, identification information indicating that the bearer is a bearer allocated when the low-priority access request of the UE is subjected to congestion or overload control, so that the CDR can be indicated by the identification information as the CDR of the bearer allocated by the UE when the low-priority access request is subjected to congestion or overload control.

Based on the system for congestion control provided in the still another embodiment, an embodiment of the present invention provides another UE 70, where the UE 70 corresponds to the UE in the method for congestion control provided in the third embodiment of the foregoing method, and therefore, specific descriptions of each module may be descriptions of the foregoing steps, which are not described herein again. As shown in fig. 14, the UE 70 includes:

the processor 701 is configured to determine that an access request with a low priority is subjected to congestion or overload control, and generate a first request, where the first request includes indication information of requesting access when the access request with the low priority is subjected to congestion or overload control.

Optionally, the processor 701 is specifically configured to reject the low-priority access request sent by the mobility management element, where the mobility management element carries time indication information for the UE in an access request response message, the UE starts a timer according to the time indication information, and during the running period of the timer, the low-priority access request cannot be sent; or

Further, the first request generated by the processor 701 further includes: priority indication information for identifying a priority of the first request; wherein the priority of the first request is a normal priority.

A sending module 702, configured to send the first request generated by the processor 701 to a mobility management network element; so that the mobility management network element and the gateway device allocate a bearer for the UE, and maintain, in the context of the bearer, identification information for identifying the bearer as the bearer allocated when a low-priority access request of the UE is subjected to congestion or overload control.

Based on the system for congestion control provided in yet another embodiment, an embodiment of the present invention provides another gateway device 80, where the gateway device 80 corresponds to the gateway device in the method for congestion control provided in the third embodiment of the foregoing method, and therefore, a detailed description of each module may be a description of the foregoing steps, which is not described herein again. As shown in fig. 15, the gateway apparatus 80 includes:

a receiving module 801, configured to receive a session management message sent by a mobility management network element, where the session management message includes identification information used to indicate that a bearer is allocated to the UE when a low-priority access request of the UE is subjected to congestion or overload control.

And the gateway equipment corresponds to the APN selected by the UE access request.

A processor 802, configured to allocate the bearer for the UE according to the session management message received by the receiving module 801, and store, in the context of the bearer, identification information indicating that the bearer is allocated when a low-priority access request of the UE is subject to congestion or overload control; and generating a session management response message, wherein the session management response message carries indication information of the bearer allocated to the UE.

A sending module 803, configured to send the first response message generated by the processor 802 to the mobility management network element.

Optionally, the sending module is configured to send the session management response message generated by the processor to the mobility management network element.

Further, the processor 802 is further configured to save, in the generated CDR of the bearer, identification information indicating that the bearer is the bearer allocated for the UE when a low priority access request of the UE is subjected to congestion or overload control.

For example, an information element in the CDR may be used to identify information identifying the bearer allocated when a low priority access request is subject to congestion or overload control. Optionally, when a flag bit in the information element is set to "allocate a bearer when the low-priority access request is subjected to congestion or overload control", the CDR is used to identify the bearer allocated by the UE when the low-priority access request is subjected to congestion or overload control.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

1. A method of congestion control, comprising:

when the access request with low priority is subjected to congestion or overload control, the UE sends the access request with normal priority to a mobile management network element;

wherein, the access request of normal priority includes the indication information of the access request when the access request of low priority is subject to congestion or overload control.

2. The method of claim 1, wherein the normal priority access request is used to request the mobility management element and the gateway device to allocate a bearer for the UE, and wherein identification information is stored in a context of the bearer, and the identification information is used to identify the bearer as the bearer allocated when a low priority access request of the UE is subjected to congestion or overload control.

3. The method of claim 2, wherein the normal priority access request further includes priority indication information, and the priority indication information is used to indicate that the priority of the normal priority access request is a normal priority.

4. The method according to any of claims 1 to 3, wherein the UE determines that a low priority access request is subject to congestion or overload control, comprising:

the access request with low priority sent by the UE is rejected by the mobility management element, an access request response message received from the mobility management element carries time indication information for the UE, the UE starts a timer according to the time indication information, and the access request with low priority cannot be sent during the running period of the timer.

5. The method according to any of claims 1 to 3, wherein the UE determines that a low priority access request is subject to congestion or overload control, comprising:

receiving indication information for enabling extended access control, EAB, for the low priority access request from a wireless access network.

6. The method according to any of claims 1 to 3, wherein the UE determines that a low priority access request is subject to congestion or overload control, comprising:

the sent Radio Resource Control (RRC) connection request message with low priority is rejected by a wireless communication network, time indication information aiming at the UE is carried in an RRC connection response message received from the wireless communication network, the UE starts a timer according to the time indication information, and the UE cannot send the RRC connection request with low priority when the timer runs.

7. Method according to any of claims 1 to 3, wherein said normal priority access request comprises a packet data network, PDN, connection request.

8. A User Equipment (UE), comprising:

a generating unit, configured to generate a normal-priority access request when the processing unit determines that the low-priority access request is subjected to congestion or overload control, where the normal-priority access request includes indication information that access is requested when the low-priority access request is subjected to congestion or overload control;

a sending unit, configured to send the access request with the normal priority generated by the generating unit to a mobility management network element.

9. The UE of claim 8, wherein the normal priority access request is used to request the mobility management element and the gateway device to allocate a bearer for the UE, wherein identification information is stored in a context of the bearer, and the identification information is used to identify the bearer as the bearer allocated when a low priority access request of the UE is subjected to congestion or overload control.

10. The UE according to claim 8 or 9, wherein the normal priority access request generated by the generating unit further includes priority indication information, and the priority indication information is used to indicate that the priority of the normal priority access request is a normal priority.

11. The UE according to claim 8 or 9, wherein the low-priority access request sent by the UE is rejected by the mobility management element, and an access request response message received from the mobility management element carries time indication information for the UE, and the processing unit is specifically configured to start a timer according to the time indication information, and during a running period of the timer, the low-priority access request cannot be sent, so as to determine that the low-priority access request is subjected to congestion or overload control.

12. The UE of claim 8 or 9, wherein the processing unit is specifically configured to receive, from a wireless communication network, indication information that extended access control, EAB, is enabled for the low priority access request, thereby determining that the low priority access request is subject to congestion or overload control.

13. The UE according to claim 8 or 9, wherein the radio resource control RRC connection request message of the low priority sent by the UE is rejected by a wireless communication network, and a RRC connection response message received from the wireless communication network carries time indication information for the UE, and the processing unit is specifically configured to start a timer according to the time indication information, and when the timer runs, the UE cannot send the RRC connection request of the low priority, thereby determining that the access request of the low priority is subject to congestion or overload control.

14. The UE of claim 8 or 9, wherein the normal priority access request comprises a packet data network, PDN, connection request.

15. A User Equipment (UE), comprising:

the processor is used for determining that the access request with low priority is subjected to congestion or overload control and generating the access request with normal priority, wherein the access request with normal priority comprises the indication information of requesting access when the access request with low priority is subjected to congestion or overload control;

a sending module, configured to send the access request with the normal priority generated by the processor to a mobility management network element.

16. The UE of claim 15, wherein the normal priority access request is used to request the mobility management element and the gateway device to allocate a bearer for the UE, wherein identification information is stored in a context of the bearer, and the identification information is used to identify the bearer as the bearer allocated when a low priority access request of the UE is subjected to congestion or overload control.

17. The UE of claim 15 or 16, wherein the normal priority access request generated by the processor further includes priority indication information, and the priority indication information is used to indicate that the priority of the normal priority access request is a normal priority.

18. The UE according to claim 15 or 16, wherein the low-priority access request sent by the UE is rejected by the mobility management element, and an access request response message received from the mobility management element carries time indication information for the UE, and the processor is specifically configured to start a timer according to the time indication information, and during a running period of the timer, the low-priority access request cannot be sent, so that it is determined that the low-priority access request is subject to congestion or overload control, and the normal-priority access request is generated.

19. The UE of claim 15 or 16, wherein the processor is further configured to receive an indication from a wireless communication network that extended access control, EAB, is enabled for the low priority access request, to determine that the low priority access request is subject to congestion or overload control, and to generate the normal priority access request.

20. The UE according to claim 15 or 16, wherein the radio resource control RRC connection request message of low priority sent by the UE is rejected by a wireless communication network, and a RRC connection response message received from the wireless communication network carries time indication information for the UE, and the processor is specifically configured to start a timer according to the time indication information, and when the timer runs, the UE cannot send the RRC connection request of low priority, thereby determining that the access request of low priority is subject to congestion or overload control, and generating the access request of normal priority.

21. The UE of claim 15 or 16, wherein the normal priority access request comprises a packet data network, PDN, connection request.

22. A computer readable storage medium having stored therein instructions which, when run on a computer, cause a processor to perform the method of any of claims 1 to 7.