BSR enhancements for xr applications

Abstract

A method and apparatus for BSR enhancement. The apparatus receives, from a network entity, a buffer state table configuration indicating one or more BSR tables, wherein the one or more BSR tables are predefined at the UE or configurable by the UE based on the buffer state table configuration. The apparatus communicates with the network entity based on a first BSR table from the one or more BSR tables. The apparatus may generate one or more BSR tables based on parameters received in the buffer state table configuration. The apparatus may receive additional control signaling indicating at least one BSR table from a set of BSR tables configured for the UE. The apparatus may send an indication to report a selected BSR table of the plurality of BSR tables, wherein the selected BSR table includes the first BSR table.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 499,464, entitled “BSR Enhancements For XR Applications” and filed on May 1, 2023, and U.S. Non-Provisional Patent Application Serial No. 18 / 583,788, entitled “BSR ENHANCEMENTS FOR XR APPLICATIONS” and filed on February 21, 2024, which are expressly incorporated by reference herein in their entirety. TECHNICAL FIELD

[0003] The present disclosure relates generally to communication systems, and more particularly, to configurations for buffer status reporting (BSR) enhancements, particularly from extended reality (XR) applications. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. One example of a telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. 5G NR is SUMMARY

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. It is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0007] In an aspect of the disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus can be a device at a UE. The device can be a processor and / or a modem at the UE or the UE itself. The apparatus receives, from a network entity, a buffer status table configuration indicating one or more buffer status report (BSR) tables. The apparatus communicates with the network entity based on a first BSR table from the one or more BSR tables.

[0008] In an aspect of the disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus can be a device at a network node. The device can be a processor and / or a modem at the network node or the network node itself. The apparatus provides, to a user equipment (UE), a buffer status table configuration indicating one or more buffer status report (BSR) tables. The apparatus communicates with the UE based on a first BSR table from the one or more BSR tables.

[0009] To the accomplishment of the foregoing and related aspects, one or more aspects comprise the features as broadly indicated herein above and specifically described below. The following description and drawings are illustrative of the various aspects and do not limit the scope of the aspects. The aspects can be better understood and readily apparent to those skilled in the art from the following detailed description, from the claims, and from the appended drawings. BRIEF DESCRIPTION OF DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe, in accordance with various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of an uplink (UL) channel within a subframe, in accordance with various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0016] Figure 4 An example of an XR flow including an XR traffic burst is illustrated.

[0017] Figure 5 is a call flow diagram of signaling between a UE and a base station.

[0018] Figure 6 is a flow diagram of a method of wireless communication.

[0019] Figure 7 is a flow diagram of a method of wireless communication.

[0020] Figure 8 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity.

[0021] Figure 9 is a flow diagram of a method of wireless communication.

[0022] Figure 10 is a flow diagram of a method of wireless communication.

[0023] Figure 11 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0024] In wireless communications, a BSR table can be configured for all applications. The BSR table has a range that covers all possible buffer sizes, with the maximum size based on the size of the largest transport block possible on the communication link. Some applications, such as but not limited to XR applications or applications encoded at high resolution, can have large data bursts and can have strict latency requirements. The network can utilize an increased amount of uplink grants to reduce scheduling latency so that buffered data can be scheduled with the least amount of transmission possible. In some instances, when the uplink grants are larger or include an increased amount, the BSR codepoint can experience an increase in quantization error. However, such errors can reduce system capacity. At least one solution to address this issue is to introduce a new BSR table with less quantization error.

[0025] Aspects presented herein provide configurations for BSR enhancements. For example, a UE can receive a buffer status configuration including one or more BSR tables, such that the UE can utilize one of the one or more BSR tables based on an amount of buffered data at the UE. At least one advantage of the present disclosure is that the one or more BSR tables can include a range that matches or is similar to the UE buffered data.

[0026] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0027] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0028] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic devices, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0029] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As examples, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0030] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0031] Deployment of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, network entity, mobility element of a network, radio access network (RAN) node, core network node, network element, or network equipment, such as a base station (BS), or one or more units (or one or more components) that perform base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a BS, such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmission reception point (TRP), or a cell, etc., can be implemented as an aggregated base station (also referred to as a standalone BS or a monolithic BS) or a disaggregated base station.

[0032] An aggregated base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station can be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operations or network designs can take into account the aggregated nature of base station functionality. For example, a disaggregated base station can be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which can enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0034] Figure 1is a diagram 100 illustrating examples of a wireless communication system and access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture can include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-RT RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CUs 110 can communicate with one or more DUs 130 via respective fronthaul links, such as an Fl interface. The DUs 130 can communicate with one or more RUs 140 via respective front-haul links. The RUs 140 can communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 can be simultaneously served by multiple RUs 140.

[0035] Each of the units (i.e., the CUs 110, the DUs 130, the RUs 140, and the near-RT RIC 125, the non-RT RIC 115, and the SMO framework 105) can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller providing instructions to the communication interfaces of these units can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include wired interfaces configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units can include wireless interfaces that can include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive and / or transmit signals to one or more of the other units over a wireless transmission medium.

[0036] In some aspects, the CU 110 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and / or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bi-directionally with the CU-CP units via an interface, such as an El interface. The CU 110 can be implemented to communicate with the DUs 130 as needed for network control and signaling.

[0037] The DU 130 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, the DU 130 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and / or the like) in accordance with, at least in part, a functional split, such as those defined by 3GPP. In some aspects, the DU 130 can further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0038] The lower layer functionality can be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 can correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, and / or the like) or both based, at least in part, on a functional split, such as a lower layer functional split. In such an architecture, the RUs 140 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DUs 130 and the CUs 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0039] The SMO framework 105 can be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non- virtualized network elements, the SMO framework 105 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform, such as Open Cloud (O-Cloud) 190, to perform network element lifecycle management, such as to instantiate a virtualized network element, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140, and near-RT RICs 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of a 4G RAN, such as Open eNB (O-eNB) 111, via an Ol interface. Additionally, in some implementations, the SMO framework 105 can communicate directly with one or more RUs 140 via an Ol interface. The SMO framework 105 can also include a non-RT RIC 115 configured to support functionality of the SMO framework 105.

[0040] The non-RT RIC 115 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updates, or policy-based direction of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or in communication with the near-RT RIC 125, such as via an Al interface. The near-RT RIC 125 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface, such as via an E2 interface, that connects one or more CUs 110, one or more DUs 130, or both, and an O-eNB with the near-RT RIC 125.

[0041] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external rich information from an external server. Such information can be utilized by the near-RT RIC 125 and can be received at the SMO framework 105 or the non-RT RIC 115 from non-network data sources or from network functions. In some examples, the non-RT RIC 115 or the near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105, such as via reconfiguration of Ol, or via creation of RAN management policies, such as Al policies.

[0042] At least one of the CU 110, the DU 130, and the RU 140 can be referred to as a base station 102. Thus, a base station 102 can include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated with a dashed line to represent that each component can or can not be included in the base station 102). The base station 102 provides an access point to a core network 120 for a UE 104. The base station 102 can include a macro cell (high power cellular base station) and / or a small cell (low power cellular base station). Small cells include femto cells, pico cells, and micro cells. Networks that include both small cells and macro cells can be referred to as heterogeneous networks. A heterogeneous network can also include home evolved node Bs (eNBs) (HeNBs), which can provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 can include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from a RU 140 to a UE 104. The communication links can use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links can be through one or more carriers, where a carrier can be a set of resource blocks (e.g., of time and frequency) that can be used for transmitting data. Each carrier can be on a different frequency. Additional carriers can be added above and / or below this set of carriers. The carriers can or can not be contiguous. The carriers can or can not span the same frequency range. The carriers can or can not be used for the same technical

