WO2010123916A1 - Method and apparatus for triggering buffer status reports after packet discarding - Google Patents

Method and apparatus for triggering buffer status reports after packet discarding Download PDF

Info

Publication number
WO2010123916A1
WO2010123916A1 PCT/US2010/031770 US2010031770W WO2010123916A1 WO 2010123916 A1 WO2010123916 A1 WO 2010123916A1 US 2010031770 W US2010031770 W US 2010031770W WO 2010123916 A1 WO2010123916 A1 WO 2010123916A1
Authority
WO
WIPO (PCT)
Prior art keywords
buffer
data
user equipment
sent
enode
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.)
Ceased
Application number
PCT/US2010/031770
Other languages
French (fr)
Inventor
Rangsan Leelahakriengkrai
Igor Filipovich
John M. Harris
Ivan N. Vukovic
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Motorola Solutions Inc
Original Assignee
Motorola Inc
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 Motorola Inc filed Critical Motorola Inc
Publication of WO2010123916A1 publication Critical patent/WO2010123916A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/28Flow control; Congestion control in relation to timing considerations
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/30Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/32Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0278Traffic management, e.g. flow control or congestion control using buffer status reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints
    • H04W28/12Flow control between communication endpoints using signalling between network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04Registration at HLR or HSS [Home Subscriber Server]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data

