WO2021072701A1 - Déclenchement de temporisateur d'état de tampon - Google Patents

Déclenchement de temporisateur d'état de tampon Download PDF

Info

Publication number
WO2021072701A1
WO2021072701A1 PCT/CN2019/111660 CN2019111660W WO2021072701A1 WO 2021072701 A1 WO2021072701 A1 WO 2021072701A1 CN 2019111660 W CN2019111660 W CN 2019111660W WO 2021072701 A1 WO2021072701 A1 WO 2021072701A1
Authority
WO
WIPO (PCT)
Prior art keywords
channel group
uplink message
retransmission timer
uplink
base station
Prior art date
Application number
PCT/CN2019/111660
Other languages
English (en)
Inventor
Jinglin Zhang
Haojun WANG
Zhenqing CUI
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2019/111660 priority Critical patent/WO2021072701A1/fr
Publication of WO2021072701A1 publication Critical patent/WO2021072701A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H04L1/1883—Time-out mechanisms using multiple timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • 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/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the following relates generally to wireless communications and more specifically to buffer status timer triggering.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • the UE may indicate whether the UE has uplink data available (e.g., buffered) for transmission to the base station. For instance, the UE may convey that uplink data is or is not available for transmission to the base station via one or more bits of a buffer status report (BSR) .
  • BSR buffer status report
  • BSR buffer status report
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support buffer status timer triggering.
  • a user equipment UE
  • a retransmission timer for a retransmission procedure may be triggered when a UE transmits, to a base station, a buffer status report (BSR) indicating that uplink data is available for transmission at the UE.
  • BSR buffer status report
  • An additional retransmission timer may be triggered if a UE indicates, in a given BSR, that no uplink data is available for transmission at the UE and the UE subsequently receives a retransmission request for the given BSR.
  • the additional retransmission timer may be shorter in duration than the initial retransmission timer and in such cases, rather than waiting for expiration of the initial retransmission timer, upon expiration of the additional retransmission timer, the UE may transmit a scheduling request (SR) if the UE has not received an uplink grant for available uplink data.
  • SR scheduling request
  • a method of wireless communications at a UE may include transmitting, to a base station, an uplink message associated with a process identifier and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group, receiving, from the base station, a request for retransmission of the uplink message, and initiating a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to transmit, to a base station, an uplink message associated with a process identifier and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group, receive, from the base station, a request for retransmission of the uplink message, and initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • the apparatus may include means for transmitting, to a base station, an uplink message associated with a process identifier and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group, receiving, from the base station, a request for retransmission of the uplink message, and initiating a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • a non-transitory computer-readable medium storing code for wireless communications at a UE is described.
  • the code may include instructions executable by a processor to transmit, to a base station, an uplink message associated with a process identifier and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group, receive, from the base station, a request for retransmission of the uplink message, and initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying that uplink data associated with the channel group may be available for transmission to the base station after transmitting the uplink message, and initiating the retransmission timer based on uplink data being available for transmission to the base station.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a second uplink message associated with a second process identifier and the channel group, the second uplink message including a second buffer indicator for the channel group indicating that uplink data may be buffered at the UE for the channel group.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, after expiration of the retransmission timer, a buffer status report associated with the process identifier and the channel group, the buffer status report indicating that uplink data may be buffered at the UE for the channel group.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for resetting the retransmission timer in response to transmitting the buffer status report.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying that uplink data associated with the channel group may be available for transmission to the base station before transmitting the uplink message, and transmitting a second uplink message associated with a second process identifier and the channel group, the second uplink message including a second buffer indicator for the channel group indicating that uplink data may be buffered at the UE for the channel group.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for initiating a second retransmission timer in response to transmitting the second uplink message, where a duration associated with the second retransmission timer may be greater than the retransmission timer.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting the second uplink message before expiration of the second retransmission timer.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting the second uplink message after expiration of the retransmission timer.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for setting a flag indicator associated with the process identifier based on the buffer indicator for the channel group indicating that no additional uplink data may be buffered at the UE for the channel group.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for initiating the retransmission timer based on a value of the flag indicator.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the base station, a second uplink message associated with the process identifier and the channel group upon expiration of the retransmission timer.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the base station, a second uplink message associated with a second process identifier and the channel group before expiration of the retransmission timer.
  • the process identifier may be associated with a hybrid automatic repeat request (HARQ) identifier
  • the channel group may be associated with a logical channel group (LCG) identifier.
  • HARQ hybrid automatic repeat request
  • LCG logical channel group
  • FIG. 1 illustrates an example of a wireless communications system that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example of a wireless communications system that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIG. 3 illustrates an example of a timeline that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a retransmission timer procedure that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIG. 5 illustrates an example of a retransmission timer procedure that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIG. 6 illustrates an example of a process flow that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIGs. 7 and 8 show block diagrams of devices that support buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIG. 9 shows a block diagram of a buffer status manager that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIG. 10 shows a diagram of a system including a device that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • FIGs. 11 through 14 show flowcharts illustrating methods that support buffer status timer triggering in accordance with aspects of the present disclosure.
  • a UE may initially transmit an indication (e.g., a buffer status report (BSR) ) that no uplink data is available for transmission, but after transmitting, uplink data becomes available at the UE.
  • BSR buffer status report
  • the UE may then transmit a second indication to the base station indicating that uplink data is available for transmission.
  • the UE may start a retransmission timer during which the UE is to wait for an uplink grant from the base station for scheduling a transmission of the uplink data.
  • the base station may grant resources for retransmission of the initial indication, and the resources may occur later in time than the transmission of the second indication.
  • the base station may determine that no uplink data is available for transmission by the UE and may refrain from scheduling uplink resources for transmission of the uplink data that became available after the first transmission of the initial indication. This may result in the UE waiting for expiration of the retransmission timer before transmitting another BSR indicating that data is available at the UE, which may increase latency experienced by the UE and reduce system throughput.
  • a UE may support the use of multiple retransmission timers and other parameters (e.g., a flag indicator such as a harqBsrZeroFlag) to reduce latency and improve network efficiency.
  • One retransmission timer (e.g., retxBSR-Timer) may be configured to start when a UE transmits, to a base station, a BSR indicating that uplink data is available for transmission at the UE. For the duration of this timer, the UE may wait for an uplink grant from the base station that schedules resources for transmission of the uplink data that is available at the UE. If the UE has not received an uplink grant prior to expiration of the timer, the UE may reset the timer and transmit another BSR (e.g., in a scheduling request (SR) ) indicating that uplink data is available for transmission.
  • SR scheduling request
  • An additional retransmission timer may be triggered if a UE indicates, in a BSR, that no uplink data is available for transmission at the UE (i.e., UE includes a value of 0 for the BSR indicating that there is no pending data at the UE) , then receives uplink data for transmission as well as a retransmission request for the BSR.
  • the duration of the additional retransmission timer may be static, dynamic, configured by the UE, configured by the base station, or any combination thereof, and in some cases, the additional retransmission timer may be shorter in duration than the initial retransmission timer.
  • the UE may wait for an uplink grant for scheduling the uplink data and if the UE has not received an uplink grant for available uplink data upon expiration of the timer, the UE may transmit an SR, which may include another BSR indicating that uplink data is available for transmission at the UE.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects are then described with respect to a timeline, retransmission timer procedures, and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to buffer status timer triggering.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • NR New Radio
  • the wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.
  • ultra-reliable e.g., mission critical
  • the base stations 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may be devices in different forms or having different capabilities.
  • the base stations 105 and the UEs 115 may wirelessly communicate via one or more communication links 125.
  • Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base station 105 may establish one or more communication links 125.
  • the coverage area 110 may be an example of a geographic area over which a base station 105 and a UE 115 may support the communication of signals according to one or more radio access technologies.
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, the base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment) , as shown in FIG. 1.
  • network equipment e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment
  • the base stations 105 may communicate with the core network 130, or with one another, or both.
  • the base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via an S1, N2, N3, or other interface) .
  • the base stations 105 may communicate with one another over the backhaul links 120 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations 105) , or indirectly (e.g., via core network 130) , or both.
  • the backhaul links 120 may be or include one or more wireless links.
  • One or more of the base stations 105 described herein may include or may be referred to by a person having ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a Home NodeB, a Home eNodeB, or other suitable terminology.
  • a base transceiver station a radio base station
  • an access point a radio transceiver
  • a NodeB an eNodeB (eNB)
  • eNB eNodeB
  • a next-generation NodeB or a giga-NodeB either of which may be referred to as a gNB
  • gNB giga-NodeB
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the base stations 105 may wirelessly communicate with one another via one or more communication links 125 over one or more carriers.
  • the term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links 125.
  • a carrier used for a communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • BWP bandwidth part
  • Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN) ) and may be positioned according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode where initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode where a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .
  • the communication links 125 shown in the wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions from a base station 105 to a UE 115.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a number of determined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the base stations 105, the UEs 115, or both
  • the wireless communications system 100 may include base stations 105 or UEs 115 that support simultaneous communications via carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related.
  • the number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) .
  • a wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams) , and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, where a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
  • Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
  • SFN system frame number
  • Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots.
  • each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing.
  • Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., the number of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed on a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • a control region for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier.
  • One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
  • Each base station 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof.
  • the term “cell” may refer to a logical communication entity used for communication with a base station 105 (e.g., over a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) .
  • a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) over which the logical communication entity operates.
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the base station 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with geographic coverage areas 110, among other examples.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
  • a small cell may be associated with a lower-powered base station 105, as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a base station 105 may support one or multiple cells and may also support communications over the one or more cells using one or multiple component carriers.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
  • protocol types e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB)
  • NB-IoT narrowband IoT
  • eMBB enhanced mobile broadband
  • a base station 105 may be movable and therefore provide communication coverage for a moving geographic coverage area 110.
  • different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105.
  • the overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105.
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.
  • Some UEs 115 may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station 105 without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception simultaneously) .
  • half-duplex communications may be performed at a reduced peak rate.
  • Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating over a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications.
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions) .
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT) , mission critical video (MCVideo) , or mission critical data (MCData) .
  • MCPTT mission critical push-to-talk
  • MCVideo mission critical video
  • MCData mission critical data
  • Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • One or more UEs 115 utilizing D2D communications may be within the geographic coverage area 110 of a base station 105.
  • Other UEs 115 in such a group may be outside the geographic coverage area 110 of a base station 105 or be otherwise unable to receive transmissions from a base station 105.
  • groups of the UEs 115 communicating via D2D communications may utilize a one-to-many (1: M) system in which each UE 115 transmits to every other UE 115 in the group.
  • a base station 105 facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs 115 without the involvement of a base station 105.
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to the network operators IP services 150.
  • the operators IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • Some of the network devices may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC) .
  • Each access network entity 140 may communicate with the UEs 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs) .
  • Each access network transmission entity 145 may include one or more antenna panels.
  • various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station 105) .
  • the wireless communications system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors.
  • the transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band, or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • SHF super high frequency
  • EHF extremely high frequency
  • the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the base stations 105, and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate use of antenna arrays within a device.
  • mmW millimeter wave
  • the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions.
  • the techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • the wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the base stations 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA) .
  • Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a base station 105 or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a base station 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations.
  • a base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.
  • the base stations 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , where multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
  • communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based.
  • a Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels.
  • RLC Radio Link Control
  • a Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency.
  • the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a base station 105 or a core network 130 supporting radio bearers for user plane data.
  • RRC Radio Resource Control
  • transport channels may be mapped to physical channels.
  • the UEs 115 and the base stations 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link 125.
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) .
  • a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • a HARQ procedure may be associated with a given HARQ process identifier (ID) , which may allow a UE 115 to support multiple ongoing HARQ processes (e.g., multiple uplink transmissions and monitoring for corresponding feedback) .
  • ID HARQ process identifier
  • a UE 115 may trigger a timer upon transmission of a BSR indicating that uplink data is available for transmission to the base station 105. After the timer is triggered, the UE 115 may wait for an uplink grant from the base station 105 that schedules resources for transmission of the uplink data.
  • a UE 115 may support multiple timers (e.g., multiple retransmission timers) , an additional timer may be triggered if the UE 115 indicates, in a given BSR, that no uplink data is available for transmission at the UE 115 and the UE 115 subsequently receives a retransmission request for the given BSR.
  • the additional retransmission timer may be shorter in duration than the initial retransmission timer and in such cases, rather than waiting for expiration of the initial retransmission timer, upon expiration of the additional retransmission timer, the UE 115 may transmit an SR, which may include another BSR, if the UE 115 has not received an uplink grant for transmission of available uplink data.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • wireless communications system 200 may implement aspects of wireless communications system 100.
  • the wireless communications system 200 includes base station 105-a and UE 115-a.
  • Base station 105-a may communicate with UE 115-a using time-frequency resources via communication link 205. For example, base station 105-a may transmit an uplink grant (e.g., an uplink grant that schedules resources for an uplink transmission) to UE 115-a via a channel of the communication link 205. In some examples, UE 115-a may transmit an uplink message (e.g., a BSR) to inform a network entity, such as base station 105-a, how much data UE 115-a has to transmit.
  • an uplink grant e.g., an uplink grant that schedules resources for an uplink transmission
  • UE 115-a may transmit an uplink message (e.g., a BSR) to inform a network entity, such as base station 105-a, how much data UE 115-a has to transmit.
  • a network entity such as base station 105-a
  • the uplink message may include a value (e.g., an index value, a buffer indicator) that indicates how much data UE 115-a is available (e.g., has buffered) for a given channel group (e.g., an LCG) .
  • a value e.g., an index value, a buffer indicator
  • an index value of 0 may indicate that UE 115-a has no uplink data to transmit for a channel group
  • an index value of 1 may indicate UE 115-a has less than or equal to 10 bytes of data to transmit for a channel group, etc.
  • the index value or buffered data may be associated with a logical channel or LCG and the uplink message that includes the index value or indication of buffered data may be associated with a HARQ process and a corresponding HARQ ID.
  • the UE 115-a may trigger (e.g., start or restart) a retransmission timer 215 (e.g., a bsrRetxTimer) .
  • the base station 105-a may monitor the communication link 205 for the uplink message and perform an error detection procedure (e.g., a cyclic redundancy check (CRC) ) on the uplink message to determine if the uplink message was successfully received and decoded. After performing a decoding procedure on the uplink message, base station 105-a may transmit an uplink grant 210 to UE 115-a. If the decoding of the uplink message is successful, and the uplink message indicated that the UE 115-a has uplink data available, the uplink grant 210 may include scheduling information for transmission of the uplink data by the UE 115-a. If the decoding of the uplink message was unsuccessful, the uplink grant 210 may indicate an unsuccessful reception of the uplink message, and may include scheduling information for retransmission of the uplink message by the UE 115-a.
  • an error detection procedure e.g., a cyclic redundancy check (CRC)
  • CRC cyclic redundancy check
  • the uplink message carrying a BSR, the uplink grant 210, or both may be associated with a process (e.g., a HARQ process) and a corresponding ID.
  • the uplink message may contain information (e.g., the BSR within the uplink message may indicate information) from a previous uplink message (e.g., a message retransmit) or alternative or additional data (e.g., a message transmit) .
  • UE 115-a may trigger (e.g., start or restart) an additional timer 220 (e.g., additionalBsrRetxTimer) based on the reception of the uplink grant 210.
  • an additional timer 220 e.g., additionalBsrRetxTimer
  • UE 115-a may start or restart the additional timer 220 if the uplink grant 210 indicates an unsuccessful reception of an uplink message. Additionally or alternatively, UE 115-a may start or restart the additional timer 220 based on an amount of data UE 115-a has buffered for an LCG. In some examples, UE 115-a may start or restart the additional timer 220 based on an amount of buffered data indicated in an uplink message. For example, if the uplink grant 210 indicates a retransmission of an uplink message indicating no additional data buffered (e.g., BSR index 0) for an LCG, UE 115-a may start or restart the additional timer 220.
  • BSR index 0 additional data buffered
  • UE 115-a may associate a process, process name, process ID, or process index with a buffer status (e.g., an amount of buffered data) and the UE 115-a may support one or more processes (e.g., HARQ processes) when communicating with a base station.
  • UE 115-a may associate a process number with a Boolean value.
  • UE 115-a may maintain an array of Boolean values that correspond to processes, and UE 115-a may use a Boolean value (e.g., 1, true) to indicate that a process is associated with an empty data buffer.
  • an index of the Boolean array may correspond to a process (e.g., a process ID, a process number, a process key, a process name, process index etc. ) .
  • the data buffer or the indication of an amount of buffered data may be for an LCG.
  • UE 115-a may transmit an uplink message indicating there is no buffered data for a channel group (e.g., an LCG) .
  • the uplink message may be associated with a process (e.g., a HARQ process) . Additionally or alternatively, UE 115-a may associate the process with an empty data buffer.
  • UE 115-a may associate a process ID with a non-empty data buffer. For example, UE 115-a may transmit an uplink message indicating that UE 115-a has buffered data for an LCG, and UE 115-a may associate a process corresponding to the uplink message with a non-empty data buffer. In some cases, UE 115-a may maintain an array of Boolean values that correspond to processes, and UE 115-a may use a Boolean value (e.g., a 0, false) to indicate that a process is associated with a non-empty data buffer.
  • a Boolean value e.g., a 0, false
  • UE 115-a may start or restart the additional timer 220 based on an uplink grant 210 (e.g., an uplink grant, downlink control information (DCI) ) , and the uplink grant 210 may be associated with one or more processes or one or more LCGs.
  • UE 115-a may receive an uplink grant 210 associated with a process (e.g., HARQ process “N” ) or an LCG.
  • the uplink grant 210 may indicate time-frequency resources for UE 115-a, which the UE 115-a may use for retransmission of the uplink message.
  • the uplink grant 210 may optionally indicate a failed message reception (e.g., a failed CRC) at base station 105-a.
  • UE 115-a may determine that a HARQ process “N” is associated with a data buffer status and an uplink message (e.g., a BSR) indicating that UE 115-a does not have data buffered for an LCG.
  • UE 115-a may start or restart the additional timer 220 based on a buffer indicator associated with the LCG.
  • UE 115-a may start or restart the additional timer 220 based on a buffer status (e.g., a buffer index value of 0) associated with the LCG.
  • UE 115-a may start or restart the additional timer 220 based on the association of HARQ process “N” . For example, if process “N” is associated with an empty data buffer (e.g., a value of 1 at index “N” of the array of Boolean values) , the UE may start the additional timer 220. For example, if process “N” is associated with a non-empty data buffer (e.g., a value of 0 at index “N” of the array of Boolean values) , UE 115-a may refrain from starting the additional timer.
  • a non-empty data buffer e.g., a value of 0 at index “N” of the array of Boolean values
  • UE 115-a may alter the association of a process based on receiving a message (e.g., a transmission grant, an uplink grant, DCI) from base station 105-a.
  • a message e.g., a transmission grant, an uplink grant, DCI
  • an uplink grant 210 may be associated with one or more processes (e.g., HARQ process “N” ) or one or more LCGs.
  • the uplink grant 210 may additionally or alternatively indicate a successful message reception (e.g., a successful CRC) .
  • UE 115-a may alter the association of process “N” based on the received uplink grant 210.
  • UE 115-a may associate process “N” with a non-empty data buffer, an uplink grant 210 (e.g., a message transmit) , a successful CRC, etc.
  • the UE may indicate the association with a Boolean value (e.g., a value of 0 at index “N” of the array of Boolean values) .
  • UE 115-a may start or restart the additional timer 220 based on a message transmission (e.g., an SR) , or based on UE 115-a receiving an uplink grant. For example, if the additional timer 220 is running and UE 115-a sends an SR, UE 115-a may reset or restart the additional timer. In some cases, UE 115-a may send an uplink message (e.g., a BSR via a physical uplink shared channel (PUSCH) ) based on the additional timer 220 expiring.
  • PUSCH physical uplink shared channel
  • UE 115-a may reset or restart the additional timer 220.
  • UE 115-a may trigger a regular BSR.
  • UE 115-a may send one or more uplink messages (e.g., BSR PUSCHs) based on the expiration of the additional timer 220.
  • the length of the additional timer 220 may be static, dynamic, determined by UE 115-a, determined by base station 105-a, or any combination thereof.
  • the length of the additional timer 220 may be based on message priority (e.g., a shorter timer length corresponding to higher importance) , network traffic (e.g., a shorter timer corresponding to less network traffic) , data type, amount of data, etc.
  • FIG. 3 illustrates an example of a timeline 300 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • timeline 300 may implement aspects of wireless communications systems 100 or 200.
  • the timeline 300 includes base station 105-b and UE 115-b, which may be examples of corresponding devices as described with reference to FIGs. 1 and 2.
  • the UE 115-b may transmit an uplink message 305, which may be associated with a process (e.g., a HARQ process 0) or a channel group (e.g., an LCG) .
  • the uplink message 305 may include one or more buffer indicators (e.g., one or more BSRs) for a given channel group.
  • a buffer indicator e.g., BSR
  • a buffer indicator included in uplink message 305 may indicate whether uplink data is buffered (e.g., available) at UE 115-b for a given channel group.
  • the UE 115-b transmits an uplink message 305 that contains a BSR value of 0 indicating that no uplink data is available for transmission at the UE 115-b.
  • UE 115-b may associate a given process (e.g., HARQ process 0 associated with the uplink message 305) with a flag (e.g., a Boolean value) used to indicate whether a BSR value of 0 was transmitted for the given process.
  • the Boolean value may be contained in an array of Boolean values such that each process identifier (e.g., HARQ process ID) may be associated with a respective Boolean value (e.g., true, false, 0, 1) based on whether a given BSR for the respective process was transmitted with a value of 0.
  • UE 115-b may generate or update a parameter used to maintain the Boolean values for each respective process identifier.
  • a parameter such as a flag may be a single parameter or an array for maintaining the list of Boolean values for each process ID, and a value for a process ID may be changed or updated depending on whether a BSR with index 0 is transmitted for the process ID.
  • the index of the Boolean value may correspond to the process (e.g., HARQ process 0, HARQ process 1) associated with the uplink message 305.
  • UE 115-b may indicate that HARQ process 0 is associated with an uplink message 305 indicating that UE 115-b does not have additional data buffered for an LCG (e.g., BSR value 0 was transmitted for HARQ process 0) , and the UE 115-b may set the Boolean value to 1 (or true) , as shown at 310.
  • LCG e.g., BSR value 0 was transmitted for HARQ process 0
  • new uplink data may arrive at UE 115-b, and the arrival of the new uplink data for transmission to base station 105-b may occur after UE 115-b transmitted the uplink message 305 indicating that UE 115-b has no more uplink data buffered for an LCG.
  • the new uplink data may be based on user input, one or more processes running on UE 115-b, data generated at UE 115-b, data generated at base station 105-b, etc.
  • UE 115-b may transmit an uplink message 320, which may be associated with a process ID (e.g., HARQ process 1) or a channel group.
  • the uplink message 320 may include one or more BSRs for a given channel group and a set of multiple BSRs may be associated with one or more LCGs.
  • a buffer indicator e.g., BSR
  • uplink message 320 may indicate that uplink data is available (e.g., buffered) at UE 115-b for the LCG (e.g., UE 115-b includes a BSR having a non-zero value in uplink message 320) .
  • the LCG associated with the uplink message 320 may be the same LCG associated with the uplink message 305. Additionally or alternatively, the LCG associated with the uplink message 320 may be a different LCG than the LCG associated with the uplink message 305. In some cases, the process (e.g., HARQ process 1) associated with the uplink message 320 may be different than the process (e.g., HARQ process 0) associated with the uplink message 305. After transmitting uplink message 320 indicating a non-zero BSR value, UE 115-b may start a transmission timer (e.g., a first retransmission timer) at 325.
  • a transmission timer e.g., a first retransmission timer
  • the transmission timer may be associated with a given process ID such as HARQ process 1, and upon expiration of the transmission timer, if the UE 115-b has not received a grant or retransmission request in response to the uplink message 320, the UE 115-b may trigger an SR (e.g., including another BSR) indicating that the UE 115-b has uplink data available for transmission.
  • SR e.g., including another BSR
  • base station 105-b may monitor for uplink message 305 and perform a decoding procedure on the uplink message 305. If the decoding procedure fails (e.g., if a CRC fails) , the base station may schedule uplink resources for the UE 115-b to retransmit uplink message 305. For instance, at 330, the base station 105-b may transmit an uplink grant scheduling retransmission of the uplink message 305.
  • the request for retransmission may indicate an unsuccessful reception of an uplink message 305 (e.g., via a negative ACK (NACK) ) and may indicate an unsuccessful decoding or error check failure (e.g., CRC failure) of the uplink message 305.
  • NACK negative ACK
  • UE 115-b may receive the grant scheduling retransmission of uplink message 305 containing a BSR value of 0, and may start an additional timer at 335.
  • the additional timer may be an additional timer 220 as described with reference to FIG. 2 and may be started for a given LCG or process ID (e.g., HARQ process 0) associated with the grant scheduling the retransmission at 330 and based on the value for the flag indicator (e.g., HarqBsrZeroFlag) .
  • UE 115-b may start the additional timer (e.g., an additional retransmission timer) for HARQ process 0 and a given LCG based on the flag parameters having a value of true or 1.
  • the UE 115-b may trigger retransmission timer at 335.
  • UE 115-b may perform retransmission of a BSR having a value of 0 (e.g., in another uplink message) to the base station 105-b.
  • the base station 105-b may successfully receive uplink message 320, which may indicate to the base station 105-b that the UE 115-b has uplink data available for transmission.
  • the base station 105-b may successfully receive the retransmission of the BSR having a value of 0, as transmitted at 340, which indicates to the base station 105-b that the UE 115-b does not have uplink data available for transmission.
  • the base station 105-b may refrain from assigning uplink resources for transmission of uplink data at the UE 115-b (i.e., the new uplink data that arrived at the UE at 315) because the base station 105-b received and decoded a BSR having a value of 0 (i.e., the retransmission of BSR having a value of 0) after receiving and decoding the BSR having a non-zero value at 345.
  • the UE 115-b may wait for expiration of the additional timer at 355, which expires sooner than the transmission timer, and transmit an SR at 360 to the base station 105-b.
  • the SR may include an indication (e.g., a BSR having a non-zero value) that uplink data (i.e., the new uplink data that arrived at 315) is available for transmission by the UE 115-b.
  • the retransmission timer length (e.g., duration) may be static or dynamic. In some examples, the length of the retransmission timer may be determined or selected by UE 115-b.
  • the length of the retransmission timer may be determined or selected by base station 105-b. In some examples, the length of the retransmission timer may be based on network conditions (e.g., interference levels, an amount of available transmission resources, a number of devices, a number of devices per resource, etc. ) . In some cases, the length of the retransmission timer be based on the type of data at UE 115-b (e.g., a reliability requirement, a priority indication, etc. ) . In some cases, the length of the retransmission timer may be shorter than the length of the retransmission timer.
  • network conditions e.g., interference levels, an amount of available transmission resources, a number of devices, a number of devices per resource, etc.
  • the length of the retransmission timer be based on the type of data at UE 115-b (e.g., a reliability requirement, a priority indication, etc. ) . In some cases, the length of the
  • the retransmission timer may be started or restarted when UE 115-b receives a retransmission message for an uplink message associated with an indication of an empty data buffer. In some examples, the retransmission timer may be started or restarted when UE 115-b receives a retransmission message associated with an LCG or an empty data buffer.
  • FIG. 4 illustrates an example of a retransmission timer procedure 400 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • retransmission timer procedure 400 may implement aspects of wireless communications systems 100 or 200.
  • a UE may operate according to retransmission timer procedure 400 when a retransmission timer is not running.
  • a UE may operate according to retransmission timer procedure 400 as well as additional or alternative procedures.
  • a UE may determine whether a BSR index value of 0 is associated with a given process (e.g., HARQ process “N” ) . If so, at 410, a UE associates HARQ process “N” with an empty buffer indicating that uplink data is available at the UE for transmission. In some examples, the UE may associate HARQ process “N” with an empty buffer by setting a Boolean value to true. In some examples, the Boolean value may be set to true and may be at an index value of “N” in an array of Boolean values.
  • the UE checks to confirm whether a CRC failure has occurred for HARQ process “N” at 415 and if no failure has occurred, the UE associated HARQ process “N” with a non-empty buffer (i.e., the UE has available uplink data for HARQ process “N” ) at 420.
  • the UE checks to confirm whether a CRC failure has occurred for HARQ process “N” at 415 and if no failure has occurred, the UE associated HARQ process “N” with a non-empty buffer (i.e., the UE has available uplink data for HARQ process “N” ) at 420.
  • the UE may determine an error check corresponding to HARQ process “N” has failed by receiving, for example, a retransmission request corresponding to HARQ process “N” , a NACK message corresponding to HARQ process “N” , etc.
  • the UE may determine an error check corresponding to HARQ process “N” has succeeded by receiving, for example, a transmission request corresponding to HARQ process “N” , an ACK message corresponding to HARQ process “N” , etc.
  • the UE may associate HARQ process “N” with a non-empty buffer by setting a Boolean value to false.
  • the Boolean value may be set to true and may be at an index of “N” in an array of Boolean values.
  • the UE may determine whether HARQ process “N” is associated with an empty buffer and whether a retransmission timer is running. In some examples, a UE may determine that process “N” is associated with an empty buffer by checking an array of Boolean values. For example, a determination that process “N” is associated with an empty buffer may be based on a Boolean value of true (e.g., 1) at index “N” of the array of Boolean values.
  • a determination that process “N” is associated with an empty buffer may be based on a Boolean value of false (e.g., 0) at index “N” of the array of Boolean values.
  • a set, hashmap, or other data structure may be used to indicate one or more processes associated with an empty buffer.
  • the retransmission timer procedure may end at 430.
  • the UE may start an additional timer (e.g., retransmission timer) .
  • the additional timer may be an example of the additional timer 220 as described with reference to FIGs. 2 and 3.
  • the UE may start the additional timer based on an LCG being associated with an empty buffer and the state of the additional timer.
  • the UE may start the additional timer based on a HARQ process “N” being associated with an empty buffer and the state of the additional timer. For example, the UE may start the additional timer when HARQ process “N” is associated with an empty buffer and the additional timer is not already running.
  • the UE may refrain from starting the additional timer when HARQ process “N” is associated with a non-empty buffer. In some examples, the UE may refrain from starting the additional timer when HARQ process “N” is not associated with a buffer. Additionally or alternatively, the UE may refrain from starting the additional timer when the additional timer is already running.
  • FIG. 5 illustrates an example of a retransmission timer procedure 500 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • retransmission timer procedure 500 may implement aspects of wireless communications systems 100 or 200.
  • a UE may follow retransmission timer procedure 500 when a retransmission timer is running.
  • a UE may follow aspects of retransmission timer procedure 500 and additional or alternative procedures.
  • a UE may determine whether an additional retransmission timer (e.g., a retransmission timer, an additional timer 220) is expired. In some cases, the UE may determine that the additional timer is expired (e.g., the additional timer is not running, a time threshold of the additional timer has been met or exceeded) and as a result, at 510, a UE may reset the additional retransmission timer. Additionally or alternatively, at 510, the UE may trigger a standard BSR procedure when the additional retransmission timer expires.
  • an additional retransmission timer e.g., a retransmission timer, an additional timer 220
  • the UE may determine whether an SR has been sent by the UE or the UE has received an uplink grant from a base station at 515. If an SR has been sent or the UE received an uplink grant, the UE may stop or reset the additional retransmission timer at 520. Otherwise, the UE goes back to 505.
  • FIG. 6 illustrates an example of a process flow 600 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • process flow 600 may implement aspects of wireless communications systems 100 or 200.
  • the process flow 600 includes base station 105-c and UE 115-c, which may be examples of the corresponding devices described with reference to FIGs. 1 through 3.
  • Buffer status timer triggering may improve communication efficiency, reduce system latency, improve user experience, or any combination thereof.
  • Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.
  • UE 115-c may transmit an uplink message to base station 105-c.
  • the uplink message may be associated with a process ID (e.g., a HARQ process ID) or a channel group (e.g., an LCG) .
  • the uplink message may include a buffer indicator (e.g., a BSR index) for the channel group.
  • the buffer indicator may indicate that no additional uplink data is buffered at UE 115-c for the channel group.
  • UE 115-c may receive a request for retransmission.
  • the request for retransmission may request the retransmission of the uplink message transmitted at 605.
  • the request for retransmission may be associated with a process ID (e.g., a HARQ process ID) or a channel group (e.g., an LCG) .
  • the channel group associated with the request for retransmission may be the same channel group associated with the uplink message.
  • UE 115-c may initiate a retransmission timer (e.g., an additional timer) .
  • UE 115-c may initiative the retransmission timer in response to receiving the request for retransmission of the uplink message.
  • UE 115-c may initiate the retransmission timer based on the buffer indicator for the channel group. For example, UE 115-c may initiate the retransmission timer based on the buffer indicator for the channel group indicating that no additional data is buffered at UE 115-c for the channel group.
  • UE 115-c may identify that uplink data associated with the channel group is available for transmission to base station 105-c after transmitting the uplink message. In some cases, UE 115-c may initiate the retransmission timer based on uplink data being available for transmission to base station 105-c. In some cases, UE 115-c may transmit a second uplink message associated with a second process ID or the channel group. In some cases, the second uplink message may include a second buffer indicator for the channel group. In some cases, the second buffer indicator for the channel group may indicate that uplink data is buffered at UE 115-c for the channel group.
  • UE 115-c may transmit a BSR associated with a process ID or channel group after expiration of the retransmission timer.
  • the buffer status report may indicate that uplink data is buffered at UE 115-c for the channel group. Additionally or alternatively, UE 115-c may reset the retransmission timer in response to transmitting the buffer status report.
  • UE 115-c may identify that uplink data associated with the channel group is available for transmission to base station 105-c before transmitting the uplink message. In some cases, UE 115-c may transmit a second uplink message associated with the channel group or a second process ID. In some cases, the second uplink message may include a second buffer indicator for the channel group. In some cases, the second buffer indicator for the channel group may indicate that uplink data is buffered at UE 115-c for the channel group. In some cases, UE 115-c may initiative a second retransmission timer in response to transmitting the second uplink message. In some cases, a duration associated with the second retransmission timer may be greater than the retransmission timer.
  • UE 115-c may transmit the second uplink message before expiration of the second retransmission timer. In some cases, UE 115-c may transmit the second uplink message after expiration of the second retransmission timer. In some cases, UE 115-c may set a flag indicator associated with the process ID based on the buffer indicator for the channel group. In some cases, UE 115-c may set the flag indicator associated with the process ID based on the buffer indicator indicating that no additional uplink data is buffered at the UE for the channel group. In some cases, UE 115-c may initiate the retransmission timer based on the value of the flag indicator.
  • FIG. 7 shows a block diagram 700 of a device 705 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the device 705 may be an example of aspects of a UE 115 as described herein.
  • the device 705 may include a receiver 710, a buffer status manager 715, and a transmitter 720.
  • the device 705 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to buffer status timer triggering, etc. ) . Information may be passed on to other components of the device 705.
  • the receiver 710 may be an example of aspects of the transceiver 1020 described with reference to FIG. 10.
  • the receiver 710 may utilize a single antenna or a set of antennas.
  • the buffer status manager 715 may transmit, to a base station, an uplink message associated with a process ID and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group, receive, from the base station, a request for retransmission of the uplink message, and initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • the buffer status manager 715 may be an example of aspects of the buffer status manager 1010 described herein.
  • the buffer status manager 715 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the buffer status manager 715, or its sub-components may be executed by a general-purpose processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the buffer status manager 715 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the buffer status manager 715, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the buffer status manager 715, or its sub-components may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • I/O input/output
  • the transmitter 720 may transmit signals generated by other components of the device 705.
  • the transmitter 720 may be collocated with a receiver 710 in a transceiver module.
  • the transmitter 720 may be an example of aspects of the transceiver 1020 described with reference to FIG. 10.
  • the transmitter 720 may utilize a single antenna or a set of antennas.
  • the communications manager 715 described herein may be implemented as a chipset of a wireless modem, and the receiver 710 and the transmitter 720 may be implemented as sets of analog components (e.g., amplifiers, filters, phase shifters, antennas, etc. )
  • the wireless modem may obtain and decode signals from the receiver 710 over a receive interface, and may output signals for transmission to the transmitter 720 over a transmit interface.
  • the actions performed by the communications manager 715 may be implemented to realize one or more potential advantages.
  • One implementation may allow a UE 115 to save power and increase battery life by reducing latency at the UE 115. Techniques herein may allow for reduced wait time for the UE 115, which may improve the efficiency of the UE 115.
  • Another implementation may provide improved quality and reliability of service at the UE 115 by improving resource utilization.
  • FIG. 8 shows a block diagram 800 of a device 805 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the device 805 may be an example of aspects of a device 705, or a UE 115 as described herein.
  • the device 805 may include a receiver 810, a buffer status manager 815, and a transmitter 835.
  • the device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 810 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to buffer status timer triggering, etc. ) . Information may be passed on to other components of the device 805.
  • the receiver 810 may be an example of aspects of the transceiver 1020 described with reference to FIG. 10.
  • the receiver 810 may utilize a single antenna or a set of antennas.
  • the buffer status manager 815 may be an example of aspects of the buffer status manager 715 as described herein.
  • the buffer status manager 815 may include an uplink message transmitter 820, a retransmission request receiver 825, and a retransmission timer component 830.
  • the buffer status manager 815 may be an example of aspects of the buffer status manager 1010 described herein.
  • the uplink message transmitter 820 may transmit, to a base station, an uplink message associated with a process ID and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group.
  • the retransmission request receiver 825 may receive, from the base station, a request for retransmission of the uplink message.
  • the retransmission timer component 830 may initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • the transmitter 835 may transmit signals generated by other components of the device 805.
  • the transmitter 835 may be collocated with a receiver 810 in a transceiver module.
  • the transmitter 835 may be an example of aspects of the transceiver 1020 described with reference to FIG. 10.
  • the transmitter 835 may utilize a single antenna or a set of antennas.
  • FIG. 9 shows a block diagram 900 of a buffer status manager 905 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the buffer status manager 905 may be an example of aspects of a buffer status manager 715, a buffer status manager 815, or a buffer status manager 1010 described herein.
  • the buffer status manager 905 may include an uplink message transmitter 910, a retransmission request receiver 915, a retransmission timer component 920, an uplink data manager 925, a BSR module 930, and a flag manager 935. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the uplink message transmitter 910 may transmit, to a base station, an uplink message associated with a process ID and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group. In some examples, the uplink message transmitter 910 may transmit a second uplink message associated with a second process ID and the channel group, the second uplink message including a second buffer indicator for the channel group indicating that uplink data is buffered at the UE for the channel group. In some cases, the uplink message transmitter 910 may transmit the second uplink message before expiration of the second retransmission timer. In some instances, the uplink message transmitter 910 may transmit the second uplink message after expiration of the retransmission timer. In some aspects, the uplink message transmitter 910 may transmit, to the base station, a second uplink message associated with the process ID and the channel group upon expiration of the retransmission timer.
  • the uplink message transmitter 910 may transmit, to the base station, a second uplink message associated with a second process ID and the channel group before expiration of the retransmission timer.
  • the process ID is associated with a HARQ identifier.
  • the channel group is associated with an LCG ID.
  • the retransmission request receiver 915 may receive, from the base station, a request for retransmission of the uplink message.
  • the retransmission timer component 920 may initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group. In some examples, the retransmission timer component 920 may initiate the retransmission timer based on uplink data being available for transmission to the base station. In some cases, the retransmission timer component 920 may reset the retransmission timer in response to transmitting the buffer status report.
  • the retransmission timer component 920 may initiate a second retransmission timer in response to transmitting the second uplink message, where a duration associated with the second retransmission timer is greater than the retransmission timer. In some aspects, the retransmission timer component 920 may initiate the retransmission timer based on a value of the flag indicator.
  • the uplink data manager 925 may identify that uplink data associated with the channel group is available for transmission to the base station after transmitting the uplink message. In some examples, the uplink data manager 925 may identify that uplink data associated with the channel group is available for transmission to the base station before transmitting the uplink message.
  • the BSR module 930 may transmit, after expiration of the retransmission timer, a buffer status report associated with the process ID and the channel group, the buffer status report indicating that uplink data is buffered at the UE for the channel group.
  • the flag manager 935 may set a flag indicator associated with the process ID based on the buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group.
  • FIG. 10 shows a diagram of a system 1000 including a device 1005 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the device 1005 may be an example of or include the components of device 705, device 805, or a UE 115 as described herein.
  • the device 1005 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a buffer status manager 1010, an I/O controller 1015, a transceiver 1020, an antenna 1025, memory 1030, and a processor 1040. These components may be in electronic communication via one or more buses (e.g., bus 1045) .
  • buses e.g., bus 1045
  • the buffer status manager 1010 may transmit, to a base station, an uplink message associated with a process ID and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group, receive, from the base station, a request for retransmission of the uplink message, and initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • the I/O controller 1015 may manage input and output signals for the device 1005.
  • the I/O controller 1015 may also manage peripherals not integrated into the device 1005.
  • the I/O controller 1015 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1015 may utilize an operating system such as or another known operating system.
  • the I/O controller 1015 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1015 may be implemented as part of a processor.
  • a user may interact with the device 1005 via the I/O controller 1015 or via hardware components controlled by the I/O controller 1015.
  • the transceiver 1020 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1020 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1020 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the device 1005 may include a single antenna 1025, or the device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1030 may include random access memory (RAM) and read only memory (ROM) .
  • the memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1030 may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the processor 1040 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (CPU) , a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1040 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1040.
  • the processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks supporting buffer status timer triggering) .
  • the code 1035 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1035 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • FIG. 11 shows a flowchart illustrating a method 1100 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the operations of method 1100 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1100 may be performed by a buffer status manager as described with reference to FIGs. 7 through 10.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may transmit, to a base station, an uplink message associated with a process ID and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group.
  • the operations of 1105 may be performed according to the methods described herein. In some examples, aspects of the operations of 1105 may be performed by an uplink message transmitter as described with reference to FIGs. 7 through 10.
  • the UE may receive, from the base station, a request for retransmission of the uplink message.
  • the operations of 1110 may be performed according to the methods described herein. In some examples, aspects of the operations of 1110 may be performed by a retransmission request receiver as described with reference to FIGs. 7 through 10.
  • the UE may initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • the operations of 1115 may be performed according to the methods described herein. In some examples, aspects of the operations of 1115 may be performed by a retransmission timer component as described with reference to FIGs. 7 through 10.
  • FIG. 12 shows a flowchart illustrating a method 1200 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the operations of method 1200 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1200 may be performed by a buffer status manager as described with reference to FIGs. 7 through 10.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may transmit, to a base station, an uplink message associated with a process ID and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group.
  • the operations of 1205 may be performed according to the methods described herein. In some examples, aspects of the operations of 1205 may be performed by an uplink message transmitter as described with reference to FIGs. 7 through 10.
  • the UE may receive, from the base station, a request for retransmission of the uplink message.
  • the operations of 1210 may be performed according to the methods described herein. In some examples, aspects of the operations of 1210 may be performed by a retransmission request receiver as described with reference to FIGs. 7 through 10.
  • the UE may identify that uplink data associated with the channel group is available for transmission to the base station after transmitting the uplink message.
  • the operations of 1215 may be performed according to the methods described herein. In some examples, aspects of the operations of 1215 may be performed by an uplink data manager as described with reference to FIGs. 7 through 10.
  • the UE may initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group and based on uplink data being available for transmission to the base station.
  • the operations of 1220 may be performed according to the methods described herein. In some examples, aspects of the operations of 1220 may be performed by a retransmission timer component as described with reference to FIGs. 7 through 10.
  • FIG. 13 shows a flowchart illustrating a method 1300 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the operations of method 1300 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1300 may be performed by a buffer status manager as described with reference to FIGs. 7 through 10.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may transmit, to a base station, an uplink message associated with a process ID and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group.
  • the operations of 1305 may be performed according to the methods described herein. In some examples, aspects of the operations of 1305 may be performed by an uplink message transmitter as described with reference to FIGs. 7 through 10.
  • the UE may receive, from the base station, a request for retransmission of the uplink message.
  • the operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be performed by a retransmission request receiver as described with reference to FIGs. 7 through 10.
  • the UE may identify that uplink data associated with the channel group is available for transmission to the base station before transmitting the uplink message.
  • the operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be performed by an uplink data manager as described with reference to FIGs. 7 through 10.
  • the UE may initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group.
  • the operations of 1320 may be performed according to the methods described herein. In some examples, aspects of the operations of 1320 may be performed by a retransmission timer component as described with reference to FIGs. 7 through 10.
  • the UE may transmit a second uplink message associated with a second process ID and the channel group, the second uplink message including a second buffer indicator for the channel group indicating that uplink data is buffered at the UE for the channel group.
  • the operations of 1325 may be performed according to the methods described herein. In some examples, aspects of the operations of 1325 may be performed by an uplink message transmitter as described with reference to FIGs. 7 through 10.
  • FIG. 14 shows a flowchart illustrating a method 1400 that supports buffer status timer triggering in accordance with aspects of the present disclosure.
  • the operations of method 1400 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1400 may be performed by a buffer status manager as described with reference to FIGs. 7 through 10.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may transmit, to a base station, an uplink message associated with a process ID and a channel group, the uplink message including a buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group.
  • the operations of 1405 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405 may be performed by an uplink message transmitter as described with reference to FIGs. 7 through 10.
  • the UE may set a flag indicator associated with the process ID based on the buffer indicator for the channel group indicating that no additional uplink data is buffered at the UE for the channel group.
  • the operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operations of 1410 may be performed by a flag manager as described with reference to FIGs. 7 through 10.
  • the UE may receive, from the base station, a request for retransmission of the uplink message.
  • the operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be performed by a retransmission request receiver as described with reference to FIGs. 7 through 10.
  • the UE may initiate a retransmission timer in response to receiving the request for retransmission of the uplink message based on the buffer indicator for the channel group indicating that no additional data is buffered at the UE for the channel group and based on a value of the flag indicator.
  • the operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operations of 1420 may be performed by a retransmission timer component as described with reference to FIGs. 7 through 10.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs de communication sans fil. Un équipement utilisateur (UE) en communication avec une station de base peut prendre en charge plusieurs temporisateurs pour des techniques de retransmission. Un premier temporisateur peut être déclenché lors de la transmission d'un rapport d'état de tampon (BSR) indiquant que des données de liaison montante sont disponibles pour une transmission au niveau de l'UE. Un temporisateur supplémentaire peut éventuellement être déclenché si l'UE indique qu'aucune donnée de liaison montante n'est disponible pour la transmission au niveau de l'UE et que l'UE reçoit ensuite une demande de retransmission pour le BSR. Le temporisateur de retransmission supplémentaire peut être de plus courte durée que le temporisateur de retransmission initial et, plutôt que d'attendre l'expiration du premier temporisateur, l'UE peut transmettre, à l'expiration du temporisateur supplémentaire, un autre BSR si l'UE n'a pas reçu d'autorisation de liaison montante pour la transmission de données de liaison montante disponibles.