[0043] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 can use the DL / UL WWAN spectrum. The D2D communication links 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication can be through a variety of wireless D2D communications systems, such as for example, Bluetooth ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR. ™

[0044] The wireless communications system can also include a Wi-Fi AP 150 in communication with UEs 104 (also known as Wi-Fi stations (STAs)) via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 / AP 150 can perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0045] The electromagnetic spectrum is often subdivided based on frequency / wavelength into various classes, bands, channels, and so on. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Despite a portion of FR1 being greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a “millimeter wave” band in documents and articles, despite such a band being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is designated as a “millimeter wave” band by the International Telecommunications Union (ITU).

[0046] ​The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Bands that fall within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Moreover, higher bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0047] With the above in mind, unless specifically stated otherwise, if the term “sub-6 GHz” or like term is used herein, this can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, if the term “millimeter wave” or like term is used herein, this can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0048] The base stations 102 and the UEs 104 can each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base stations 102 can transmit to UEs 104 in one or more transmit directions 186 on the downlink 104. The UEs 104 can transmit to the base stations 102 in one or more transmit directions 188 on the uplink 106. The base stations 102 / UEs 104 can perform beam training to determine the best receive and transmit directions for each of the base stations 102 / UEs 104. The transmit and receive directions for the base stations 102 can or can not be the same. The transmit and receive directions for the UEs 104 can or can not be the same.

[0049] The base stations 102 can include and / or be referred to as gNBs, NodeBs, eNBs, access points, base transceiver stations, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), TRPs, network nodes, network entities, network equipment, or some other suitable terminology. The base stations 102 can be implemented as integrated access and backhaul (IAB) nodes, relay nodes, sidelink nodes, aggregated (monolithic) base stations with baseband units (BBUs) including CUs and DUs and RUs, or as disaggregated base stations including one or more of CUs, DUs, and / or RUs. A collection of base stations that can include disaggregated base stations and / or aggregated base stations can be referred to as a next generation (NG) RAN (NG-RAN).

[0050] The core network 120 can include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 can include one or more location / determination servers, which can include one or more of a GMLC 165, an LMF 166, a positioning determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), and the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute a position of the UE 104. The NG-RAN can utilize one or more positioning methods to determine a position of the UE 104. Positioning the UE 104 can involve signal measurements, position estimation, and optional velocity calculations based on these measurements. The signal measurements can be made by the UE 104 and / or the base stations 102 serving the UE 104. The measured signals can be based on one or more of a satellite positioning system (SPS) 170 (e.g., Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or other satellite positioning / location system), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensors, motion sensors), NR Enhanced Cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0051] Examples of a UE 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functional device. Some of the UEs 104 can be referred to as IoT devices (e.g., a parking meter, gas pump, toaster, vehicle, heart monitor, etc.). The UE 104 can also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE can also apply to one or more accessory devices such as in a device constellation arrangement. One or more of these devices can collectively or individually access a network and / or access the network.

[0052] Referring again to Figure 1 In certain aspects, the UE 104 can include a configuration component 198 configured to receive, from a network entity, a buffer status table configuration indicating one or more BSR tables; and communicate with the network entity based on a first BSR table from the one or more BSR tables.

[0053] Referring again to Figure 1 In certain aspects, the base station 102 can include a configuration component 199 configured to provide, to a UE, a buffer status table configuration indicating one or more BSR tables; and communicate with the UE based on a first BSR table from the one or more BSR tables.

[0054] While the following description can focus on 5G NR, the concepts described herein can be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0055] Figure 2A FIG. 200 is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG. 230 is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG. 250 is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Figure 2Dis a diagram 280 illustrating an example of UL channels in a 5G NR subframe. The 5G NR frame structure can be a frequency division duplex (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes are dedicated for DL or UL, or can be a time division duplex (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes are dedicated for both DL and UL. In the examples provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible that can be used between DL / UL, and subframe 3 is configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with a slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the following description applies to 5G NR frame structures that are TDD as well. Figure 2A 、 Figure 2C In the examples provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible that can be used between DL / UL, and subframe 3 is configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with a slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the following description applies to 5G NR frame structures that are TDD as well.

[0056] Figures 2A to 2D The frame structure is illustrated, and aspects of the present disclosure can be applicable to other wireless communication technologies that can have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini-slots, which can include 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols, depending on whether a cyclic prefix (CP) is normal or extended. For a normal CP, each slot can include 14 symbols, and for an extended CP, each slot can include 12 symbols. Symbols on the DL can be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see TABLE 1). The symbol length / duration is scalable with 1 / SCS.

[0057]

[0058] Table 1: Numerology, SCS and CP

[0059] For normal CP (14 symbols / slot), different numerologies µ 0 to 4 allow for 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, numerology 2 allows for 4 slots per subframe. Thus, for normal CP and numerology µ, there are 14 symbols / slot and 2 µ slots / subframe. The subcarrier spacing can equal where is the numerology 0 to 4. Thus, the subcarrier spacing for numerology µ = 0 is 15 kHz, and the subcarrier spacing for numerology µ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D An example is provided for normal CP with 14 symbols per slot and numerology µ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μβ. Within a frame collection, there can be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP can have a particular numerology and CP (normal or extended).

[0060] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0061] As illustrated in Figure 2A , some of the REs carry reference (pilot) signals (RS) for the UE. The RS can include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0062] Figure 2BExamples of various DL channels are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP can be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH search space (e.g., common search space, UE-specific search space) for PDCCH candidates during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies of the channel bandwidth. A primary synchronization signal (PSS) can be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) can be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)), and paging messages.

[0063] As Figure 2C illustrated, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols of a slot. The PUCCH DM-RS can be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE can transmit sounding reference signals (SRS). The SRS can be transmitted in the last symbol(s) of a slot. The SRS can have a comb-2 structure, and a UE can transmit SRS on one of the combs. The SRS can be used by a base station for channel quality estimation to enable frequency-dependent scheduling for the UL.

[0064] Figure 2DExamples of various UL channels within a subframe are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data, and can additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0065] Figure 3 is a block diagram of the components of base station 310 and UE 350, which can be used in the access network. In the DL, IP packets from the core network are provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration and reporting for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams if multiple spatial streams are used. Channel estimates from a channel estimator 374 can be used to determine the beamforming

[0067] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions can be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0068] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 can be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0069] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0070] The TX processor 368 can use channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 are provided to the different antenna 352 via separate transmitters 354. Each transmitter 354 modulates an RF carrier with a respective spatial stream for transmission.

[0071] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318 receives a signal through its respective antenna 320. Each receiver 318 recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0072] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 can be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the core network. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0073] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform coupling. Figure 1 The configuration components of 198 are in various aspects.

[0074] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform coupling. Figure 1 The configuration components of 199 are in various aspects.