Definitions

  • the present invention relates generally to the sending of buffer status reports in a wireless communication system, and in particular to sending buffer status reports that are triggered when the number of packets changes in the buffer such as when packets are discarded from the buffer.
  • the user equipment informs the eNode B, or base station, how much data it has in a buffer that is to be sent to the eNode B.
  • the user equipment sends a buffer status report (BSR) for this purpose where the BSR indicates the amount of data that is in the buffer that is ready to be sent.
  • BSR buffer status report
  • the BSR is sent when a new packet arrives from the user equipment's application layer to an empty medium access channel transmit queue, the uplink resources that are allocated for the user equipment is more than was requested by the regular BSR such that the user equipment has enough space to send another BSR along with the data, a serving cell change occurs or a periodic BSR timer expires.
  • the user equipment sends the BSR because it needs a specific allocation from the eNode B to send data.
  • the BSR indicates the Quality of Service (QoS) that is required to send the data from the buffer.
  • QoS Quality of Service
  • the eNode B Upon receipt of the BSR, the eNode B sends a grant to the user equipment within a given time frame, usually approximately 100 ms, where the grant indicates the amount of data the user equipment can send from the buffer to the eNode B.
  • the user equipment In addition to waiting for a grant before sending data from the buffer to the eNode B, the user equipment needs to receive an indication that it can send the BSR. The user equipment is therefore allocated a slot in the communications between the user equipment and the eNode B to send a tone or a scheduling request indicator.
  • the scheduling request indicator does not indicate the amount of data that is in the buffer as that information is reserved for the BSR.
  • FIG. 1 is an example of a wireless communication system that operates in accordance with some embodiments of the invention.
  • FIG. 2 is a flow chart demonstrating the operation of the user equipment and eNode B in accordance with some embodiments of the invention.
  • FIG. 3 is a flow chart demonstrating the operation of the user equipment and eNode B in accordance with other embodiments of the invention.
  • Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention. Detailed Description
  • embodiments of the invention described herein may be comprised of one or more conventional processors and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of a method and apparatus for triggering buffer status reports in response to changes in the amount of data in a buffer described herein.
  • the non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices. As such, these functions may be interpreted as steps of a method to trigger buffer status reports in response to changes in the amount of data in a buffer.
  • the present invention is directed to a method and apparatus for triggering buffer status reports in response to changes in the amount of data in a buffer.
  • a method is disclosed that includes a user equipment sending a first buffer status report to indicate an amount of data in a buffer that is to be sent. After the first buffer status report is sent data can be discarded from the buffer. The method also includes sending a second buffer status report to indicate that data the change in the amount of data in the buffer as a result of discarding data as a result of the expiration of a timer, the trigger of a buffer overflow method, the detection of malicious data or for other reasons.
  • the first and second buffer status report includes an amount of data in the buffer.
  • the method can include receiving a grant from the eNode B that is in response to the BSR to send at least a portion of the data in the buffer.
  • the second buffer status report further comprises using a portion of grant to send the second buffer status report.
  • the method includes sending data from the buffer according to the received grant.
  • a method in another embodiment, includes a user equipment sending a first buffer status report to indicate an amount of data in a buffer that is to be sent. After the first buffer status report is sent, the amount of data in the buffer can change so that the user equipment sends a second buffer status report to indicate the change in the amount of data in the buffer that is to be sent.
  • the amount of data in the buffer can change because data is discarded from or added to the buffer since the first buffer report was sent such as new data is generated by upper protocol layer or data from a higher- or lower-priority buffer is added to the buffer due to a policy change.
  • the method can include receiving a grant to send at least a portion of the data in the buffer and sending the second buffer status report further comprising using a portion of the grant to send the second buffer status report.
  • An apparatus includes a buffer to store data to be sent from the apparatus, a transceiver to send the stored data, and a processor coupled to the buffer and the transceiver wherein the processor creates a first buffer status report to indicate an amount of data stored in the buffer to be sent by the transceiver and wherein the processor creates a second buffer status report when the amount of data in the buffer changes after the first buffer status report is sent by the transceiver.
  • the transceiver sends the first buffer status report after receiving a grant that indicates at least a portion of the data in the buffer to be sent by the transceiver.
  • the transceiver also sends the portion of data in the buffer indicated in the grant. The amount of data changes because data is discarded or because data is added to the buffer.
  • the transceiver can receive an indication to send the first buffer status report.
  • System 100 includes a plurality of base stations or eNode Bs 102 that provides wireless communications to a plurality of user equipment 104 that operate within the cells defined by the eNode Bs 102.
  • the wireless communications between the eNode B 102 and the user equipment 104 operates according to known and developing standards including UMTS, LTE and WiMAX 802.16 standard protocols.
  • the eNode B 102 includes a processor 112, memory 114, transceiver 115 and antenna 116.
  • the user equipment 104 also includes a processor 118, memories 120, transceiver 121, antenna 122 and buffer 123.
  • the eNode B 102 and user equipment 104 transmit and receive messages with one another using the processors 112 and 118, memories 114 and 120 antennae 116 and 122, respectively, according to standard protocol methods and according to the methods and procedures described here. Messages are transmitted from user equipment 104 to an eNode B 102 on an uplink channel 124 according to these methods. Messages are transmitted from the eNode B 102 to the user equipment 104 on a downlink channel 126 also according to these methods.
  • FIG. 2 a method of sending data from the user equipment to the eNode B according to the principles disclosed is shown.
  • the user equipment 104 stores 202 data that is to be sent from the user equipment 102 to the eNode B 102 in the memory 120 and more particularly buffer 123.
  • the data in the buffer is not sent from the user equipment 104 to the eNode B 102 until the user equipment receives an indication that the eNode B can receive the data and how much data it is prepared to receive.
  • the user equipment awaits 204 a slot of time during which it can send 206 a scheduling request indicator (SRI) to the eNode B.
  • SRI scheduling request indicator
  • the SRI indicates to the eNode B 102 that user equipment 104 has data in its buffer 123 to be transmitted on the uplink, but it does not indicate how much data or what type of data is to be sent.
  • the slot can occur at intervals of 5 ms or other values according to standards.
  • the eNode B Upon receipt of the SRI from the user equipment 104, the eNode B sends 208 an indication to the user equipment that eNode B 102 is ready to receive a buffer status report (BSR).
  • BSR buffer status report
  • the SRI and BSR are in the format and sent according to the rules set for them in various standards for OFDM communications.
  • the user equipment 104 sends 210 the BSR to the eNode B 102.
  • the BSR informs the eNode B 102 that the user equipment 104 has data in its buffer 123 that is ready to be sent to the eNode B.
  • the BSR includes information regarding the amount of data, e.g. bits or bytes of data, that is in the buffer and the desired Quality of Service (QoS) that is needed to send the data to the eNode B.
  • QoS Quality of Service
  • Other data can be included in the BSR as is required.
  • the eNode B determines according to known methods how much of the data in the buffer 123 it can receive from the user equipment 104 by taking into consideration various factors. Based upon this determination, the eNode B 102 sends 212 a grant to the user equipment 104 that states how much data can be sent and when the data can be sent. At the designated time, the user equipment 102 sends 214 the amount of data allotted in the grant to the eNode B 104. [0022] The eNode B 102 will continue to send grants to the user equipment until the amount of data indicated in BSR has been sent to the eNode B. For example, the BSR may indicate that the user equipment has 3000 bytes of data to be sent.
  • the eNode B can send a first grant for 1000 bytes of data and then send 2 subsequent grants for 1000 bytes each so that all the data is sent.
  • the amount of data in the buffer 123 may change for reasons other than the mere fact that the user equipment sends data to the eNode B in response to the grants.
  • data can be discarded 216 from the buffer 123 because it is stale, irrelevant, overflowing buffer, malicious or for other reasons.
  • the data can be determined to be stale or irrelevant for being in the buffer for too long, and this can be determined by the expiration of a timer in the user equipment.
  • the SRI is not used to indicate that data has been discarded from the buffer.
  • the SRI purpose is to inform the eNode B 102 that the user equipment wants to send a BSR. At this stage in the process, the eNode B has received a BSR and has calculated that the user equipment 104 has data in the buffer 123.
  • Data can be discarded when in a logical channel with a tight delay budget and without persistent scheduling such as with video streaming or game applications the packet delay budget.
  • congestion or power limitation of the cell edge can prolong the transmission grant for user equipment and thus cause packet discarding.
  • any amount of data can be discarded from the buffers after the BSR has been sent. As such, there may not be the need to send as many grants. From the example given above, if 1000 bytes of data has been discarded for various reasons, the last grant does not need to be sent. Thus, after the discarding of data, the user equipment 104 sends 218 an updated BSR to the eNode B 102.
  • the updated BSR like the initial BSR, will indicate the amount of data that is in the buffer 123 of the user equipment 104 to be sent to the eNode B and the QoS requirements for that data. In this example, the BSR will state that there is 1000 bytes of data in the buffer 123.
  • the updated BSR can be sent at different times and does not need to be in response to a grant.
  • the updated BSR can be sent as a part of a response to a grant. If the BSR includes 4 bytes of data, a portion of the response to the grant can be reserved for the updated BSR.
  • the eNode B will be configured to determine if the response to the grant includes an updated BSR.
  • the updated BSR displaces data that is being sent in response to the grant and is therefore given a higher priority than the data in the buffer 123.
  • data can be reserved in the response to indicate that an updated BSR is needed and the eNode B can send a supplemental grant for the updated BSR. If there is no data discarded by the user equipment 104, the user equipment will continue to respond to grants until all the data in the buffer is sent to the eNode B.
  • a threshold can be used to determine if an updated BSR will be sent to the eNode B. If the amount of discarded data is less than the threshold then the updated BSR is not sent.
  • the threshold will be set so that the efficiencies of the communications will be maintained. For example, the threshold can be set at 4 bytes, which is the amount of data needed for a BSR.
  • FIG. 3 illustrates another embodiment for sending updated BSRs.
  • the user equipment 104 stores 302 data that is to be sent from the user equipment 102 to the eNode B 102 in buffer 123.
  • the user equipment 104 awaits 304 for the slot of time during which it can send 306 the SRI to the eNode B.
  • the eNode B Upon receipt of the SRI from the user equipment 104, the eNode B sends 308 an indication to the user equipment that it is ready to receive the BSR.
  • the user equipment 104 sends 310 the BSR to the eNode B 102.
  • the BSR informs the eNode B 102 that the user equipment 104 has data in its buffer that is ready to be sent to the eNode B.
  • the eNode B 102 knows how much data the user equipment 104 has to send.
  • the eNode B determines according to known methods how much of the data in the buffer it can receive from the user equipment by taking into consideration various factors. Based upon this determination, the eNode B 102 sends 312 the grant to the user equipment 104 that states how much data can be sent and when the data can be sent. At the designated time, the user equipment 102 sends 314 the amount of data allotted in the grant to the eNode B 104.
  • the amount of data in the buffer 123 may change for reasons other than the mere fact that the user equipment sends data to the eNode B in response to the grants.
  • data can be added 316 to the buffer 123 because the user equipment has more data to send.
  • the SRI is not used to indicate that the amount of data in the buffer has changed.
  • the user equipment 104 sends 318 an updated BSR to the eNode B 102.
  • the updated BSR like the initial BSR, will indicate the amount of data that is in the buffer 123 of the user equipment 104 to be sent to the eNode B and the QoS requirements for that data.
  • the eNode B 102 will continue to send grants to the user equipment 104 until it has determined that all of the data has been sent from user equipment according to the last BSR it has received.

