Buffer status report messages

Abstract

A user equipment (UE) may receive data for transmission at a buffer of the UE, such as when data is generated by an application of the UE. The UE may periodically send a buffer status report (BSR) to indicate an amount of data present at the buffer of the UE, as well as other information. Some aspects described herein enable enhanced buffer status reporting. For example, a UE may dynamically generate a buffer status report table based at least in part on a set of configuration parameters (e.g., a network node may signal to the UE).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 481,377, filed on January 24, 2023, entitled “BUFFER STATUS REPORTING MESSAGE,” and U.S. Non-Provisional Patent Application No. 18 / 409,135, filed on January 10, 2024, entitled “BUFFER STATUS REPORTING MESSAGE,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for buffer status report messages. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, national, regional and / or global level. 5G (which may be referred to as New Radio (NR)) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. 5G is designed to better support mobile broadband internet access by using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements to 4G, 5G and other radio access technologies remain useful. Summary of the Invention

[0007] A user equipment (UE) may receive data for transmission at a buffer of the UE, such as when the data is generated by an application of the UE. The UE may periodically send a buffer status report (BSR) to indicate the amount of data present at the buffer of the UE, as well as other information. The UE may report the total layer 2 (L2) buffer size per logical control group (LCG) to a network node in a buffer status report medium access control (MAC) control element (CE) (MAC-CE). In some examples, the UE may encode the buffer size per LCG using 5 bits or 8 bits based at least in part on the format of the MAC-CE that the UE will use to send the buffer status report. For example, the UE may use a 5-bit indicator for a short format BSR MAC-CE and an 8-bit indicator for a long format BSR MAC-CE.

[0008] To encode the buffer size using a set of bits, the UE may use a buffer status report coding table, which may have values ​​associated with the following equation:

[0009] Where p=(B max / B min ) 1 / (N-1) –1

[0010] Among them B min is the minimum report buffer size value, B max is the maximum report buffer size value, N is the number of code points (e.g., 32 for 5-bit BSR and 256 for 8-bit BSR), p is the error value, k is the step size, and B kis the buffer size to be reported. Using the above formula, the UE achieves a roughly constant error percentage p (e.g., for all values ​​of k, (B k+1 –B k ) / B k The UE may use a step size of approximately 4,957,949 bytes for k=252 and k=253, but may have a larger absolute error for larger values ​​of k. For example, at k=252 and k=253, the UE uses a step size of approximately 4,957,949 bytes. Therefore, the absolute error (e.g., the difference between the actual buffer size when k=252 and the reported buffer size for k=252) may be quite large, which may result in inefficient allocation of network resources to the UE for enabling transmission of the data in the buffer.

[0011] Some aspects described herein enable enhanced buffer status reporting. For example, a UE may dynamically generate a buffer status reporting table based at least in part on a set of configuration parameters (e.g., that a network node may signal to the UE). Additionally or alternatively, the UE may receive an indication of a buffer status reporting table to be used based at least in part on one or more parameters determined by the network node. In this way, the UE and / or the network node may minimize absolute errors in buffer size reporting, thereby achieving more efficient allocation of network resources. For example, the UE may predict an expected size of a video frame in an extended reality (XR) application, and may use the expected size of the video frame to generate a BSR table for buffer size encoding and reporting. In this way, the UE may ensure more efficient utilization of network resources for data-intensive applications (such as XR applications).

[0012] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving data for transmission at a buffer. The method may include sending a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values.

[0013] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving, at a buffer of the UE, a buffer status report message regarding data for transmission from the UE, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values. The method may include communicating with the UE based at least in part on content of the buffer status report message.

[0014] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive data for transmission at a buffer. The one or more processors may be configured to send a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values.

[0015] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, at a buffer of the UE, a buffer status report message regarding data for transmission from the UE, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values. The one or more processors may be configured to communicate with the UE based at least in part on content of the buffer status report message.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive data for transmission at a buffer. The instruction set, when executed by one or more processors of the UE, may cause the UE to: send a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer being encoded using a buffer status report table based at least in part on one or more parameter values.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to: receive, from a UE at a buffer of the UE, a buffer status report message regarding data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values. The instruction set, when executed by the one or more processors of the network node, may cause the network node to: communicate with the UE based at least in part on content of the buffer status report message.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving data for transmission at a buffer. The apparatus may include means for sending a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, at a buffer of the UE, a buffer status report message regarding data for transmission from the UE, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values. The apparatus may include means for communicating with the UE based at least in part on content of the buffer status report message.

[0020] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, network entities, network nodes and / or processing systems as fully described with reference to and as illustrated by the accompanying drawings and description.

[0021] The features and technical advantages of the examples according to the present disclosure have been summarized in a rather broad manner above so that the detailed description below may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0023] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0024] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0025] Figures 4A to 4D is a diagram illustrating an example associated with using a buffer status report message according to the present disclosure.

[0026] Figure 5 is a flow chart of an example method of wireless communication according to the present disclosure.

[0027] Figure 6 is a flow chart of an example method of wireless communication according to the present disclosure.

[0028] Figure 7 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0029] Figure 8 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system according to the present disclosure.

[0030] Figure 9 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0031] Figure 10 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system according to the present disclosure. DETAILED DESCRIPTION

[0032] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0033] Several aspects of telecommunication systems will now be presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, 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 overall system.

[0034] By way of example, an element, or any part of an element, or any combination of elements, can be implemented using a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, 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 can execute software. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, etc., whether referred to by software, firmware, middleware, microcode, hardware description languages, or other names.