[0075] Wireless communication can include various types of services. Among other examples of service types, wireless communication systems can support extended reality (XR) services. XR services can refer to wireless communication used for technologies such as virtual reality (VR), mixed reality (MR), and / or augmented reality (AR). VR can refer to technology that immerses users in a simulated experience similar to or different from the real world. Users can interact with VR systems through VR headsets or multi-projection environments that generate realistic images, sounds, and other sensations that simulate the user's physical presence in the virtual environment. MR can refer to technology in which aspects of virtual and real environments are mixed. AR can refer to technology in which computer-generated perceptual information is used to augment objects residing in the real world (sometimes across multiple sensory modalities such as vision, hearing, touch, somatosensory, and / or olfaction). AR systems can combine the real and virtual worlds, real-time interaction, and accurate 3D registration of virtual and real objects. In examples, AR systems can overlay sensory information (e.g., images) onto and / or mask real objects from the natural environment. XR services can include video and / or audio data. XR services can be sent by the base station and received by the UE, or XR services can be sent by the UE and received by the base station.

[0076] XR services can arrive in periodic service bursts (“XR service bursts”). XR service bursts can vary in terms of the number of packets in each burst and / or the size of each packet in a burst. Figure 4 Figure 400 illustrates a first XR stream 402 including a first XR service burst 404 and a second XR service burst 406. As illustrated in Figure 400, the service bursts may include different numbers of packets; for example, the first XR service burst 404 is shown as having three packets (represented as rectangles in Figure 400), and the second XR service burst 406 is shown as having two packets. Furthermore, as illustrated in Figure 400, the three packets in the first XR service burst 404 and the two packets in the second XR service burst 406 may differ in size; that is, the packets within the first XR service burst 404 and the second XR service burst 406 may include different amounts of data.

[0077] XR traffic bursts can arrive in non-integer periods (i.e., in non-integer cycles). The period can differ from an integer number of symbols, slots, etc. In an example, for 60 frames per second (FPS) video data, XR traffic bursts can arrive in a 1 / 60 = 16.67 ms period. In another example, for 120 FPS video data, XR traffic bursts can arrive in a 1 / 120 = 8.33 ms period.

[0078] The arrival time of XR traffic can vary. For example, an XR traffic burst can arrive and be available for transmission at an earlier or later time than the UE (or base station) expects the XR traffic burst. The variability of packet arrival relative to a period (e.g., a 16.76 ms period, an 8.33 ms period, etc.) can be referred to as “jitter.” In an example, the jitter of XR traffic can range from -4 ms (earlier than expected arrival) to +4 ms (later than expected arrival). For example, referring to the first XR stream 402, the UE can expect the first packet of the first XR traffic burst 404 to arrive at time tO, but the first packet of the first XR traffic burst 404 arrives at time ti.

[0079] XR traffic can include multiple streams that arrive at the UE (or base station) concurrently (or within a threshold period of time) with each other. For example, the diagram 400 includes a second XR stream 408. The second XR stream 408 can have different characteristics than the first XR stream 402. For example, the second XR stream 408 can have XR traffic bursts with a different number of packets, different sizes of packets, etc. In one example, the first XR stream 402 can include video data, and the second XR stream 408 can include audio data for the video data. In another example, the first XR stream 402 can include intra-coded picture frames (I-frames) that contain complete images, and the second XR stream 408 can include picture frames (P-frames) that contain predictions of changes from previous images.

[0080] As described herein, XR traffic can have an associated e2e PDB. If a packet does not arrive within the e2e PDB, the UE (or base station) can discard the packet. In an example, if a packet corresponding to a video frame of a video does not arrive at the UE within the e2e PDB, the UE can discard the packet because the video has progressed beyond the frame. However, the RDB at the UE can not be considered in light of discarding the packet. An example time diagram 450 illustrates a length of time corresponding to a PDB 454. At a particular point in time 456, a residual delay budget 452 is the remaining portion of the PDB 454.

[0081] The XR traffic overall PDB can include a portion for a communication delay (e2e PDB) of data between a UE and a computing device (e.g., a server) hosting an application (e.g., for XR), and a portion for additional time (e.g., residual delay (e.g., RDB)) after the communication delay before the data is discarded. For example, the diagram 400 includes a packet delay budget flow 410. The packet delay budget flow 410 illustrates a UE 412, a network entity 414, and a server 416 hosting an application 418. In the illustrated aspect, a communication delay 420 is shown to include a RAN portion between the UE 502 and the network entity 414, and a CN portion between the network entity 414 and the server 416. The communication delay 420 can apply to both UL and DL communications. Additionally, a residual delay 422 is shown at the UE 412 for DL communications, and a residual delay 424 is shown at the server 416 for UL communications. The communication delay 420 and the residual delay 422 can constitute an overall PDB for DL XR communications, e.g., a DL PDB 426. Likewise, the communication delay 420 and the residual delay 424 can constitute an overall PDB for UL XR communications (not shown for clarity of illustration).

[0082] Generally, XR traffic can be characterized by a relatively high data rate and a relatively low latency. Latency in XR traffic can impact user experience. For example, XR traffic can be applied in eMBB and URLLC services.

[0083] Various aspects can be employed to provide power savings and / or capacity improvements for wireless communications (e.g., including XR traffic). A scheduling mechanism, such as semi-persistent scheduling (SPS) or configured grant (CG), can be used to provide periodic resources for UL or DL communications that can be used without dynamic grant of resources. Some types of wireless communication systems can employ dynamic grants for scheduling purposes to accommodate traffic (e.g., XR traffic). In dynamic grants, a scheduler (e.g., such as a network entity) can use control signaling to allocate resources (e.g., grants of UL or DL resources) for transmission or reception at a UE. Dynamic grants can be flexible and can accommodate changes in traffic behavior. CGs can provide periodic or semi-static resources that a UE can use to transmit or receive communications without receiving a separate grant. For example, a UE can receive a configured grant in an RRC configuration. The UE can then transmit and / or receive using the granted resources without additional DCI. In some aspects, a UE can receive a MAC-CE that activates a previously configured CG. For dynamic grant based wireless communications, a UE can monitor a PDCCH including a DCI that schedules (e.g., allocates specific resources to) the UE to transmit or receive communications with a base station (e.g., instructions to receive data on a PDSCH). In some aspects, such as when a UE has data to transmit, the UE can transmit a scheduling request to a network entity to trigger the network entity to allocate resources for transmission, such as in a DCI. Various aspects also provide for dynamic grant (DG) of resources requested by a UE for UL communications (e.g., reporting measured delay statistics). SPS or CG scheduling can be configured to accommodate periodic traffic, multiple streams, jitter, latency, and reliability for wireless traffic and can improve capacity and / or latency for such wireless communications. DG requests / grants can similarly accommodate multiple streams, jitter, latency, and reliability of wireless traffic and can improve capacity and / or latency for such wireless communications for urgent reporting of measured delay statistics and / or for reporting measured delay statistics in cases where CG or other uplink resources are not available. By way of example, traffic bursts, such as XR bursts, are periodic and can include some time jitter in arrival.

[0084] In wireless communications, BSR tables are configured for all applications. The BSR tables have a range that covers all possible buffer sizes, with the maximum size based on the size of the largest transport block possible on the communication link. In some instances, the size range can be quantized to 256 codepoints, with the step size between two consecutive codepoints exponentially increasing.