Landscapes

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

Abstract

A method and apparatus are disclosed that includes a user equipment (104) sending a first buffer status report to an eNode B (102) to(210) indicate an amount of data in a buffer that is to be sent. After the first buffer status report is sent, the amount of data in the buffer can change (216) so that the user equipment sends (218) a second buffer status report to indicate the change in the amount of data in the buffer that is to be sent.

Description

METHOD AND APPARATUS FOR TRIGGERING BUFFER STATUS REPORTS AFTER PACKET DISCARDING
Field of the Invention [0001] The present invention relates generally to the sending of buffer status reports in a wireless communication system, and in particular to sending buffer status reports that are triggered when the number of packets changes in the buffer such as when packets are discarded from the buffer.
Background
[0002] In Orthogonal Frequency Division Multiplex (OFDM) wireless communication systems, the user equipment informs the eNode B, or base station, how much data it has in a buffer that is to be sent to the eNode B. The user equipment sends a buffer status report (BSR) for this purpose where the BSR indicates the amount of data that is in the buffer that is ready to be sent. The BSR is sent when a new packet arrives from the user equipment's application layer to an empty medium access channel transmit queue, the uplink resources that are allocated for the user equipment is more than was requested by the regular BSR such that the user equipment has enough space to send another BSR along with the data, a serving cell change occurs or a periodic BSR timer expires.
[0003] The user equipment sends the BSR because it needs a specific allocation from the eNode B to send data. In addition to the amount of data in the buffer, the BSR indicates the Quality of Service (QoS) that is required to send the data from the buffer. Upon receipt of the BSR, the eNode B sends a grant to the user equipment within a given time frame, usually approximately 100 ms, where the grant indicates the amount of data the user equipment can send from the buffer to the eNode B.
[0004] In addition to waiting for a grant before sending data from the buffer to the eNode B, the user equipment needs to receive an indication that it can send the BSR. The user equipment is therefore allocated a slot in the communications between the user equipment and the eNode B to send a tone or a scheduling request indicator. The scheduling request indicator does not indicate the amount of data that is in the buffer as that information is reserved for the BSR.
[0005] After a BSR has been sent, it is possible for the amount of data in the buffer to change. Data can be discarded from the buffer according to a policy such as being stale, irrelevant, buffer overflowing (or close to overflowing), malicious data (e.g., virus, worm, phishing) detected or for other reasons. Data can also be added to the buffer for various reasons. Once the BSR has been sent the eNode B knows the amount of data that is in the buffer, and there currently is no mechanism to update the eNode B. Thus, there is a need to determine a means by which the user equipment can update the eNode B of changes in the amount of data in the buffer after a BSR has been sent.
Brief Description of the Figures
[0006] The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views and which together with the detailed description below are incorporated in and form part of the specification, serve to further illustrate various embodiments and to explain various principles and advantages all in accordance with the present invention.
[0007] FIG. 1 is an example of a wireless communication system that operates in accordance with some embodiments of the invention.
[0008] FIG. 2 is a flow chart demonstrating the operation of the user equipment and eNode B in accordance with some embodiments of the invention.
[0009] FIG. 3 is a flow chart demonstrating the operation of the user equipment and eNode B in accordance with other embodiments of the invention. [0010] Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention. Detailed Description
[0011] Before describing in detail embodiments that are in accordance with the present invention, it should be observed that the embodiments reside primarily in combinations of method steps and apparatus components related to method and apparatus for triggering buffer status reports in response to changes in the amount of data in a buffer. Accordingly, the apparatus components and method steps have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
[0012] In this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises ...a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
[0013] It will be appreciated that embodiments of the invention described herein may be comprised of one or more conventional processors and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of a method and apparatus for triggering buffer status reports in response to changes in the amount of data in a buffer described herein. The non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices. As such, these functions may be interpreted as steps of a method to trigger buffer status reports in response to changes in the amount of data in a buffer. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used. Thus, methods and means for these functions have been described herein. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.
[0014] The present invention is directed to a method and apparatus for triggering buffer status reports in response to changes in the amount of data in a buffer. In an embodiment, a method is disclosed that includes a user equipment sending a first buffer status report to indicate an amount of data in a buffer that is to be sent. After the first buffer status report is sent data can be discarded from the buffer. The method also includes sending a second buffer status report to indicate that data the change in the amount of data in the buffer as a result of discarding data as a result of the expiration of a timer, the trigger of a buffer overflow method, the detection of malicious data or for other reasons. In an embodiment, the first and second buffer status report includes an amount of data in the buffer. In addition, the method can include receiving a grant from the eNode B that is in response to the BSR to send at least a portion of the data in the buffer. In this situation, the second buffer status report further comprises using a portion of grant to send the second buffer status report. Moreover, the method includes sending data from the buffer according to the received grant.
[0015] In another embodiment, a method is disclosed that includes a user equipment sending a first buffer status report to indicate an amount of data in a buffer that is to be sent. After the first buffer status report is sent, the amount of data in the buffer can change so that the user equipment sends a second buffer status report to indicate the change in the amount of data in the buffer that is to be sent. The amount of data in the buffer can change because data is discarded from or added to the buffer since the first buffer report was sent such as new data is generated by upper protocol layer or data from a higher- or lower-priority buffer is added to the buffer due to a policy change. As stated, the method can include receiving a grant to send at least a portion of the data in the buffer and sending the second buffer status report further comprising using a portion of the grant to send the second buffer status report.
[0016] An apparatus is also disclosed that includes a buffer to store data to be sent from the apparatus, a transceiver to send the stored data, and a processor coupled to the buffer and the transceiver wherein the processor creates a first buffer status report to indicate an amount of data stored in the buffer to be sent by the transceiver and wherein the processor creates a second buffer status report when the amount of data in the buffer changes after the first buffer status report is sent by the transceiver. The transceiver sends the first buffer status report after receiving a grant that indicates at least a portion of the data in the buffer to be sent by the transceiver. The transceiver also sends the portion of data in the buffer indicated in the grant. The amount of data changes because data is discarded or because data is added to the buffer. Moreover, the transceiver can receive an indication to send the first buffer status report.
[0017] Turning to FIG. 1, there is shown a wireless telecommunication system 100. System 100 includes a plurality of base stations or eNode Bs 102 that provides wireless communications to a plurality of user equipment 104 that operate within the cells defined by the eNode Bs 102. The wireless communications between the eNode B 102 and the user equipment 104 operates according to known and developing standards including UMTS, LTE and WiMAX 802.16 standard protocols.
[0018] As is understood, the eNode B 102 includes a processor 112, memory 114, transceiver 115 and antenna 116. Likewise, the user equipment 104 also includes a processor 118, memories 120, transceiver 121, antenna 122 and buffer 123. The eNode B 102 and user equipment 104 transmit and receive messages with one another using the processors 112 and 118, memories 114 and 120 antennae 116 and 122, respectively, according to standard protocol methods and according to the methods and procedures described here. Messages are transmitted from user equipment 104 to an eNode B 102 on an uplink channel 124 according to these methods. Messages are transmitted from the eNode B 102 to the user equipment 104 on a downlink channel 126 also according to these methods.
[0019] In FIG. 2, a method of sending data from the user equipment to the eNode B according to the principles disclosed is shown. The user equipment 104 stores 202 data that is to be sent from the user equipment 102 to the eNode B 102 in the memory 120 and more particularly buffer 123. According to certain wireless communication standards including those that use OFDM technology, the data in the buffer is not sent from the user equipment 104 to the eNode B 102 until the user equipment receives an indication that the eNode B can receive the data and how much data it is prepared to receive. Thus, the user equipment awaits 204 a slot of time during which it can send 206 a scheduling request indicator (SRI) to the eNode B. The SRI indicates to the eNode B 102 that user equipment 104 has data in its buffer 123 to be transmitted on the uplink, but it does not indicate how much data or what type of data is to be sent. The slot can occur at intervals of 5 ms or other values according to standards. [0020] Upon receipt of the SRI from the user equipment 104, the eNode B sends 208 an indication to the user equipment that eNode B 102 is ready to receive a buffer status report (BSR). The SRI and BSR are in the format and sent according to the rules set for them in various standards for OFDM communications. After receiving the indication, the user equipment 104 sends 210 the BSR to the eNode B 102. The BSR informs the eNode B 102 that the user equipment 104 has data in its buffer 123 that is ready to be sent to the eNode B. The BSR includes information regarding the amount of data, e.g. bits or bytes of data, that is in the buffer and the desired Quality of Service (QoS) that is needed to send the data to the eNode B. Other data can be included in the BSR as is required. [0021] With the BSR, the eNode B 102 knows how much data the user equipment
104 has to send. The eNode B determines according to known methods how much of the data in the buffer 123 it can receive from the user equipment 104 by taking into consideration various factors. Based upon this determination, the eNode B 102 sends 212 a grant to the user equipment 104 that states how much data can be sent and when the data can be sent. At the designated time, the user equipment 102 sends 214 the amount of data allotted in the grant to the eNode B 104. [0022] The eNode B 102 will continue to send grants to the user equipment until the amount of data indicated in BSR has been sent to the eNode B. For example, the BSR may indicate that the user equipment has 3000 bytes of data to be sent. In response, the eNode B can send a first grant for 1000 bytes of data and then send 2 subsequent grants for 1000 bytes each so that all the data is sent. It can be appreciated, however, that the amount of data in the buffer 123 may change for reasons other than the mere fact that the user equipment sends data to the eNode B in response to the grants. For example, data can be discarded 216 from the buffer 123 because it is stale, irrelevant, overflowing buffer, malicious or for other reasons. The data can be determined to be stale or irrelevant for being in the buffer for too long, and this can be determined by the expiration of a timer in the user equipment. Because of the format and construction of the SRI, the SRI is not used to indicate that data has been discarded from the buffer. The SRI purpose is to inform the eNode B 102 that the user equipment wants to send a BSR. At this stage in the process, the eNode B has received a BSR and has calculated that the user equipment 104 has data in the buffer 123.
[0023] Data can be discarded when in a logical channel with a tight delay budget and without persistent scheduling such as with video streaming or game applications the packet delay budget. In addition, congestion or power limitation of the cell edge can prolong the transmission grant for user equipment and thus cause packet discarding.
[0024] Any amount of data can be discarded from the buffers after the BSR has been sent. As such, there may not be the need to send as many grants. From the example given above, if 1000 bytes of data has been discarded for various reasons, the last grant does not need to be sent. Thus, after the discarding of data, the user equipment 104 sends 218 an updated BSR to the eNode B 102. The updated BSR, like the initial BSR, will indicate the amount of data that is in the buffer 123 of the user equipment 104 to be sent to the eNode B and the QoS requirements for that data. In this example, the BSR will state that there is 1000 bytes of data in the buffer 123.
[0025] The updated BSR can be sent at different times and does not need to be in response to a grant. In an embodiment, the updated BSR can be sent as a part of a response to a grant. If the BSR includes 4 bytes of data, a portion of the response to the grant can be reserved for the updated BSR. In this configuration, the eNode B will be configured to determine if the response to the grant includes an updated BSR. In this embodiment, the updated BSR displaces data that is being sent in response to the grant and is therefore given a higher priority than the data in the buffer 123. In another embodiment, data can be reserved in the response to indicate that an updated BSR is needed and the eNode B can send a supplemental grant for the updated BSR. If there is no data discarded by the user equipment 104, the user equipment will continue to respond to grants until all the data in the buffer is sent to the eNode B.
[0026] In an embodiment, a threshold can be used to determine if an updated BSR will be sent to the eNode B. If the amount of discarded data is less than the threshold then the updated BSR is not sent. The threshold will be set so that the efficiencies of the communications will be maintained. For example, the threshold can be set at 4 bytes, which is the amount of data needed for a BSR.
[0027] FIG. 3 illustrates another embodiment for sending updated BSRs. The user equipment 104 stores 302 data that is to be sent from the user equipment 102 to the eNode B 102 in buffer 123. The user equipment 104 awaits 304 for the slot of time during which it can send 306 the SRI to the eNode B. Upon receipt of the SRI from the user equipment 104, the eNode B sends 308 an indication to the user equipment that it is ready to receive the BSR. After receiving the indication, the user equipment 104 sends 310 the BSR to the eNode B 102. The BSR informs the eNode B 102 that the user equipment 104 has data in its buffer that is ready to be sent to the eNode B.
[0028] With the BSR, the eNode B 102 knows how much data the user equipment 104 has to send. The eNode B determines according to known methods how much of the data in the buffer it can receive from the user equipment by taking into consideration various factors. Based upon this determination, the eNode B 102 sends 312 the grant to the user equipment 104 that states how much data can be sent and when the data can be sent. At the designated time, the user equipment 102 sends 314 the amount of data allotted in the grant to the eNode B 104. [0029] It can be appreciated, however, that the amount of data in the buffer 123 may change for reasons other than the mere fact that the user equipment sends data to the eNode B in response to the grants. For example, data can be added 316 to the buffer 123 because the user equipment has more data to send. As stated above, the SRI is not used to indicate that the amount of data in the buffer has changed. Thus, after adding data to the buffer 123, the user equipment 104 sends 318 an updated BSR to the eNode B 102. The updated BSR, like the initial BSR, will indicate the amount of data that is in the buffer 123 of the user equipment 104 to be sent to the eNode B and the QoS requirements for that data. The eNode B 102 will continue to send grants to the user equipment 104 until it has determined that all of the data has been sent from user equipment according to the last BSR it has received.
[0030] In the foregoing specification, specific embodiments of the present invention have been described. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.

