Implicit BSR format adapted based on size of TB carrying that bsr

Abstract

A method, apparatus, and computer program product are provided. The method includes determining a size of a physical uplink channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR). The method further includes selecting a size profile-based BSR format based on the size of the PUSCH allocation of the TB carrying the BSR, where selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, where a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. The method includes transmitting, to a network node, the BSR in the selected size profile-based BSR format.

Description

IMPLICIT BSR FORMAT ADAPTED BASED ON SIZE OF TB CARRYING THAT BSRTECHNOLOGICAL FIELD

[0001] Example embodiments relate generally to a buffer status report (BSR) format and, more particularly, to a BSR format adapted based on a size of a transport block (TB) carrying that BSRBACKGROUND

[0002] Availability of uplink traffic is signaled to a network node via a buffer status report (BSR), which is a medium access control element (MAC CE) that carries the information of how much data is in the user equipment (UE) buffer to be sent out. 4G long term evolution (LTE) and 5G new radio (NR) standards for informing uplink resource allocation by the network support BSRs. The BSR allows a network to allocate uplink (UL) resources via a UL grant when the UE has something to transmit and attempts to limit the amount of over-allocation by granting only what the UE needs, so as to limit the amount NW grants resources granted for UL bytes in excess of what the UE has to transmit.

[0003] There is uncertainty when a base station allocates resources as, for example, a buffer size field of the BSR MAC CE may be only 5 or 8 bits long, depending on if it is a short or one of the long formats. Instead of reporting bytes in a buffer, the UE uses pre-defined tables to discretize the actual buffer status (BS = number of bytes in the buffer) to an index from the tables, where each index is associated with a rounded-up version of the true bytes in the buffer. As such, the base station only works with an upper limit. For NR, formats for BSR reporting by the UE are specified in section 6.1.3.1 of 3GPP TS 38.321, one of which is shown in Table 1 below.< < < < < < < < < < < < < < < < < < < < < < < < < < << < < >Table 1

[0004] In some circumstances, if a logical channel group (LCG) has larger amounts of higher priority data, it can be implicitly known by the UE and network node (NW) that the LCG borrows additional bits from other later lower priority LCGs which are reporting smaller amounts of data. If the allocation is not large enough to carry the BSR report, it is known to use a different BSR format. For example, if the size of the allocation is smaller, a short or truncated BSR may be provided instead of a long BSR. As such, the (short or truncated) format selected depends on the size of the physical uplink shared channel PUSCH allocation.BRIEF SUMMARY