[0085] In some applications, such as but not limited to XR applications or applications coded at high resolutions, there can be large data bursts. Some applications can have strict latency requirements. The network can utilize an increased amount of uplink grants to reduce scheduling latency so that buffered data can be scheduled with the least amount of transmission possible. In some instances, when the uplink grant is larger or includes an increased amount, the BSR codepoint can experience an increase in quantization error. However, such errors can reduce system capacity. At least one solution to address this issue is to introduce new BSR tables with less quantization error.

[0086] Aspects presented herein provide configurations for BSR enhancements. For example, a UE can receive a buffer status configuration including one or more BSR tables so that the UE can utilize one of the one or more BSR tables based on an amount of buffered data at the UE. At least one advantage of the present disclosure is that the one or more BSR tables can include ranges that match or are similar to the UE buffered data.

[0087] In some instances, such as for example XR traffic, the size range of the UE buffered data can be determined by the size range of a video frame, which can in turn be known in advance once the corresponding encoding rate and frame rate are known. For example, if an XR application applies a codec with 4K resolution and produces a bit rate in the range of 20Mbps-150Mbps. Then with 60 frames per second (fps), the size range of the video frame can be 41KB-321KB. At 90fps, the corresponding size range of the video frame can be 28KB-208KB. Thus, the buffer status configuration can include two BSR tables based on these two ranges. In some instances, the buffer status configuration can include a BSR table that covers both ranges (e.g., 28KB-321KB).

[0088] Examples of known encoding rates and frame rates that can be supported can include HD, 4K, 8K for encoding rate, and 24fps, 25fps, 30fps, 50fps, 60fps, 90fps, and 120fps for frame rate. As such examples, up to 3x7=21 BSR tables can be included in the buffer status configuration. Some frame rates can be very close (e.g., 24fps, 25fps, and 30fps, or 50fps and 60fps) so that they can be covered by a single BSR table. Thus, the actual number of BSR tables in the buffer status configuration can be less (e.g., 12).

[0089] In some instances, each codepoint in each BSR table in the specification can or can not be designated. This is possible, in part, because all codepoints in a BSR table are designated based on four parameters: a minimum buffer size, a maximum buffer size, a total number of codepoints, and whether the step size is linear or exponential. Thus, a BSR table can be based on one or more of the four parameters.

[0090] In some instances, a pre-defined BSR table can be preferable to an RRC configured BSR table because the UE does not need to generate the BSR table on demand, which would result in reduced UE vendor implementation and testing efforts. Thus, at least some BSR tables can be pre-defined in the buffer status configuration. However, a pre-defined table can not be forward compatible or future facing. Moreover, a network / operator can want greater flexibility in the range and encoding of the BSR table, such as to handle unusual encoding rates that result in data bursts that are not well covered by a pre-defined BSR table due to specific XR application usage. Thus, it can also be beneficial to allow the network to configure the BSR table on demand. This on-demand BSR table can be generated by the UE based on parameters provided by the network in the buffer status configuration. In some aspects, the network can use an RRC message (e.g., dedicated signaling) to configure the UE with one or more of the parameters. In some aspects, the network can broadcast one or more parameters for a set of BSR tables via system information. The network can indicate to the UE which BSR table(s) to use with dedicated signaling.

[0091] In some instances, if a BSR table is generated on demand based on parameters provided by the network, the parameters and formulas used in their computation can be configured to produce the same results in different UE implementations. For example, a UE can apply a formula to generate a BSR table.

[0092] B k = B min ·(1+p) k , where p = (B max / B min ) 1 / (N-1) – 1,

[0093] and the network specifies B min and B max , then the UE can compute p, which involves division and the Nth root of a fraction. If different UE implementations have different floating point precisions in those computations, they can produce different codepoints for the table. The parameters configured by the network and the generating formula to be specified can be defined in a way that does not have this implementation dependency. For example, the generating formula can use addition and multiplication and avoid division and other arithmetic operations. For example, the network can signal B minand a step size factor p. Depending on the range of the BSR table, the codepoints can be generated based on a linear function or an exponential function. For example, if the range of the table is relatively small and a linear step can provide sufficient quantization accuracy, an equal step size between two consecutive codepoints can be specified. Otherwise, an exponentially spaced step size can provide lower quantization error.

[0094] If the network indicates that the step size is linear, the buffer size B k : B1 = B min , and B k = B k-1 + floor(B min x p), where k = 2,..., N.

[0095] If the network indicates that the step size is exponential, the buffer size B k : B1 = B min , and B k = B k-1 + floor(B k-1 x p), where k = 2,..., N.

[0096] In some aspects, a UE can be configured to generate a new BSR table based on a reference BSR table and a scaling / adjustment parameter. The reference BSR table can be configurable or pre-configured. The scaling / adjustment can be provided by the network (e.g., RRC configuration). In some instances, after a UE changes its coding rate or its frame rate, the network can signal the UE an adjustment or scaling parameter. The UE can utilize the adjustment or scaling parameter to derive the actual BSR table that the UE should use. For example, if the kth codepoint in the reference BSR table is B ref_k , and the adjustment or scaling parameter is p adj , the actual BSR value for the kth codepoint can be derived based on B ref_k x p adj . The determination of the kth codepoint based on B ref_k and p adj may be used in instances where the minimum range and / or maximum range of data burst scales linearly with the UE coding rate and / or frame rate.

[0097] It can be beneficial to use different BSR tables for different logical channel groups (LCGs) to take full advantage of the best range / resolution that all tables can provide. Thus, the network can configure a particular BSR from one or more BSR tables that the LCG can use to encode and report its buffer size.

[0098] In some aspects, a BSR table can have a shorter range than an existing BSR table, otherwise the resolution of the BSR table can not be higher with the same number of encoding points. Thus, an LCG can use both the BSR table from the buffer status configuration and the existing BSR table based on the UE buffer size. More specifically, if the buffer size is within the range of the BSR table, the UE can utilize the BSR table from the buffer status configuration, otherwise the existing BSR table can be used.

[0099] Figure 5 is a call flow diagram 500 of signaling between a UE 502 and a base station 504. The base station 504 can be configured to provide at least one cell. The UE 502 can be configured to communicate with the base station 504. For example, in Figure 1 In the context of FIG. 1, the base station 504 can correspond to the base station 102 and the UE 502 can correspond to at least the UE 104. In another example, in Figure 3 In the context of FIG. 3, the base station 504 can correspond to the base station 310 and the UE 502 can correspond to the UE 350.

[0100] At 506, the base station 504 can provide a buffer status table configuration indicating one or more BSR tables. The network entity can provide the buffer status table configuration to the UE 502. The UE 502 can receive the buffer status table configuration from the base station 504. In some aspects, the buffer status table configuration can indicate one or more BSR tables from a set of defined BSR tables. In some aspects, the buffer status table configuration can configure at least one parameter for the one or more BSR tables. The buffer status table configuration can configure at least one parameter for each of the one or more BSR tables, which can include at least one of: a minimum buffer size, a maximum buffer size, a step size factor, or a step size type. In some aspects, the one or more BSR tables can include at least one of: a different minimum buffer size, a different maximum buffer size, a different step size factor, or a different step size type. In some aspects, the buffer status table configuration can be included within radio resource control (RRC) signaling or system information (SI).

