Apparatus and method for congestion control in wireless communication networks

• US 9,288,434 B2
• Filed: 12/27/2013
• Issued: 03/15/2016
• Est. Priority Date: 04/26/2013
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Bangolae, Sangeetha L., Martinez Tarradell, Marta, Pinheiro, Ana Lucia, Jain, Puneet, Shan, Chang Hong, Choi, Hyung-Nam
• Primary Examiner(s): Louis, Vincelas
• Application Number:
  US14/141,985
• Publication Number:
  US 20140321272A1
• Time in Patent Office: 809 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04J 11/00 Orthogonal multiplex systems, e.g. using WALSH codesH04J13/00 takes precedence
• CPC Class Codes: H04J 11/0023 Interference mitigation or co-ordination direct sequence spread spectrum [DSSS] systems H04B1/7097; frequency hopping H04B1/713; allocation criteria for ingress interference avoidance H04L5/0062; frequency allocation criteria for requirements on out-of-channel emissions H04L5/0066; arrangements for removing intersymbol interference or baseband equalisers H04L25/03006; peak power aspects in multicarrier modulation H04L27/2614; power management H04W52/00; traffic scheduling H04W72/54, H04W72/541
• CPC Class Codes: H04J 11/005 of intercell interference
• CPC Class Codes: H04L 1/1671 the supervisory signal being transmitted together with control information
• CPC Class Codes: H04L 1/1812 Hybrid protocols; Hybrid automatic repeat request [HARQ]
• CPC Class Codes: H04L 1/1861 Physical mapping arrangements for ACK signaling see also H04L5/0053
• CPC Class Codes: H04L 12/1407 Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 5/0007 the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04L 5/0032 Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
• CPC Class Codes: H04L 5/0033 each allocating device acting autonomously, i.e. without negotiation with other allocating devices
• CPC Class Codes: H04L 5/0044 allocation of payload
• CPC Class Codes: H04L 5/005 of common pilots, i.e. pilots destined for multiple users or terminals
• CPC Class Codes: H04L 5/0055 Physical resource allocation for ACK/NACK for physical mapping arrangements in ARQ protocols H04L1/1861
• CPC Class Codes: H04L 5/0073 Allocation arrangements that take into account other cell interferences for intercell interference mitigation or co-ordination in orthogonal multiplex systems H04J11/005
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1073 : Registration or de-registration
• CPC Class Codes: H04L 65/1104 : Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/403 : Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/65 : Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 65/80 : Responding to QoS
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• CPC Class Codes: H04N 21/4728 : for selecting a Region Of Interest [ROI], e.g. for requesting a higher resolution version of a selected region
• CPC Class Codes: H04N 21/4788 : communicating with other users, e.g. chatting arrangements for providing for computer conferences, e.g. chat rooms, to substation in data switching networks H04L12/1813; distributed application using peer-to-peer [P2P] networks H04L67/104
• CPC Class Codes: H04N 21/6437 : Real-time Transport Protocol [RTP]
• CPC Class Codes: H04N 7/141 : between two video terminals, e.g. videophone telephonic communication systems combined with television receiver for reception of entertainment or information matter H04M11/085
• CPC Class Codes: H04N 7/147 : Communication arrangements, e.g. identifying the communication as a video-communication, intermediate storage of the signals selecting H04Q
• CPC Class Codes: H04N 7/15 : Conference systems
• CPC Class Codes: H04W 24/06 : Testing, supervising or monitoring using simulated traffic
• CPC Class Codes: H04W 28/0236 : radio quality, e.g. interference, losses or delay
• CPC Class Codes: H04W 28/0289 : Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 36/0066 : of control information between different types of networks in order to establish a new radio link in the target network
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 48/06 : based on traffic conditions
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/0216 : using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/08 : Closed loop power control
• CPC Class Codes: H04W 52/146 : Uplink power control
• CPC Class Codes: H04W 52/242 : taking into account path loss
• CPC Class Codes: H04W 52/32 : TPC of broadcast or control channels
• CPC Class Codes: H04W 52/325 : Power control of control or pilot channels
• CPC Class Codes: H04W 60/00 : Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 68/00 : User notification, e.g. alerting and paging, for incoming communication, change of service or the like
• CPC Class Codes: H04W 68/02 : Arrangements for increasing efficiency of notification or paging channel
• CPC Class Codes: H04W 72/04 : Wireless resource allocation
• CPC Class Codes: H04W 72/044 : based on the type of the allocated resource
• CPC Class Codes: H04W 72/0446 : Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/0453 : Resources in frequency domain, e.g. a carrier in FDMA
• CPC Class Codes: H04W 72/20 : Control channels or signalling for resource management
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/52 : based on load
• CPC Class Codes: H04W 72/542 : using measured or perceived quality
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 76/18 : Management of setup rejection or failure
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 76/38 : triggered by timers
• CPC Class Codes: H04W 8/005 : Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 8/22 : Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Embodiments of wireless communication devices and method for congestion control in a wireless network are generally described herein. Some of these embodiments describe a method, performed by an evolved NodeB (eNodeB), that includes operations of determining that a congestion condition exists on the network. An example method can also include transmitting a suspension notification to a user equipment (UE), the UE being in an RRC_CONNECTED state with the eNodeB, to notify the UE that a radio bearer (RB) operating in the network will be suspended. Other methods and apparatuses are also described.