[0035] Therefore, in one or more example embodiments, the described functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored or encoded as one or more instructions or codes 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. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disc ROM (CD-ROM), or other optical disc storage devices, magnetic disk storage devices, or other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0036] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0037] A user equipment (UE) may receive data for transmission at a buffer of the UE, such as when the data is generated by an application of the UE. The UE may periodically send a buffer status report (BSR) to indicate the amount of data present at the buffer of the UE, as well as other information. The UE may report the total layer 2 (L2) buffer size per logical control group (LCG) to a network node in a buffer status report medium access control (MAC) control element (MAC-CE). In some examples, the UE may encode the buffer size per LCG using 5 bits or 8 bits based at least in part on the format of the MAC-CE that the UE will use to send the buffer status report. For example, the UE may use a 5-bit indicator for a short format BSR MAC-CE and an 8-bit indicator for a long format BSR MAC-CE.

[0038] To encode the buffer size using a set of bits, the UE may use a buffer status report encoding table, but using a fixed table may result in a large absolute error for large values ​​of the fixed table. Therefore, the absolute error (e.g., the difference between the actual buffer size and the reported buffer size) may be quite large, which may result in inefficient allocation of network resources to the UE for transmitting the data in the buffer.

[0039] Various aspects generally relate to enhanced buffer status reporting. Some aspects more specifically relate to a UE that can dynamically generate a buffer status reporting table based at least in part on a set of configuration parameters (e.g., that a network node can signal to the UE). Additionally or alternatively, the UE can receive an indication of a buffer status reporting table to use based at least in part on one or more parameters determined by the network node. In some aspects, the UE can use a BSR MAC-CE in a specific format to convey one or more fields associated with the BSR table that the UE can use to report buffer sizes.

[0040] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, by using a dynamically generated BSR table, a new statically configured BSR table, or a network configured BSR table, as described herein, a UE and / or network node may minimize absolute errors in buffer size reporting, thereby achieving more efficient allocation of network resources. In some examples, a UE may predict the expected size of a video frame in an extended reality (XR) application, and the expected size of the video frame may be used to generate a BSR table for buffer size encoding and reporting. By generating a BSR table, the described techniques may be used to ensure more efficient utilization of network resources for data-intensive applications (such as XR applications, etc.).

[0041] Figure 11 is a diagram illustrating an example of a wireless network 100. Wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. Wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is an example of a network node communicating with UE 120. As shown, network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0042] In some examples, network node 110 is a network node (such as an RU) that communicates with UE 120 via a radio access link, or includes a network node (such as an RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link, or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as a converged network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network nodes 110 may include NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, transmit receive points (TRPs), DUs, RUs, CUs, mobility elements of a network, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, the network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in the wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0043] In some examples, network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​network node 110 or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, or another type of cell. A macrocell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0044] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0045] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.

[0046] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0047] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with each other directly or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0048] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate via a wireless or wired medium.

[0049] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags that can communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included inside a housing that houses components of the UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0050] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology or air interface. A frequency may also be referred to as a carrier or frequency channel. Each frequency in a given geographic area may support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0051] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0052] Devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0053] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and therefore the features of FR1 or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0054] With these examples in mind, unless otherwise specifically stated, if the term "sub-6 GHz" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, frequencies that may be within FR1, or frequencies that may include mid-band frequencies. Furthermore, unless otherwise specifically stated, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, frequencies that may be within FR2, FR4, FR4-a, FR4-1, or FR5, or frequencies that may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

[0055] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive data for transmission at a buffer; and transmit a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0056] In some aspects, network node 110 may include a communications manager 150. As described in greater detail elsewhere herein, communications manager 150 may receive a buffer status report message from a UE regarding data for transmission at a buffer of the UE, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values, and communicate with the UE based at least in part on the content of the buffer status report message. Additionally or alternatively, communications manager 150 may perform one or more other operations described herein.

[0057] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0058] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0059] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may use one or more channel quality indicators (CQIs) received from UE 120 to select one or more modulation and coding schemes (MCSs) for UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 using the MCS selected for UE 120 and may provide data symbols to UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0060] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other parameters. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0061] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0062] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or a plurality of antenna elements coupled to one or more transmit or receive components (such as antennas 234a to 234t, antennas 252a to 252r). Figure 2 One or more antenna elements of one or more components).

[0063] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the processes described herein.

[0064] At the network node 110, uplink signals from the UE 120 or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information transmitted via the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the processes described herein.

[0065] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component in the may perform one or more techniques associated with buffer status reporting, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the may perform or direct e.g. Figure 5 Method 500, Figure 6 600 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 5 Method 500, Figure 6 The method 600 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among other things.

[0066] In some aspects, the UE 120 includes: means for receiving data for transmission at a buffer; and / or means for sending a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer being encoded using a buffer status report table based at least in part on one or more parameter values. Means for the UE 120 to perform the operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0067] In some aspects, the network node 110 includes: means for receiving, at a buffer of the UE, a buffer status report message regarding data for transmission from the UE, the buffer status report message including an indication of the buffer, the indication of the buffer being encoded using a buffer status report table based at least in part on one or more parameter values; and means for communicating with the UE based at least in part on the contents of the buffer status report message. Means for the network node 110 to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0068] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0069] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0070] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also known as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0071] A converged base station (e.g., a converged network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0072] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an 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 known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Each unit of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0073] Figure 3 FIG2 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0074] Each of the units (including the CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may 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 that provides instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0075] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among others. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 may 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0076] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers, at least in part according to a functional split (such as that defined by 3GPP). In some aspects, the one or more higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like. In some aspects, the DU 330 may also host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0077] Each RU 340 may implement low-layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as low-layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0078] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0079] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0080] In some implementations, the non-RT RIC 315 can receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in the near-RT RIC 325. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or through the creation of RAN management policies (such as A1 interface policies).