[0101] At 508, the base station 504 can provide additional control signaling indicating at least one BSR table from a set of BSR tables configured for the UE 502. The UE 502 can receive the additional control signaling from the base station 504 indicating the at least one BSR table. In some aspects, the buffer status table configuration can indicate a set of BSR tables for the UE. In such instances, the additional control signal can indicate at least one BSR table from the set of BSR tables for the UE to use.

[0102] At 510, the UE 502 can generate one or more BSR tables. The UE can generate the one or more BSR tables based on parameters received in the buffer status table configuration. In some aspects, the parameters received in the buffer status table configuration can include adjustment or scaling parameters. In such instances, the UE can generate the one or more BSR tables based on the adjustment or scaling parameters and a reference BSR table. The reference BSR table can be configurable or can be preconfigured within the UE.

[0103] At 512, the UE 502 can transmit an indication reporting a selected BSR table from the multiple BSR tables. The UE can transmit the indication reporting the selected BSR table to the base station 504. The base station 504 can obtain the indication reporting the selected BSR table from the UE 502. In some aspects, the buffer status table configuration can indicate multiple BSR tables for the UE. The UE can select a BSR table from the multiple BSR tables. In some aspects, the selected BSR table can include the first BSR table. The UE can use the selected BSR table to look up a codepoint for an amount of data in its buffer. The UE can provide the codepoint to the base station in a BSR. The base station can use the BSR table to decode the codepoint received from the UE, such that the base station is informed of the amount of data that the UE wants to send to the base station.

[0104] At 514, the UE 502 and the base station 504 can communicate with each other based on the BSR table. In some aspects, the UE and the base station can communicate with each other based on the first BSR table selected by the UE from the one or more BSR tables. In some aspects, the communication with the network entity based on the first BSR table can include transmitting a BSR to the network entity using a codepoint corresponding to an amount of buffered data and an entry in the first BSR table. The base station can obtain the BSR from the UE.

[0105] Figure 6 FIG. 6 is a flow diagram of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104; the apparatus 804). One or more of the illustrated operations can be omitted, transposed, or combined. The method can configure the UE with one or more BSR tables.

[0106] At 602, the UE can receive a buffer status table configuration indicating one or more BSR tables. For example, 602 can be performed by configuration component 198 of apparatus 804. The UE can receive the buffer status table configuration from a network entity. In some aspects, the buffer status table configuration can indicate one or more BSR tables from a set of defined BSR tables. In some aspects, the buffer status table configuration can configure at least one parameter for the one or more BSR tables. The buffer status table configuration can configure at least one parameter for each of the one or more BSR tables, which can include at least one of: a minimum buffer size, a maximum buffer size, a step size factor, or a step size type. In some aspects, the one or more BSR tables can include at least one of: a different minimum buffer size, a different maximum buffer size, a different step size factor, or a different step size type. In some aspects, the buffer status table configuration can be included within RRC signaling or SI.

[0107] At 604, the UE can communicate with the network entity. For example, 604 can be performed by configuration component 198 of apparatus 804. The UE can communicate with the network entity based on a first BSR table from the one or more BSR tables. In some aspects, the communication with the network entity based on the first BSR table can include transmitting a BSR to the network entity using a codepoint corresponding to a quantity of buffered data and an entry in the first BSR table.

[0108] Figure 7 is a flow diagram of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104; the apparatus 804). One or more of the illustrated operations can be omitted, transposed, or combined. The method can configure a UE with one or more BSR tables.

[0109] At 702, the UE can receive a buffer status table configuration indicating one or more BSR tables. For example, 702 can be performed by configuration component 198 of apparatus 804. The UE can receive the buffer status table configuration from a network entity. In some aspects, the buffer status table configuration can indicate one or more BSR tables from a set of defined BSR tables. In some aspects, the buffer status table configuration can configure at least one parameter for the one or more BSR tables. The buffer status table configuration can configure at least one parameter for each of the one or more BSR tables, which can include at least one of: a minimum buffer size, a maximum buffer size, a step size factor, or a step size type. In some aspects, the one or more BSR tables can include at least one of: a different minimum buffer size, a different maximum buffer size, a different step size factor, or a different step size type. In some aspects, the buffer status table configuration can be included within RRC signaling or SI.

[0110] At 704, the UE can receive additional control signaling. For example, 704 can be performed by configuration component 198 of apparatus 804. The UE can receive the additional control signaling indicating at least one BSR table from a set of BSR tables configured for the UE. In some aspects, the buffer status table configuration can indicate the set of BSR tables for the UE. In such instances, the additional control signaling can indicate at least one BSR table from the set of BSR tables for the UE to use.

[0111] At 706, the UE can generate one or more BSR tables. For example, 706 can be performed by configuration component 198 of apparatus 804. The UE can generate the one or more BSR tables based on parameters received in the buffer status table configuration. In some aspects, the parameters received in the buffer status table configuration can include adjustment or scaling parameters. In such instances, the UE can generate the one or more BSR tables based on the adjustment or scaling parameters and a reference BSR table. The reference BSR table can be configurable or can be preconfigured within the UE.

[0112] At 708, the UE can transmit an indication reporting a selected BSR table. For example, 708 can be performed by configuration component 198 of apparatus 804. The UE can transmit an indication reporting a selected BSR table of the plurality of BSR tables. In some aspects, the buffer status table configuration can indicate a plurality of BSR tables for the UE. The UE can select the BSR table from the plurality of BSR tables. In some aspects, the selected BSR table can include a first BSR table.

[0113] At 710, the UE can communicate with a network entity. For example, 710 can be performed by configuration component 198 of apparatus 804. The UE can communicate with the network entity based on a first BSR table from the one or more BSR tables. In some aspects, the communication with the network entity based on the first BSR table can include transmitting a BSR to the network entity using a codepoint corresponding to an amount of buffered data and an entry in the first BSR table.

[0114] Figure 8is a diagram 800 illustrating an example of a hardware implementation for an apparatus 804. The apparatus 804 can be a UE, a component of a UE, or can implement UE functionality. In some aspects, the apparatus 804 can include at least one cellular baseband processor 824 (also referred to as a modem) coupled with one or more transceivers 822 (e.g., a cellular RF transceiver). The cellular baseband processor 824 can include at least one on-chip memory 824’. In some aspects, the apparatus 804 can also include one or more subscriber identity modules (SIM) cards 820, and at least one application processor 806 coupled with a secure digital (SD) card 808 and a screen 810. The application processor 806 can include on-chip memory 806’. In some aspects, the apparatus 804 can also include a Bluetooth module 812, a WLAN module 814, a SPS module 816 (e.g., a GNSS module), one or more sensor modules 818 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technology for positioning), an additional memory module 826, a power source 830, and / or a camera 832. The Bluetooth module 812, the WLAN module 814, and the SPS module 816 can include on-chip transceivers (TRXs) (or in some cases, only receivers (RXs)). The Bluetooth module 812, the WLAN module 814, and the SPS module 816 can include their own dedicated antennas and / or communicate using the antennas 880. The cellular baseband processor 824 communicates with the UE 104 and / or with a RU associated with the network entity 802 via the transceiver 822 by way of the one or more antennas 880. The cellular baseband processor 824 and the application processor 806 can each include computer-readable media / memory 824’, 806’, respectively. The additional memory module 826 can also be considered a computer-readable medium / memory. Each computer-readable medium / memory 824’, 806’, 826 can be non-transitory. The cellular baseband processor 824 and the application processor 806 are configured to perform the various functions described above with respect to the computer-readable media / memory. That is, the cellular baseband processor 824 and the application processor 806 can be configured to perform a first subset of the various functions described above without the information stored in the memory, and can be configured to perform a second subset of the various functions described above based on the information stored in the memory.The computer-readable media / memory can also be used to store data utilized by the cellular baseband processor 824 / application processor 806 in executing software. The cellular baseband processor 824 / application processor 806 can be a component of the UE 350 and can include at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 804 can be a Figure 3 chipset (modem and / or application) and only include the cellular baseband processor 824 and / or the application processor 806, while in another configuration, the apparatus 804 can be the entire UE (e.g., see FIG. 1’s UE 350) and include the additional modules of the apparatus 804.