Claims

We claim:
1. A method comprising: sending a first buffer status report to indicate an amount of data in a buffer that is to be sent; discarding data from the buffer, and sending a second buffer status report to indicate the change in the amount of data in the buffer as a result of discarding data.
2. The method of claim 1 wherein the first buffer status report includes an amount of data in the buffer.
3. The method of claim 1 further comprising receiving a grant to send at least a portion of the data in the buffer.
4. The method of claim 1 further comprising receiving a grant to send the first buffer status report.
5. A method comprising : sending a first buffer status report to indicate an amount of data in a buffer that is to be sent; changing the amount of data in the buffer; sending a second buffer status report to indicate the change in the amount of data in the buffer that is to be sent.
6. The method of claim 5 wherein changing the amount of data in the buffer comprises discarding data from the buffer since the first buffer report was sent.
7. The method of claim 5 further comprising receiving a grant to send at least a portion of the data in the buffer.
8. An apparatus comprising: a buffer to store data to be sent from the apparatus; a transceiver to send the stored data, and a processor coupled to the buffer and the transceiver wherein the processor creates a first buffer status report to indicate an amount of data stored in the buffer to be sent by the transceiver and wherein the processor creates a second buffer status report when the amount of data in the buffer changes after the first buffer status report is sent by the transceiver.
9. The apparatus of claim 8 wherein the transceiver sends the first buffer status report after receiving a grant that indicates at least a portion of the data in the buffer to be sent by the transceiver.
10. The apparatus of claim 8 wherein the transceiver receives and indication to send the first buffer status report.
PCT/US2010/031770 2009-04-24 2010-04-20 Method and apparatus for triggering buffer status reports after packet discarding Ceased WO2010123916A1 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US17249509P 2009-04-24 2009-04-24
US61/172,495 2009-04-24
US12/722,598 US20100271990A1 (en) 2009-04-24 2010-03-12 Method and apparatus for triggering buffer status reports with packet discarding
US12/722,598 2010-03-12