[0081] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0082] A UE may receive data for transmission at a buffer of the UE, such as when data is generated by an application of the UE. The UE may periodically send a buffer status report (BSR) to indicate the amount of data present at the buffer of the UE, as well as other information. The UE may report the total layer 2 (L2) buffer size per logical control group (LCG) to a network node in a buffer status report MAC control element (CE) (MAC-CE). In some examples, the UE may encode the buffer size per LCG using 5 bits or 8 bits based at least in part on the format of the MAC-CE that the UE will use to send the buffer status report. For example, the UE may use a 5-bit indicator for a short format BSR MAC-CE and an 8-bit indicator for a long format BSR MAC-CE.

[0083] To encode the buffer size using a set of bits, the UE may use a buffer status report encoding table, but using a fixed table may result in a large absolute error for large values ​​of the fixed table. Therefore, the absolute error (e.g., the difference between the actual buffer size and the reported buffer size) may be quite large, which may result in inefficient allocation of network resources to the UE for transmitting the data in the buffer.

[0084] Some aspects described herein implement enhanced buffer status reporting. For example, a UE may dynamically generate a buffer status reporting table based at least in part on a set of configuration parameters (e.g., that a network node may signal to the UE). Additionally or alternatively, the UE may receive an indication of a buffer status reporting table to be used based at least in part on one or more parameters determined by the network node. In this way, the UE and / or the network node may minimize absolute errors in buffer size reporting, thereby achieving more efficient allocation of network resources. For example, a UE may predict an expected size of a video frame in an extended reality (XR) application, and may use the expected size of the video frame to generate a BSR table for buffer size encoding and reporting. In this way, the UE may ensure more efficient utilization of network resources for data-intensive applications (such as XR applications).

[0085] Figures 4A to 4D 4 is a diagram illustrating an example 400 associated with using a buffer status report message according to the present disclosure. As shown in FIG4 , the example 400 includes communications between a network node 110 and a UE 120.

[0086] As in Figure 4A In the embodiment and as indicated by reference numeral 410, UE 120 may receive configuration information. For example, UE 120 may receive configuration information associated with configuring a buffer status report. In some aspects, UE 120 may receive configuration information associated with dynamically generating a buffer status report table. For example, UE 120 may receive information associated with identifying one or more parameters, such as a minimum reported buffer status value B. min , Maximum report buffer status value B max , coding error value p, or the number of code points N of the buffer status report, etc. In this case, as a specific example, the network node 110 may send the identifier B min 、B max Information, identification information B min 、B max and N's information or identification B min 、B max , p, and N, as well as other combination examples. Based at least in part on the received parameter set, UE 120 may dynamically generate a buffer status report table (or other data structure) from which to select values ​​for the buffer status report. In other words, UE 120 may generate a buffer status report table for encoding the buffer status report in conjunction with a buffer size encoding equation, where B min As the minimum value, B max As the maximum value, N as B min and B maxIn this case, the buffer size encoding equation configured for UE 120 may be:

[0087] Where p=(B max / B min ) 1 / (N-1) –1

[0088] where p is the encoding error value parameter, as described above.

[0089] In some aspects, UE 120 may receive information identifying one or more parameters via a type of signaling. For example, network node 110 may broadcast information identifying the parameters via system information transmission, such as system information block (SIB) transmission. Additionally or alternatively, network node 110 may transmit dedicated signaling identifying the parameters, such as radio resource control (RRC) signaling, downlink control information (DCI) signaling, or medium access control (MAC) control element (CE) (MAC-CE) signaling. In some aspects, UE 120 may set an inhibit timer associated with the dedicated signaling. For example, when UE 120 receives first signaling identifying a parameter set, UE 120 may set an inhibit timer for a configured time length (e.g., which may be configured in a specification or via network node signaling). In this case, if UE 120 receives second signaling identifying a new parameter set before the inhibit timer expires, UE 120 may ignore the new parameter set and may continue to use the parameter set signaled using the first signaling.

[0090] In some aspects, UE 120 may receive information identifying a buffer status report table. For example, UE 120 may be configured with a B min 、B max , N, and / or p. In some aspects, the UE 120 may be configured with a plurality of BSR tables corresponding to different combinations of possible parameter values ​​for N, N, and / or p. In this case, the possible values ​​of the parameters may be associated with the data type. For example, when the buffer of the UE 120 is associated with conveying video frames of an extended reality (XR) application, the UE 120 may be configured with a plurality of BSR tables corresponding to possible parameter values ​​for the video frame size, encoding rate, or resolution of the XR application. In this case, the UE 120 may receive configuration information associated with indicating a selection of a BSR table or indicating that the UE 120 is to use the configured BSR table. In some aspects, the UE 120 may be configured with a parameter indicating the maximum number of possible step sizes of the BSR tables and / or the maximum number of BSR tables with which the UE 120 can be configured.

[0091] In some aspects, UE 120 may receive configuration information indicating selection of a per-logical control group (LCG) BSR table. For example, network node 110 may configure a plurality of BSR tables with an LCG that do not include overlapping ranges. Thus, as part of an LCG, UE 120 may use either a configured BSR table associated with the LCG or a legacy BSR table (e.g., not configured on a per-LCG basis). For example, when an LCG has a buffer size within the range of a configured per-LCG BSR table, UE 120 may use the associated per-LCG BSR table. Alternatively, when an LCG has a buffer size that is not within the range of any configured per-LCG BSR table, UE 120 may use a legacy BSR table (e.g., not configured on a per-LCG basis).