[0115] As discussed above, the components 198 can be configured to receive, from a network entity, a buffer status table configuration indicating one or more BSR tables; and communicate, with the network entity, based on a first BSR table from the one or more BSR tables. The components 198 can be within the cellular baseband processor 824, the application processor 806, or both the cellular baseband processor 824 and the application processor 806. The components 198 can be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When performing the stated processes / algorithm, the multiple processors can perform the processes / algorithm individually or in combination. As illustrated, the apparatus 804 can include a variety of components configured for various functions. In one configuration, the apparatus 804 (and in particular the cellular baseband processor 824 and / or the application processor 806) includes means for receiving, from a network entity, a buffer status table configuration indicating one or more BSR tables. The apparatus includes means for communicating, with the network entity, based on a first BSR table from the one or more BSR tables. The apparatus further includes means for generating the one or more BSR tables based on parameters received in the buffer status table configuration. The apparatus further includes means for receiving additional control signaling indicating at least one BSR table from a set of BSR tables configured for the UE. The apparatus further includes means for transmitting an indication reporting a selected BSR table of the plurality of BSR tables, where the selected BSR table includes the first BSR table. The means can be the components 198 of the apparatus 804 configured to perform the functions recited by the means. As described above, the apparatus 804 can include the TX processor 368, the RX processor 356, and the controller / processor 359. Accordingly, in one configuration, the means can be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0116] Figure 9 FIG. 9 is a flowchart 900 of a method of wireless communication. The method can be performed by a base station (e.g., the base station 102; the network entity 1102). One or more of the illustrated operations can be omitted, transposed, or combined. The method can configure a UE with one or more BSR tables.

[0117] At 902, the network entity can provide a buffer status table configuration indicating one or more BSR tables. For example, 902 can be performed by the configuration component 199 of the network entity 1102. The network entity can provide the buffer status table configuration to the UE. In some aspects, the buffer status table configuration can indicate one or more BSR tables from a set of defined BSR tables. In some aspects, the buffer status table configuration can configure at least one parameter for the one or more BSR tables. The buffer status table configuration can configure at least one parameter for each of the one or more BSR tables, which can include at least one of: a minimum buffer size, a maximum buffer size, a step size factor, or a step size type. In some aspects, the one or more BSR tables can include at least one of: a different minimum buffer size, a different maximum buffer size, a different step size factor, or a different step size type. In some aspects, the buffer status table configuration can be included within RRC signaling or SI.

[0118] At 904, the network entity can communicate with the UE. For example, 904 can be performed by the configuration component 199 of the network entity 1102. The network entity can communicate with the UE based on a first BSR table from the one or more BSR tables. In some aspects, the communication with the UE based on the first BSR table can include obtaining a BSR from the UE based on a codepoint corresponding to a quantity of buffered data and an entry in the first BSR table.

[0119] Figure 10 FIG. 10 is a flowchart 1000 of a method of wireless communication. The method can be performed by a base station (e.g., the base station 102; the network entity 1102). One or more of the illustrated operations can be omitted, transposed, or combined. The method can configure a UE with one or more BSR tables.

[0120] At 1002, the network entity can provide a buffer status table configuration indicating one or more BSR tables. For example, 1002 can be performed by configuration component 199 of network entity 1102. The network entity can provide a buffer status table configuration to a UE. In some aspects, the buffer status table configuration can indicate one or more BSR tables from a set of defined BSR tables. In some aspects, the buffer status table configuration can configure at least one parameter for the one or more BSR tables. The buffer status table configuration can configure at least one parameter for each BSR table of the one or more BSR tables, which can include at least one of: a minimum buffer size, a maximum buffer size, a step size factor, or a step size type. In some aspects, the one or more BSR tables can include at least one of: a different minimum buffer size, a different maximum buffer size, a different step size factor, or a different step size type. In some aspects, the buffer status table configuration can be included within RRC signaling or SI.

[0121] At 1004, the network entity can provide additional control signaling. For example, 1004 can be performed by configuration component 199 of network entity 1102. The network entity can provide additional control signaling indicating at least one BSR table from a set of BSR tables configured for the UE. In some aspects, the buffer status table configuration can indicate a set of BSR tables for the UE. In such instances, the additional control signal can indicate at least one BSR table from the set of BSR tables for the UE to use.

[0122] At 1006, the network entity can obtain an indication of a selected BSR table to report. For example, 1006 can be performed by configuration component 199 of network entity 1102. The network entity can obtain an indication of a selected BSR table of a plurality of BSR tables to report. In some aspects, the buffer status table configuration can indicate a plurality of BSR tables for the UE. The UE can select a BSR table from the plurality of BSR tables. In some aspects, the selected BSR table can include a first BSR table.

[0123] At 1008, the network entity can communicate with the UE. For example, 1008 can be performed by configuration component 199 of network entity 1102. The network entity can communicate with the UE based on a first BSR table from the one or more BSR tables. In some aspects, the communication with the UE based on the first BSR table can include obtaining a BSR from the UE based on a codepoint corresponding to an amount of buffered data and an entry in the first BSR table.

[0124] Figure 11is a diagram 1100 illustrating an example of a hardware implementation for a network entity 1102. The network entity 1102 can be a BS, a component of a BS, or can implement BS functionality. The network entity 1102 can include at least one of a CU 1110, a DU 1130, or a RU 1140. For example, depending on the layer functionality handled by the components 199, the network entity 1102 can include the CU 1110; both the CU 1110 and the DU 1130; each of the CU 1110, the DU 1130, and the RU 1140; the DU 1130; both the DU 1130 and the RU 1140; or the RU 1140. The CU 1110 can include at least one CU processor 1112. The CU processor 1112 can include on-chip memory 1112’. In some aspects, the CU 1110 can also include an additional memory module 1114 and a communication interface 1118. The CU 1110 communicates with the DU 1130 over a backhaul link, such as an Fl interface. The DU 1130 can include at least one DU processor 1132. The DU processor 1132 can include on-chip memory 1132’. In some aspects, the DU 1130 can also include an additional memory module 1134 and a communication interface 1138. The DU 1130 communicates with the RU 1140 over a front-haul link. The RU 1140 can include at least one RU processor 1142. The RU processor 1142 can include on-chip memory 1142’. In some aspects, the RU 1140 can also include an additional memory module 1144, one or more transceivers 1146, antennas 1180, and a communication interface 1148. The RU 1140 communicates with the UE 104. The on-chip memories 1112’, 1132’, 1142’ and the additional memory modules 1114, 1134, 1144 can each be considered a computer- readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1112, 1132, 1142 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described supra. The computer-readable medium / memory can also be used for storing data that is manipulated by the processor when executing software.