Publications (1)

Publication Number Publication Date
WO2010123916A1 true WO2010123916A1 (en) 2010-10-28

Family

ID=42992044

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2010/031770 Ceased WO2010123916A1 (en) 2009-04-24 2010-04-20 Method and apparatus for triggering buffer status reports after packet discarding

Country Status (2)

Country Link
US (1) US20100271990A1 (en)
WO (1) WO2010123916A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4614896A4 (en) * 2022-11-03 2025-11-26 Beijing Xiaomi Mobile Software Co Ltd Buffer status report uploading method and apparatus, and device, storage medium and chip

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572913A (en) * 2008-04-28 2009-11-04 华为技术有限公司 Processing method and device for status report of buffer area
KR101331048B1 (en) * 2009-12-16 2013-11-19 한국전자통신연구원 Buffer status reporting method for uplink scheduling and communication system using the same
CN106200616B (en) 2010-05-14 2019-11-19 久益环球表层采矿公司 Periodic decomposition analysis for remote machine monitoring
CN102612143A (en) * 2011-01-20 2012-07-25 华为技术有限公司 Method for processing resource request, user equipment and communication system
US20150341938A1 (en) * 2014-05-22 2015-11-26 Qualcomm Incorporated Uplink operation for rlc communications
CN114222372B (en) * 2015-04-17 2025-10-21 索尼公司 Electronic device and method for wireless communication
US12279289B2 (en) * 2022-05-12 2025-04-15 Qualcomm Incorporated Techniques for improving scheduling request transmission in wireless communications
CN119948907A (en) * 2022-09-28 2025-05-06 上海诺基亚贝尔股份有限公司 Cache status reporting triggered by data discard
CN118741593A (en) * 2023-03-31 2024-10-01 荣耀终端有限公司 Information processing method and device
WO2025065685A1 (en) * 2023-09-28 2025-04-03 Nokia Shanghai Bell Co., Ltd. Buffer status calculation method considering expected packet discarding

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1710963A1 (en) * 2005-04-04 2006-10-11 Samsung Electronics Co.,Ltd. Method and apparatus for reporting a buffer status using node B-estimated buffer status information in a mobile communication system
WO2008156198A2 (en) * 2007-06-19 2008-12-24 Nec Corporation Buffer status reporting

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6993342B2 (en) * 2003-05-07 2006-01-31 Motorola, Inc. Buffer occupancy used in uplink scheduling for a communication device
EP1509012A2 (en) * 2003-08-20 2005-02-23 Samsung Electronics Co., Ltd. Method and apparatus for scheduling uplink packet transmission in a mobile communication system
TWI401918B (en) * 2005-02-03 2013-07-11 Nokia Corp Communication method for transmitting a buffer parameter signal indicating a receiver buffer architecture
KR100912784B1 (en) * 2006-01-05 2009-08-18 엘지전자 주식회사 Data transmission method and data retransmission method
US20080076427A1 (en) * 2006-08-21 2008-03-27 Nokia Corporation Apparatus, method, system, network element, and software product for discontinuous reception priority map to enhance measurement gap control
CN101132220B (en) * 2006-08-22 2011-11-30 上海贝尔阿尔卡特股份有限公司 Method and device for reporting ascending scheduling request or emergency in wireless network
US8031655B2 (en) * 2006-10-03 2011-10-04 Industrial Technology Research Institute Systems and methods for determining granularity level of information about buffer status
JP4922407B2 (en) * 2006-11-15 2012-04-25 サムスン エレクトロニクス カンパニー リミテッド Method and apparatus for buffer status reporting in a mobile communication system
WO2008112233A2 (en) * 2007-03-14 2008-09-18 Interdigital Technology Corporation Method and apparatus for supporting uplink starvation avoidance in a long term evolution system
US8619752B2 (en) * 2007-03-16 2013-12-31 Qualcomm Incorporated Method and apparatus for polling in a wireless communication system
US8041780B2 (en) * 2007-03-29 2011-10-18 Alcatel Lucent Method and apparatus for dynamically pushing content over wireless networks
KR101476188B1 (en) * 2007-04-30 2014-12-24 엘지전자 주식회사 Method for generating data block in mobile communication system
US8406179B2 (en) * 2007-08-07 2013-03-26 Samsung Electronics Co., Ltd. Method and apparatus for performing random access procedure in a mobile communication system
KR101422032B1 (en) * 2007-08-10 2014-07-23 엘지전자 주식회사 Method of setting a channel in a wireless communication system
EP2028890B1 (en) * 2007-08-12 2019-01-02 LG Electronics Inc. Handover method with link failure recovery, wireless device and base station for implementing such method
KR100937432B1 (en) * 2007-09-13 2010-01-18 엘지전자 주식회사 Radio Resource Allocation Method in Wireless Communication System
WO2009040395A1 (en) * 2007-09-26 2009-04-02 Nokia Siemens Networks Oy Method, apparatus and system for signalling of buffer status information
KR101422293B1 (en) * 2007-10-05 2014-07-22 삼성전자주식회사 Method and apparatus for adjusting the reverse data rate in a mobile communication system
WO2009058086A1 (en) * 2007-11-01 2009-05-07 Telefonaktiebolaget L M Ericsson (Publ) Buffer status reporting based on radio bearer configuration
EP2079202A1 (en) * 2008-01-08 2009-07-15 NEC Corporation Method for optimizing the triggering of the transmission of buffer status reporting (BSR) information
US8243667B2 (en) * 2008-01-28 2012-08-14 Lg Electronics Inc. Method for transmitting scheduling request effectively in wireless communication system
EP2235994B1 (en) * 2008-01-30 2014-03-05 Telefonaktiebolaget L M Ericsson (publ) Method and arrangement in a telecommunication system
EP2094038B1 (en) * 2008-02-20 2015-11-04 Amazon Technologies, Inc. Apparatus and method for constructing a data unit that includes a buffer status report
JP4772080B2 (en) * 2008-03-14 2011-09-14 三星電子株式会社 Method and system for transmission and configuration of state information in a communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1710963A1 (en) * 2005-04-04 2006-10-11 Samsung Electronics Co.,Ltd. Method and apparatus for reporting a buffer status using node B-estimated buffer status information in a mobile communication system
WO2008156198A2 (en) * 2007-06-19 2008-12-24 Nec Corporation Buffer status reporting

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) protocol specification (Release 8)", 3GPP STANDARD; 3GPP TS 36.321, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V8.5.0, 1 March 2009 (2009-03-01), pages 1 - 43, XP050377621 *
MOTOROLA: "BSR triggering", 3GPP DRAFT; R2-084426_ BSR TRIGGERING_V01, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. Jeju; 20080812, 12 August 2008 (2008-08-12), XP050319491 *
NEC: "Optimised buffer status reporting", vol. R2-072515, pages 1 - 6, XP002503220, Retrieved from the Internet <URL:www.3gpp.org> [retrieved on 20081110] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4614896A4 (en) * 2022-11-03 2025-11-26 Beijing Xiaomi Mobile Software Co Ltd Buffer status report uploading method and apparatus, and device, storage medium and chip