[0005] In one or more embodiments, a user equipment (120) for wireless communication is provided, including at least one processor and at least one memory storing instructions thereon that, when executed by the at least one processor, cause the user equipment (120) to determine (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) is further caused to select (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile- based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group.

[0006] In one or more embodiments, a network node (112) for wireless communication is provided, including at least one processor and at least one memory storing instructions thereon that, when executed by the at least one processor, cause the network node (112) to transmit (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. The network node (112) is further caused to receive (612), from the user equipment (120), the BSR (612a) in a selected size profilebased BSR format.

[0007] In one or more embodiments, a user equipment (120) for wireless communication is provided, including means for determining (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) further includes means for selecting (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. In one or more embodiments, the user equipment (120) further includes means for transmitting (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0008] In one or more embodiments, a network node (112) for wireless communication is provided, including means for transmitting (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. The network node (112) further includes means for receiving (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.

[0009] In one or more embodiments, a computer implemented method is provided that is performed by a user equipment (120) and includes determining (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the method further includes selecting (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. In one or more embodiments, the method further includes transmitting (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0010] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes transmitting (608), to a user equipment (120), asecond message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. The network node (112) further includes receiving (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.

[0011] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (120), cause the user equipment (120) to determine (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) is further caused to select (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. In one or more embodiments, the user equipment (120) is further caused to transmit (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0012] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause the network node (112) to transmit (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile- based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profilebased BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. The network node (112) is further caused to receive (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.

[0013] In one or more embodiments, a user equipment (120) for wireless communication is provided, including at least one processor and at least one memory storing instructions thereonthat, when executed by the at least one processor, cause the user equipment (120) to determine (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) is further caused to select (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile- based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. In one or more embodiments, the user equipment (120) is further caused to transmit (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0014] In one or more embodiments, a network node (112) for wireless communication is provided, including at least one processor and at least one memory storing instructions thereon that, when executed by the at least one processor, cause the network node (112) to transmit (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. The network node (112) is further caused to receive (612), from the user equipment (120), the BSR (612a) in a selected size profilebased BSR format.

[0015] In one or more embodiments, a user equipment (120) for wireless communication is provided, including means for determining (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) further includes means for selecting (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. In one or more embodiments, the user equipment (120) further includes means for transmitting (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0016] In one or more embodiments, a network node (112) for wireless communication is provided, including means for transmitting (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-basedbuffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. The network node (112) further includes means for receiving (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.

[0017] In one or more embodiments, a computer implemented method is provided that is performed by a user equipment (120) and includes determining (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the method further includes selecting (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. In one or more embodiments, the method further includes transmitting (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0018] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes transmitting (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. The network node (112) further includes receiving (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.

[0019] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (120), cause the user equipment (120) to determine (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) is further caused to select (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. In one or more embodiments, the user equipment(120) is further caused to transmit (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0020] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause the network node (112) to transmit (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profilebased BSR format comprises a bin size selection based on a likely range of buffer size levels reported. The network node (112) is further caused to receive (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Having thus described certain example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and where:

[0022] FIG. 1 is a communication network to which example embodiments disclosed herein may be applied;

[0023] FIG. 2 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure;

[0024] FIG. 3 depicts a BSR value table graphing packet size against traffic model probability distribution in accordance with the prior art;

[0025] FIGS. 4A-4C depict BSR fields in accordance with the prior art;

[0026] FIG. 5 illustrates a first size profile BSR format and an alternate size profile BSR format in accordance with example embodiments of the present disclosure;

[0027] FIG. 6 illustrates a signaling diagram of a user equipment sending a BSR of a size profile- based BSR format to a network node in accordance with example embodiments of the present disclosure;

[0028] FIG. 7 illustrates a flow chart of a user equipment sending a BSR of a size profile-based BSR format to a network node in accordance with example embodiments of the present disclosure;

[0029] FIG. 8 illustrates bit allocations to different logical channel groups (LCGs) in accordance with example embodiments of the present disclosure;

[0030] FIG. 9 illustrates a transport block dependency in the context of extended reality traffic in uplink in accordance with example embodiments of the present disclosure;

[0031] FIG. 10 illustrates a relationship between buffer status report bytes reported and physical uplink channel allocation size in accordance with example embodiments of the present disclosure;

[0032] FIG. 11 illustrates a flowchart of a method performed by a user equipment to transmit a BSR in a selected size profile-based BSR format in accordance with example embodiments of the present disclosure; and

[0033] FIG. 12 illustrates a flowchart of a method performed by a network node to determine, based whether a user equipment should select a size profile-based BSR format based on the size of a PUSCH allocation of a TB carrying a BSR in accordance with example embodiments of the present disclosure.DETAILED DESCRIPTION

[0034] The following embodiments are exemplary. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Further, when a particular feature, structure, or characteristic is described in connection of an embodiment, it is within the knowledge of one skilled in the art to apply such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. It shall be understood that although the terms “first,” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0035] For the purposes of the present disclosure, the phrases “at least one of A or B”, “at least one of A and B”, and “A and / or B” means (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0036] Embodiments described may be implemented in a communication network, such as any of the following radio access technologies (RATs): Worldwide Interoperability for Micro- wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE- Advanced, and enhanced LTE (eLTE), 5G (also called NR), or any future RAT such as 6G. Moreover, communication within the communication network may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT-s-OFDM).

[0037] As used herein, the term “network device” or “network node” refers to a node in a communication network via which user equipment may access the network and / or which is capable of controlling radio communication and managing radio resources within a cell. The network node or network device may be referred to as a base station (BS), an access point (AP) or an access node. The network device may be, depending on the applied technology, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node, a nonterrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, or an aircraft network device.

[0038] Moreover, in connection of split radio access network (RAN), the network device may refer to a centralized unit (CU) of a base station and / or a distributed unit (DU) of a base station. An interface between CU and DU may be referred to as an Fl interface in NR. In the split RAN architecture, node operations may be carried out, at least partly, in the central / centralized unit, CU, (e.g. server, host or node) operationally coupled to the DU, (e.g. a radio head / node). OneCU may control one or more DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some embodiments, the DUs may comprise e.g. a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the CU may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layers. Other functional splits are possible too. In practice, any processing task may be performed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may depend on the applied implementation.

[0039] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example, a terminal device may be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may include a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehiclemounted wireless terminal devices, USB dongles, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like.

[0040] A term “resource”, as used herein, may refer to radio resources in time domain, in frequency domain, in space domain, and / or in code domain. Some examples of resources include e.g. a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a sub-carrier, a beam, etc. The term “transmission” and / or “reception” may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on radio resources.

[0041] Fig. 1 illustrates an example of a communication network to which examples disclosed herein may be applied. The communication network or a cellular communication network may comprise a network node 110 providing one or more cells, such as cell 100, and a network node 112 providing one or more other cells, such as cell 102. Each cell may be, e.g., a macro cell, amicro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding access node.

[0042] The network node 110 may provide a user equipment (UE) 120 (one or more UEs) with wireless access to the communication network. The wireless access may comprise downlink (DL) communication from the network node to the UE 120 and uplink (UL) communication from the UE 120 to the network node. Examples of uplink channels comprise physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channels comprise physical downlink control channel (PDCCH) for transmitting control information and physical downlink shared channel (PDSCH) for transmitting data towards the user equipment.

[0043] There may be a plurality of UEs 120, 122 in the system. Each of them may be served by the same or by different network nodes 110, 112. UE may be configured with dual connectivity (DC), wherein the UE, e.g. UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to-device (D2D) communication interface is established between them via a so-called sidelink (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0044] In the case of multiple network nodes in the communication network, the network nodes may be connected to each other via an interface. LTE specifications call such an interface as X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes may be called Xn interface.

[0045] The network nodes 110 and 112 may be further connected via another interface to a core network 116 of the communication network. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise e.g. a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). The 5G core may comprise e.g. an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other functions. The AMF may handle termination of non-access stratum (NAS) signalling, NAS ciphering & integrity protection,registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example.

[0046] Fig. 2 shows, by way of example, a block diagram of an apparatus 10. The apparatus 10 comprises, for example, at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, cause the apparatus 10 at least to perform the method or methods as disclosed herein, and any of the embodiments thereof. In an example, the at least one memory and the instructions (e.g. a computer program code, software), are configured, with the at least one processor, to cause the apparatus 10 to perform the method or methods as disclosed herein, and any of the embodiments thereof.

[0047] A processor 12 may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with example embodiments described herein. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and / or digital circuitry, and (b) combinations of hardware circuits and software, such as, as applicable: (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a user equipment, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0048] The memory 14 may be implemented using any suitable data storage technology. The memory may comprise a database for storing data. The memory 14 may be at least in part external to apparatus 10 but accessible to apparatus 10.

[0049] The instructions 15 may be comprised in a computer readable medium or a non- transitory computer readable medium. A term non-transitory, as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. random access memory, RAM, vs. read only memory, ROM).

[0050] For example, the apparatus 10 is a terminal device, such as the UE of Fig. 1. As another example, the apparatus is comprised in such a terminal device, e.g. as a chipset configured to control the terminal device. The apparatus 10 may be caused or configured to perform at least the method of Figs. 11-12 and / or any one or more of the embodiments described.

[0051] As another example, the apparatus 10 is a network node, e.g. the network node of Fig. 1. In another embodiment, the apparatus is comprised in such a network node, e.g. as a chipset configured to control the network node. The apparatus 10 may be caused or configured to perform at least the method of Figs. 11-12 and / or any one or more of the embodiments described.

[0052] The apparatus may comprise one or more entities of any of protocol layers, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity or a PHY entity. In some embodiments, the entity is configured to perform at least the method of Fig. 11 or Fig. 12, and / or any one or more of the embodiments described.

[0053] The apparatus 10 comprises a radio interface 16. The radio interface 16 may provide the apparatus 10 with communication capabilities. The radio interface 16 may comprise a receiver configured to receive information in accordance with at least one cellular or non-cellular standard. The radio interface 16 may comprise a transmitter configured to transmit information in accordance with at least one cellular or non-cellular standard. The receiver may comprise more than one receiver. The transmitter may comprise more than one transmitter. The radio interface 16 may comprise a transceiver configured to receive and transmit information in accordance with at least one cellular or non-cellular standard. The transceiver may comprise more than one transceiver.

[0054] The apparatus 10 may comprise a user interface 18 comprising, for example, at least one of a keypad, a microphone, a touch display, a display, a speaker, etc. The user interface 18 maybe used to control the apparatus by the user. The user interface 18 may be external to the apparatus 10. For example, the apparatus 10 may be connected to another device, such as a computer, either via wireless or wired connection, and the apparatus 10 is controlled by the user via the computer.

[0055] In an embodiment, at least some of the processes described herein may be carried out by an apparatus comprising means for carrying out at least some of the described processes. Means for performing method steps as disclosed herein may include software and / or hardware components of the apparatus 10. For example, the at least one processor 12, the memory 14, and the computer program code form means for carrying out the method or methods as disclosed herein, and any of the embodiments thereof. As used herein the term “means” is to be construed in singular form, i.e. referring to a single element, or in plural form, i.e. referring to a combination of single elements. Therefore, terminology “means for [performing A, B, C]”, is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C. Further, terminology “means for performing A, means for performing B, means for performing C” is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.

[0056] Turning now to FIG. 3, a BSR value table 300 graphing packet size against traffic model probability distribution is provided in accordance with the prior art. An alternate BSR format is used where that BSR format is optimized to traffic with a certain size profile. A bell curve around 21.5 KB is expected for that logical channel group based on user equipment assistance information.

[0057] Turning now to FIG. 4A-4C, example buffer status report formats are illustrated in accordance with the prior art. FIG. 4A depicts a short BSR 402 with a short truncated BSR MAC CE. FIG. 4B depicts a long BSR 404 with a long truncated BSR and pre-emptive BSR MAC CE. FIG. 4C depicts a refined long BSR MAC CE 406. Traditionally, the network groups different quality of service flows of similar requirements into an LCG Unrelated quality of service flows can end up in the same LCG. Quality of service flows for the same service, but with different quality requirements, can end up in different LCGs. For example, extended reality services havevideo, audio, and pose information all related to each other and to the one extended reality service, but they require very different quality of service.

[0058] In some embodiments of the present disclosure, refined long BSR targets a select subset of extended reality traffic parameters from about 10 Mbps@ 120 FPS to 150 Mbps@ 24 FPS. LCGs can be selectively enabled to support this table and in the case where the buffer status value is outside the new refined long range of the table, the BSR is reported with the legacy long BSR table. In some examples, the average error rate of a new refined long BSR table is 1% for a realistic uplink extended reality video traffic and 3.1% for a legacy 8 bit long BSR table.However, Protocol data units (PDUs) can accumulate in the user equipment’s buffer, leading to buffer status values outside of the refined long table scope, resulting in fallback reports with a 3.1% error rate.

[0059] BSR refinement yields benefits to systems. Full dynamic BSR table generation based on gNB and UE signaling is too slow, a user equipment 120 would not have enough time and computational resources to generate new tables on time. Defining multiple static BSR tables with different resolutions or ranges requires excessive signaling, constantly updating the two ends of the link, which table is in use. A compromise solution for only one extra table is the introduction of refined long BSR, where BSR MAC CEs were updated with the BT field to indicate the table. New tables achieve better granularity by specifically targeting some data ranges, and it is not universally applicable as the legacy table. Example embodiments herein include an implicit table identification method based entirely on basic and already available information at both the UE and the gNB.

[0060] In example embodiments of the present disclosure, a size profile is used to determine a BSR table and / or a redistribution of buffer status bits among LCGs used by the UE and NW in a first allocation (for a first LCG), where that size profile (and thus the BSR table and / or the redistribution of BS bits among LCGs) is based on the size of that first allocation (for a first LCG).

[0061] In example embodiments herein, a user equipment and network node both implicitly switch to use an alternate size profile based BSR format (i.e., size profile used to determine the BSR table and / or the redistribution of BS bits among LCGs which is used by the UE and NW in a first allocation (for a first LCG)) if the BSR is being transmitted within a larger PUSCH allocation which was granted for that LCG. In some examples, this implicitly indicates the sizeprofile based BSR table and LCG bit redistribution while avoiding the additional real time signaling overhead to explicitly indicate that change. In some examples, based on radio resource control (RRC) pre-configured capabilities and thresholds, the NW can implicitly indicate the size profile based BSR determination in a generic manner so that any traffic type can have both a full range of possible values as well as adaptive granularity based on its size profile so that BSR accuracy and effective granularity is improved.

[0062] In some examples, a new UE capability and configuration is introduced to configure LCG specific behavior enabling a refined BSR based on size profile as inferred from the size of an allocation. In some examples, a TB size (and LCG specific aspect of the grant for that TB) is known by both sides (i.e., the UE and NW) from the DCI allocating that PUSCH allocation, the size profile based BSR can be implicitly known by the gNB on receiving the UL TB where the size profile based BSR depends on the TB size. In some examples, the size profile based BSR (and its buffer status field in particular) is linked to the TB carrying the BSR MAC CE.

[0063] Turning now to FIG. 5, a first size profile-based BSR format 508 and an alternate size profile-based BSR format 504 is depicted in accordance with example embodiments of the present disclosure. In one or more embodiments, the first size profile-based BSR format 508 is a baseline size profile- based BSR format. In some examples, a TB size is a response to values reported in the BSR in a previous TB. In some examples, initial TBs allocated are smaller in response to a scheduling request (SR) specifically targeting the sending of the BSR. In some examples, the BSR value 508 or 504 is the amount reported to the network node which will influence the size of the next PUSCH allocation. In some examples, the size profile-based BSR used inside the first transport block depends on the size of the current PUSCH allocation 502 or 506 which is carrying that BSR. For example, a larger PUSCH allocation 502 will carry an alternate size profile-based BSR format 504 and a smaller PUSCH allocation 506 will carry a first (or baseline) size profile-based BSR format 508.

[0064] In some examples, the size of the PUSCH allocation 502 / 506 has some relation to values reported in a subsequent BSR which is carried in that PUSCH allocation. For example, a greater amount of data (e.g., PUSCH allocation 502) leads to an expectation of more data later and a smaller amount of data (e.g., PUSCH allocation 506) leads to an expectation of less data later. When an example first TB carries a BSR, a larger first TB size effectively informs a networknode that a next TB to be allocated should be somewhat similar and / or proportional to the first already-granted TB, such that a larger size profile based BSR report is more likely appropriate.

[0065] In some examples, a larger PUSCH allocation 502 leads to an expectation of more data later, as reported by alternate size profile BSR 504. In some examples, this leads to more accurate buffer status information for the next TB. For example, this leads to less buffer status overhead and less buffer status quantization error. In some examples, a smaller PUSCH allocation 506 (due to, e.g., lighter traffic, poor radio frequency, heavy congestion, and / or the like), the size profile based BSR used is a first or baseline size profile BSR 508.

[0066] Turning now to FIG. 6, a signaling diagram of a user equipment sending a BSR of a size profile- based BSR format to a network node is provided in accordance with example embodiments of the present disclosure.

[0067] In one or more embodiments, at operation 602, the user equipment 120 transmits a first message 602a to the network node 112 reporting its capabilities 602b of deploying size profile based BSR selection. For example, the user equipment 120 reports its capabilities 602b of redistributing buffer status bits among LCGs. In some examples, the user equipment 120 reports its capabilities of tracking TB size and deploying size profile based BSR selection based on the TB size. In some examples, the first message 602a may be sent over radio resource control (RRC), medium access control (MAC) control elements (CEs), or the like.

[0068] In one or more embodiments, at operation 604, the network node 112 gathers traffic information. In some examples, the traffic information is necessary for BSR size profile schemes. In some examples, the network node 112 may decide whether the user equipment should use different size profile BSR formats with RRC based on the traffic information at step 606. In some examples, network node 112 may differentiate between smaller traffic allocations and larger allocations with a threshold. In some examples, the traffic information collected includes user assisted info (UAI) signaling 604a from the user equipment 110 to the network node 112. The UAI signaling 604a indicates a BSR size profile based on traffic information expected to be reported over the BSR for a logical channel group. The UAI signaling may indicate whether the BSR is in a smaller or larger PUSCH allocation. In some examples, the traffic information collected includes information signaled from core network 116 (e.g., protocol data unit (PDU) session information 604b). In some examples, the network node 112 itself tracks traffic information and evaluates it at operation 605. For example, the network node 112 mayobserve size profile based BSR values reported in smaller allocations and larger allocations. The network node 112 may observe size profile base BSR values for a particular cell, time of day, international mobile equipment identity - software version (IMEISV), and / or the like. The network node 112 may analyze what tracking size profile based BSR formats would be best for BSR values in smaller and larger allocations (e.g., above and below a threshold).

[0069] In one or more embodiments, at operation 606, the network node 112 evaluates the capabilities of user equipment 120 and the expected traffic. In some examples, network node 112 decides whether a TB size tracking size profile based BSR format selection scheme is to be deployed. For example, the network node 112 may determine a conditional threshold, such that user equipment 120 will report using different size profile-based BSR formats for allocations above and below the conditional threshold. In some examples, the network node 112 decides to enable implicit determination of the size profile-based BSR format.

[0070] In one or more embodiments, at operation 608, the network node 112, a second message 608a configuring the user equipment 120 to automatically select a size profile-based BSR format based on PUSCH allocation size. In some examples, network node enables a TB size tracking BSR format selection scheme for determining a size profile- based BSR format. In some examples, the second message 608a is transmitted over RRC, MAC CE, and / or the like. In some examples, the second message 608a may include an enablement flag, scheme selection among UE supported options, a logical channel grouping indication, one or more possible TB size thresholds, and / or the like.

[0071] In one or more embodiments, at operation 610, the user equipment 120 selects a size profile-based BSR format and prepares the BSR. In some examples, the size profile-based BSR format is determined implicitly. For a smaller allocation, user equipment 120 may select a first or baseline size profile- based BSR report format. For a larger allocation, user equipment 120 may select an alternate size profile- based BSR report format.

[0072] In some examples, the BSR is triggered and at least partially prepared before a TB is granted, so that the BSR format is not known at the time of triggering. In some examples, the user equipment 110 avoids some implementation challenges by preparing multiple different BSR reports for multiple size profiles at the time of triggering, and then selects the appropriate one after the size of the PUSCH allocation is known. For example, a header may be prepared in advance, and a final value of the buffer status field is set based on a specific table size. In someexamples, the exact time of updating a buffer status value of a MAC CE is left up to user equipment implementation. In some examples, user equipment 120 may do a buffer status field update just before TB sending, capturing any late data arrivals in the buffer. In other examples, user equipment 120 may lock the value in advance due to time limitations. In some examples, an increase of table sizes increases the severity of time constraints, even when using binary search with O(log n) complexity. In some examples, each operation is one more clock cycle.

[0073] In some examples, a search space may be limited when performing a secondary buffer status update or a TB size driven buffer status field refinement. For example, a user equipment 120 may have BSR reporting triggered without a granted TB and perform legacy index search in a legacy 8 bit table. Upon finding an index corresponding to a buffer status value when a UL grant arrives with some TB size that dictates BS field size of 10 bits (finer resolution), the secondary index search can begin from the index of the larger table reducing necessary operations of the binary search.

[0074] In one or more embodiments, at operation 612, the user equipment 120 sends a BSR 612a of the selected size profile-based BSR format. In some examples, the BSR is sent as an extension to a MAC CE. In some examples, the BSR is sent in response to a TB being granted via a DCI at optional operation 611.

[0075] In one or more embodiments, at operation 614, the network node 112 decodes the BSR 612a using the implicitly determined size profile for that BSR report, i.e., with the TB size tracking logic. In some examples, the network node 112 parses a received BSR MAC CE and extracts buffer status information from the selected BSR format (i.e., the first or baseline size profile- based BSR format or the alternate size profile-based BSR format). In some examples, network node 112 determines the selected BSR format by looking at the size of the PUSCH allocation in bytes or physical resource blocks (PRBs) received from the UE for a logical channel group. If the PUSCH allocation being decoded for a logical channel group is smaller than 3 KB, network node 112 may conclude that the user equipment 120 did not use the alternate size profile-based BSR format. If the PUSCH allocation being decoded for a logical channel group is larger than 3KB (and the allocation was for the logical channel group associated with the new RRC configuration transmitted at operation 608), the network node 112 determines that the user equipment 120 used the alternate size profile-based BSR format.

[0076] Turning now to FIG. 7, a flowchart of a user equipment determining whether to use a BSR of a size profile-based BSR format is provided in accordance with example embodiments of the present disclosure. Example steps 602-608 described below are identical to those described with respect to FIG. 6.

[0077] In one or more embodiments, at operation 602, the user equipment 120 transmits a first message 602a to the network node 112 reporting its capabilities 602b of deploying size profile based BSR selection. For example, the user equipment 120 reports its capabilities 602b of redistributing buffer status bits among LCGs. In some examples, the user equipment 120 reports its capabilities of tracking TB size and deploying size profile based BSR selection based on the TB size. In some examples, the first message 602a may be sent over radio resource control (RRC), medium access control (MAC) control elements (CEs), or the like.

[0078] In one or more embodiments, at operation 604, the network node 112 gathers traffic information. In some examples, the traffic information is necessary for BSR size profile schemes. In some examples, the network node 112 may decide whether the user equipment should use different size profile BSR formats with RRC based on the traffic information at step 606. In some examples, network node 112 may differentiate between smaller traffic allocations and larger allocations with a threshold. In some examples, the traffic information collected includes user assisted info (UAI) signaling 604a from the user equipment 110 to the network node 112. The UAI signaling 604a indicates a BSR size profile based on traffic information expected to be reported over the BSR for a logical channel group. The UAI signaling may indicate whether the BSR is in a smaller or larger PUSCH allocation. In some examples, the traffic information collected includes information signaled from core network 116 (e.g., protocol data unit (PDU) session information 604b). In some examples, the network node 112 itself tracks traffic information and evaluates it at operation 605. For example, the network node 112 may observe size profile based BSR values reported in smaller allocations and larger allocations. The network node 112 may observe size profile base BSR values for a particular cell, time of day, international mobile equipment identity - software version (IMEISV), and / or the like. The network node 112 may analyze what tracking size profile based BSR formats would be best for BSR values in smaller and larger allocations (e.g., above and below a threshold).

[0079] In one or more embodiments, at operation 606, the network node 112 evaluates the capabilities of user equipment 120 and the expected traffic. In some examples, network node 112decides whether a TB size tracking size profile based BSR format selection scheme is to be deployed. For example, the network node 112 may determine a conditional threshold, such that user equipment 120 will report using different size profile-based BSR formats for allocations above and below the conditional threshold. In some examples, the network node 112 decides to enable implicit determination of the size profile-based BSR format.

[0080] In one or more embodiments, at operation 608, the network node 112, a second message 608a configuring the user equipment 120 to automatically select a size profile-based BSR format based on PUSCH allocation size. In some examples, network node enables a TB size tracking BSR format selection scheme for determining a size profile-based BSR format. In some examples, the second message 608a is transmitted over RRC, MAC CE, and / or the like. In some examples, the second message 608a may include an enablement flag, scheme selection among UE supported options, a logical channel grouping indication, one or more possible TB size thresholds, and / or the like.

[0081] In one or more embodiments, at operation 702, the user equipment 120 decides whether to use an alternate size profile-based BSR format. In some examples, the user equipment 120 determines whether to use the alternate size profile-based BSR format based on whether a PUSCH allocation 702a size is above or below a threshold 702b. In some examples, more than two size profile-based BSR formats are selected from. In some examples, the PUSCH allocation 702a size is used as a parameter in an equation used to generate a BSR bin size formatting table.

[0082] If the PUSCH allocation 702a size is above the threshold 702b, the user equipment 120 may determine to use a first (i.e., normal or baseline) size profile-based BSR format at operation 704. In some examples, a first number of bits are used for a logical channel group. In some examples, a baseline equation is used optimized for the bell curve of FIG. 3 for a smaller volume of traffic. In some examples, a first piecewise linear equation is used (i.e., an equation composed of a series of linear lines).

[0083] If the PUSCH allocation 702a size is below the threshold 702b, the user equipment 120 may determine to use an alternate size profile-based BSR format at operation 706. In some examples, a greater number of bits than the first number of bits are used for a logical channel group (e.g., by using a secondary subfield), and less bits are used for a different logical channel group. In some examples, an equation is used optimized for a bell curve shifted to the rightcompared to the bell curve of FIG. 3. In some examples, a second piecewise linear equation is used.

[0084] In some examples, selecting the baseline size profile-based BSR format and the alternate size profile-based BSR format includes a bin sizing / table selection and / or a number of bits per logical channel group selection in a BSR format based on the size profile, which is based on TB size and the logical channel group indicating in downlink control information granting that TB. In some embodiments, bin sizing / table selection refers to making bins be smaller if those bins are for reporting a more likely range of buffer size levels reported. In some examples, number of bits per logical channel group is described below with respect to FIG. 8.

[0085] Turning now to FIG. 8, example bit allocations to different logical channel groups (LCGs) 802 and 804 are provided in accordance with example embodiments of the present disclosure. In one or more embodiments, logical channel group 804 is allocated less bits to report its buffer status value, so that logical channel group 802 may be allocated more bits in second subfield 806 to report its buffer status value. In some embodiments, logical channel group 802 is allocated more bits because its TB size is larger and a downlink control information (DCI) for that TB was for a first logical channel group, so that user equipment 120 and network node 112 expect logical channel group 802 to have larger buffer size levels to report and / or a larger range of buffer size levels to report (i.e., a “larger” buffer size profile is expected). In some examples, a buffer status report quantization overhead is incurred when a PUSCH allocation is large enough to clear a user equipment buffer of remaining bytes which were last reported by the last BSR. In some examples, the BSR quantization overhead is not incurred when the PUSCH allocation is for only a portion of the remaining bytes which were last reported by the last BSR.

[0086] Turning now to FIG. 9, a transport block dependency in the context of extended reality traffic in uplink is provided in accordance with example embodiments of the present disclosure. In some examples, a number used to report a logical channel group are shifted to a logical channel group with a larger expected size profile. In some examples, UL traffic may be 10 Mbps video traffic with truncated Gaussian distribution with typical 60 frames per second rate (about 16.67 ms between frames). In some examples, pose information is included and modeled as 100 byte packets every 4 ms, which may be a significant difference in data volume.

[0087] In one or more embodiments, as shown in FIG. 9, 10 Mbps extended reality video uplink traffic is ongoing. In some examples, the mean frame size is 20-25K bytes, and such size frame arrives as shown at 902 of FIG. 9, and that the current channel capacity allows for an approximately even distribution of TBs over the next few milliseconds of about 5K bytes. In some examples, a 25K bytes frame is sent in 5 transmissions of about 5K bytes. In some examples, pose information 904 is sent every 4 ms with 100 bytes each. For TBs 906a, 906c, and 906d, 100 bytes of pose 904 is insignificant amount of data compared to 5K bytes of video. However, the pose 904 arrival being critical control information (and in some examples requiring different quality of service than the video) is isolated in a separate, higher priority logical channel group or logical channel, therefore triggering a BSRto be sent in each of uplink slots 908a-d. In some examples, TB 906e is small and carries only pose information 904. In some examples, this scheme is enabled for video logical channel groups.

[0088] In one or more embodiments, a threshold TB size is configured so that TBs above the threshold would report with a 10-bit BSR table, while TBs below the threshold will report with an 8-bit table. In some examples, the threshold is 4500 bytes. A 10-bit table may be populated with the same exponential distribution as an 8-bit table but for more bins. In some examples, a network node 112 has a reasonable prediction and grants TB1 in advance.

[0089] Under legacy behavior (user equipment always uses 8-bit table), for TB 906a, video logical channel group has 20K bytes and reports index 121 (20181 bytes). For TB 906c, video logical channel group has 10K bytes and reports index 110 (10104 bytes). For TB 906d, video logical channel group has 5K bytes and reports index 99 (5059 bytes). For TB 906e, video logical channel group has 0 bytes left but the allocation request is 5059 bytes- an overhead of 59 bytes. In all cases (906a, 906c, 906d, and 906e), the pose logical channel group will report index 37 (103) - 4x3 bytes = 12 bytes. In capacity limited networks, the last allocation incurs actual overhead due to BSR inaccuracy and only the BSR sent in TB 5 is relevant.

[0090] In example embodiments of the present disclosure, a user equipment uses 10-bit BSR. In some examples, focusing on TB 906e for a 10-bit BSR, the value reported is 5056, an overhead of 56 bytes. In some examples, in capacity limited scenarios, a buffer builds up and large quantization errors in the BSR do not lead to realized TB overhead until the last TB to be transmitted, emptying the buffer. In some examples, the persistent pose update triggering new BSRs serves as a periodic refinement towards the last TB. In some examples with larger frameand TB sizes (e.g., 250K bytes frame and 50K bytes per TB), TB 906e will be 50272 (index 608) bytes in a 10-bit table, compared to 51836 (index 136) bytes in legacy 8-bit table. In these examples, the legacy has nearly 6 times larger overhead than the example 10-bit table. For a 2.5 M bytes frame and 500K bytes per TB, TB 906e is 531156 bytes (index 173) in the legacy 8-bit table and 508800 (index 738) bytes in a 10-bit table. In some examples, BSR overhead added is only 2 bits to extend the table from 8 to 10 bits with increasing benefits as traffic increases. In some examples, a subscriber performing a larger uplink transfer over a larger PUSCH allocation is more likely to continue to have a larger number of bytes to report as part of that ongoing larger PUSCH transfer as per the heavy tailed distribution of file transfers (where if a transfer thus far is larger, the remainder of the transfer is expected to be even larger).

[0091] Turning now to FIG. 10, a graph 1000 is provided illustrating a relationship between buffer status reported and transport block size in real networks in accordance with example embodiments of the present disclosure. As can be seen in graph 1000, the example number of bytes reported begins to increase at a greater rate when the PUSCH allocation is greater than 3000 bytes. In some examples, dependency of buffer status report values reported to the TB size is observed in real network data, over many thousands of BSR reports as illustrated in graph 1000.

[0092] Turning now to FIG. 11, an example flowchart is illustrated for a process 1100 performed by an apparatus embodied by, associated with or otherwise in communication with (hereinafter generally referenced as being embodied by) a user equipment (120) for wireless communication in order to transmit a BSR in a selected size profile- based BSR format.

[0093] As shown in block 1110 of FIG. 11, the apparatus embodied by the user equipment (120) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for determining (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In some examples, the user equipment (120) further includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for transmitting (602), to the network node (112), a first message (602a) indicating a capability (602b) of the user equipment (120) for selecting (610) the size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a). In some examples, the user equipment (120) further includes means, such as the processor (12), the radio interface (16), the user interface (18),and / or the like, for receiving (608), from the network node (112), a second message (608a) indicating a decision that the user equipment (120) should select the size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a). In some examples, the user equipment (120) further includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for transmitting user assisted information (UAI) (604a) to the network node (112), wherein the UAI (604a) indicates the likely range of buffer size levels reported over one or more PUSCH allocation sizes (702a). In one or more embodiments, the second message (608a) comprises at least one of an enablement flag, a scheme selection among user equipment (120) supported options, a logical channel group indication, or a TB size threshold (702b). In one or more embodiments, the second message (608a) comprises a radio resource control message, a medium access control (MAC) control element message, or a downlink control information (DCI) on a physical downlink control channel (PDCCH).

[0094] As shown in block 1120 of FIG. 11, the apparatus embodied by the user equipment (120) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for selecting (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a). In one or more embodiments, selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. In one or more embodiments, selecting (610) the size profile- based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. In one or more embodiments, the first logical channel group has larger buffer size levels to report or a larger range of buffer size levels to report, and wherein the second logical channel group has smaller buffer size levels to report or a smaller range of buffer size levels to report. In one or more embodiments, the selecting (610) the size profile- based BSR format comprises selecting (610) a first size profile BSR format (704) for allocations (702a) below a threshold (702b) or an alternate size profile BSR format (706) for allocations (702a) above the threshold (702b). In one or more embodiments, the first size profile BSR format comprises a baseline size profile BSR format.

[0095] As shown in block 1130 of FIG. 11, the apparatus embodied by the user equipment (120) includes means, such as the processor (12), the radio interface (16), the user interface (18),and / or the like, for transmitting (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format. In one or more embodiments, the size profile-based BSR format is based on which logical channel group was specified in a downlink control information granting the TB (611).

[0096] Turning now to FIG. 12, an example flowchart is illustrated for a process 1200 performed by an apparatus embodied by, associated with or otherwise in communication with (hereinafter generally referenced as being embodied by) a network node (112) for wireless communication in order to receive a BSR in a selected size profile- based BSR format.

[0097] As shown in block 1210 of FIG. 12, the apparatus embodied by the network node (112) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for transmitting (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based BSR format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR) (612a). In one or more embodiments, selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. In one or more embodiments, the first logical channel group has larger buffer size levels to report or a larger range of buffer size levels to report, and wherein the second logical channel group has smaller buffer size levels to report or a smaller range of buffer size levels to report. In one or more embodiments, selecting (610) the size profile-based BSR format comprises a bin size selection based on a likely range of buffer size levels reported. In one or more embodiments, the second message (608a) comprises at least one of an enablement flag, a scheme selection among user equipment (120) supported options, a logical channel group indication, or a TB size threshold (702b). In one or more embodiments, the second message (608a) comprises a radio resource control message, a medium access control (MAC) control element message, or a downlink control information (DCI) on a physical downlink control channel (PDCCH). In one or more embodiments, the selected size profile-based BSR format comprises a first size profile BSR format (704) for allocations (702a) below a threshold (702b) or an alternate size profile BSR format (706) for allocations (702a) above the threshold (702b). In one or more embodiments, the first size profile BSR format comprises a baseline size profile BSR format.

[0098] In one or more embodiments, network node (112) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (602), from the user equipment (120), a first message (602a) indicating a capability (602b) of the user equipment (120) for selecting (610) the size profile-based buffer status report (BSR) format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR. In one or more embodiments, network node (112) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for collecting (604) traffic information. In one or more embodiments, the traffic information comprises at least one of (i) user assisted information (UAI) (604a) received from the user equipment (120) and indicating the likely range of buffer size levels reported over one or more PUSCH allocation sizes (702a) or (ii) protocol data unit (PDU) session information (604b) received from the core network (114). In one or more embodiments, network node (112) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for determine (606), based on the traffic information and expected traffic, whether the user equipment (120) should select the size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR. In one or more embodiments, the traffic information comprises traffic information for at least one allocation (702a) with a size above the threshold (702b) and traffic information for one or more allocations (702a) with a size below the threshold (702b).

[0099] As shown in block 1220 of FIG. 12, the apparatus embodied by the network node (112) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format. In one or more embodiments, the network node (112) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for decoding (614) the BSR (612a) based on the selected size profile-based BSR format. In one or more embodiments, decoding (614) the size profile- based BSR format is based on which logical channel group was specified in a downlink control information granting the TB.

[0100] FIGS. 11-12 illustrate flowcharts depicting methods according to an example embodiment of the present disclosure. It will be understood that each block of the flowcharts and combination of blocks in the flowcharts may be implemented by various means, such as hardware, firmware, processor, circuitry, and / or other communication devices associated with execution of software including one or more computer program instructions. For example, one or more of the proceduresdescribed above may be embodied by computer program instructions. In this regard, the computer program instructions 15 which embody the procedures described above may be stored by a memory 14 of an apparatus employing an embodiment and executed by a processor 12. As will be appreciated, any such computer program instructions may be loaded into a computer or other programmable apparatus (for example, hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart blocks. The computer program instructions may also be loaded into a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.

[0101] In one or more embodiments, a user equipment (120) for wireless communication is provided, including at least one processor and at least one memory storing instructions thereon that, when executed by the at least one processor, cause the user equipment (120) to determine (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) is further caused to select (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile- based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group.

[0102] In one or more embodiments, the user equipment (120) is further caused to transmit (602), to the network node (112), a first message (602a) indicating a capability (602b) of the user equipment (120) for selecting (610) the size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a). In one or more embodiments, the user equipment (120) is further caused to receive (608), from the network node (112), a second message (608a) indicating a decision that the user equipment (120) should select the size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a).

[0103] In one or more embodiments, the first logical channel group has larger buffer size levels to report or a larger range of buffer size levels to report, and wherein the second logical channel group has smaller buffer size levels to report or a smaller range of buffer size levels to report.

[0104] In one or more embodiments, the user equipment (120) is further caused to transmit user assisted information (UAI) (604a) to the network node (112), wherein the UAI (604a) indicates the likely range of buffer size levels reported over one or more PUSCH allocation sizes (702a).

[0105] In one or more embodiments, the second message (608a) comprises at least one of an enablement flag, a scheme selection among user equipment (120) supported options, a logical channel group indication, or a TB size threshold (702b).

[0106] In one or more embodiments, selecting (610) the size profile-based BSR format is based on which logical channel group was specified in a downlink control information granting the TB (6H).

[0107] In one or more embodiments, the second message (608a) comprises a radio resource control message, a medium access control (MAC) control element message, or a downlink control information (DCI) on a physical downlink control channel (PDCCH).

[0108] In one or more embodiments, the selecting (610) the size profile-based BSR format comprises selecting (610) a first size profile BSR format (704) for allocations (702a) below a threshold (702b) or an alternate size profile BSR format (706) for allocations (702a) above the threshold (702b).

[0109] In one or more embodiments, the first size profile BSR format comprises a baseline size profile BSR format.

[0110] In one or more embodiments, a network node (112) for wireless communication is provided, including at least one processor and at least one memory storing instructions thereon that, when executed by the at least one processor, cause the network node (112) to transmit (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits toreport buffer size values than a second logical channel group. The network node (112) is further caused to receive (612), from the user equipment (120), the BSR (612a) in a selected size profilebased BSR format.

[0111] In one or more embodiments, the network node (112) is further caused to receive (602), from the user equipment (120), a first message (602a) indicating a capability (602b) of the user equipment (120) for selecting (610) the size profile-based buffer status report (BSR) format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR. In one or more embodiments, the network node (112) is further caused to collect (604) traffic information. In one or more embodiments, the network node (112) is further caused to determine (606), based on the traffic information and expected traffic, whether the user equipment (120) should select the size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR.

[0112] In one or more embodiments, the first logical channel group has larger buffer size levels to report or a larger range of buffer size levels to report, and wherein the second logical channel group has smaller buffer size levels to report or a smaller range of buffer size levels to report.

[0113] In one or more embodiments, the traffic information comprises at least one of (i) user assisted information (UAI) (604a) received from the user equipment (120) and indicating the likely range of buffer size levels reported over one or more PUSCH allocation sizes (702a) or (ii) protocol data unit (PDU) session information (604b) received from the core network (114).

[0114] In one or more embodiments, the second message (608a) comprises at least one of an enablement flag, a scheme selection among user equipment (120) supported options, a logical channel group indication, or a TB size threshold (702b).

[0115] In one or more embodiments, the second message (608a) comprises a radio resource control message, a medium access control (MAC) control element message, or a downlink control information (DCI) on a physical downlink control channel (PDCCH).

[0116] In one or more embodiments, the network node (112) is further caused to decode (614) the BSR (612a) based on the selected size profile-based BSR format.

[0117] In one or more embodiments, decoding (614) the size profile-based BSR format is based on which logical channel group was specified in a downlink control information granting the TB.

[0118] In one or more embodiments, the selected size profile-based BSR format comprises a first size profile BSR format (704) for allocations (702a) below a threshold (702b) or an alternate size profile BSR format (706) for allocations (702a) above the threshold (702b).

[0119] In one or more embodiments, the first size profile BSR format comprises a baseline size profile BSR format.

[0120] In one or more embodiments, the traffic information comprises traffic information for at least one allocation (702a) with a size above the threshold (702b) and traffic information for one or more allocations (702a) with a size below the threshold (702b).

[0121] In one or more embodiments, a user equipment (120) for wireless communication is provided, including means for determining (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) further includes means for selecting (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. In one or more embodiments, the user equipment (120) further includes means for transmitting (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0122] In one or more embodiments, a network node (112) for wireless communication is provided, including means for transmitting (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. The network node (112) further includes means for receiving (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.

[0123] In one or more embodiments, a computer implemented method is provided that is performed by a user equipment (120) and includes determining (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the method further includes selecting (610) a sizeprofile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. In one or more embodiments, the method further includes transmitting (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0124] In one or more embodiments, the method further includes transmitting (602), to the network node (112), a first message (602a) indicating a capability (602b) of the user equipment (120) for selecting (610) the size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a). In one or more embodiments, the user equipment (120) is further caused to receive (608), from the network node (112), a second message (608a) indicating a decision that the user equipment (120) should select the size profilebased BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a).

[0125] In one or more embodiments, the first logical channel group has larger buffer size levels to report or a larger range of buffer size levels to report, and wherein the second logical channel group has smaller buffer size levels to report or a smaller range of buffer size levels to report.

[0126] In one or more embodiments, the method further includes transmitting user assisted information (UAI) (604a) to the network node (112), wherein the UAI (604a) indicates the likely range of buffer size levels reported over one or more PUSCH allocation sizes (702a).

[0127] In one or more embodiments, the second message (608a) comprises at least one of an enablement flag, a scheme selection among user equipment (120) supported options, a logical channel group indication, or a TB size threshold (702b).

[0128] In one or more embodiments, selecting (610) the size profile-based BSR format is based on which logical channel group was specified in a downlink control information granting the TB (6H).

[0129] In one or more embodiments, the second message (608a) comprises a radio resource control message, a medium access control (MAC) control element message, or a downlink control information (DCI) on a physical downlink control channel (PDCCH).

[0130] In one or more embodiments, the selecting (610) the size profile-based BSR format comprises selecting (610) a first size profile BSR format (704) for allocations (702a) below athreshold (702b) or an alternate size profile BSR format (706) for allocations (702a) above the threshold (702b).

[0131] In one or more embodiments, the first size profile BSR format comprises a baseline size profile BSR format.

[0132] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes transmitting (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. The network node (112) further includes receiving (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.

[0133] In one or more embodiments, the method further includes receiving (602), from the user equipment (120), a first message (602a) indicating a capability (602b) of the user equipment (120) for selecting (610) the size profile-based buffer status report (BSR) format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR. In one or more embodiments, the method further includes collecting (604) traffic information. In one or more embodiments, the method further includes determining (606), based on the traffic information and expected traffic, whether the user equipment (120) should select the size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR.

[0134] In one or more embodiments, the first logical channel group has larger buffer size levels to report or a larger range of buffer size levels to report, and wherein the second logical channel group has smaller buffer size levels to report or a smaller range of buffer size levels to report.

[0135] In one or more embodiments, the traffic information comprises at least one of (i) user assisted information (UAI) (604a) received from the user equipment (120) and indicating the likely range of buffer size levels reported over one or more PUSCH allocation sizes (702a) or (ii) protocol data unit (PDU) session information (604b) received from the core network (114).

[0136] In one or more embodiments, the second message (608a) comprises at least one of an enablement flag, a scheme selection among user equipment (120) supported options, a logical channel group indication, or a TB size threshold (702b).

[0137] In one or more embodiments, the second message (608a) comprises a radio resource control message, a medium access control (MAC) control element message, or a downlink control information (DCI) on a physical downlink control channel (PDCCH).

[0138] In one or more embodiments, the method further includes decoding (614) the BSR (612a) based on the selected size profile-based BSR format.

[0139] In one or more embodiments, decoding (614) the size profile-based BSR format is based on which logical channel group was specified in a downlink control information granting the TB.

[0140] In one or more embodiments, the selected size profile-based BSR format comprises a first size profile BSR format (704) for allocations (702a) below a threshold (702b) or an alternate size profile BSR format (706) for allocations (702a) above the threshold (702b).

[0141] In one or more embodiments, the first size profile BSR format comprises a baseline size profile BSR format.

[0142] In one or more embodiments, the traffic information comprises traffic information for at least one allocation (702a) with a size above the threshold (702b) and traffic information for one or more allocations (702a) with a size below the threshold (702b).

[0143] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (120), cause the user equipment (120) to determine (702) a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a buffer status report (BSR). In one or more embodiments, the user equipment (120) is further caused to select (610) a size profile-based BSR format based on the size of the PUSCH allocation (702a) of the TB carrying the BSR (612a), wherein selecting (610) the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. In one or more embodiments, the user equipment (120) is further caused to transmit (612), to a network node (112), the BSR (612a) in the selected size profile-based BSR format.

[0144] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause thenetwork node (112) to transmit (608), to a user equipment (120), a second message (608a) indicating a decision that the user equipment (120) should select a size profile-based buffer status report (BSR) format based on a size of a physical uplink shared channel (PUSCH) allocation (702a) of a transport block (TB) carrying a BSR (612a), wherein selecting (610) the size profilebased BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group. The network node (112) is further caused to receive (612), from the user equipment (120), the BSR (612a) in a selected size profile-based BSR format.

[0145] Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

Claims

What is claimed is:

1. A user equipment for wireless communication, comprising:at least one processor; andat least one memory storing instructions thereon that, when executed by the at least one processor, cause the user equipment to:determine a size of a physical uplink shared channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR);select a size profile-based BSR format based on the size of the PUSCH allocation of the TB carrying the BSR, wherein selecting the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group; andtransmit, to the network node, the BSR in the selected size profile-based BSR format.

2. The user equipment of claim 1, wherein the user equipment is further caused to: transmit, to the network node, a first message indicating a capability of the user equipment for selecting the size profile-based BSR format based on the size of the PUSCH allocation of the TB carrying the BSR; andreceive, from the network node, a second message indicating a decision that the user equipment should select the size profile-based BSR format based on the size of the PUSCH allocation of the TB carrying the BSR.

3. The user equipment of claim 1, wherein the first logical channel group has larger buffer size levels to report or a larger range of buffer size levels to report, and wherein the second logical channel group has smaller buffer size levels to report or a smaller range of buffer size levels to report.

4. The user equipment of claim 1 , wherein the user equipment is further caused to transmit user assisted information (UAI) to the network node, wherein the UAI indicates the likely range of buffer size levels reported over one or more PUSCH allocation sizes.

5. The user equipment of claim 2, wherein the second message comprises at least one of an enablement flag, a scheme selection among user equipment supported options, a logical channel group indication, or a TB size threshold.

6. The user equipment of claim 1, wherein selecting the size profile-based BSR format is based on which logical channel group was specified in a downlink control information granting the TB.

7. The user equipment of claim 2, wherein the second message comprises a radio resource control message, a medium access control (MAC) control element message, or a downlink control information (DCI) on a physical downlink control channel (PDCCH).

8. The user equipment of claim 1, wherein the selecting the size profile-based BSR format comprises selecting a first size profile BSR format for allocations below a threshold or an alternate size profile BSR format for allocations above the threshold.

9. The user equipment of claim 8, wherein the first size profile BSR format comprises a baseline size profile BSR format.

10. A network node for wireless communication, comprising:at least one processor; andat least one memory storing instructions thereon that, when executed by the at least one processor, cause the network node to:transmit, to a user equipment, a second message indicating a decision that the user equipment should select a size profile-based BSR format based on a size of a physical uplink shared channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR), wherein selecting the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group; andreceive, from the user equipment, the BSR in a selected size profile-based BSR format.

11. The network node of claim 10, further caused to:receive, from the user equipment, a first message indicating a capability of the user equipment for selecting the size profile-based buffer status report (BSR) format based on the size of the PUSCH allocation of the TB carrying the BSR;collect traffic information; anddetermine, based on the traffic information and expected traffic, whether the user equipment should select the size profile-based BSR format based on the size of the PUSCH allocation of the TB carrying the BSR.

12. The network node of claim 10, wherein the first logical channel group has larger buffer size levels to report or a larger range of buffer size levels to report, and wherein the second logical channel group has smaller buffer size levels to report or a smaller range of buffer size levels to report.

13. The network node of claim 10, wherein the traffic information comprises at least one of (i) user assisted information (UAI) received from the user equipment and indicating the likely range of buffer size levels reported over one or more PUSCH allocation sizes or (ii) protocol data unit (PDU) session information received from the core network.

14. The network node of claim 10, wherein the second message comprises at least one of an enablement flag, a scheme selection among user equipment supported options, a logical channel group indication, or a TB size threshold.

15. The network node of claim 10, wherein the second message comprises a radio resource control message, a medium access control (MAC) control element message, or a downlink control information (DCI) on a physical downlink control channel (PDCCH).

16. The network node of claim 10, wherein the network node is further caused to decode the BSR based on the selected size profile-based BSR format.

17. The network node of claim 16, wherein decoding the size profile-based BSR format is based on which logical channel group was specified in a downlink control information granting the TB.

18. The network node of claim 10, wherein the selected size profile-based BSR format comprises a first size profile BSR format for allocations below a threshold or an alternate size profile BSR format for allocations above the threshold.

19. The network node of claim 18, wherein the first size profile BSR format comprises a baseline size profile BSR format.

20. The network node of claim 11 , wherein the traffic information comprises traffic information for at least one allocation with a size above the threshold and traffic information for one or more allocations with a size below the threshold.

21. A user equipment for wireless communication, comprising:means for determining a size of a physical uplink shared channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR);means for selecting a size profile-based BSR format based on the size of the PUSCH allocation of the TB carrying the BSR, wherein selecting the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group; and means for transmitting, to the network node, the BSR in the selected size profile-based BSR format.

22. A network node for wireless communication, comprising:means for transmitting, to a user equipment, a second message indicating a decision that the user equipment should select a size profile- based BSR format based on a size of a physical uplink shared channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR), wherein selecting the size profile-based BSR format comprises a selection of bitsper logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group; andmeans for receiving, from the user equipment, the BSR in a selected size profile-based BSR format.

23. A computer- implemented method, performed by a user equipment, comprising:determining a size of a physical uplink shared channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR);selecting a size profile-based BSR format based on the size of the PUSCH allocation of the TB carrying the BSR, wherein selecting the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group; andtransmitting, to the network node, the BSR in the selected size profile-based BSR format.

24. A computer-implemented method, performed by a network node, comprising:transmitting, to a user equipment, a second message indicating a decision that the user equipment should select a size profile-based BSR format based on a size of a physical uplink shared channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR), wherein selecting the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group; andreceiving, from the user equipment, the BSR in a selected size profile-based BSR format.

25. A non-transitory computer readable storage medium, including computer instructions that, when executed by a user equipment, cause the user equipment to:determine a size of a physical uplink shared channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR);select a size profile-based BSR format based on the size of the PUSCH allocation of the TB carrying the BSR, wherein selecting the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group; andtransmit, to the network node, the BSR in the selected size profile-based BSR format.

26. A non-transitory computer readable storage medium, including computer instructions that, when executed by a network node, cause the network node to:transmit, to a user equipment, a second message indicating a decision that the user equipment should select a size profile-based BSR format based on a size of a physical uplink shared channel (PUSCH) allocation of a transport block (TB) carrying a buffer status report (BSR), wherein selecting the size profile-based BSR format comprises a selection of bits per logical channel group, wherein a first logical channel group is allocated more bits to report buffer size values than a second logical channel group; andreceive, from the user equipment, the BSR in a selected size profile-based BSR format.

Images