[0092] In some aspects, UE 120 may receive configuration information that explicitly identifies a BSR table to be used for reporting the buffer size of an LCG. For example, UE 120 may receive a BSR MAC CE with an indicator of a BSR table from among multiple configured BSR tables. In some aspects, if the LCG buffer size is within the range of multiple BSR tables, UE 120 may select a particular BSR table with the smallest step size. In some aspects, UE 120 may select a BSR table based at least in part on the uplink grant size. For example, when the uplink grant includes an amount of network resources to be used with a BSR MAC CE configured for, for example, a non-legacy BSR table (such as a per-LCG BSR table), UE 120 may select a non-legacy BSR table for BSR reporting with a non-legacy (e.g., enhanced) BSR MAC-CE. Alternatively, when the uplink grant is not large enough to include an indication associated with a non-legacy BSR table, UE 120 may use a legacy BSR table and send a legacy BSR MAC-CE.

[0093] As in Figure 4A , and further indicated by reference numeral 420, UE 120 may receive data for transmission. For example, UE 120 may have a buffer for transmitting data (e.g., control data or payload data) and may identify that the buffer includes data to be transmitted. In some aspects, UE 120 may generate data. For example, an application of UE 120 may generate data and provide the data (or an indication of the data) to a buffer, which may indicate to UE 120 that UE 120 will transmit the data.

[0094] As in Figure 4A, and further indicated by reference numeral 430, UE 120 may send a BSR message. For example, UE 120 may send a BSR MAC-CE to network node 110 to indicate the status of data for transmission at a buffer of UE 120. In some aspects, UE 120 may send a BSR MAC-CE with a first format. For example, as in Figure 4B In the example and as indicated by reference numeral 440, the BSR MAC-CE may include an LCG bitmap L m , which indicates the corresponding LCG (LCG m ) whether to include buffer data, such as the first octet of the LCG bitmap L i Additionally or alternatively, the first format of the BSR MAC-CE may include a BSR table bitmap T m , which may indicate whether the legacy BSR table or the enhanced BSR table is being used to report the LCG m , such as the second octet of the BSR table B i Additionally or alternatively, the first format of the BSR MAC-CE may include a buffer size indicator for the LCG, which may indicate the LCG m The size of the buffer (e.g., the amount of data) of the buffer, as shown in the third octet to the nth octet. In some aspects, when the network node 110 configures the BSR table with no overlapping range to the UE 120, the UE 120 may use the first format and may determine whether to use the enhanced BSR table or the legacy BSR table, as described above.

[0095] Additionally or alternatively, as in Figure 4C In the embodiment and as indicated by reference numeral 450, UE 120 may send a BSR MAC-CE with a second format. In the second format, the BSR MAC-CE may include an LCG bitmap indicator L m and the index value B that identifies the BSR table m For example, in up to octet n, each LCG reporting a buffer status may have a corresponding BSR in octet 2 and octet 3 identifying the BSR table used to generate the buffer status being reported. i In some aspects, when UE 120 is configured to indicate which BSR table is being used to report the buffer size of the LCG, UE 120 may use the second format, as described above.

[0096] Additionally or alternatively, as in Figure 4D In the third format, UE 120 may include a BSR MAC-CE for LCG. m BSR table index value Bm , but the LCG bitmap L used in the first format and the second format may be omitted m In this case, when corresponding to LCG m When the value of the BSR table index is 0 (or another configured value), the network node 110 may interpret the BSR table index as indicating the LCG m There is no buffer data for reporting buffer size. Alternatively, for LCG m The value of the field indicates the LCG being used to report m In some aspects, when UE 120 is configured to indicate which BSR table is being used to report the buffer size of the LCG, UE 120 may use the second format, as described above.

[0097] As indicated above, Figures 4A to 4D are provided as examples. Other examples may be used with respect to Figures 4A to 4D The examples described are different.

[0098] Figure 5 is a flow chart of an example method 500 of wireless communication. Method 500 may be performed, for example, by a UE (eg, UE 120).

