CN103379659A - Method and apparatus for realizing access request in dual priority scene - Google Patents
Method and apparatus for realizing access request in dual priority scene Download PDFInfo
- Publication number
- CN103379659A CN103379659A CN2012101134339A CN201210113433A CN103379659A CN 103379659 A CN103379659 A CN 103379659A CN 2012101134339 A CN2012101134339 A CN 2012101134339A CN 201210113433 A CN201210113433 A CN 201210113433A CN 103379659 A CN103379659 A CN 103379659A
- Authority
- CN
- China
- Prior art keywords
- priority
- timer
- access request
- message
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000009977 dual effect Effects 0.000 title abstract description 10
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 230000011664 signaling Effects 0.000 description 5
- 101100264195 Caenorhabditis elegans app-1 gene Proteins 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 101100055496 Arabidopsis thaliana APP2 gene Proteins 0.000 description 2
- 101100016250 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) GYL1 gene Proteins 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method and an apparatus for realizing an access request in a dual priority scene, so that in a network congestion scene, a terminal can deal with different access requests of applications having different priorities in different ways according to a retreat timer, and access demands of equipment having multiple priorities can be satisfied. The method comprises steps that a user terminal (UE) determines a priority limited by a retreat timer according to a priority identifier of the retreat timer when a retreat timer is running locally; and the UE compares a priority of the to-be-sent access request with the priority limited by the retreat timer, and if the priority of the to-be-sent access request is higher than the priority limited by the retreat timer, the UE sends the access request to a network side.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing an access request in a multi-priority scenario.
Background
At this stage, the terminal can use only one access priority, i.e. low access priority (low access priority) or normal access priority (normal access priority). A terminal configured as a non-access stratum (NAS) layer low-priority (NAS signaling low priority) can only initiate an access request with priority of lowaccess priority. According to the existing congestion control protocol, in order to solve the network congestion and overload situation which may be caused by introducing machine communication, the network introduces a back-off timer mechanism, that is, once a terminal starts a back-off timer, before the timer is overtime, the terminal cannot initiate any other access request except an urgent (emergency) access request and an access request with a higher access level (such as an access request with an access level of 11-15).
At present, 3GPP proposes a requirement for a multi-priority device (dual priority device), that is, in some special scenarios (for example, sending service alarm information or notification), the NAS signaling lowpriority may also be configured to initiate an access request with a priority of a normal access priority. Therefore, the terminal may send an access request to the network using different access priorities according to different requirements of the application program, including a mobility management request message and a session management request message.
This requires that when congestion and overload occur in the network, the network can treat requests of different access priorities of the terminal differently according to the current congestion status. For example, when the network congestion procedure is light, only the access request with the priority of low access priority initiated by the terminal is rejected, and the access request with the priority of normal access priority initiated by the terminal is still accepted and processed according to the relevant protocol; after a major disaster occurs and when network congestion is serious, the network only processes an emergency access request, and rejects an access request with a priority of low access priority or an access request with a priority of normal access priority.
However, according to the existing protocol, the backoff timer cannot differentiate the priority of the access request of the terminal, which results in that only the terminal starts the corresponding backoff timer, and the terminal cannot initiate the access request with the priority of low access priority or initiate the access request with the priority of normal access priority, regardless of whether the terminal is configured with NAS signaling low priority or configured with NASsignaling normal priority.
In summary, the back-off timer mechanism in the existing standard cannot satisfy the requirement of the dual priority device proposed by 3 GPP.
Disclosure of Invention
The invention provides a method and a device for realizing an access request in a multi-priority scene, so that a terminal can perform different treatment on the access requests of applications with different priorities according to a backoff timer in a network congestion scene to meet the access requirements of equipment with multiple priorities.
The embodiment of the invention provides the following specific technical scheme:
a method for realizing an access request under a multi-priority scene comprises the following steps:
when a back-off timer runs locally at a User Equipment (UE), determining the priority limited by the back-off timer according to the priority identification of the back-off timer;
and the UE compares the priority of the access request to be sent with the priority limited by the back-off timer, and if the priority is higher than the priority of the back-off timer, the UE sends the access request to a network side.
An access request implementation device under a multi-priority scene comprises:
the determining unit is used for determining the limited priority of the back-off timer according to the priority identifier of the back-off timer when the back-off timer runs locally;
and the comparison unit is used for comparing the priority of the access request to be sent with the priority limited by the back-off timer, and sending the access request to a network side if the priority is higher than the priority limited by the back-off timer.
Based on the above technical solution, in the embodiment of the present invention, a priority identifier is added to a locally running back-off timer to identify a highest priority level backed-off by the back-off timer, so that when it is determined that a priority level of an access request to be sent is higher than the highest priority level, the access request is sent to a network side, and when it is determined that the priority level of the access request to be sent is not higher than the highest priority level, the access request is not sent. The method provided by the invention can realize the differential treatment of the access requests to be sent with different priorities, can realize the network congestion control under the condition that the multi-priority equipment is accessed to the network and simultaneously provide the maximum possible service for the user, and meets the access requirement of the multi-priority equipment without changing the existing signaling flow. The method provided by the invention is suitable for a mobility management back-off timer and is also suitable for a session management back-off timer.
Drawings
FIG. 1 is a flowchart of a method for implementing an access request in a multi-priority scenario according to an embodiment of the present invention;
FIG. 2 is a flowchart of a detailed method of one embodiment of the present invention;
FIG. 3 is a flowchart of a detailed method of a second embodiment of the present invention;
FIG. 4 is a flowchart of a detailed method of a third embodiment of the present invention;
FIG. 5 is a flowchart detailing a method according to an embodiment of the present invention;
FIG. 6 is a flowchart detailing a method implemented in accordance with an embodiment of the present invention;
FIG. 7 is a schematic structural diagram of an apparatus for implementing an access request in a multi-priority scenario according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of an access request implementation apparatus in another multi-priority scenario according to an embodiment of the present invention.
Detailed Description
When a User Equipment (UE) is a device with multiple priorities, different access priorities are provided for different applications, in the prior art, a backoff timer locally run by the UE cannot distinguish the access priorities of the different applications, that is, cannot distinguish access requests to be sent with different priorities, and as long as the backoff timer is locally run, except for an emergency access and an access request with a higher access level (for example, an access request with an access level of 11 to 15), the UE is prohibited from initiating an access request for each application regardless of the access priority of the application. In order to meet the access requirements of devices with multiple priorities, and in particular to meet the access requirements of dual priority devices proposed by 3GPP, embodiments of the present invention provide an access request implementation method in a multiple priority scenario, so that a terminal can perform differentiated treatment on access requests of applications with different priorities according to a backoff timer in a network congestion scenario.
Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
In the embodiment of the present invention, the UE may be in an idle state or a connected state.
The back-off timer is a session management back-off timer or a mobility management back-off timer, and the corresponding access request is a session management request or a mobility management request.
In the embodiment of the invention, the access request refers to a request except an emergency (emergency) request and an access request with a higher access level (such as an access request with an access level of 11-15).
As shown in fig. 1, in the embodiment of the present invention, a detailed method for implementing an access request in a multi-priority scenario is as follows:
step 101: and when the UE locally has a back-off timer running, determining the priority limited by the back-off timer according to the priority identifier of the back-off timer.
The priority identifier of the back-off timer is configured by the UE according to a message carrying back-off timer information sent by a network side.
The information of the back-off timer at least comprises a back-off time value, and the back-off time value is used for setting an initial value of the back-off timer. Those skilled in the art can know from the disclosure of the present invention that the back-off timer can be set only by carrying the back-off timer in the message, and in practical applications, those skilled in the art can know that the message also carries other information besides the back-off time value, and can determine other information included in the message according to a specific application scenario.
The priority identifier of the back-off timer is configured according to a message carrying back-off timer information sent by a network side, and can be configured according to a reject message returned by the network side for rejecting UE access; or configuring the priority identifier of the backoff timer according to a release message sent by the network side for releasing the connection established by the UE.
In practical application, as long as the information related to the back-off timer configuration (such as the back-off time value of the back-off timer) is carried in the message sent by the network side, the priority identifier of the back-off timer can be configured according to the message, and is not limited to reject messages and release messages.
In the embodiment of the present invention, configuring the priority identifier of the back-off timer may be to set or update the priority identifier of the back-off timer. Specifically, after receiving a message carrying back-off timer information from a network side, the UE determines whether a back-off timer is currently running, and if not, starts the back-off timer and sets a priority identifier of the back-off timer; if yes, updating the priority identifier of the back-off timer.
Preferably, when starting the back-off timer and setting the priority identifier of the back-off timer, setting the back-off time value carried in the reject message or the release message as the initial value of the back-off timer and starting the back-off timer; and setting the priority identifier of the back-off timer as the priority identifier of the priority of the access request rejected by the rejection message, or as the priority identifier of the priority of the connection released by the release message. The realization mode does not need to change the message structure of the rejection message or the release message, and has simple realization and higher compatibility.
Preferably, when the priority identifier of the back-off timer is updated, the priority identifier of the back-off timer is updated to the priority identifier of the priority of the access request rejected by the reject message, or to the priority identifier of the priority of the connection released by the release message. The realization mode does not need to change the message structure of the rejection message or the release message, and has simple realization and higher compatibility.
In the LTE system, the connection released by the release message may be at least any one of a Packet Data Network (PDN) connection or a bearer; in a 3G system, the connection released by the release message may be a Packet data Protocol context (PDP context).
According to a specific application, the back-off timer information may further include priority indication information in addition to the back-off time value. In practical application, a priority indication bit for carrying priority indication information may be added to the reject message or the release message. And carrying priority indication information by adopting the priority indication bit, namely taking the value of the priority indication bit to indicate the priority. The UE and the network side only need to mutually agree on the position of the priority indication bit in the message and agree on the values of different priorities.
Optionally, when starting the back-off timer and setting the priority identifier of the back-off timer, setting the back-off time value carried in the reject message or the release message as the initial value of the back-off timer and starting the back-off timer; and when determining that the reject message or the release message carries the priority indication information, setting the priority identifier of the back-off timer as the priority identifier indicated by the priority indication information carried in the reject message or the release message.
Optionally, when the priority identifier of the back-off timer is updated and it is determined that the reject message or the release message carries the priority indication information, the priority identifier of the back-off timer is updated to the priority identifier indicated by the priority indication information carried in the reject message or the release message.
Preferably, the priority indicated by the priority indication information carried in the rejection message or the release message is the highest priority of the current backoff of the network side.
For example, when the priority indicated by the priority indication information carried in the reject message is low priority and the UE does not run a backoff timer locally, the backoff time value carried in the reject message is used as an initial value of the backoff timer, and the backoff timer is started after the priority identifier of the backoff timer is set to low priority, so that the UE can initiate an access request with a priority higher than low priority.
In the embodiment of the invention, the UE sets a corresponding priority identifier for each backoff timer which runs locally.
Step 102: and the UE compares the priority of the access request to be sent with the priority limited by the back-off timer, and if the priority is higher than the priority limited by the back-off timer, the UE sends the access request to a network side.
Preferably, the UE adds the priority indication information of the access request to the access request before sending the access request. Specifically, an upper layer application of the UE sends a request to an NAS layer of the UE, the request sent by the upper layer application of the UE carries priority indication information, the NAS layer of the UE determines, according to the priority indication information carried in the request, a priority of an access request to be sent generated for the request of the upper layer application, and the access request to be sent carries the priority indication information.
The access request is preset with a priority indication bit, the priority indication bit is adopted to carry priority indication information, namely, the value of the priority indication bit represents the priority of the access request. The UE and the network side only need to mutually agree on the position of the priority indication bit in the access request and agree on the values of different priorities. For example, when the priority indication bit is 0, it indicates that the priority of the access request is low priority; when the priority indication bit is 1, it indicates that the priority of the access request is a normal priority. In practical applications, the priority indication bits preset in the access request may be extended to more than one bit for describing priority indication information of more levels of priority.
Preferably, after the UE determines the priority level limited by the back-off timer, if it is determined that the priority level of the access request to be sent is not higher than the priority level limited by the back-off timer, the access request is not initiated.
Specifically, after determining the priority level limited by the back-off timer according to the priority level identifier of the back-off timer, the NAS layer of the UE determines whether the priority level of the access request is higher than the priority level limited by the back-off timer. When the access request is higher than the preset access request, the NAS layer sends the access request to a network side; and when the current time is not higher than the preset time, the NAS layer refuses the access request sent by the upper layer application, or caches the access request sent by the upper layer application.
Optionally, the NAS layer caches the access request sent by the upper application, and may send the access request to the network side after the NAS layer waits for the backoff timer to time out.
For example, the UE determines that the priority of the back-off timer limit is low priority, and when the priority of the access request to be sent is low priority, determines that the priority of the access request to be sent is not higher than the priority of the back-off timer limit, does not send the access request.
For another example, the UE determines that the priority of the back-off timer limit is low priority, and when the priority of the access request to be sent is normal priority, determines that the priority of the access request to be sent is higher than the priority of the back-off timer limit, sends the access request to the network side.
After receiving an access request of UE, a network side determines that the priority of the access request is not in a backoff priority range, then receives the access request and establishes connection with the UE, in the network operation process, network congestion is caused by equipment and the like, the network determines to release the connection with the priority in a preset range, the network releases the established connection aiming at the access request of the UE, returns a release message to the UE, and carries priority indication information in the release message; after receiving an access request of the UE, the network side determines that the priority of the access request is within the backoff priority range, directly rejects the access request, returns a rejection message to the UE, and carries priority indication information in the rejection message.
The method for implementing the back-off timer according to the embodiment of the present invention is specifically described below with reference to specific embodiments.
As shown in fig. 2, a specific embodiment provided by the embodiment of the present invention is as follows:
step 201: the upper application of the UE triggers the NAS layer of the UE to initiate an access request to the network, wherein the access request is a mobility management request or a session management request.
Step 202: the NAS layer of the UE determines whether a related backoff timer runs, if so, performs step 203, otherwise, performs step 204.
Step 203: the NAS layer of the UE determines the priority limited by the back-off timer according to the priority identifier (priority _ for _ timer) of the back-off timer, and judges whether the priority of the access request is higher than the priority limited by the running back-off timer, if so, step 204 is executed, otherwise, according to the existing protocol, the NAS layer of the UE sends the access request to the network side after waiting for the back-off timer to time out.
When the access request is a mobile management request, the NAS layer of the UE judges whether the priority of the access request is higher than that of a running mobile management back-off timer or not; when the access request is a session management request, the NAS layer of the UE judges whether the priority of the access request is higher than that of an operating session management back-off timer.
Step 204: the NAS layer of the UE sends the access request to the network side.
Step 205: if the network is currently in the congestion state, the network rejects the access request of the UE, and step 206 is executed, otherwise, the network processes the access request sent by the UE according to a corresponding procedure (mobility management procedure or session management procedure) specified by the existing protocol.
Step 206: if the NAS layer of the UE runs a backoff timer, updating the priority _ for _ timer of the backoff timer to a priority identifier indicated by priority indication information carried in a reject message; otherwise, taking the back-off time value carried in the reject message as the initial value of the back-off timer, starting the back-off timer, and updating the priority _ for _ timer of the back-off timer to the priority identifier indicated by the priority indication information carried in the reject message.
As shown in fig. 3, a second embodiment provided by the embodiment of the present invention is as follows:
the specific embodiment describes how to apply the back-off timer implementation method to mobility congestion control of an NAS layer after introducing a dual priority device, where a specific application scenario is that a UE is in an idle state and does not run a back-off timer, and at this time, an upper layer application a with a priority of low priority requests an NAS layer of the UE to establish a Packet Data Network (PDN) connection for the UE.
Step 301: the upper layer application a with the priority of low requests the NAS layer to establish the PDN connection for it.
Step 302: the NAS layer of the UE initiates a service request (service request) message, and sets the priority indication information to low priority in the service request message.
Step 303: when the network is in a congestion state, a Mobility Management Entity (MME) at the network side determines an access request with a backoff priority of low priority or a priority lower than the low priority.
Step 304: the MME on the network side rejects the service request message of the UE, generates a reject (service reject) message, carries a back-off time value (T3346) of the mobility management back-off timer in the service reject message, and sends the reject message to the UE.
Step 305: the UE sets a corresponding mobility management back-off timer according to the back-off time value T3346 carried in the service request message, and sets the priority identifier priority _ for _ timer of the mobility management back-off timer to be the priority low corresponding to the rejected service request message.
In another implementation, the service reject message also carries indication information of a highest priority of a current backoff of the MME on the network side (for example, the highest priority of the current backoff of the MME is low priority), and then the priority identifier priority _ for _ timer of the mobility management backoff timer is set to the priority identifier indicated by the indication information carried in the service reject message (for example, the priority identifier of the mobility management backoff timer is set to the priority identifier low indicated by the low priority indicated by the indication information carried in the reject message).
Step 306: the application b with the priority of normal priority requests the NAS layer to establish a PDN connection for it.
Step 307: and the UE judges that the priority of the service request message of the application program b is higher than the priority to be backed off by the mobility management back-off timer.
Step 308: the UE initiates a service request message and sets priority indication information to a normal priority in the service request message.
Step 309: the MME on the network side receives the service request message, and returns a service accept (service accept) message for accepting the request to the UE.
Step 310: the PDN connection is successfully established for application b.
As shown in fig. 4, a third specific embodiment provided by the embodiment of the present invention is as follows:
the specific embodiment describes how to use the backoff timer implementation method for session management congestion control based on an Access Point Name (APN) after introducing a dual priority device, where a specific application scenario is that a UE is in a connected state, a session management backoff timer runs (the backoff time value of the session management backoff timer is T3396, and hereinafter, the session management backoff timer is referred to as T3396), the backoff priority of the session management backoff timer is low, and at this time, an application a and an application B that are accessed to the same APN3 and have different access priorities respectively request NAS layers of the UE to establish PDN connections for the application a and the application B.
Step 401: the UE is in connected state, and a session management backoff timer T3396 with APN3 runs, and the priority to backoff is low.
Step 402: application a with low priority sends app1 to the NAS layer requesting to establish PDN connectivity access to APN 3.
Step 403: the NAS layer of the UE determines that the priority of the application a corresponding to the app1 is not higher than the priority to be backed off by the T3396, and rejects the app1 request of the application a.
Step 404: application B with normal priority requests to send app2 to establish PDN connectivity access to APN 3.
Step 405: the NAS layer of the UE determines that the priority of application B corresponding to the app2 is higher than the priority to be backed off by T3396.
Step 406: the NAS layer of the UE transmits a PDN connection request (PDN connectivity request) to the network and sets priority indication information to a normal priority in the PDN connection request.
Step 407: due to the device, the APN3 requested by APP2 is in a heavily congested state, and the network decides to reject all access requests with a priority of normal priority or lower to APN 3.
Step 408: the network rejects the PDN connection request of the UE and returns a PDN rejection (PDNConnecticity reject) message to the UE.
Step 409: the UE updates the backoff priority flag of T3396 to normal.
The updating of the priority identifier of T3396 may specifically be that the UE updates according to APP2, or that the UE updates according to the received reject message, and the specific implementation is the same as the above improved updating method, which is not described herein again.
As shown in fig. 5, a fourth specific embodiment provided by the embodiment of the present invention is as follows:
the specific embodiment describes how to apply the back-off timer implementation method to APN-based mobility management congestion control after a dual priority device is referred. The embodiment can solve the problem existing after the existing back-off timer management mechanism introduces the dual priority device: and when the network is congested, the UE requests to access the network through the normal priority so as to acquire the loophole of the low-priority service.
Step 501: the UE moves to a new network, initiates an attach request (attach request) to the network, wherein the attach request message does not carry a designated APN, and sets priority indication information in the attach request as a normal priority.
Step 502: the default APN (default APN) for the attach request is overloaded and the network decides to back off all the attach requests with low priority or below low priority for accessing the default APN.
Step 503: the network determines that the priority of the received attach request is higher than that of the request to be backed off, receives the attach request of the UE, establishes the connection between the UE and the default APN, and returns an attach accept (attach accept) message to the UE.
Step 504: and the UE initiates a PDN connection request of an application with low priority to the network, and sets the priority indication information in the PDN connection request to be low priority.
Step 505: the network is in a congestion state at present, decides to back off the PDN connection request with low priority or lower than low priority, rejects the PDN connection request of the UE, returns a PDN connection reject (PDN connection reject) message to the UE, and carries a back-off time value of a session management back-off timer in the reject message (T3396).
Step 506: the UE starts a session management back-off timer, sets an initial value of the session management back-off timer to T3396, and sets a priority flag of the session management back-off timer to low.
As shown in fig. 6, a fifth embodiment provided by the embodiment of the present invention is as follows:
the specific embodiment provides a process of setting a back-off timer according to a release message carrying a back-off time value and used for releasing an established connection, when receiving the release message sent by a network side.
Step 601: the UE is in a connected state, and a session management backoff timer without the APN4 runs; or the session management backoff timer T3396 of APN4 runs (the backoff time value of the backoff timer is T3396, which is referred to as T3396 herein as the session management backoff timer), and the backoff priority thereof is low.
Step 602: application a4 with a normal priority sends a request to the UE's NAS layer to establish PDN connectivity access to APN 4.
Step 603: and the NAS layer of the UE determines that a corresponding backoff timer does not operate or determines that the priority of the application A4 is not in the range backed off by the backoff timer T3396, sends a PDN connection request to the network side, and sets priority indication information to a normal priority in the PDN connection request.
Step 604: and the network receives the PDN connection request of the UE and accepts the PDN connection request.
Step 605: the network returns a PDN connection Accept (PDN connectivity Accept) message to the UE.
Step 606: the UE establishes PDN connection of the application A4 with the network and performs data transmission of the application A4.
Step 607: the network congestion situation is aggravated, the network only provides service for the emergency access, and the connection with the established priority being the normal priority or lower is determined to be released.
Step 608: the network returns a release message to the UE to release the PDN connection established by application a4, where the release message carries a back-off time value (e.g. T3396).
Optionally, the release message further carries priority indication information, where the priority indicated by the priority indication information is a normal priority.
Step 609: after receiving a release message for releasing the PDN connection established by the application A4, the UE judges whether a session management backoff timer with the APN4 is locally operated, and if the session management backoff timer is locally operated, the UE updates the priority identifier of the session management backoff timer to normal according to priority indication information carried in the release message or the priority of the PDN connection request; otherwise, the session management backoff timer for APN4 is started, its initial value is set to T3396, and its priority flag is set to normal.
In the second to fifth embodiments, the LTE network system is taken as an example, the MME performs corresponding operations on the network side in the LTE network system, and other network entities may perform corresponding operations on other network systems, for example, in a third generation wireless communication system (3G), the serving GPRS (General Packet Radio Service) support node (SGSN) performs corresponding operations on the network side, and a specific processing procedure is the same as a specific processing procedure of the MME, which is not described herein again.
Based on the same inventive concept, in the embodiments of the present invention, there is also provided an apparatus for implementing an access request in a multi-priority scenario, where the apparatus may be in an idle state or a connected state, and an implementation principle of the apparatus is the same as that of the above method for implementing a backoff timer, and the same parts are not described again, as shown in fig. 7, the apparatus mainly includes the following processing units:
a determining unit 701, configured to determine, when a backoff timer runs locally, a priority level limited by the backoff timer according to a priority level identifier of the backoff timer;
a comparing unit 702, configured to compare the priority of the access request to be sent with the priority limited by the back-off timer, and if the priority is higher than the priority limited by the back-off timer, send the access request to the network side.
The comparing unit 702 is specifically configured to add the priority indication information of the access request to the access request before sending the access request.
The comparing unit 702 is further configured to not initiate the access request when the priority of the access request to be sent is not higher than the priority limited by the back-off timer.
Preferably, as shown in fig. 8, the apparatus further includes a configuration unit 703 configured to configure a priority identifier of the backoff timer according to a message carrying backoff timer information sent by the network side.
The configuration unit 703 is specifically configured to configure a priority identifier of the back-off timer according to a reject message returned by the network side for rejecting UE access; or, configuring the priority identifier of the back-off timer according to a release message sent by the network side for releasing the connection established by the UE.
The configuration unit 703 is specifically configured to determine whether a back-off timer is currently running, and if not, start the back-off timer and set a priority identifier of the back-off timer; if yes, updating the priority identifier of the back-off timer.
Preferably, the configuration unit 703 is specifically configured to, when starting the backoff timer and setting a priority identifier of the backoff timer, set a backoff time value carried in the reject message or the release message as an initial value of the backoff timer and start the backoff timer; and
and setting the priority identifier of the back-off timer as the priority identifier of the priority of the access request rejected by the rejection message, or as the priority identifier of the priority of the connection released by the release message.
Preferably, the configuration unit 703 is specifically configured to, when updating the priority identifier of the back-off timer, update the priority identifier of the back-off timer to the priority identifier of the priority of the access request rejected by the reject message, or to the priority identifier of the priority of the connection released by the release message.
Optionally, the configuration unit 703 is specifically configured to, when starting the backoff timer and setting a priority identifier of the backoff timer, set a backoff time value carried in the reject message or the release message as an initial value of the backoff timer and start the backoff timer; and when determining that the reject message or the release message carries the priority indication information, setting the priority identifier of the back-off timer as the priority identifier indicated by the priority indication information carried in the reject message or the release message.
Optionally, the configuration unit 703 is specifically configured to, when the priority identifier of the back-off timer is updated and it is determined that the reject message or the release message carries the priority indication information, update the priority identifier of the back-off timer to the priority identifier indicated by the priority indication information carried in the reject message or the release message.
Preferably, the priority indicated by the priority indication information carried in the rejection message or the release message is the highest priority of the current backoff of the network side.
The back-off timer is a session management back-off timer or a mobility management back-off timer.
Based on the above technical solution, in the embodiment of the present invention, a priority identifier is added to a locally running back-off timer to identify a highest priority level backed-off by the back-off timer, so that when it is determined that a priority level of an access request to be sent is higher than the highest priority level, the access request is sent to a network side, and when it is determined that the priority level of the access request to be sent is not higher than the highest priority level, the access request is not sent. Therefore, the different treatment of the access requests to be sent with different priorities can be realized, the maximum possible service can be provided for the user while the network congestion control is carried out under the condition that the multi-priority equipment is accessed to the network, the access requirements of the multi-priority equipment are met, particularly the access requirements of the dual priority equipment proposed by the 3GPP are met, and the existing signaling flow does not need to be changed.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (26)
1. A method for realizing an access request under a multi-priority scene is characterized by comprising the following steps:
when a back-off timer runs locally at a User Equipment (UE), determining the priority limited by the back-off timer according to the priority identification of the back-off timer;
and the UE compares the priority of the access request to be sent with the priority limited by the back-off timer, and if the priority is higher than the priority limited by the back-off timer, the UE sends the access request to a network side.
2. The method of claim 1, wherein the UE adds priority indication information for the access request to the access request prior to sending the access request.
3. The method of claim 1 or 2, wherein the UE compares the priority of the access request to be sent to the priority of the back-off timer limit, further comprising:
and if the priority of the access request to be sent is not higher than the priority limited by the back-off timer, not initiating the access request.
4. The method of claim 1, wherein the priority flag is configured by the UE according to a message carrying backoff timer information sent by a network side.
5. The method of claim 4, wherein the configuring the priority identifier of the back-off timer according to the message carrying the back-off timer information sent by the network side comprises:
configuring the priority identifier of the back-off timer according to a rejection message returned by a network side and used for rejecting the access of the UE;
or,
and configuring the priority identifier of the back-off timer according to a release message which is sent by a network side and used for releasing the connection established by the UE.
6. The method of claim 5, wherein configuring the priority identification of the back-off timer comprises:
the UE judges whether the back-off timer runs currently, if not, the back-off timer is started and the priority identification of the back-off timer is set;
and if so, updating the priority identifier of the back-off timer.
7. The method of claim 6, wherein starting the backoff timer and setting a priority identification of the backoff timer comprises:
setting the back-off time value carried in the rejection message or the release message as the initial value of the back-off timer and starting the back-off timer; and
and setting the priority identifier of the back-off timer as the priority identifier of the priority of the access request rejected by the rejection message, or as the priority identifier of the priority of the connection released by the release message.
8. The method of claim 6, wherein starting the backoff timer and setting a priority identification of the backoff timer comprises:
setting the back-off time value carried in the rejection message or the release message as the initial value of the back-off timer and starting the back-off timer; and
and when determining that the reject message or the release message carries priority indication information, setting the priority identifier of the back-off timer as the priority identifier indicated by the priority indication information carried in the reject message or the release message.
9. The method of claim 6, wherein updating the priority identification of the back-off timer comprises:
and updating the priority identifier of the back-off timer to be the priority identifier of the priority of the access request rejected by the rejection message, or to be the priority identifier of the priority of the connection released by the release message.
10. The method of claim 6, wherein updating the priority identification of the back-off timer comprises:
and updating the priority identifier of the back-off timer to the priority identifier indicated by the priority indication information carried in the rejection message or the release message when the rejection message or the release message is determined to carry the priority indication information.
11. The method according to claim 8 or 10, wherein the priority indicated by the priority indication information carried in the reject message or the release message is the highest priority of the current backoff at the network side.
12. The method of claim 1 or 2, wherein the UE is in an idle state or a connected state.
13. The method of claim 1, wherein the back-off timer is a session management back-off timer or a mobility management back-off timer.
14. An access request implementation apparatus under a multi-priority scenario, comprising:
the determining unit is used for determining the limited priority of the back-off timer according to the priority identifier of the back-off timer when the back-off timer runs locally;
and the comparison unit is used for comparing the priority of the access request to be sent with the priority limited by the back-off timer, and sending the access request to a network side if the priority is higher than the priority limited by the back-off timer.
15. The apparatus as claimed in claim 14, wherein the comparing unit is specifically configured to add the priority indication information of the access request to the access request before sending the access request.
16. The apparatus according to claim 14 or 15, wherein the comparing unit is further configured to not initiate the access request when the priority of the access request to be sent is not higher than the priority of the back-off timer limit.
17. The apparatus of claim 14, further comprising a configuration unit, configured to configure the priority identifier of the back-off timer according to a message carrying back-off timer information sent by a network side.
18. The apparatus of claim 17, wherein the configuration unit is specifically configured to configure the priority identifier of the back-off timer according to a reject message returned by a network side for rejecting UE access;
or,
and configuring the priority identifier of the back-off timer according to a release message which is sent by a network side and used for releasing the connection established by the UE.
19. The apparatus according to claim 18, wherein the configuration unit is specifically configured to determine whether the back-off timer is currently running, and if not, start the back-off timer and set a priority identifier of the back-off timer;
and if so, updating the priority identifier of the back-off timer.
20. The apparatus according to claim 19, wherein the configuration unit is specifically configured to, upon starting the back-off timer and setting a priority identification of the back-off timer,
setting the back-off time value carried in the rejection message or the release message as the initial value of the back-off timer and starting the back-off timer; and
and setting the priority identifier of the back-off timer as the priority identifier of the priority of the access request rejected by the rejection message, or as the priority identifier of the priority of the connection released by the release message.
21. The apparatus according to claim 19, wherein the configuration unit is specifically configured to, upon starting the back-off timer and setting a priority identification of the back-off timer,
setting the back-off time value carried in the rejection message or the release message as the initial value of the back-off timer and starting the back-off timer; and
and when determining that the reject message or the release message carries priority indication information, setting the priority identifier of the back-off timer as the priority identifier indicated by the priority indication information carried in the reject message or the release message.
22. The apparatus according to claim 19, wherein the configuration unit is specifically configured to, upon updating a priority identification of the back-off timer,
and updating the priority identifier of the back-off timer to be the priority identifier of the priority of the access request rejected by the rejection message, or to be the priority identifier of the priority of the connection released by the release message.
23. The apparatus according to claim 19, wherein the configuration unit is specifically configured to, upon updating a priority identification of the back-off timer,
and updating the priority identifier of the back-off timer to the priority identifier indicated by the priority indication information carried in the rejection message or the release message when the rejection message or the release message is determined to carry the priority indication information.
24. The apparatus according to claim 21 or 23, wherein the priority indicated by the priority indication information carried in the reject message or the release message is the highest priority of the current backoff at the network side.
25. The apparatus of claim 14 or 15, wherein the apparatus is in an idle state or a connected state.
26. The apparatus of claim 14, wherein the back-off timer is a session management back-off timer or a mobility management back-off timer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210113433.9A CN103379659B (en) | 2012-04-17 | 2012-04-17 | Access request implementation method and device under a kind of multipriority scene |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210113433.9A CN103379659B (en) | 2012-04-17 | 2012-04-17 | Access request implementation method and device under a kind of multipriority scene |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103379659A true CN103379659A (en) | 2013-10-30 |
| CN103379659B CN103379659B (en) | 2016-08-03 |
Family
ID=49464079
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210113433.9A Active CN103379659B (en) | 2012-04-17 | 2012-04-17 | Access request implementation method and device under a kind of multipriority scene |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103379659B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015109600A1 (en) * | 2014-01-27 | 2015-07-30 | 华为技术有限公司 | Ue and relevant call and response method |
| CN106097600A (en) * | 2016-05-30 | 2016-11-09 | 广州广电运通金融电子股份有限公司 | Device management method based on ATL, system and financial self-service equipment |
| CN106454999A (en) * | 2015-08-13 | 2017-02-22 | 中国移动通信集团公司 | Access control method and device |
| CN107079332A (en) * | 2014-11-10 | 2017-08-18 | Lg 电子株式会社 | Stop the method and user equipment of network insertion by ACDC |
| CN108632914A (en) * | 2017-03-17 | 2018-10-09 | 大唐移动通信设备有限公司 | One kind preventing terminal table tennis reorientation method and base station |
| CN109788525A (en) * | 2017-11-15 | 2019-05-21 | 展讯通信（上海）有限公司 | A kind of acceptance controlling method and device, storage medium, terminal |
| CN114208292A (en) * | 2020-06-29 | 2022-03-18 | 北京小米移动软件有限公司 | Access control method and device and storage medium |
| WO2022068813A1 (en) * | 2020-09-30 | 2022-04-07 | 维沃移动通信有限公司 | Congestion control method and apparatus, and terminal and network-side device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1533643A (en) * | 2001-06-18 | 2004-09-29 | 伊特兰通信有限公司 | Channel access method for power line carrier based media access control protocol |
| WO2012041197A1 (en) * | 2010-09-30 | 2012-04-05 | 电信科学技术研究院 | Method and network side device for handling mobility management process |
| CN102547912A (en) * | 2012-01-17 | 2012-07-04 | 电信科学技术研究院 | Access control method and device |
-
2012
- 2012-04-17 CN CN201210113433.9A patent/CN103379659B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1533643A (en) * | 2001-06-18 | 2004-09-29 | 伊特兰通信有限公司 | Channel access method for power line carrier based media access control protocol |
| WO2012041197A1 (en) * | 2010-09-30 | 2012-04-05 | 电信科学技术研究院 | Method and network side device for handling mobility management process |
| CN102547912A (en) * | 2012-01-17 | 2012-07-04 | 电信科学技术研究院 | Access control method and device |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015109600A1 (en) * | 2014-01-27 | 2015-07-30 | 华为技术有限公司 | Ue and relevant call and response method |
| CN107079332A (en) * | 2014-11-10 | 2017-08-18 | Lg 电子株式会社 | Stop the method and user equipment of network insertion by ACDC |
| US10972960B2 (en) | 2014-11-10 | 2021-04-06 | Lg Electronics Inc. | Method and user equipment for blocking network access by ACDC |
| US10645633B2 (en) | 2015-08-13 | 2020-05-05 | China Mobile Communications Group Co., Ltd. | Access control method and device |
| CN106454999A (en) * | 2015-08-13 | 2017-02-22 | 中国移动通信集团公司 | Access control method and device |
| CN106454999B (en) * | 2015-08-13 | 2019-10-08 | 中国移动通信集团公司 | A kind of connection control method and device |
| CN106097600A (en) * | 2016-05-30 | 2016-11-09 | 广州广电运通金融电子股份有限公司 | Device management method based on ATL, system and financial self-service equipment |
| CN106097600B (en) * | 2016-05-30 | 2019-01-25 | 广州广电运通金融电子股份有限公司 | Device management method, system and financial self-service equipment based on ATL |
| CN108632914B (en) * | 2017-03-17 | 2020-08-28 | 大唐移动通信设备有限公司 | Method and base station for preventing ping-pong redirection of terminal |
| CN108632914A (en) * | 2017-03-17 | 2018-10-09 | 大唐移动通信设备有限公司 | One kind preventing terminal table tennis reorientation method and base station |
| CN109788525A (en) * | 2017-11-15 | 2019-05-21 | 展讯通信（上海）有限公司 | A kind of acceptance controlling method and device, storage medium, terminal |
| CN109788525B (en) * | 2017-11-15 | 2020-09-18 | 展讯通信（上海）有限公司 | Admission control method and device, storage medium and terminal |
| CN114208292A (en) * | 2020-06-29 | 2022-03-18 | 北京小米移动软件有限公司 | Access control method and device and storage medium |
| CN114208292B (en) * | 2020-06-29 | 2024-01-30 | 北京小米移动软件有限公司 | Access control method and device and storage medium |
| WO2022068813A1 (en) * | 2020-09-30 | 2022-04-07 | 维沃移动通信有限公司 | Congestion control method and apparatus, and terminal and network-side device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103379659B (en) | 2016-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103379659B (en) | Access request implementation method and device under a kind of multipriority scene | |
| CN111466152B (en) | Method for processing resource shortage during protocol data unit session establishment process and user equipment thereof | |
| EP3574675B1 (en) | Control and management of reflective qos | |
| CN102186224B (en) | Method for controlling access and device | |
| CN107204938B (en) | Method and apparatus for transmitting low priority data, and method and apparatus for processing the same | |
| JP5607085B2 (en) | Method for managing emergency bearer service in a wireless communication system | |
| CN105723798B (en) | Method for enhancing packet data network connection process and user equipment | |
| US20180054778A1 (en) | Access Control Method and Device | |
| CN113301518A (en) | Communication method and device | |
| CN109729505B (en) | Service processing method and network equipment | |
| CN110035424A (en) | Policy-related (noun) communication means, device and system | |
| CN110062479A (en) | Method for controlling the service in wireless communication system | |
| WO2014176863A1 (en) | Access control method and device | |
| US20170086186A1 (en) | Method and apparatus for providing network access to a user equipment requesting voice service | |
| CN102413504B (en) | Congestion control method and equipment | |
| CN102404792A (en) | Overload control method and system | |
| WO2019091077A1 (en) | Method and device for triggering network switching, and computer storage medium | |
| EP2552132B1 (en) | Method, apparatus and system for processing enhanced multimedia priority service in circuit switched fallback mechanism | |
| CN103428822A (en) | Access method and system for shunting to wireless local area network, MME and UE | |
| CN103857005A (en) | Access control method and device | |
| EP3595345B1 (en) | Control plane connection management method and device | |
| CN103379578B (en) | A kind of method for controlling network congestion and terminal | |
| CN106797595B (en) | Method and apparatus for enhancing bearer continuity for 3GPP system changes | |
| CN103369709A (en) | A method and an apparatus for establishing PDN connectivity | |
| WO2013149554A1 (en) | Pdn connection deleting method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210602 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |