WO2013097503A1 - Procédé et dispositif de régulation d'encombrement - Google Patents

Procédé et dispositif de régulation d'encombrement Download PDF

Info

Publication number
WO2013097503A1
WO2013097503A1 PCT/CN2012/081968 CN2012081968W WO2013097503A1 WO 2013097503 A1 WO2013097503 A1 WO 2013097503A1 CN 2012081968 W CN2012081968 W CN 2012081968W WO 2013097503 A1 WO2013097503 A1 WO 2013097503A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility management
congestion control
network side
terminal
network
Prior art date
Application number
PCT/CN2012/081968
Other languages
English (en)
Chinese (zh)
Inventor
王胡成
Original Assignee
电信科学技术研究院
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院 filed Critical 电信科学技术研究院
Publication of WO2013097503A1 publication Critical patent/WO2013097503A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H04W74/085—Random access procedures, e.g. with 4-step access with collision treatment collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections

Definitions

  • the priority of the Chinese Patent Application for "Congestion Control Method and Apparatus” is hereby incorporated by reference in its entirety.
  • TECHNICAL FIELD The present invention relates to the field of wireless communications, and in particular, to a congestion control method and apparatus.
  • BACKGROUND OF THE INVENTION The existing 3rd Generation Partnership Project (3GPP) protocol proposes an Access Point Name (APN) based APN based Mobility Management control mechanism.
  • APN Access Point Name
  • the network performs APN-based mobility management congestion control on user equipment (UE) that subscribes to a special APN, and when the UE sends a mobility management (MM) request (request)
  • UE user equipment
  • MM mobility management
  • the network determines whether to initiate the APN-based mobility management congestion control, and if so, sends the mobile management request rejection message to the UE, and may carry the mobility management backoff timer in the rejection message.
  • the information of the -off timer is that after receiving the information of the mobility management backoff timer, the UE does not initiate an attach procedure other than the emergency service to the network before the mobility management backoff timer expires.
  • the mobility management backoff time value that is, the timeout period of the mobility management backoff timer
  • the network rejects the UE before the time corresponding to the mobility management backoff time value arrives. In addition to the emergency request of the emergency business.
  • the foregoing network determines that the APN-based mobility management congestion control is initiated as follows: The rate of the Mobile Management Non-Access Stratum (NAS) message sent by a group of UEs that have subscribed to the special APN exceeds a certain threshold or Dropped below a certain threshold; and/or, configuration in network management.
  • NAS Mobile Management Non-Access Stratum
  • the existing 3GPP protocol also proposes a general NAS layer mobility management congestion control (General NAS Mobility Management Congestion Control) mechanism.
  • General NAS Mobility Management Congestion Control General NAS Mobility Management Congestion Control
  • the mobility management congestion control of the NAS layer is common.
  • the network determines whether to initiate the movement of the universal NAS layer. Management congestion control, if yes, sending a rejection message of the mobility management request to the UE, and carrying the information of the mobility management backoff timer in the rejection message, after receiving the information of the mobility management backoff timer, the UE starts the local The backoff timer, before the backoff timer expires, the UE cannot initiate any non-emergency service, non-high priority or mobile management request of the called service to the network.
  • the timeout value is the timeout period of the mobility management backoff timer.
  • the network rejects the mobility management request of any non-called service sent by the UE; if the network side is already the UE Once the emergency bearer context is established, the network can accept any mobility management request from the UE.
  • the UE in the connected state may initiate a Tracking Area Update (TAU) procedure.
  • TAU Tracking Area Update
  • the above judgment starts the general NAS layer mobile management congestion control based on the following:
  • the network is in the General Overload Condition.
  • the UE may initiate a mobility management request for the emergency bearer service, but the mobility management backoff The timer continues to run.
  • the UE may initiate a mobility management request for the emergency bearer service during the operation of the mobility management backoff timer, the purpose of which is to consider that the network may have recovered from the congestion state before the mobility management backoff timer expires, so that the UE may receive the Mobile management request.
  • This mechanism has been introduced in 3GPP TS 24.301.
  • the mobility management request initiated by the UE is a service request (service request), a TAU, or a Routing Area Update (RAU) request
  • the NAS layer of the network cannot determine whether the mobility management request is for the emergency bearer service. Therefore, the network may still reject the mobility management request, making the mechanism impossible.
  • the congestion control method proposed by the 3GPP by sending a mobility management backoff timer, prevents the terminal from initiating a mobility management request in the case of network congestion, and saves the mobility management backoff time value on the network side, and rejects the mobility management request initiated by the subsequent UE.
  • this method may bring the following problems: If the network has recovered from the congestion state before the time corresponding to the mobility management backoff time value arrives, the mobile management request initiated by the terminal will still be rejected by the network, thereby making the terminal unable to access normally.
  • the internet SUMMARY OF THE INVENTION
  • the embodiments of the present invention provide a congestion control method and device, which are used to improve the success rate of a terminal accessing a network.
  • a congestion control method comprising:
  • the network side device sets the mobility management backoff time value to be invalid after determining that the current network congestion state is restored and the time corresponding to the saved mobility management backoff time value for congestion control is not reached;
  • the network side device After receiving the mobility management request sent by the terminal, the network side device determines whether to accept the mobility management request according to the current network condition.
  • a congestion control device comprising:
  • a first setting unit configured to determine, in the congestion state of the current network, the saved and saved for congestion control After the time corresponding to the management backoff time value has not arrived, the mobile management backoff time value is set to be invalid; the control unit is configured to: after receiving the mobility management request sent by the terminal, determine whether to accept the mobile according to the current network condition. Manage requests.
  • FIG. 1 is a schematic flow chart of a method for providing an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a device according to an embodiment of the present invention.
  • DETAILED DESCRIPTION OF THE EMBODIMENTS In order to improve the success rate of a terminal accessing a network, the embodiment of the present invention provides a congestion control method.
  • a network management device recovers from a current network congestion state and saves a mobility management backoff time for congestion control. When the time corresponding to the value does not arrive, the saved mobility management backoff time value is set to be invalid. Thereafter, after receiving the mobility management request sent by the terminal, the mobility management request is no longer directly rejected according to the mobility management backoff time value.
  • a congestion control method provided by an embodiment of the present invention includes the following steps:
  • Step 10 After determining that the current network congestion state is restored and the saved time corresponding to the mobility management backoff time value for congestion control is not reached, the network management device sets the mobility management backoff time value to be invalid.
  • Step 11 After receiving the mobility management request sent by the terminal, the network side device determines whether to accept the mobility management request according to the current network condition.
  • the specific implementation can be as follows:
  • the network side device determines, according to the current network condition, whether a condition for starting the mobility management congestion control based on the APN of the terminal subscription is met, and if not, determining that the mobility management signaling of the terminal that has subscribed to the APN is on the network side. No congestion occurs, and congestion state recovery is determined. If yes, it is determined that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side, and it is determined that the congestion state is not restored.
  • the condition for starting the mobility management congestion control of the APN based on the subscription of the terminal is: the rate of the mobility management non-access stratum (NAS) message sent by the group of UEs that have subscribed to the special APN exceeds a certain threshold or is lowered. Below a certain threshold; and / or, in network management Configuration.
  • NAS mobility management non-access stratum
  • the network-side device When the network-side device initiates the APN-based mobility management congestion control for the terminal, the network-side device may set the value of the first congestion control startup identifier corresponding to the APN, so that the first congestion control startup identifier indicates that the terminal is subscribed to the APN.
  • Mobile management signaling is congested on the network side;
  • the mobility management backoff time value is set to be invalid, and the specific implementation may be as follows:
  • the network side device modifies the value of the first congestion control startup identifier, so that the first congestion control startup identifier indicates the mobility management of the terminal that has subscribed to the APN. Signaling does not occur on the network side.
  • step 10 it is determined whether the current network congestion state is restored, and the specific implementation may be 3 ⁇ 4 mouth:
  • the network side device determines, according to the current network condition, whether the condition for starting the universal mobility management congestion control is met, and if not, determining that the network side device is not overloaded, and determining that the network congestion state is restored, if satisfied, Then, it is determined that the network side device is overloaded, and it is determined that the network congestion state is not restored.
  • the condition for starting the general mobility management congestion control is:
  • the network managed by the network side device is in a general overload condition (General Overload Condition).
  • the network side device When the network side device starts the general mobility management congestion control for the terminal, the network side device may set the second congestion control startup identifier corresponding to the network side device, so that the second congestion control startup identifier indicates that the network side device is overloaded;
  • the mobility management backoff time value is set to be invalid.
  • the specific implementation may be as follows: The network side device modifies the value of the second congestion control startup identifier, so that the second congestion control startup identifier indicates that the network side device has not been overloaded.
  • step 10 it is determined whether the current network congestion state is restored.
  • the specific implementation can be as follows:
  • the network side device determines, according to the current network condition, whether the condition for starting the universal mobility management congestion control is met, and if not, determining that the network side device is not overloaded, and determining that the network congestion state is restored, if satisfied, Then, it is determined that the network side device is overloaded, and it is determined that the network congestion state is not restored.
  • the network side device When the network side device starts the general mobility management congestion control for the terminal, the network side device may set the second congestion control startup identifier corresponding to the network side device, so that the second congestion control startup identifier indicates that the network side device is overloaded;
  • the mobility management backoff time value is set to be invalid, and the specific implementation may be as follows: If it is determined that the congestion state of the network managed by the network side device is restored, the network side device modifies the value of the second congestion control startup identifier to The second congestion control activation flag indicates that the network side device is not overloaded. Specifically, in the terminal that is not attached to the network, in step 11, determining whether to accept the mobility management request according to the current network status, the specific implementation may be as follows:
  • the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the mobility management request, and if yes, starts Universal mobility management congestion control;
  • the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached. If not, the mobile management request is rejected. If yes, the mobility management congestion control based on the one or more APNs is started. ;
  • the network side device accepts the mobility management request.
  • step 11 determining whether to accept the mobile management request according to the current network status
  • the specific implementation may be as follows:
  • the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the mobility management request, and if yes, starts Universal mobility management congestion control;
  • the network side device accepts the mobility management request.
  • the network side device determines that the current network is in the congestion state again, and may perform one of the following two operations:
  • the network side device sets the mobility management backoff time value to be valid. Specifically, if the mobility management signaling of the terminal that has subscribed to the APN is on the network side again If the congestion occurs, the first congestion control activation identifier corresponding to the APN is modified, so that the first congestion control startup identifier indicates that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side; if the network side device occurs again If the overload occurs, the second congestion control activation identifier corresponding to the network side device is modified, so that the second congestion control startup identifier indicates that the network side device is overloaded; and subsequently determining whether to accept the reception according to the mobility management backoff time value according to the prior art.
  • the network side device starts the congestion control for the terminal again.
  • the first congestion control initiation identifier of the APN is used to indicate whether the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side;
  • the second congestion control startup identifier of the network side device is used to indicate The Whether the network side device is overloaded.
  • the initial value of the first congestion control initiation identifier needs to indicate that the mobility management signaling of the terminal that has subscribed to the APN does not have congestion on the network side
  • the initial value of the second congestion control startup identifier needs to indicate that the network side device does not have an overload.
  • the network side device may be any device capable of performing congestion control such as an MME (Mobility Management Entity).
  • MME Mobility Management Entity
  • the mobility management request is an attach request
  • the mobility management request is a request other than the attach request
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • This embodiment is directed to a non attached UE, which is specifically as follows:
  • Step 1 after receiving the attach request sent by the terminal, the MME determines that the condition of starting the mobility management congestion control of the APN based on the terminal subscription is met, and determines that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side. ;
  • Step 2 The MME sends a reject message rejecting the attach request to the terminal, where the reject message carries the information of the mobility management backoff timer; and the mobile management backoff time value is the timeout period of the mobility management backoff timer; and the APN is set.
  • the value of the corresponding first congestion control initiation identifier is 1, to indicate that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side;
  • Step 3 After determining, according to the current network condition, that the MME does not meet the preset condition for starting the mobility management congestion control of the terminal-based APN, and the time corresponding to the saved mobility management backoff time value has not arrived, modify the first corresponding to the APN.
  • the value of the congestion control startup identifier is 0, so that the mobility management signaling of the terminal that has subscribed to the APN does not cause congestion on the network side.
  • Step 4 After receiving the attach request sent by the terminal, the MME determines whether to accept the attach request according to the following method:
  • Method 1 If the current second congestion control initiation identifier indicates that the MME is overloaded, the MME determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the attach request, and if yes, initiates a general mobility Manage congestion control;
  • the MME determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the attach request, and if so, initiates mobility management congestion control based on the one or more APNs;
  • Step 5 After the MME determines that the condition for starting the mobility management congestion control of the APN based on the terminal subscription is met again, if the time corresponding to the saved mobility management backoff time value does not arrive, the first congestion control corresponding to the APN is performed.
  • the startup identifier is modified to 1 to indicate that the mobility management signaling of the terminal that has subscribed to the APN is congested on the network side, and then the attachment request sent by the terminal is received, and the attachment request is directly rejected according to the mobility management backoff time value. ; If the time corresponding to the saved mobility management backoff time value has arrived or passed, go to step 2.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • This embodiment is directed to a non attached UE, as follows:
  • Step 1 After receiving the attach request sent by the terminal, determining that the pre-set condition for starting the general mobility management congestion control is met, determining that the network managed by the terminal is in a congested state;
  • Step 2 Send a reject message rejecting the attach request to the terminal, where the reject message carries the information of the mobility management backoff timer; and save the mobility management backoff time value, that is, the timeout period of the mobility management backoff timer;
  • the corresponding second congestion control startup identifier has a value of 1 to indicate that the fault occurs.
  • Step 3 After determining that the preset general mobility management congestion control condition is not met according to the current network condition, and the time corresponding to the saved mobility management backoff time value has not arrived, modifying the second congestion control startup identifier corresponding to the ⁇ The value of 0 is to indicate that the ⁇ has not been overloaded;
  • Step 4 After receiving the attach request sent by the terminal, determine whether to accept the attach request according to the foregoing method 1;
  • Step 5 After determining that the pre-set condition of the general mobility management congestion control is met again, if the time corresponding to the saved mobility management backoff time value has not arrived, the second congestion control startup identifier corresponding to the UI is modified to 1 . In order to indicate that the ⁇ has an overload, and then receives the attach request sent by the terminal, the acknowledgment request is directly rejected according to the mobility management backoff time value; if the saved mobility management backoff time value has not arrived or passed, then the step is 2.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • This embodiment is directed to the attached UE, as follows:
  • Step 1 After receiving the MM request sent by the terminal, determining that the pre-set condition for starting the universal mobile management congestion control is met, determining that the network managed by the MME is in a congested state;
  • Step 2 The MME sends a reject message rejecting the MM request to the terminal, where the reject message carries the information of the mobility management backoff timer; and the mobile management backoff time value is the timeout period of the mobility management backoff timer; and the MME is set.
  • the value of the corresponding second congestion control initiation identifier is 1 to indicate that the MME is overloaded.
  • Step 3 The MME determines, according to the current network status, that the preset mobility management congestion control condition is not met and the saved mobility management After the time corresponding to the backoff time value is not reached, the value of the second congestion control start identifier corresponding to the MME is changed to 0, indicating that the MME does not have an overload;
  • Step 4 After receiving the MM request sent by the terminal, the MME determines, according to the method 2, whether to accept the mobile tube. Request
  • Method 2 If the current second congestion control initiation identifier indicates that the MME is overloaded, the MME determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the MM request, and if yes, initiates general mobility management. Congestion control
  • Step 5 After the MME determines that the condition for starting the general mobility management congestion control is met again, if the time corresponding to the saved mobility management backoff time value does not arrive, the second congestion control startup identifier corresponding to the MME is modified to 1 . In order to indicate that the MME is overloaded, and then receives an attach request sent by the terminal, the attach request is directly rejected according to the mobility management backoff time value; if the saved mobility management backoff time value has not arrived or passed, then the step is 2.
  • an embodiment of the present invention provides a congestion control device, where the device includes:
  • the first setting unit 20 is configured to set the mobility management backoff time value to be invalid after determining that the current network congestion state is restored and the time corresponding to the saved mobility management backoff time value for congestion control is not reached;
  • the control unit 21 is configured to determine, after receiving the mobility management request sent by the terminal, whether to accept the mobility management request according to the current network condition.
  • the first setting unit 20 is configured to:
  • the congestion control initiated for the terminal is based on the mobile management congestion control of the access point name APN signed by the terminal, it is determined according to the current network condition whether the preset is satisfied.
  • Starting the condition of the mobility management congestion control based on the APN if not, determining that the mobility management signaling of the terminal that has subscribed to the APN does not cause congestion on the network side, and determining that the congestion state is restored, and if yes, determining that the contract is signed.
  • the mobility management signaling of the terminal of the APN is congested on the network side, and it is determined that the congestion state is not restored.
  • the device further includes:
  • a second setting unit 22 configured to: when the APN-based mobility management congestion control is initiated for the terminal, set a value of the first congestion control startup identifier corresponding to the APN, so that the first congestion control startup identifier indicates that the first congestion control startup identifier is The mobility management signaling of the terminal of the APN is congested on the network side;
  • the first setting unit 20 is configured to:
  • the value of the first congestion control initiation identifier is modified such that the first congestion control initiation identifier indicates that the mobility management signaling of the terminal that has subscribed to the APN does not cause congestion on the network side.
  • the first setting unit 20 is configured to:
  • the congestion control initiated for the terminal is a general mobility management congestion control
  • the congestion control initiated for the terminal is a general mobility management congestion control
  • the device further includes:
  • the third setting unit 23 is configured to: when the universal mobility management congestion control is started for the terminal, set a second congestion control startup identifier corresponding to the device, so that the second congestion control startup identifier indicates that the device is overloaded;
  • the first setting unit 20 is configured to:
  • the value of the second congestion control initiation identifier is modified such that the second congestion control activation identifier indicates that the device has not been overloaded.
  • the first setting unit 20 is configured to:
  • the congestion control initiated for the terminal is a general mobility management congestion control
  • the congestion control initiated for the terminal is a general mobility management congestion control
  • the device further includes:
  • the fourth setting unit 24 is configured to: when the universal mobility management congestion control is started for the terminal, set a second congestion control startup identifier corresponding to the device, so that the second congestion control startup identifier indicates that the device is overloaded;
  • the first setting unit 20 is configured to:
  • the value of the second congestion control initiation identifier is modified such that the second congestion control activation identifier indicates that the device has not been overloaded.
  • control unit 21 is configured to:
  • the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the mobility management request, and if yes, starts Universal mobility management congestion control;
  • the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached. If not, the mobile management request is rejected. If yes, the mobility management congestion control based on the one or more APNs is started. ;
  • the network side device accepts the mobility management request.
  • control unit 21 is configured to:
  • the network side device determines whether the time corresponding to the stored mobility management backoff time value is reached, and if not, rejects the mobility management request, and if yes, starts Universal mobility management congestion control; If the current second congestion control activation indicator indicates that the network side device does not have an overload, the network side device accepts the mobility management request.
  • the device further includes:
  • the recovery unit 25 is configured to: after determining that the current network enters the congestion state again, set the mobility management backoff time value to be valid; and determine, according to the mobility management backoff time value, whether to accept the received mobility management request sent by the terminal. Or,
  • the congestion control is initiated again for the terminal.
  • An embodiment of the present invention further provides a mobility management entity (MME), where the MME includes the congestion control device.
  • MME mobility management entity
  • the network side device sets the saved mobility management backoff time value to be invalid when the current network congestion state is restored and the time corresponding to the saved mobility management backoff time value for congestion control is not reached.
  • the mobility management request is no longer directly rejected according to the mobility management backoff time value, that is, when the network congestion state is restored, the mobility management request sent by the terminal is not controlled by the network due to congestion. And refuse, thereby improving the success rate of the terminal accessing the network.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention can be embodied in the form of a computer program product embodied on one or more computer-usable storage interfaces (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • computer-usable storage interfaces including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions are provided for implementing one or more processes and/or block diagrams in the flowchart The steps of the function specified in the box or in multiple boxes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention appartient au domaine technique des communications sans fil, et concerne un procédé et un dispositif de régulation d'encombrement, qui sont utilisés pour améliorer le taux de taux d'aboutissement des accès d'un terminal à un réseau. Dans la présente invention, lorsqu'un état d'encombrement d'un réseau actuel se rétablit, l'instant correspondant à une valeur de temps d'attente de gestion de la mobilité mémorisée pour la régulation d'encombrement n'étant pas atteint, un dispositif côté réseau spécifie la valeur mémorisée de temps d'attente de gestion de la mobilité pour la régulation d'encombrement comme invalide puis, après avoir reçu une demande de gestion de la mobilité envoyée par le terminal, le dispositif côté réseau ne rejette pas directement la demande de gestion de la mobilité en fonction de la valeur de temps d'attente de gestion de la mobilité, c'est-à-dire que, lorsque l'état d'encombrement du réseau se rétablit, la demande de gestion de la mobilité envoyée par le terminal n'est pas rejetée par le réseau en raison de la régulation d'encombrement, améliorant ainsi le taux d'aboutissement des accès du terminal au réseau.
PCT/CN2012/081968 2011-12-30 2012-09-26 Procédé et dispositif de régulation d'encombrement WO2013097503A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110457449.7A CN102413504B (zh) 2011-12-30 2011-12-30 拥塞控制方法和设备
CN201110457449.7 2011-12-30

Publications (1)

Publication Number Publication Date
WO2013097503A1 true WO2013097503A1 (fr) 2013-07-04

Family

ID=45915279

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/081968 WO2013097503A1 (fr) 2011-12-30 2012-09-26 Procédé et dispositif de régulation d'encombrement

Country Status (2)

Country Link
CN (1) CN102413504B (fr)
WO (1) WO2013097503A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102413504B (zh) * 2011-12-30 2014-12-10 电信科学技术研究院 拥塞控制方法和设备
WO2014015518A1 (fr) * 2012-07-27 2014-01-30 华为技术有限公司 Procédé de gestion de congestion et entité et dispositif de gestion de mobilité
US9603186B2 (en) * 2014-05-08 2017-03-21 Intel IP Corporation Mobility management entity, user equipment and methods for machine type communication
CN108574964B (zh) * 2017-03-10 2019-08-23 电信科学技术研究院 一种控制面数据的拥塞控制方法和装置
CN110650495A (zh) * 2018-06-27 2020-01-03 电信科学技术研究院有限公司 一种拥塞控制方法、设备及装置
CN112738848B (zh) * 2019-10-14 2022-12-06 中国移动通信集团安徽有限公司 核心网负荷调整方法、装置、设备及计算机可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050025176A1 (en) * 2003-07-29 2005-02-03 Seong-Yun Ko Medium access control in wireless local area network
CN101494588A (zh) * 2008-01-22 2009-07-29 中兴通讯股份有限公司 一种用于空中接口的快速路由打开方法
CN102224756A (zh) * 2008-09-23 2011-10-19 高通股份有限公司 用于减少接入终端的连续预注册尝试的方法和装置
CN102244916A (zh) * 2011-07-29 2011-11-16 电信科学技术研究院 一种会话管理的控制方法和设备
CN102413504A (zh) * 2011-12-30 2012-04-11 电信科学技术研究院 拥塞控制方法和设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102098759A (zh) * 2011-02-18 2011-06-15 电信科学技术研究院 一种接入控制的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050025176A1 (en) * 2003-07-29 2005-02-03 Seong-Yun Ko Medium access control in wireless local area network
CN101494588A (zh) * 2008-01-22 2009-07-29 中兴通讯股份有限公司 一种用于空中接口的快速路由打开方法
CN102224756A (zh) * 2008-09-23 2011-10-19 高通股份有限公司 用于减少接入终端的连续预注册尝试的方法和装置
CN102244916A (zh) * 2011-07-29 2011-11-16 电信科学技术研究院 一种会话管理的控制方法和设备
CN102413504A (zh) * 2011-12-30 2012-04-11 电信科学技术研究院 拥塞控制方法和设备

Also Published As

Publication number Publication date
CN102413504B (zh) 2014-12-10
CN102413504A (zh) 2012-04-11

Similar Documents

Publication Publication Date Title
US10165618B2 (en) Service processing method and device
WO2012110002A1 (fr) Procédé et dispositif pour un contrôle d'accès
WO2013097503A1 (fr) Procédé et dispositif de régulation d'encombrement
WO2012094982A1 (fr) Procédé et dispositif de contrôle d'accès
WO2012041197A1 (fr) Procédé et dispositif côté réseau pour le processus de gestion de mobilité
WO2012174943A1 (fr) Procédé, appareil et système pour déterminer l'état d'un terminal
WO2012119512A1 (fr) Procédé de traitement de message de battement de cœur, procédé d'acquisition d'une période de battement de cœur et dispositif de réseau d'accès
WO2012097708A1 (fr) Procédé et dispositif pour accomplir une procédure de préparation en vue d'un transfert intercellulaire de connexion lipa
CN103379659B (zh) 一种多优先级场景下接入请求实现方法及装置
WO2012041184A1 (fr) Procédé et dispositif côté réseau d'instruction de réduction de puissance de gestion de session, et procédé et équipement utilisateur de réduction de puissance de gestion de session
WO2012048656A1 (fr) Procédé et dispositif de réinitialisation d'un processus de gestion de session d'un système eps
WO2012041185A1 (fr) Procédé de notification de capacité et procédé, système et dispositif de régulation de la congestion d'un réseau
WO2014101171A1 (fr) Procédé, dispositif et système destinés à remédier à un défaut de connexion
CN103857005A (zh) 接入控制方法和设备
WO2012041238A1 (fr) Procédé et dispositif permettant de traiter un contexte de gestion de mobilité
WO2012100717A1 (fr) Procédé, système et élément de réseau permettant le lancement d'une pagination active
WO2011130990A1 (fr) Procédé, système et dispositif pour rejeter le rétablissement d'une connexion de ressource radio pendant le transfert intercellulaire de station de base
WO2013064067A1 (fr) Procédé et système de régulation de l'encombrement d'un réseau
WO2015100564A1 (fr) Procédé de gestion des défaillances, réseau de données par paquets, entité de gestion de mobilité et système de réseau
WO2012016546A1 (fr) Procédé de traitement de radiomessagerie destiné à un équipement utilisateur et équipement
WO2012041250A1 (fr) Procédé et dispositif de gestion de congestion dans des communications du type machine
WO2016019559A1 (fr) Appareil, système, et procédé d'identification d'équipement d'utilisateur de réseau partagé
WO2019214606A1 (fr) Procédé de commande exécuté dans un équipement utilisateur, et équipement utilisateur
WO2013178178A2 (fr) Dispositif et procédé de libération de ressources
WO2010124644A1 (fr) Procédé de mise en oeuvre de services d'urgence, système de mise en oeuvre de services d'urgence et dispositif réseau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12863520

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12863520

Country of ref document: EP

Kind code of ref document: A1