[0099] At 510, in some aspects, the UE may receive configuration information. For example, the UE (e.g., using Figure 7 The depicted communication manager 140 and / or receiving component 702) may receive signaling identifying one or more parameter values ​​via system information transmission and dedicated signaling. Additionally or alternatively, a UE (e.g., using Figure 7 The communications manager 140 and / or receiving component 702 depicted in FIG. 1 may receive configuration information associated with configuring a buffer status reporting table, wherein the configuration information is on a per-logical channel group basis.

[0100] In some aspects, the one or more parameter values ​​include at least one of a minimum reported buffer status value, a maximum reported buffer status value, a coding error value, or a number of code points for a buffer status report message. In some aspects, the one or more parameter values ​​are selected from a set of possible parameter values ​​based at least in part on at least one of a predicted data size, a resolution, or a coding rate. In some aspects, a buffer status reporting table is based at least in part on one or more static parameters, the one or more static parameters including at least one of a maximum number of step sizes or a maximum number of buffer status reporting tables. In some aspects, the configuration information configures a buffer status reporting table for a logical channel group such that a range of the buffer status reporting table does not overlap with any other range of any other buffer status reporting table for any other logical channel group.

[0101] In some aspects, the buffer status report message includes information identifying a buffer status report table. For example, the buffer status report message may include a bitmap with a set of values ​​identifying the buffer status report table. Additionally or alternatively, the buffer status report message may include a bitmap with a set of values ​​identifying the type of buffer status report table. For example, the bitmap may include a first value for indicating a first type of buffer status report table (e.g., a legacy buffer status report table) and a second value for indicating a second type of buffer status report table (e.g., an enhanced or new buffer status report table).

[0102] At 520, the UE may receive data for transmission at a buffer. For example, a UE (e.g., using Figure 7 140 and / or receiving component 702) may receive data for transmission at a buffer, as described above. In some aspects, the UE is triggered to send a buffer status report message to report the data received at the buffer for transmission. In some aspects, the UE may select a buffer status report table from a set of available buffer status report tables based at least in part on characteristics of the buffer.

[0103] At 530, the UE may send a buffer status report message. For example, the UE (e.g., using Figure 7 , the communication manager 140 and / or the transmitting component 704 depicted in FIG. 3 may transmit a buffer status report message regarding data for transmission, as described above. In some aspects, the buffer status report message may include an indication of a buffer, the indication of the buffer encoded using a buffer status reporting table based at least in part on one or more parameter values. In some aspects, the buffer status report message is a MAC-CE including at least one of the following: a logical channel control group indicator, a logical channel control group queue indicator, a buffer status reporting table indicator, or a buffer size indicator.

[0104] although Figure 5 Example blocks of method 500 are shown, but in some aspects, method 500 may include Figure 5 The blocks depicted in the method 500 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the method 500. Additionally or alternatively, two or more of the blocks in the method 500 may be executed in parallel.

[0105] Figure 6 is a flow diagram of an example method 600 of wireless communication. The method 600 may be performed, for example, by a network node (eg, network node 110).

[0106] At 610, in some aspects, the network node may send configuration information. For example, the network node (e.g., using Figure 9The communications manager 150 and / or sending component 904 depicted in can send configuration information, as described above.

[0107] In some aspects, a network node may transmit signaling identifying one or more parameter values ​​via system information transmission or dedicated signaling. In some aspects, the one or more parameter values ​​include at least one of: a minimum reported buffer status value, a maximum reported buffer status value, a coding error value, or a number of code points for a buffer status report message. In some aspects, the one or more parameter values ​​are based at least in part on at least one of a predicted data size, a resolution, or a coding rate.

[0108] In some aspects, the network node is configured to send configuration information associated with configuring a buffer status reporting table, wherein the configuration information is based on a per-logical channel group basis. In some aspects, the buffer status reporting table is based at least in part on one or more static parameters, the one or more static parameters including at least one of a maximum number of step sizes or a maximum number of buffer status reporting tables. In some aspects, the configuration information configures the buffer status reporting table for the logical channel group such that a range of the buffer status reporting table does not overlap with any other range of any other buffer status reporting table for the logical channel group. In some aspects, the network node may configure the UE to select a buffer status reporting table from a set of available buffer status reporting tables based at least in part on characteristics of the buffer.

[0109] At 620, the network node may receive a buffer status report message. For example, the network node (e.g., using Figure 9 The communication manager 150 and / or receiving component 902 depicted in FIG. 1 may receive a buffer status report message from the UE regarding data for transmission at a buffer of the UE, as described above. In some aspects, the buffer status report message may include an indication of the buffer. In some aspects, the indication of the buffer may be encoded using a buffer status report table based at least in part on one or more parameter values. In some aspects, the buffer status report message includes information identifying the buffer status report table. For example, the buffer status report message may include a bitmap with a set of values ​​identifying the buffer status report table. Additionally or alternatively, the buffer status report message may include a bitmap with a set of values ​​identifying the type of buffer status report table. For example, the bitmap may include a first value indicating a first type of buffer status report table (e.g., a legacy buffer status report table) and a second value indicating a second type of buffer status report table (e.g., an enhanced or new buffer status report table). In some aspects, the buffer status report message is a MAC control element including at least one of the following: a logical channel control group indicator, a logical channel control group queue indicator, a buffer status report table indicator, or a buffer size indicator.

[0110] At 630, the network node may communicate with the UE based at least in part on the contents of the buffer status report message. Figure 9 904) may communicate with the UE based at least in part on the contents of the buffer status report message, as described above. In some aspects, the network node may schedule resources for the UE to send data on the buffer based at least in part on the contents of the buffer status report message. In some aspects, the network node may receive the transmission of data on the buffer.

[0111] although Figure 6 Example blocks of method 600 are shown, but in some aspects, method 600 may include Figure 6 The blocks depicted in the method 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the method 600. Additionally or alternatively, two or more of the blocks in the method 600 may be executed in parallel.

[0112] Figure 7 is a diagram of an example apparatus 700 for wireless communication according to the present disclosure. Apparatus 700 may be a UE, or a UE may include apparatus 700. In some aspects, apparatus 700 includes a receiving component 702 and a transmitting component 704 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 700 may use receiving component 702 and transmitting component 704 to communicate with another apparatus 706 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 700 may include a communications manager 140. Communications manager 140 may include one or more of a BSR configuration component 708, among others.

[0113] In some aspects, the apparatus 700 may be configured to perform one or more operations described herein. Additionally or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as Figure 5 Method 500. In some aspects, Figure 7 The illustrated apparatus 700 and / or one or more components may include a combination of Figure 2 Additionally or alternatively, one or more components of the UE described. Figure 7 One or more of the components shown may be combined Figure 2Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0114] The receiving component 702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 706. The receiving component 702 may provide the received communications to one or more other components of the device 700. In some aspects, the receiving component 702 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 700. In some aspects, the receiving component 702 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0115] The transmitting component 704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 706. In some aspects, one or more other components of the apparatus 700 may generate communications and may provide the generated communications to the transmitting component 704 for transmission to the apparatus 706. In some aspects, the transmitting component 704 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 706. In some aspects, the transmitting component 704 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 704 can be co-located with the receive component 702 in a transceiver.

[0116] Receiving component 702 can receive data for transmission at a buffer. Sending component 704 can send a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values.

[0117] Receiving component 702 can receive signaling identifying one or more parameter values ​​via system information transmission or dedicated signaling. Receiving component 702 can receive configuration information associated with configuring a buffer status report table, wherein the configuration information is on a per-logical channel group basis. BSR configuration component 708 can generate or select a BSR table for encoding BSR information in a BSR message.

[0118] Figure 7 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 7 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 7 Two or more components shown may be implemented in a single component, or Figure 7 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 7 The illustrated set of components (one or more) may be described as being executable by Figure 7 Another group of components is shown performing one or more functions.

[0119] Figure 8 is a diagram illustrating an example 800 of a hardware implementation for an apparatus 805 employing a processing system 810 according to the present disclosure. The apparatus 805 may be a UE.

[0120] The processing system 810 may be implemented using a bus architecture, generally represented by bus 815. Bus 815 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 810 and the overall design constraints. Bus 815 links together various circuits including one or more processors and / or hardware components (represented by processor 820, illustrated components, and computer-readable media / memory 825). Bus 815 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0121] The processing system 810 may be coupled to a transceiver 830. The transceiver 830 is coupled to one or more antennas 835. The transceiver 830 provides components for communicating with various other devices via a transmission medium. The transceiver 830 receives signals from the one or more antennas 835, extracts information from the received signals, and provides the extracted information to the processing system 810 (specifically, the receiving component 702). In addition, the transceiver 830 receives information from the processing system 810 (specifically, the transmitting component 704) and generates signals to be applied to the one or more antennas 835 based at least in part on the received information.