[0125] As discussed above, the component 199 is configured to provide, to a UE, a buffer status table configuration indicating one or more BSR tables; and communicate with the UE based on a first BSR table from the one or more BSR tables. The component 199 can be within one or more processors of one or more of the CU 1110, the DU 1130, and the RU 1140. The component 199 can be one or more hardware components specifically configured to perform the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the stated processes / algorithm can be performed separately or combined to be performed by the multiple processors. The network entity 1102 can include multiple components that are configured to perform various functions. In one configuration, the network entity 1102 includes means for providing, to a UE, a buffer status table configuration indicating one or more BSR tables. The network entity includes means for communicating with the UE based on a first BSR table from the one or more BSR tables. The network entity also includes means for providing additional control signaling indicating at least one BSR table from a set of BSR tables configured for the UE. The network entity also includes means for obtaining an indication reporting a selected BSR table from the one or more BSR tables, where the selected BSR table includes the first BSR table. The means can be the component 199 of the network entity 1102 configured to perform the functions recited by the means. As described above, the network entity 1102 can include the TX processor 316, the RX processor 370, and the controller / processor 375. Accordingly, in one configuration, the means can be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0126] It should be understood that the particular order or hierarchy of steps in the processes / flow diagrams disclosed is merely an example. It should be appreciated that a particular order or hierarchy of steps can be rearranged, some steps can be performed simultaneously, some steps can be performed concurrently, and the like. Also, some steps can be omitted.

[0127] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not to be limited to the aspects described herein, but are to be given the full scope defined by the language of the claims. Unless otherwise defined, a reference to a singular element includes “one and only one” or “one or more.” The term “if’ includes “when” within the context of the special language used herein. That is, the phrase, “if X happens,” as used herein does not necessarily indicate that X will happen, but rather indicates that X can or will happen, depending upon the context. The term “example” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “example” is not necessarily to be construed as preferred or advantageous over other aspects. Unless otherwise specified, the term “some” refers to one or more. The terms “at least one of’ “one or more of’ “at least one of’ “one or more of’ and “one or more of’ include any combination of one or more where the quantity of each element in the combination is not limited to a single instance of that element. Specifically, the terms “at least one of’ “one or more of’ “at least one of’ “one or more of’ and “one or more of’ can be interpreted to include one each of the elements in the combination, or one or more instances of each element in the combination. A set shall be interpreted to include one or more elements. Accordingly, a set of X includes one or more X. When a set of one or more processors is configured to perform a set of functions, each processor in the set of one or more processors is configured to perform a particular subset of the set of functions, either alone or in combination with other processors in the set. Thus, each processor can be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty set. A processor can be referred to as processor circuitry. A memory / memory module can be referred to as memory circuitry. If a first device receives data from a second device, or transmits data to the second device, the data can be received / transmitted directly between the first and second devices, or indirectly between the first and second devices via a set of devices. An apparatus configured to “output” or “provide” data, such as a signal or message, may, for example, transmit the data with a transceiver, or can pass the data to an apparatus that transmits the data.A device configured to "obtain" data (such as transmit, signal, or message) can, for example, receive the data with a transceiver, or can obtain the data from a device that receives the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," and the like do not require that all of these components be implemented in a common physical housing or by a common physical device. Furthermore, the described features, processes, etc., can be altered in a variety of ways without deviating from the spirit or scope of the various aspects. Any aspect of the disclosure can encompass one or more aspects of the disclosure.

[0128] As used herein, the phrase "based on" shall not be construed as a signification of an exclusive set of items, conditions, factors, etc. on which information, condition, factor, etc. is to be relied upon. Rather, the phrase "based on" shall be construed as meaning "based, at least in part, on."

[0129] The following aspects are merely exemplary and can be combined with other aspects or teachings described herein without limitation.

[0130] Aspect 1 is a method of wireless communication at a UE, comprising: receiving, from a network entity, a buffer status table configuration indicating one or more BSR tables, wherein the one or more BSR tables are predefined at the UE or are configurable by the UE based on the buffer status table configuration; and communicating with the network entity based on a first BSR table from the one or more BSR tables.

[0131] Aspect 2 is the method of aspect 1, further comprising: the buffer status table configuration indicating the one or more BSR tables from a set of defined BSR tables.

[0132] Aspect 3 is the method of any of aspects 1 and 2, further comprising: the buffer status table configuration configuring at least one parameter for the one or more BSR tables.

[0133] Aspect 4 is the method of any of aspects 1-3, further comprising: the buffer status table configuration being included within RRC signaling or SI.

[0134] Aspect 5 is the method of any of aspects 1-4, further comprising: the buffer status table configuration configuring, for each of the one or more BSR tables, at least one of: a minimum buffer size, a maximum buffer size, a step size factor, or a step size type.

[0135] Aspect 6 is the method of any of aspects 1-5, further comprising: generating the one or more BSR tables based on parameters received in the buffer status table configuration.

[0136] Aspect 7 is the method of any of aspects 1-6, further comprising: the parameters received in the buffer status table configuration include an adjustment parameter, wherein the one or more BSR tables are generated based on the adjustment parameter and a reference BSR table, wherein the reference BSR table is configurable or preconfigured.

[0137] Aspect 8 is the method of any of aspects 1-7, further comprising: the buffer status table configuration indicating a set of BSR tables for the UE, the method further comprising: receiving additional control signaling indicating at least one BSR table from the set of BSR tables configured for the UE.

[0138] Aspect 9 is the method of any of aspects 1-8, further comprising: the buffer status table configuration indicating a plurality of BSR tables for the UE, the method further comprising: transmitting an indication reporting a selected BSR table of the plurality of BSR tables, wherein the selected BSR table includes the first BSR table.

[0139] Aspect 10 is the method of any of aspects 1-9, further comprising: communicating with the network entity based on the first BSR table includes transmitting a BSR to the network entity using a codepoint corresponding to an amount of buffered data and an entry in the first BSR table.

[0140] Aspect 11 is the method of any of aspects 1-10, further comprising: the one or more BSR tables include at least one of: a different minimum buffer size, a different maximum buffer size, a different step size factor, or a different step size type.

[0141] Aspect 12 is an apparatus for wireless communication at a UE, comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement any of aspects 1-11.

[0142] Aspect 13 is an apparatus for wireless communication at a UE, comprising means for implementing any of aspects 1 through 11.

[0143] Aspect 14 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 through 11.

[0144] Aspect 15 is a method of wireless communication at a network entity, comprising: providing, to a UE, a buffer status table configuration indicating one or more BSR tables; and communicating with the UE based on a first BSR table from the one or more BSR tables.

[0145] Aspect 16 is the method of aspect 15, further comprising: the buffer status table configuration indicating the one or more BSR tables from a set of defined BSR tables.

[0146] Aspect 17 is the method of any of aspects 15 and 16, further comprising: the buffer status table configuration configuring at least one parameter for the one or more BSR tables.

[0147] Aspect 18 is the method of any of aspects 15 through 17, further comprising: the buffer status table configuration being included within RRC signaling or SI.