PCT/CN2019/111660 2019-10-17 2019-10-17 Déclenchement de temporisateur d'état de tampon WO2021072701A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/111660 WO2021072701A1 (fr) 2019-10-17 2019-10-17 Déclenchement de temporisateur d'état de tampon

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/111660 WO2021072701A1 (fr) 2019-10-17 2019-10-17 Déclenchement de temporisateur d'état de tampon

Publications (1)

Publication Number Publication Date
WO2021072701A1 true WO2021072701A1 (fr) 2021-04-22

Family

ID=75537400

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/111660 WO2021072701A1 (fr) 2019-10-17 2019-10-17 Déclenchement de temporisateur d'état de tampon

Country Status (1)

Country Link
WO (1) WO2021072701A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115276919A (zh) * 2021-04-29 2022-11-01 维沃移动通信有限公司 上行传输方法、装置及终端

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016035988A1 (fr) * 2014-09-03 2016-03-10 Lg Electronics Inc. Procédé de configuration d'un nouveau temporisateur de retransmission de rapport d'état de tampon dans un système de communication d2d et dispositif associé
US20170155477A1 (en) * 2015-12-01 2017-06-01 Denso Corporation Communication device
CN107360591A (zh) * 2017-06-15 2017-11-17 电信科学技术研究院 一种上报缓存状态报告的方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016035988A1 (fr) * 2014-09-03 2016-03-10 Lg Electronics Inc. Procédé de configuration d'un nouveau temporisateur de retransmission de rapport d'état de tampon dans un système de communication d2d et dispositif associé
US20170155477A1 (en) * 2015-12-01 2017-06-01 Denso Corporation Communication device
CN107360591A (zh) * 2017-06-15 2017-11-17 电信科学技术研究院 一种上报缓存状态报告的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA SIEMENS NETWORKS: "Padding BSR and Empty Transmission Buffers", 3GPP DRAFT; R2-104307 PADDING BSR AND EMPTY BUFFERS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Madrid, Spain; 20100823, 17 August 2010 (2010-08-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP050451814 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115276919A (zh) * 2021-04-29 2022-11-01 维沃移动通信有限公司 上行传输方法、装置及终端
WO2022228328A1 (fr) * 2021-04-29 2022-11-03 维沃移动通信有限公司 Procédé et appareil de transmission en liaison montante, et terminal

Similar Documents

Publication Publication Date Title
US11838931B2 (en) Feedback of remaining delay budget
WO2022164891A2 (fr) Procédures multiples d'occasion de canal de rétroaction de liaison latérale
US11546933B2 (en) Cross carrier shared channel repetition
US11595982B2 (en) Intra-device collision handling
EP4169336A1 (fr) Priorisation de trafic de liaison montante à travers de multiples liaisons
US11870588B2 (en) Feedback process reuse in wireless communications
US11889327B2 (en) Network coding with dynamic redundancy overhead
WO2021072701A1 (fr) Déclenchement de temporisateur d'état de tampon
WO2021196064A1 (fr) Rétroaction pour des informations de commande de liaison descendante unique à une planification multi-cellule
EP4158827A1 (fr) Synchronisation pour l'ordonnancement croisé et le déclenchement d'un signal de référence
EP4150806A1 (fr) Adaptation de liaison lors d'une détermination de blocage de faisceau
US11490419B2 (en) Contention window updates with integrated access and backhaul nodes for unlicensed operations
WO2022170613A1 (fr) Transmissions d'accusé de réception négatif pendant des problèmes de couche physique
US11792802B2 (en) Uplink shared channel feedback piggybacking
US12004193B2 (en) Intra-device collision handling
US11778590B2 (en) Techniques for selecting a sidelink sensing mode based on duplex mode
US11716732B2 (en) Feedback configuration for uplink control messages
WO2022147636A1 (fr) Activation et désactivation de ressources pour différents modes de duplexage
WO2022051968A1 (fr) Techniques d'indication d'état de ressource de rétroaction pour communications sans fil
US20220303880A1 (en) Search space set group switching for cross-carrier scheduling
WO2022151015A1 (fr) Surveillance de canal de commande réduite pour des procédures d'accès aléatoire
EP4378095A1 (fr) Décodage de débit de données pour blocs de transport
WO2022198223A1 (fr) Commutation de groupes d'ensembles d'espaces de recherche pour une planification inter-porteuses
CN116964979A (zh) 用于跨载波调度的搜索空间集组切换

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

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

Country of ref document: EP

Kind code of ref document: A1