Also Published As

Publication number Publication date
US20100271990A1 (en) 2010-10-28

Similar Documents

Publication Publication Date Title
US20100271990A1 (en) Method and apparatus for triggering buffer status reports with packet discarding
EP3737173B1 (en) Method for sending data and communication device
EP2428091B1 (en) Handling a scheduling request trigger
US9167594B2 (en) Method and related device of a trigger mechanism of buffer status report and scheduling request in a wireless communication system
EP2158773B1 (en) Methods and systems for scheduling resources in a telecommunication system
EP3627933A1 (en) Communication method, terminal, and base station
US20210243795A1 (en) Flexible data transmission methods considering configured grant timers
CN103369509B (en) A kind of reporting cached state method and terminal device
US9877201B2 (en) Method for communicating in a network, a secondary station and a system therefor
KR101999852B1 (en) Method for communicating in a network, a secondary station and a system therefor
CN114270979A (en) Apparatus and method for CSI acquisition on sidelink
EP3440882B1 (en) Semi-persistent resource allocation enhancement for v2x communication
US20200112989A1 (en) Terminal Communication Method and Related Device
CN110637433A (en) HARQ process for grant-less uplink transmission
US20190238278A1 (en) Retransmission handling at tti length switch
KR101595992B1 (en) Method for communicating and radio station therefor
EP3914003A1 (en) Method and device for resource allocation
KR20100139041A (en) Method for communication and radio station for him
EP2324586A2 (en) Method for communicating in a network, a secondary station and a system therefor
WO2014047918A1 (en) Methods and apparatus for contention-based transmission
WO2024026756A9 (en) Methods and apparatuses of enhanced transmission on preconfigured resource
CN115516982A (en) Uplink Data Grant Scheduling
EP2989843A1 (en) Configuration of communications link to backhaul hub according to predicted backhaul capacity need based on control signalling received prior to user data
KR20250024941A (en) Wireless communication method and device thereof
WO2008155688A1 (en) Method for allocating transmission resources in a telecommunication system, a primary station and a secondary station for carrying out the method.

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: 10715446

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: 10715446

Country of ref document: EP

Kind code of ref document: A1