[0148] Aspect 19 is the method of any of aspects 15 through 18, further comprising: the buffer status table configuration configuring, for each of the one or more BSR tables, at least one of: a minimum buffer size, a maximum buffer size, a step size factor, or a step size type.

[0149] Aspect 20 is the method of any of aspects 15 through 19, further comprising: the buffer status table configuration indicating a set of BSR tables for the UE, the method further comprising: providing additional control signaling indicating at least one BSR table from the set of BSR tables configured for the UE.

[0150] Aspect 21 is the method of any of aspects 15 through 20, further comprising: the buffer status table configuration indicating a plurality of BSR tables for the UE, the method further comprising: obtaining an indication reporting a selected BSR table from the one or more BSR tables, wherein the selected BSR table comprises the first BSR table.

[0151] Aspect 22 is the method of any of aspects 15 through 21, further comprising communicating with the UE based on the first BSR table further comprises obtaining a BSR from the UE based on a codepoint corresponding to an amount of buffered data and an entry in the first BSR table.

[0152] Aspect 23 is the method of any of aspects 15 through 22, further comprising the one or more BSR tables comprise at least one of: different minimum buffer size, different maximum buffer size, different step size factor, or different step size type.

[0153] Aspect 24 is an apparatus for wireless communication at a network entity, the apparatus comprising: at least one processor configured to implement any of aspects 15 through 23, coupled to a memory and at least one transceiver.

[0154] Aspect 25 is an apparatus for wireless communication at a network entity, the apparatus comprising means for implementing any of aspects 15 through 23.

[0155] Aspect 26 is a computer readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 15 through 23.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: Receive a buffer state table configuration from a network entity that indicates one or more buffer state report (BSR) tables, wherein the one or more BSR tables are predefined at the UE or can be configured by the UE based on the buffer state table configuration; as well as Communicating with the network entity based on a first BSR table derived from one or more BSR tables.

2. The apparatus according to claim 1, further comprising: A transceiver coupled to the at least one processor.

3. The apparatus of claim 1, wherein the buffer state table configuration indicates one or more BSR tables from a defined set of BSR tables.

4. The apparatus of claim 1, wherein the buffer state table configuration configures at least one parameter for the one or more BSR tables.

5. The apparatus of claim 1, wherein the buffer status table configuration is included in Radio Resource Control (RRC) signaling or System Information (SI).

6. The apparatus of claim 1, wherein the buffer state table configuration configures at least one of the following for each of the one or more BSR tables: minimum buffer size, maximum buffer size, step size factor, or step size type.

7. The apparatus of claim 6, wherein the at least one processor is configured to: The one or more BSR tables are generated based on the parameters received in the buffer state table configuration.

8. The apparatus of claim 7, wherein the parameters received in the buffer state table configuration include adjustment parameters, wherein the one or more BSR tables are generated based on the adjustment parameters and a reference BSR table, wherein the reference BSR table is configurable or pre-configured.

9. The apparatus of claim 1, wherein the buffer state table configuration indicates a BSR table set for the UE, wherein the at least one processor is configured to: Receive additional control signaling indicating at least one BSR table from the BSR table set configured for the UE.

10. The apparatus of claim 1, wherein the buffer state table configuration indicates a plurality of BSR tables for the UE, wherein the at least one processor is configured to: Send an instruction to select a BSR table from the plurality of BSR tables, wherein the selected BSR table includes the first BSR table.

11. The apparatus of claim 1, wherein, in order to communicate with the network entity based on the first BSR table, the at least one processor is configured to: The BSR is sent to the network entity using code points corresponding to the amount of buffered data and the entries in the first BSR table.

12. The apparatus of claim 1, wherein the one or more BSR tables comprise at least one of the following: Different minimum buffer sizes, Different maximum buffer sizes, Different step size factors, or Different step size types.

13. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive a buffer state table configuration from a network entity that indicates one or more buffer state report (BSR) tables, wherein the one or more BSR tables are predefined at the UE or can be configured by the UE based on the buffer state table configuration; as well as Communicating with the network entity based on a first BSR table derived from one or more BSR tables.

14. The method of claim 13, wherein the buffer state table configuration configures at least one parameter for the one or more BSR tables.

15. The method of claim 14, wherein the buffer state table configuration configures at least one of the following for each of the one or more BSR tables: minimum buffer size, maximum buffer size, step size factor, or step size type.

16. The method according to claim 15, further comprising: The one or more BSR tables are generated based on the parameters received in the buffer state table configuration.

17. The method of claim 16, wherein the parameters received in the buffer state table configuration include adjustment parameters, wherein the one or more BSR tables are generated based on the adjustment parameters and a reference BSR table, wherein the reference BSR table is configurable or pre-configured.

18. The method of claim 13, wherein the buffer state table configuration indicates a set of BSR tables for the UE, the method further comprising: Receive additional control signaling indicating at least one BSR table from the BSR table set configured for the UE.

19. The method of claim 13, wherein the buffer state table configuration indicates a plurality of BSR tables for the UE, the method further comprising: Send an instruction to select a BSR table from the plurality of BSR tables, wherein the selected BSR table includes the first BSR table.

20. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: Provide the user equipment (UE) with a buffer state table configuration that indicates one or more buffer state report (BSR) tables, wherein the one or more BSR tables are predefined at the UE or can be configured by the UE based on the buffer state table configuration; as well as The UE is communicated based on a first BSR table derived from one or more BSR tables.

21. The apparatus of claim 20, further comprising: A transceiver coupled to the at least one processor.

22. The apparatus of claim 20, wherein the buffer state table configuration indicates one or more BSR tables from a defined set of BSR tables.

23. The apparatus of claim 20, wherein the buffer state table configuration configures at least one parameter for the one or more BSR tables.

24. The apparatus of claim 20, wherein the buffer status table configuration is included in Radio Resource Control (RRC) signaling or System Information (SI).

25. The apparatus of claim 23, wherein the buffer state table configuration configures at least one of the following for each of the one or more BSR tables: minimum buffer size, maximum buffer size, step size factor, or step size type.

26. The apparatus of claim 20, wherein the buffer state table configuration indicates a BSR table set for the UE, wherein the at least one processor is configured to: Provide additional control signaling indicating at least one BSR table from the set of BSR tables configured for the UE.

27. The apparatus of claim 20, wherein the buffer state table configuration indicates a plurality of BSR tables for the UE, wherein the at least one processor is configured to: Obtain an instruction to select a BSR table from the one or more BSR tables, wherein the selected BSR table includes the first BSR table.

28. The apparatus of claim 20, wherein, in order to communicate with the UE based on the first BSR table, the at least one processor is configured to: The BSR is obtained from the UE based on the code points corresponding to the amount of buffered data and the entries in the first BSR table.

29. The apparatus of claim 20, wherein the one or more BSR tables comprise at least one of the following: Different minimum buffer sizes, Different maximum buffer sizes, Different step size factors, or Different step size types.

30. A method for wireless communication at a network entity, the method comprising: Provide the user equipment (UE) with a buffer state table configuration that indicates one or more buffer state report (BSR) tables, wherein the one or more BSR tables are predefined at the UE or can be configured by the UE based on the buffer state table configuration; as well as The UE is communicated based on a first BSR table derived from one or more BSR tables.

Images