[0122] The processing system 810 includes a processor 820 coupled to a computer-readable medium / memory 825. The processor 820 is responsible for general processing, including executing software stored on the computer-readable medium / memory 825. This software, when executed by the processor 820, enables the processing system 810 to perform the various functions described herein for any particular device. The computer-readable medium / memory 825 may also be used to store data manipulated by the processor 820 when executing the software. The processing system also includes at least one of the components illustrated. A component may be a software module running on the processor 820, resident / stored in the computer-readable medium / memory 825, one or more hardware modules coupled to the processor 820, or some combination thereof.

[0123] In some aspects, the processing system 810 can be a component of the UE 120 and can include the memory 282 and / or at least one of the TX MIMO processor 266, the receive (RX) processor 258, and / or the controller / processor 280. In some aspects, the apparatus 805 for wireless communication includes: means for receiving data for transmission at a buffer; and / or means for sending a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values. The aforementioned means can be one or more of the aforementioned components of the apparatus 700 and / or the processing system 810 of the apparatus 805 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 810 can include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned components may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations described herein.

[0124] Figure 8 is provided as an example. Other examples can be combined with Figure 8 The examples described are different.

[0125] Figure 9is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a network node, or a network node may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may use receiving component 902 and transmitting component 904 to communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include, among other things, a BSR configuration component 908.

[0126] In some aspects, the apparatus 900 may be configured to perform one or more operations described herein. Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 6 Method 600. In some aspects, Figure 9 The device 900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the described network node. Figure 9 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0127] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0128] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 906. In some aspects, one or more other components of the apparatus 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the apparatus 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the described network nodes. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0129] Receiving component 902 can receive a buffer status report message from the UE regarding data for transmission at a buffer of the UE, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values. Receiving component 902 and / or sending component 904 can communicate with the UE based at least in part on the content of the buffer status report message.

[0130] Transmitting component 904 can transmit signaling identifying one or more parameter values ​​via system information transmission or dedicated signaling. Transmitting component 904 can transmit configuration information associated with configuring a buffer status report table, wherein the configuration information is on a per-logical channel group basis. BSR configuration component 908 can configure or determine a set of parameters from which the UE can select or generate a BSR table. BSR configuration component 908 can select a BSR table for the UE.

[0131] Figure 9 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 9 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 9 Two or more components shown may be implemented in a single component, or Figure 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The illustrated set of components (one or more) may be described as being executable by Figure 9 Another group of components is shown performing one or more functions.

[0132] Figure 10is a diagram illustrating an example 1000 of a hardware implementation for an apparatus 1005 employing a processing system 1010 according to the present disclosure. The apparatus 1005 may be a network node.

[0133] The processing system 1010 may be implemented using a bus architecture, generally represented by bus 1015. Bus 1015 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1010 and the overall design constraints. Bus 1015 links together various circuits including one or more processors and / or hardware components (represented by processor 1020, illustrated components, and computer-readable media / memory 1025). Bus 1015 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0134] The processing system 1010 may be coupled to a transceiver 1030. The transceiver 1030 is coupled to one or more antennas 1035. The transceiver 1030 provides components for communicating with various other devices via a transmission medium. The transceiver 1030 receives signals from the one or more antennas 1035, extracts information from the received signals, and provides the extracted information to the processing system 1010 (specifically, the receiving component 902). In addition, the transceiver 1030 receives information from the processing system 1010 (specifically, the transmitting component 904) and generates signals to be applied to the one or more antennas 1035 based at least in part on the received information.