Claims

1. A method, performed by an evolved NodeB (eNodeB), for congestion control in a network, the method comprising:

determining that a congestion condition exists on the network; and

transmitting a suspension notification to a user equipment (UE), the UE being in an RRC_CONNECTED state with the eNodeB, to notify the UE that a radio bearer (RB) operating in the network will be suspended, upon determining that the congestion condition exists, wherein the suspension notification is transmitted in a radio resource control (RRC) Suspend Radio Bearer message including a backoff timer to indicate a time duration for which the UE shall wait before requesting resources on the corresponding RB, and wherein a packet data convergence protocol (PDCP) discard timer has been modified based on a value of the backoff timer.

2. The method of claim 1, wherein the suspension notification is transmitted in a Radio Resource Control (RRC) reconfiguration message.

3. The method of claim 1, wherein the suspension notification is transmitted in the radio resource control (RRC) Suspend Radio Bearer message in accordance with a standard of the 3rd Generation Partnership Project (3GPP) family of standards for long-term evolution (LTE).

4. The method of claim 1, further comprising:

transmitting a resume notification, at a point subsequent to transmitting the suspension notification, to notify the UE that the corresponding RB is available for use.

5. The method of claim 1, further comprising:

receiving an acknowledgement message from the UE, in response to notifying the UE that at least one RB will be unavailable, the acknowledgement including identification information of the corresponding RB.

6. The method of claim 1, wherein the eNodeB determines that the congestion condition exists based on RB congestion information maintained by the eNodeB.

7. The method of claim 6, wherein the eNodeB determines that the congestion condition exists based on congestion information received from a mobility management entity (MME) for an access point name (APN).

8. A user equipment (UE) for operating in a wireless communication network, the UE comprising:

physical layer circuitry arranged to

enter an RRC_CONNECTED state with the wireless communication network;

receive a suspension notification from the wireless communication network, while the UE is in an RRC_CONNECTED state, that a radio bearer (RB) operating in the wireless communication network has been suspended, wherein the suspension notification is received in a radio resource control (RRC) Suspend Radio Bearer message including a backoff timer to indicate a time duration for which the UE shall wait before requesting resources on the corresponding RB, and wherein a packet data convergence protocol (PDCP) discard timer has been modified based on a value of the backoff timer; and

transmit an acknowledgement of the suspension notification.

9. The UE of claim 8, wherein the physical layer circuitry is further configured to:

receive the value for the backoff timer indicating the time duration for which the UE shall not request resources on the RB; and

refrain from transmitting on the RB for at least the time duration.

10. The UE of claim 9, further comprising a memory and processing circuitry, and wherein the processing circuitry is arranged to buffer data for uplink transmission in the memory for at least the time duration.

11. The UE of claim 10, wherein the processing circuitry is arranged to transmit the buffer data upon expiration of the backoff timer.

12. The UE of claim 10, wherein the processing circuitry is arranged to discard the buffer data upon expiration of the backoff timer.

13. An evolved NodeB (eNodeB) operating in a network, the eNodeB comprising:

processing circuitry arranged to determine that usage of a radio bearer (RB) operating in the network should be suspended, based on congestion information related to the RB; and

a transceiver arranged to

transmit a suspension notification, upon determining that usage of the RB should be suspended, to notify a user equipment (UE) that is in an RRC_CONNECTED state with the eNodeB that the RB will be suspended, wherein the suspension notification is transmitted in a radio resource control (RRC) Suspend Radio Bearer message including a backoff timer to indicate a time duration for which the UE shall wait before requesting resources on the corresponding RB, and wherein a packet data convergence protocol (PDCP) discard timer has been modified based on a value of the backoff timer.

14. The eNodeB of claim 13, wherein the physical layer circuitry is further arranged to transmit the suspension notification in a radio resource control (RRC) reconfiguration message or in an RRC Suspend Radio Bearer message in accordance with a standard of the 3rd Generation Partnership Project 3GPP) family of standards for long-term evolution (LTE).

15. A method, performed by a user equipment (UE) for operating in a wireless communicating network, the method comprising:

entering into an RRC_CONNECTED state with the wireless communicating network;

receiving a suspension notification from the wireless communicating network, while the UE is in an RRC_CONNECTED state, that a radio bearer (RB) has been suspended from use, wherein the suspension notification is received in a radio resource control (RRC) Suspend Radio Bearer message including a backoff timer to indicate a time duration for which the UE shall wait before requesting resources on the corresponding RB, and wherein a packet data convergence protocol (PDCP) discard timer has been modified based on a value of the backoff timer; and

transmitting an acknowledgement of the suspension notification; and

refraining from operating on the RB for at least a time duration specified in the suspension notification.

16. The method of claim 15, further comprising:

buffering data in a memory for the time duration; and

transmitting the data upon receiving a resume notification indicating that the RB is available for use.