[0135] The processing system 1010 includes a processor 1020 coupled to a computer-readable medium / memory 1025. The processor 1020 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1025. This software, when executed by the processor 1020, enables the processing system 1010 to perform the various functions described herein for any particular device. The computer-readable medium / memory 1025 may also be used to store data manipulated by the processor 1020 when executing the software. The processing system also includes at least one of the components illustrated. A component may be a software module running on the processor 1020, resident / stored in the computer-readable medium / memory 1025, one or more hardware modules coupled to the processor 1020, or some combination thereof.

[0136] In some aspects, the processing system 1010 may be a component of the network node 110 and may include the memory 242 and / or at least one of the TX MIMO processor 230, the RX processor 238, and / or the controller / processor 240. In some aspects, the apparatus 1005 for wireless communication includes: means for receiving, at a buffer of the UE, a buffer status report message regarding data for transmission from the UE, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status report table based at least in part on one or more parameter values; and / or means for communicating with the UE based at least in part on the contents of the buffer status report message. The aforementioned means may be one or more of the aforementioned components of the apparatus 900 and / or the processing system 1010 of the apparatus 1005 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1010 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned components may be the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240 configured to perform the functions and / or operations recited herein.

[0137] Figure 10 is provided as an example. Other examples can be combined with Figure 10 The examples described are different.

[0138] The following provides an overview of some aspects of the disclosure:

[0139] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving data for transmission at a buffer; and sending a buffer status report message regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer being encoded using a buffer status reporting table based at least in part on one or more parameter values.

[0140] Aspect 2: The method according to aspect 1 further comprises: receiving signaling identifying the one or more parameter values ​​via system information transmission or dedicated signaling transmission.

[0141] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the one or more parameter values ​​include at least one of the following: a minimum reported buffer status value, a maximum reported buffer status value, a coding error value, or the number of coding points of the buffer status report message.

[0142] Aspect 4: The method of any one of aspects 1 to 3, wherein the one or more parameter values ​​are selected from a set of possible parameter values ​​based at least in part on at least one of prediction data size, resolution, or coding rate.

[0143] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the buffer status reporting table is based at least in part on one or more static parameters, the one or more static parameters including at least one of a maximum number of step sizes or a maximum number of buffer status reporting tables.

[0144] Aspect 6: The method according to any one of aspects 1 to 5, further comprising: receiving configuration information associated with configuring the buffer status report table, wherein the configuration information is based on a per-logical channel group basis.

[0145] Aspect 7: The method according to Aspect 6, wherein the configuration information configures the buffer status reporting table of the logical channel group so that the range of the buffer status reporting table does not overlap with any other range of any other buffer status reporting table of the logical channel group.

[0146] Aspect 8: The method according to any one of aspects 1 to 7, wherein the buffer status report message includes information identifying the buffer status report table.

[0147] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the buffer status report message is a medium access control (MAC) control element, and the medium access control (MAC) control element includes at least one of the following: a logical channel control group indicator, a logical channel control group queue indicator, a buffer status report table indicator or a buffer size indicator.

[0148] Aspect 10: The method according to any one of aspects 1 to 9, wherein the information identifying the buffer status report table comprises a bitmap.

[0149] Aspect 11: A method of wireless communication performed by a network node, the method comprising: receiving a buffer status report message about data for transmission from a user equipment (UE) at a buffer of the UE, the buffer status report message including an indication of the buffer, the indication of the buffer being encoded using a buffer status report table based at least in part on one or more parameter values; and communicating with the UE based at least in part on the content of the buffer status report message.

[0150] Aspect 12: The method according to aspect 11, further comprising: receiving signaling identifying the one or more parameter values ​​via system information transmission or dedicated signaling transmission.

[0151] Aspect 13: A method according to any one of Aspects 11 to 12, wherein the one or more parameter values ​​include at least one of the following: a minimum reported buffer status value, a maximum reported buffer status value, a coding error value, or the number of coding points of the buffer status report message.

[0152] Aspect 14: The method of any one of aspects 11 to 13, wherein the one or more parameter values ​​are based at least in part on at least one of a prediction data size, a resolution, or an encoding rate.

[0153] Aspect 15: A method according to any one of Aspects 11 to 14, wherein the buffer status reporting table is based at least in part on one or more static parameters, the one or more static parameters including at least one of a maximum number of step sizes or a maximum number of buffer status reporting tables.

[0154] Aspect 16: The method according to any one of aspects 11 to 15, further comprising: sending configuration information associated with configuring the buffer status report table, wherein the configuration information is based on a per-logical channel group basis.

[0155] Aspect 17: The method according to Aspect 16, wherein the configuration information configures the buffer status reporting table of the logical channel group so that the range of the buffer status reporting table does not overlap with any other range of any other buffer status reporting table of the logical channel group.

[0156] Aspect 18: The method according to any one of aspects 11 to 17, wherein the buffer status report message includes information identifying the buffer status report table.

[0157] Aspect 19: A method according to any one of Aspects 11 to 18, wherein the buffer status report message is a medium access control (MAC) control element, and the medium access control (MAC) control element includes at least one of the following: a logical channel control group indicator, a logical channel control group queue indicator, a buffer status report table indicator or a buffer size indicator.

[0158] Aspect 20: The method according to any one of aspects 11 to 19, wherein the information identifying the buffer status report table comprises a bitmap.

[0159] Aspect 21: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in aspects 1 to 20.

[0160] Aspect 22: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 20.

[0161] Aspect 23: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 20.

[0162] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 20.

[0163] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 20.

[0164] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0165] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0166] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0167] Although the specific combination of features is described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other arrangement of a, b and c).

[0168] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "group" are intended to include one or more projects, and can be used interchangeably with "one or more". If only want to refer to a project, then use the phrase "only one" or similar terms. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving data for transmission at a buffer; as well as A buffer status report message is sent regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status reporting table based at least in part on one or more parameter values. 2 . The UE according to claim 1 , wherein the buffer status report message includes information identifying the buffer status report table. The UE according to claim 2 , wherein the information identifying the buffer status report table comprises a bitmap.

4. The UE of claim 1 , wherein the one or more processors are further configured to: Signaling identifying the one or more parameter values ​​is received via system information transmission or dedicated signaling transmission.

5. The UE according to claim 1 , wherein the one or more parameter values ​​include at least one of the following: Minimum report buffer status value, Maximum report buffer status value, Encoding error value, or The number of code points of the buffer status report message.

6. The UE of claim 1, wherein the one or more parameter values ​​are selected from a set of possible parameter values ​​based at least in part on at least one of predicted data size, resolution, or coding rate.

7. The UE of claim 1 , wherein the buffer status reporting table is based at least in part on one or more static parameters, the one or more static parameters comprising at least one of a maximum number of step sizes or a maximum number of buffer status reporting tables.

8. The UE of claim 1 , wherein the one or more processors are further configured to: Configuration information associated with configuring the buffer status reporting table is received, wherein the configuration information is on a per-logical channel group basis.

9. The UE according to claim 8, wherein the configuration information configures the buffer status reporting table of a logical channel group so that a range of the buffer status reporting table does not overlap with any other range of any other buffer status reporting table of the logical channel group.

10. The UE of claim 1 , wherein the buffer status report message is a medium access control (MAC) control element, the medium access control (MAC) control element comprising at least one of the following: Logical channel control group indicator, Logical Channel Control Group Queue Indicator, Buffer Status Report Table indicator, or Buffer size indicator.

11. The UE of claim 1 , wherein the UE is configured to select the buffer status reporting table from a set of available buffer status reporting tables based at least in part on characteristics of the buffer.

12. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving, at a buffer of a user equipment (UE), a buffer status report message from the UE regarding data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status reporting table based at least in part on one or more parameter values; and Communicating with the UE is performed based at least in part on the contents of the buffer status report message.

13. The network node according to claim 12, wherein the buffer status report message includes information identifying the buffer status report table.

14. The network node of claim 13, wherein the information identifying the buffer status report table comprises a bitmap.

15. The network node of claim 12, wherein the one or more processors are further configured to: Signaling identifying the one or more parameter values ​​is sent via system information transmission or dedicated signaling transmission.

16. The network node of claim 12, wherein the one or more parameter values ​​include at least one of: Minimum report buffer status value, Maximum report buffer status value, Encoding error value, or The number of code points of the buffer status report message.

17. The network node of claim 12, wherein the one or more parameter values ​​are based at least in part on at least one of a predicted data size, a resolution, or a coding rate.

18. The network node of claim 12, wherein the buffer status reporting table is based at least in part on one or more static parameters, the one or more static parameters comprising at least one of a maximum number of step sizes or a maximum number of buffer status reporting tables.

19. The network node of claim 12, wherein the one or more processors are further configured to: Configuration information associated with configuring the buffer status report table is sent, wherein the configuration information is based on a per logical channel group basis.

20. The network node according to claim 19, wherein the configuration information configures the buffer status reporting table of a logical channel group so that a range of the buffer status reporting table does not overlap with any other range of any other buffer status reporting table of the logical channel group.

21. The network node of claim 12, wherein the buffer status report message is a medium access control (MAC) control element, the medium access control (MAC) control element comprising at least one of: Logical channel control group indicator, Logical Channel Control Group Queue Indicator, Buffer Status Report Table indicator, or Buffer size indicator.

22. The network node of claim 12, wherein the buffer status reporting table is selected from a set of available buffer status reporting tables based at least in part on characteristics of the buffer.

23. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving data for transmission at a buffer; as well as A buffer status report message is sent regarding the data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status reporting table based at least in part on one or more parameter values.

24. The method of claim 23, wherein the buffer status report message includes information identifying the buffer status report table.

25. The method according to claim 23, further comprising: Signaling identifying the one or more parameter values ​​is received via system information transmission or dedicated signaling transmission.

26. The method of claim 23, wherein the one or more parameter values ​​include at least one of: Minimum report buffer status value, Maximum report buffer status value, Encoding error value, or The number of code points of the buffer status report message.

27. The method of claim 23, wherein the one or more parameter values ​​are selected from a set of possible parameter values ​​based at least in part on at least one of prediction data size, resolution, or encoding rate.

28. The method of claim 23, wherein the buffer status reporting table is based at least in part on one or more static parameters, the one or more static parameters comprising at least one of a maximum number of step sizes or a maximum number of buffer status reporting tables.

29. A method of wireless communication performed by a network node, the method comprising: receiving, at a buffer of a user equipment (UE), a buffer status report message from the UE regarding data for transmission, the buffer status report message including an indication of the buffer, the indication of the buffer encoded using a buffer status reporting table based at least in part on one or more parameter values; and Communicating with the UE is performed based at least in part on the contents of the buffer status report message.

30. The method of claim 29, wherein the buffer status report message includes information identifying the buffer status report table.

Images