EP4599572A1

EP4599572A1 - Allocating resources for high-throughput ultra-reliable low-latency communication (urllc) traffic transmissions

Info

Publication number: EP4599572A1
Application number: EP23813520.6A
Authority: EP
Inventors: Shiangrung YE
Original assignee: Google LLC
Current assignee: Google LLC
Priority date: 2022-11-09
Filing date: 2023-11-01
Publication date: 2025-08-13
Also published as: WO2024102280A1

Abstract

A UE (102) receives (408), from a network (104), an uplink grant that indicates uplink resources for transmission (414) of a MAC PDU. Individual PDUs of a PDU set are allocated to the MAC PDU from a logical channel based on a number of available tokens in a token bucket dedicated to the logical channel. The UE (102) transmits (414), to the network (104), the MAC PDU including the PDU set when the number of available tokens in the token bucket is of an amount that allows for allocation of at least one of the individual PDUs of the PDU set to the MAC PDU but not an entirety of the PDU set to the MAC PDU.

Description

ALLOCATING RESOURCES FOR HIGH-THROUGHPUT ULTRA-RELIABLE LOW- LATENCY COMMUNICATION (URLLC) TRAFFIC TRANSMISSIONS CROSS REFERENCE TO RELATED APPLICATION(S) [0001] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63/424,092, entitled “ALLOCATING RESOURCES FOR HIGH-THROUGHPUT ULTRA-RELIABLE LOW-LATENCY COMMUNICATION (URLLC) TRAFFIC TRANSMISSIONS” and filed on November 9, 2022, which is expressly incorporated by reference herein in its entirety. TECHNICAL FIELD [0002] The present disclosure relates generally to wireless communication, and more particularly, to resource allocations for high-throughput ultra-reliable low-latency communication (URLLC), such as extended reality (XR) and/or cloud gaming (CG) traffic transmissions. BACKGROUND [0003] The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR). An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), a user equipment (UE), etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and/or increased capacity compared to prior generation cellular communication systems. [0004] Wireless communication systems, in general, may be configured to provide various telecommunication services (e.g., telephony, video, data, messaging, broadcasts, etc.) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies. For example, extended reality (XR) and/or cloud gaming (CG) traffic may be associated with delivery characteristics that drop a packet if the packet is not received according to certain protocols. Hence, high-throughput ultra-reliable low latency communication (URLLC) traffic awareness may allow a UE and an application server/network to adapt packet generation and communication techniques to reduce packet drops. BRIEF SUMMARY [0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor 1143801610WO delineates the scope of any or all aspects. sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later. [0006] High-throughput ultra-reliable low latency communication (URLLC) such as extended reality (XR) and/or cloud gaming (CG) traffic, communicated between a user equipment (UE) and an application server, may have a non-integer periodicity or may be quasi-periodic, which might lead to jitter in video frames displayed at the UE. The high-throughput URLLC traffic might also have a variable data rate. For example, data rates for streams of the XR/CG traffic, such as video frame streams, communicated between the UE and the application server might change dynamically. Hence, high-throughput URLLC application awareness by the UE and the network might allow the network to select radio parameters that can improve a quality of the streams of the XR/CG traffic as well as improve a battery life of the UE. [0007] The UE transmits, to the network, a medium access control (MAC) protocol data unit (PDU) including a number of bytes. The number of bytes in the MAC PDU available for transferring data from a particular logical channel might be limited based on a number of available tokens in a token bucket dedicated to the logical channel. In some examples, there may not be enough available tokens in the token bucket to include an entire PDU set (e.g., radio link control (RLC) PDUs of the logical channel) in the MAC PDU, despite the MAC PDU being otherwise able to accommodate the entire PDU set. A PDU set includes one or more PDUs carrying a payload of one unit of information generated at an application layer (e.g. a frame or video slice for XR services). In some implementations, all PDUs in the PDU set have to be received at the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover part(s) or all of the information when some PDUs are missing from the PDU set. [0008] Some XR/CG applications might have to receive the entire PDU set to generate a video frame, so those XR/CG applications might wait for a remainder of the PDUs in the PDU set to arrive at the UE before displaying the video frame at the UE. Delays in receiving the remainder of the PDU set might increase a likelihood that a delivery deadline of the PDU set will be missed and that the video frame will be dropped as a result of not receiving the entire PDU set by the delivery deadline. Accordingly, aspects of the present disclosure address the above-noted and other deficiencies by including the entire PDU set in a MAC PDU transmission, as long as the token bucket has enough available tokens to transmit at least one PDU from the PDU set. [0009] According to some aspects, the UE receives, from the network, an uplink grant that indicates uplink resources for transmission of the MAC PDU. Individual PDUs of a PDU set are 1143801610WO allocated to the MAC PDU from a logical based on the number of available tokens in the token bucket dedicated to the logical channel. The UE transmits, to the network, the MAC PDU including the PDU set when the number of available tokens in the token bucket is of a first amount/large enough to allow for allocation of at least a portion of one of the individual PDUs of the PDU set to the MAC PDU but is not of a second amount/large enough to allow for allocation of the entire PDU set to the MAC PDU. [0010] According to some other aspects, the network transmits, to the UE, a configuration for including the entire PDU set in the MAC PDU when the number of available tokens in the token bucket dedicated to the logical channel is of the amount described above. The network further transmits, to the UE, the uplink grant that indicates uplink resources for reception of the MAC PDU including the entire PDU set from the UE. BRIEF DESCRIPTION OF THE DRAWINGS [0011] FIG. 1 illustrates a diagram of a wireless communications system that includes a plurality of user equipments (UEs) and network entities in communication over one or more cells. [0012] FIG.2 is a diagram illustrating a protocol stack that includes a physical (PHY) layer, a medium access control (MAC) layer, and a radio link control (RLC) layer. [0013] FIG.3 is a diagram illustrating logical channel prioritization. [0014] FIG.4 is a signaling diagram that illustrates a resources allocation procedure, such as for high-throughput ultra-reliable low-latency communication (URLLC). [0015] FIG. 5 is a diagram illustrating an algorithm for transmitting an entire protocol data unit (PDU) set in a MAC PDU. [0016] FIG.6 is a flowchart of a method of wireless communication at a UE. [0017] FIG.7 is a flowchart of a method of wireless communication at a network. [0018] FIG. 8 is a diagram illustrating a hardware implementation for an example UE apparatus. [0019] FIG. 9 is a diagram illustrating a hardware implementation for one or more example network entities. DETAILED DESCRIPTION [0020] FIG.1 illustrates a diagram 100 of a wireless communications system associated with a plurality of cells 190. The wireless communications system includes user equipments (UEs) 102 and base stations 104, where some base stations 104c include an aggregated base station architecture and other base stations 104a-104b include a disaggregated base station architecture. The aggregated base station architecture includes a radio unit (RU) 106, a distributed unit (DU) 108, and a centralized unit (CU) 110 that are configured to utilize a radio protocol stack that is 1143801610WO physically or logically integrated a single radio access network (RAN) node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., RUs 106, DUs 108, CUs 110). For example, a CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 may be implemented to communicate with one or more RUs 106. Each of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). A base station 104 and/or a unit of the base station 104, such as the RU 106, the DU 108, or the CU 110, may be referred to as a transmission reception point (TRP). [0021] Operations of the base stations 104 and/or network designs may be based on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (IAB) network, an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN) which may also be referred to a cloud radio access network (C-RAN). Disaggregation may include distributing functionality across the two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the CU 110a communicates with the DUs 108a-108b via respective midhaul links 162 based on F1 interfaces. The DUs 108a-108b may respectively communicate with the RU 106a and the RUs 106b-106c via respective fronthaul links 160. The RUs 106a-106c may communicate with respective UEs 102a-102c and 102s via one or more radio frequency (RF) access links based on a Uu interface. In examples, multiple RUs 106 and/or base stations 104 may simultaneously serve the UEs 102, such as the UE 102a of the cell 190a that the access links for the RU 106a of the cell 190a and the base station 104c of the cell 190e simultaneously serve. [0022] One or more CUs 110, such as the CU 110a or the CU 110d, may communicate directly with a core network 120 via a backhaul link 164. For example, the CU 110d communicates with the core network 120 over a backhaul link 164 based on a next generation (NG) interface. The one or more CUs 110 may also communicate indirectly with the core network 120 through one or more disaggregated base station units, such as a near-real time RAN intelligent controller (RIC) 128 via an E2 link and a service management and orchestration (SMO) framework 116, which may be associated with a non-real time RIC 118. The near-real time RIC 128 might communicate with the SMO framework 116 and/or the non-real time RIC 118 via an 1143801610WO A1 link. The SMO framework 116 the non-real time RIC 118 might also communicate with an open cloud (O-cloud) 130 via an O2 link. The one or more CUs 110 may further communicate with each other over a backhaul link 164 based on an Xn interface. For example, the CU 110d of the base station 104c communicates with the CU 110a of the base station 104b over the backhaul link 164 based on the Xn interface. Similarly, the base station 104c of the cell 190e may communicate with the CU 110a of the base station 104b over a backhaul link 164 based on the Xn interface. [0023] The RUs 106, the DUs 108, and the CUs 110, as well as the near-real time RIC 128, the non-real time RIC 118, and/or the SMO framework 116, may include (or may be coupled to) one or more interfaces configured to transmit or receive information/signals via a wired or wireless transmission medium. A base station 104 or any of the one or more disaggregated base station units can be configured to communicate with one or more other base stations 104 or one or more other disaggregated base station units via the wired or wireless transmission medium. In examples, a processor, a memory, and/or a controller associated with executable instructions for the interfaces can be configured to provide communication between the base stations 104 and/or the one or more disaggregated base station units via the wired or wireless transmission medium. For example, a wired interface can be configured to transmit or receive the information/signals over a wired transmission medium, such as for the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 of the cell 190d or, more specifically, the fronthaul link 160 between the RU 106d and DU 108d. The BBU 112 includes the DU 108d and a CU 110d, which may also have a wired interface configured between the DU 108d and the CU 110d to transmit or receive the information/signals between the DU 108d and the CU 110d based on a midhaul link 162. In further examples, a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), can be configured to transmit or receive the information/signals via the wireless transmission medium, such as for information communicated between the RU 106a of the cell 190a and the base station 104c of the cell 190e via cross-cell communication beams of the RU 106a and the base station 104c. [0024] One or more higher layer control functions, such as function related to radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and the like, may be hosted at the CU 110. Each control function may be associated with an interface for communicating signals based on one or more other control functions hosted at the CU 110. User plane functionality such as central unit-user plane (CU-UP) functionality, control plane functionality such as central unit-control plane (CU-CP) functionality, or a combination thereof may be implemented based on the CU 110. For example, the CU 110 can include a logical 1143801610WO split between one or more CU-UP and/or one or more CU-CP procedures. The CU- UP functionality may be based on bidirectional communication with the CU-CP functionality via an interface, such as an E1 interface (not shown), when implemented in an O-RAN configuration. [0025] The CU 110 may communicate with the DU 108 for network control and signaling. The DU 108 is a logical unit of the base station 104 configured to perform one or more base station functionalities. For example, the DU 108 can control the operations of one or more RUs 106. One or more of a radio link control (RLC) layer, a medium access control (MAC) layer, or one or more higher physical (PHY) layers, such as forward error correction (FEC) modules for encoding/decoding, scrambling, modulation/demodulation, or the like can be hosted at the DU 108. The DU 108 may host such functionalities based on a functional split of the DU 108. The DU 108 may similarly host one or more lower PHY layers, where each lower layer or module may be implemented based on an interface for communications with other layers and modules hosted at the DU 108, or based on control functions hosted at the CU 110. [0026] The RUs 106 may be configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions, or lower layer PHY functionality, such as execution of fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RUs 106 may be based on the functional split, such as a functional split of lower layers. [0027] The RUs 106 may transmit or receive over-the-air (OTA) communication with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b, which may correspond to inter-cell communication beams or cross-cell communication beams. For example, the UE 102b of the cell 190b may communicate with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and an RU beam set 136 of the RU 106a. Both real-time and non-real-time features of control plane and user plane communications of the RUs 106 can be controlled by associated DUs 108. Accordingly, the DUs 108 and the CUs 110 can be utilized in a cloud-based RAN architecture, such as a vRAN architecture, whereas the SMO framework 116 can be utilized to support non-virtualized and virtualized RAN network elements. For non-virtualized network elements, the SMO framework 116 may support deployment of dedicated physical resources for RAN coverage, where the dedicated physical resources may be managed through an operations and maintenance interface, such as an O1 interface. For virtualized network elements, the SMO Framework 116 may interact with a cloud computing platform, such as the O-cloud 130 via the 1143801610WO O2 link (e.g., cloud computing platform , to manage the network elements. Virtualized network elements can include, but are not limited to, RUs 106, DUs 108, CUs 110, near-real time RICs 128, etc. [0028] The SMO framework 116 may be configured to utilize an O1 link to communicate directly with one or more RUs 106. The non-real time RIC 118 of the SMO framework 116 may also be configured to support functionalities of the SMO framework 116. For example, the non- real time RIC 118 implements logical functionality that enables control of non-real time RAN features and resources, features/applications of the near-real time RIC 128, and/or artificial intelligence/machine learning (AI/ML) procedures. The non-real time RIC 118 may communicate with (or be coupled to) the near-real time RIC 128, such as through the A1 interface. The near- real time RIC 128 may implement logical functionality that enables control of near-real time RAN features and resources based on data collection and interactions over an E2 interface, such as the E2 interfaces between the near-real time RIC 128 and the CU 110a and the DU 108b. [0029] The non-real time RIC 118 may receive parameters or other information from external servers to generate AI/ML models for deployment in the near-real time RIC 128. For example, the non-real time RIC 118 receives the parameters or other information from the O-cloud 130 via the O2 link for deployment of the AI/ML models to the real-time RIC 128 via the A1 link. The near-real time RIC 128 may utilize the parameters and/or other information received from the non- real time RIC 118 or the SMO framework 116 via the A1 link to perform near-real time functionalities. The near-real time RIC 128 and the non-real time RIC 115 may be configured to adjust a performance of the RAN. For example, the non-real time RIC 116 monitors patterns and long-term trends to increase the performance of the RAN. The non-real time RIC 116 may also deploy AI/ML models for implementing corrective actions through the SMO framework 116, such as initiating a reconfiguration of the O1 link or indicating management procedures for the A1 link. [0030] Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106, the DU 108, or the CU 110. The base stations 104 provide the UEs 102 with access to the core network 120. That is, the base stations 104 might relay communications between the UEs 102 and the core network 120. The base stations 104 may be associated with macrocells for high-power cellular base stations and/or small cells for low-power cellular base stations. For example, the cell 190e corresponds to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A cell structure that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network.” 1143801610WO [0031] Transmissions from a UE 102 a base station 104/RU 106 are referred to uplink (UL) transmissions, whereas transmissions from the base station 104/RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104c of cell 190d to transmit a downlink/forward link communication to the UE 102d or receive an uplink/reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104c/RU 106d. [0032] Communication links between the UEs 102 and the base stations 104/RUs 106 may be based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be associated with one or more carriers. The UEs 102 and the base stations 104/RUs 106 may utilize a spectrum bandwidth of Y MHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink carriers may be allocated in an asymmetric manner, more or fewer carriers may be allocated to either the uplink or the downlink. A primary component carrier and one or more secondary component carriers may be included in the component carriers. The primary component carrier may be associated with a primary cell (PCell) and a secondary component carrier may be associated with as a secondary cell (SCell). [0033] Some UEs 102, such as the UEs 102a and 102s, may perform device-to-device (D2D) communications over sidelink. For example, a sidelink communication/D2D link utilizes a spectrum for a wireless wide area network (WWAN) associated with uplink and downlink communications. The sidelink communication/D2D link may also use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and/or a physical sidelink control channel (PSCCH), to communicate information between UEs 102a and 102s. Such sidelink/D2D communication may be performed through various wireless communications systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, Long Term Evolution (LTE) systems, New Radio (NR) systems, etc. [0034] The electromagnetic spectrum is often subdivided into different classes, bands, channels, etc., based on different frequencies/wavelengths associated with the electromagnetic spectrum. Fifth-generation (5G) NR is generally associated with two operating frequency ranges 1143801610WO (FRs) referred to as frequency range 1 and frequency range 2 (FR2). FR1 ranges from 410 MHz – 7.125 GHz and FR2 ranges from 24.25 GHz – 71.0 GHz, which includes FR2-1 (24.25 GHz – 52.6 GHz) and FR2-2 (52.6 GHz – 71.0 GHz). Although a portion of FR1 is actually greater than 6 GHz, FR1 is often referred to as the “sub-6 GHz” band. In contrast, FR2 is often referred to as the “millimeter wave” (mmW) band. FR2 is different from, but a near subset of, the “extremely high frequency” (EHF) band, which ranges from 30 GHz – 300 GHz and is sometimes also referred to as a “millimeter wave” band. Frequencies between FR1 and FR2 are often referred to as “mid-band” frequencies. The operating band for the mid-band frequencies may be referred to as frequency range 3 (FR3), which ranges 7.125 GHz – 24.25 GHz. Frequency bands within FR3 may include characteristics of FR1 and/or FR2. Hence, features of FR1 and/or FR2 may be extended into the mid-band frequencies. Higher operating frequency bands have been identified to extend 5G NR communications above 52.6 GHz associated with the upper limit of FR2. Three of these higher operating frequency bands include FR2-2, which ranges from 52.6 GHz – 71.0 GHz, FR4, which ranges from 71.0 GHz – 114.25 GHz, and FR5, which ranges from 114.25 GHz – 300 GHz. The upper limit of FR5 corresponds to the upper limit of the EHF band. Thus, unless otherwise specifically stated herein, the term “sub-6 GHz” may refer to frequencies that are less than 6 GHz, within FR1, or may include the mid-band frequencies. Further, unless otherwise specifically stated herein, the term “millimeter wave”, or mmW, refers to frequencies that may include the mid-band frequencies, may be within FR2-1, FR4, FR2-2, and/or FR5, or may be within the EHF band. [0035] The UEs 102 and the base stations 104/RUs 106 may each include a plurality of antennas. The plurality of antennas may correspond to antenna elements, antenna panels, and/or antenna arrays that may facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of beams 132 to the UE 102b in one or more transmit directions of the RU 106b. The UE 102b may receive the downlink beamformed signal based on a second set of beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b may also transmit an uplink beamformed signal to the RU 106b based on the second set of beams 134b in one or more transmit directions of the UE 102b. The RU 106b may receive the uplink beamformed signal from the UE 102b in one or more receive directions of the RU 106b. The UE 102b may perform beam training to determine the best receive and transmit directions for the beam formed signals. The transmit and receive directions for the UEs 102 and the base stations 104/RUs 106 might or might not be the same. In further examples, beamformed signals may be communicated between a first base station 104c and a second base station 104b. For instance, the RU 106a of cell 190a may transmit a 1143801610WO beamformed signal based on the RU 136 to the base station 104c of cell 190e in one or more transmit directions of the RU 106a. The base station 104c of the cell 190e may receive the beamformed signal from the RU 106a based on a base station beam set 138 in one or more receive directions of the base station 104c. Similarly, the base station 104c of the cell 190e may transmit a beamformed signal to the RU 106a based on the base station beam set 138 in one or more transmit directions of the base station 104c. The RU 106a may receive the beamformed signal from the base station 104c of the cell 190e based on the RU beam set 136 in one or more receive directions of the RU 106a. [0036] The base station 104 may include and/or be referred to as a network entity. That is, “network entity” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and/or the CU 110. The base station 104 may also include and/or be referred to as a next generation evolved Node B (ng-eNB), a generation NB (gNB), an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station with an RU 106 and a BBU that includes a DU 108 and a CU 110, or as a disaggregated base station 104b including one or more of the RU 106, the DU 108, and/or the CU 110. A set of aggregated or disaggregated base stations 104a-104b may be referred to as a next generation-radio access network (NG-RAN). In some examples, the UE 102b operates in dual connectivity (DC) with the base station 104a and the base station 104b. In such cases, the base station 104a can be a master node and the base station 104b can be a secondary node. In other examples, the UE 102b operates in DC with the DU 108a and the DU 108b. In such cases, the DU 108a can be the master node and the DU 108b can be the secondary node. [0037] The core network 120 may include an Access and Mobility Management Function (AMF) 121, a Session Management Function (SMF) 122, a User Plane Function (UPF) 123, a Unified Data Management (UDM) 124, a Gateway Mobile Location Center (GMLC) 125, and/or a Location Management Function (LMF) 126. The core network 120 may also include one or more location servers, which may include the GMLC 125 and the LMF 126, as well as other functional entities. For example, the one or more location servers include one or more location/positioning servers, which may include the GMLC 125 and the LMF 126 in addition to one or more of a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. 1143801610WO [0038] The AMF 121 is the control that processes the signaling between the UEs 102 and the core network 120. The AMF 121 supports registration management, connection management, mobility management, and other functions. The SMF 122 supports session management and other functions. The UPF 123 supports packet routing, packet forwarding, and other functions. The UDM 124 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The GMLC 125 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 126 receives measurements and assistance information from the NG-RAN and the UEs 102 via the AMF 121 to compute the position of the UEs 102. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UEs 102. Positioning the UEs 102 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UEs 102 and/or the serving base stations 104/RUs 106. [0039] Communicated signals may also be based on one or more of a satellite positioning system (SPS) 114, such as signals measured for positioning. In an example, the SPS 114 of the cell 190c may be in communication with one or more UEs 102, such as the UE 102c, and one or more base stations 104/RUs 106, such as the RU 106c. The SPS 114 may correspond to one or more of a Global Navigation Satellite System (GNSS), a global position system (GPS), a non- terrestrial network (NTN), or other satellite position/location system. The SPS 114 may be associated with LTE signals, NR signals (e.g., based on round trip time (RTT) and/or multi-RTT), wireless local area network (WLAN) signals, a terrestrial beacon system (TBS), sensor-based information, NR enhanced cell ID (NR E-CID) techniques, downlink angle-of-departure (DL- AoD), downlink time difference of arrival (DL-TDOA), uplink time difference of arrival (UL- TDOA), uplink angle-of-arrival (UL-AoA), and/or other systems, signals, or sensors. [0040] The UEs 102 may be configured as a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a GPS, a multimedia device, a video device, a digital audio player (e.g., moving picture experts group (MPEG) audio layer-3 (MP3) player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an utility meter, a gas pump, appliances, a healthcare device, a sensor/actuator, a display, or any other device of similar functionality. Some of the UEs 102 may be referred to as Internet of Things (IoT) devices, such as parking meters, gas pumps, appliances, vehicles, healthcare equipment, etc. The UE 102 may also be referred to as a station (STA), a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, 1143801610WO a mobile device, a wireless device, a communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a mobile client, a client, or other similar terminology. The term UE may also apply to a roadside unit (RSU), which may communicate with other RSU UEs, non-RSU UEs, a base station 104, and/or an entity at a base station 104, such as an RU 106. [0041] Still referring to FIG. 1, in certain aspects, the UE 102 may include a MAC PDU generation component 140 configured to receive, from a network, an uplink grant that indicates uplink resources for transmission of a MAC PDU, where individual PDUs of a PDU set are allocated to the MAC PDU from a logical channel based on a number of available tokens in a token bucket dedicated to the logical channel; and transmit, to the network, the MAC PDU including the PDU set when the number of available tokens in the token bucket is of an amount that allows for allocation of at least a portion of one of the individual PDUs of the PDU set to the MAC PDU but not an entirety of the PDU set to the MAC PDU. [0042] In certain aspects, the base station 104 or a network entity of the network may include a MAC PDU configuration component 150 configured to transmit, to a UE, a configuration for including a PDU set in a MAC PDU when a number of available tokens in a token bucket dedicated to a logical channel is of an amount that allows for allocation of at least a portion of one PDU of the PDU set to the MAC PDU but not an entirety of the PDU set to the MAC PDU; and transmit, to the UE, an uplink grant that indicates uplink resources for reception of the MAC PDU. [0043] Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein, such as aspects illustrated in FIGs. 2-4. Further, although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G- Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies, such as 6G. [0044] FIG.2 is a diagram 200 that illustrates a protocol stack including a PHY layer 250, a MAC layer 260, and an RLC layer 270. The PHY layer 250 corresponds to layer 1 (L1). The MAC layer 260 and the RLC layer 270, along with a PDCP layer (not shown) that sits above the RLC layer 270, may also be referred to as sublayers of layer 2 (L2). That is, an L2 protocol stack includes a PDCP sublayer, an RLC sublayer, and a MAC sublayer. Both the UE and a network entity, such as a base station, perform transmissions in association with the protocol stack of the diagram 200. [0045] The PHY layer 250 provides transport channels to the MAC layer 260 for downlink/uplink transmissions. The transport channels may carry one or more transport blocks 1143801610WO (TBs) 252a, 252b. The MAC layer 260 scheduling functionality and/or priority handling functionality for downlink and uplink transmissions. The MAC layer 260 also includes multiplexing functionality for the downlink/uplink transmissions and demultiplexing functionality for the downlink/uplink transmissions. The MAC layer 260 may perform hybrid automatic repeat request (HARQ) procedures for each downlink/uplink transmission on a particular downlink/uplink CC associated with a particular UE. The RLC layer 270 includes segmentation and automatic repeat request (ARQ) functionality for downlink/uplink data communicated to/from one or more UEs. In LTE applications, the RLC layer 270 may perform concatenation of RLC SDUs 272 into an RLC PDU 274. For example, the RLC PDU 274a concatenates a first RLC SDU 272a and a second RLC SDU 272b. In NR applications, the RLC layer 270 may not perform concatenation. Instead, the RLC layer 270 may perform (re)segmentation of the RLC SDUs 272. [0046] Internet protocol (IP) packets may include data that is communicated through the layers 250-270 of the protocol stack. In an example, the PDCP layer (not shown) performs IP header compression through robust header compression (ROHC) techniques, followed by ciphering, such that the PDCP layer produces one or more RLC service data units (SDUs) 272. The ROHC techniques may reduce a size of upper layer headers that include static information, such as for voice over internet protocol (VoIP) packet headers that might otherwise correspond to more than a half of a packet size. In examples, the reduced PDCP header size might be between 1 and 3 bytes. The PDCP header also includes information for deciphering the packet at a mobile terminal. [0047] An output from the PDCP layer (e.g., the one or more RLC SDUs 272) goes as input to the RLC layer 270. The RLC layer 270 may perform concatenation and/or segmentation of the RLC SDUs 272 to produce RLC PDUs 274 in addition to adding an RLC header 276a, 276b, 276c to the RLC PDUs 274. For example, the RLC layer 270 may concatenate a first RLC SDU 272a and a second RLC SDU 272b into a first RLC PDU 274a associated with a first logical channel, and segment a third RLC SDU 272c into a second RLC PDU 274b and a third RLC PDU 274c associated with a second logical channel. In other examples, the first RLC PDU 274a, the second RLC PDU 274b, and the third RLC PDU 274c may form an RLC PDU set 275 associated with a same logical channel. The RLC PDUs 274 include RLC headers 276a, 276b, 276c for in sequence delivery (e.g., per logical channel) in the mobile terminal and for identiﬁcation of individual RLC PDUs 274 in cases of retransmission. In cases of packet segmentation and/or concatenation, additional RLC sub-headers may be added to the RLC PDUs 274. An RLC PDU 274 can include part of, or all of, a PDU packet or several PDU packets (e.g., RLC SDUs 272) depending on a size of an allocation for the UE. 1143801610WO [0048] The RLC PDUs 274 are to the MAC layer 260, which become MAC SDUs 262 according to 3GPP nomenclature. The MAC layer 260 may similarly perform concatenation and/or segmentation of the MAC SDUs 262 into MAC PDUs 264 in addition to adding a MAC header 266a, 266b to the MAC PDUs 264. For example, the MAC layer 260 may concatenate a first MAC SDU 262a and a second MAC SDU 262b into a first MAC PDU 264a, and may incorporate a third MAC SDU 272c into a second MAC PDU 264b (e.g., without concatenation or segmentation). The MAC layer 260 appends MAC headers 266 to the MAC PDUs payload to form a TB 252a, 252b. [0049] The MAC layer 260 includes a radio resource scheduler that determines how much data is currently in buffer(s) awaiting transmission from the logical channel(s). The MAC layer 260 may also determine information about the radio link quality for different UEs, whether there are any packets for retransmission, a UE status (e.g., whether the UE is in a scanning/monitoring mode or a power saving/sleep mode), a schedule for system information transmissions, (e.g., synchronization signals, master information blocks (MIBs), and/or system information blocks (SIBs)), etc. The resource scheduler may allocate radio resources to one or more UEs and indicate transmission parameters for each TTI. The resource scheduler may further indicate an amount of data (e.g., in bits) that can be transmitted within a TTI (e.g., 1 ms), which may correspond to a TB size. [0050] A size of each TB 252 may be based on an instantaneous data rate selected for link adaptation. Thus, link adaptations may impact both MAC and RLC processing. The PHY layer 250 further includes a cyclic redundancy check (CRC) with the TB 252 for error detection procedures. The CRC size may be 24 bits and used to distinguish between successful and unsuccessful packet decoding at a receiver. PHY layer processing is performed prior to transmitting a signal to an air interface. Inverse functionality may be similarly performed for downlink communications when the UE receives one or more TBs 252 on downlink from the base station. [0051] FIG.3 is a diagram 300 that illustrates logical channel prioritization at the MAC layer of the protocol stack of FIG. 2. A data transmission process may be based on multiple logical channels 310-313 that carry data through multiple physical paths. A single transmission path of the multiple physical paths may transmit a finite amount of data/resources per transmission time interval (TTI). If the amount of data in buffer(s) of the logical channels 310-313 exceeds a transmission capacity of a MAC PDU 364, then the data in the logical channel buffers will not fit (in their entirety) within a single MAC PDU 364. Hence, a scheduling entity may determine which logical channel data to provide to the MAC PDU 364 for transmission, and which other 1143801610WO logical channel data may remain in the (s) of the logical channel(s) 310-313 for future transmission at a different MAC PDU transmission occasion. [0052] A UE might generate a MAC PDU 364 according to a predefined protocol that allows the UE to satisfy a quality of service (QoS) for each configured radio bearer. The UE may determine the amount of data to incorporate from each logical channel 310-313 into a current MAC PDU 364 based on an uplink resource grant signaled to the UE on a physical downlink control channel (PDCCH). The UE may also allocate resources for a MAC-control element (MAC-CE) within the MAC PDU 364. The UE can perform a logical channel prioritization procedure for each MAC PDU transmission. Logical channel prioritization refers to incorporating data in the MAC PDU 364 from the different logical channels 310-313 based on priority values of the different logical channels 310-313. [0053] If MAC resources are not large enough to accommodate the logical channel data from all of the logical channel buffers, the MAC resources may be allocated based on a priority level for each logical channel 310-313. For example, an RRC parameter indicates the priority level of each logical channel 310-313, where priority 0 is a highest priority, priority 1 is a next highest priority, and so on. The diagram 300 includes four logical channels 310-313 that correspond to logical channel 0310 having priority 0, logical channel 1311 having priority 1, logical channel 2 312 having priority 2, and logical channel 3313 having priority 3. Each logical channel 310-313 includes data for transmission in the MAC PDU 364. [0054] In a first implementation of the MAC PDU 364b, the logical channel data may be incorporated into the MAC PDU 364b based on a descending order of priority, beginning with priority 0, until all of the available MAC PDU resources are allocated. For instance, the MAC PDU 364b accommodates the data from logical channel 0310, logical channel 1311, and logical channel 2312, but does not have enough remaining resources available to accommodate the data from logical channel 3313. Hence, the data from logical channel 3313 may remain in the buffer of logical channel 3313 until a future MAC PDU has available space to transmit the data from logical channel 3313. If no further data flows into the buffers for logical channels (0, 1, 2) 310- 312, the data from logical channel 3313 may be incorporated into a next MAC PDU transmission. [0055] While strict logical channel prioritization may be sufficient in many instances, if data continues to flow into logical channels (0, 1, 2) 310-312 before each MAC PDU transmission instance, the data held by the buffer for logical channel 3313 may experience “starvation”. That is, the data in logical channel 3313 is repeatedly passed over for incorporation into MAC PDU transmissions in favor of higher priority bearers. Starvation refers to lower priority data that cannot be transmitted over an extended time duration because higher priority data repeatedly 1143801610WO consumes the available MAC PDU resources without allowing the lower priority data to be incorporated into subsequent versions of the MAC PDU 364b for transmission. [0056] To avoid starvation while still serving the logical channels 310-313 based on priority levels, a second implementation of the MAC PDU 364a uses a prioritized bit rate (PBR) 315 configured via RRC to set a data rate for higher priority logical channels that limits resources allocated to the higher priority logical channels before resources begin to be allocated to the lower priority logical channels. This approach reduces starvation of lower priority data, even if high priority data continues to flow into the higher priority logical channels. Each logical channel 310- 313 may be configured with an independent PBR 315. For example, the PBR 315a of logical channel 0310 may be larger or smaller than the PBR 315b of logical channel 1311. [0057] In the second implementation of the MAC PDU 364a, each logical channel 310-313 is served in decreasing order of priority to account for both the PBR 315 and the priority value, and the amount of data from each logical channel 310-313 included in the MAC PDU 364a is initially limited based on the PBR 315 of each logical channel 310-313. If all of the logical channels (0, 1, 2, 3) 310-313 have been served up to their respective PBRs 315, then each logical channel (0, 1, 2, 3) 310-313 can be served again in decreasing priority until the logical channels 310-313 have no more data remaining in their buffers or until all of the available MAC PDU resources are exhausted, whichever comes first. [0058] RRC parameters may control the scheduling of uplink data from each logical channel 310-313, such as parameters for the PBRs 315, a bucket size duration (BSD) for data transmission tokens, and/or indicating that increasing priority values correspond to decreasing levels of priority. Data transmission tokens and a token buckets algorithm prioritizes various logical channel transmissions as described further below. The UE can maintain variable token bucket sizes (Bj) for each logical channel j. The token bucket size (Bj) is initialized to zero when the corresponding logical channel is established, and incremented by a product of PBR × TTI duration for each TTI, where the PBR 315 corresponds to logical channel j. A value of Bj cannot exceed the token bucket size (e.g., more tokens than the bucket can hold) and is, thus, limited to the token bucket size of each logical channel j. The bucket size of a logical channel 310-313 is equal to PBR × BSD, where PBR and BSD are configured based on upper layer parameters. [0059] A MAC-CE included in the MAC PDU 364 may have a higher priority than any of the logical channels 310-313, as the MAC-CE controls operations of a MAC entity. Thus, when the UE generates a MAC PDU 364, the MAC-CE may be included in the MAC PDU 364 first (not shown), such that remaining space in the MAC PDU 364 is used for data allocations from the logical channels 310-313. An exception may be when the UE transmits a first RRC message to a 1143801610WO target cell during a handover procedure. cases, a MAC-CE, such as a buffer status report (BSR), can have a lower priority than the signaling radio bearers (SRBs), so that the handover procedure can be completed as sooner, rather than later. Otherwise, a data transfer interruption time might be extended and a probability of a handover failure might increase as a result of delayed signaling. [0060] Even in examples where higher priority channels are configured with a PBR 315, the lower priority channels/data may still experience starvation if the higher priority channels are associated with large PBRs 315 that consume the available MAC PDU resources before all of the logical channels 310-313 have received an allocation. Hence, in a third implementation of the MAC PDU 364a, which may be regarded as an extension to the second implementation, data from the logical channels 310-313 may be incorporated into the MAC PDU 364a based on techniques that balance the PBRs 315 against instances of starvation of low priority data. [0061] In an example, the priority 3 data from logical channel 3313 might be included in the MAC PDU 364a even if higher priority logical channels (e.g., 310-312) have data in buffers. The third implementation of the MAC PDU 364a may be based on a timing duration/restriction for the logical channels 310-313 according to priority. Each logical channel 310-313 may be associated with a countdown timer, such that each time a logical channel 310-313 transmits an amount of data equal in size to the PBR 315 for the logical channel 310-313, the timer is decreased by 1. If the countdown timer becomes negative, the higher priority logical channel may cede its opportunity to transmit data in an upcoming MAC PDU to a lower priority logical channel. Hence, the countdown timer may prevent higher priority logical channels from monopolizing the MAC PDUs 364a, even if the high priority logical channels have data to transmit (e.g., with high PBRs 315). The countdown timer may be configured based on an RRC parameter bucketSizeDuration. FIG.3 describes how logical channel data is incorporated into a MAC PDU 364 based on a value of a token bucket. FIG.4 describes how a PDU set is transmitted in a MAC PDU. [0062] FIG.4 is a signaling diagram 400 that illustrates a resources allocation procedure, such as for high-throughput ultra-reliable low-latency communication (URLLC). High-throughput URLLC, such as XR/CG traffic, may be communicated between a UE 102 and a network 104, which may include an application server. XR/CG traffic may be associated with various types of augmented reality (AR), virtual reality (VR), and/or mixed reality (MR) environments, where human-to-machine and human-to-human communication may be performed with the assistance of handheld and wearable end-user devices (e.g., the UE 102). CG refers to a set of use cases where an increased number of gaming-related computations (e.g., single-player or multi-player) is offloaded from the UE 102 to one or more edge or remote servers. XR refers to a set of multiple 1143801610WO heterogeneous use cases and services may be roughly divided into AR, VR, and MR applications. [0063] XR/CG traffic may be associated with increased complexities for mobile systems. For example, XR/CG traffic may have a non-integer periodicity or may be quasi-periodic, which might lead to jitter in video frames displayed at the UE 102. The XR/CG traffic might also have a variable data rate that causes streams of the XR/CG traffic, such as video frame streams, communicated between the UE 102 and the application server to change dynamically. A high data rate for downlink communications (e.g., video steams) combined with frequent uplink communications, such as pose/control updates, and/or an uplink video stream may also result in jitter at the UE 102. Both downlink and uplink traffic may have strict packet delay thresholds (PDBs), which may cause one or more video frames to be dropped if the PDBs are not satisfied. [0064] End-user XR/CG devices may correspond to mobile and small-scale devices, which may have limited battery power resources. Therefore, additional power enhancements may be implemented to reduce an overall power consumption of the UE 102 whiles executing XR/CG services. However, current discontinuous reception (DRX) configurations may not be suitable to address the non-integer traffic periodicity or the quasi-periodic XR/CG traffic and/or the variable data rate of the XR/CG traffic. Hence, high-throughput URLLC awareness by the UE 102 and the application server support the network 104 to select radio parameters that improve a quality of the streams of the XR/CG traffic as well as improve a battery life of the UE 102. [0065] XR/CG data streams (e.g., video streams) may change dynamically while XR/CG services are executing over wireless communication systems. Therefore, additional information from higher layers, such as information indicative of a QoS flow association, a frame-level QoS, an application data unit (ADU)-based QoS, an XR-specific QoS, etc, may assist the network 104 in selecting the one or more radio parameters. High-throughput URLLC awareness by the UE 102 and the network 104 may improve a system capacity for supporting XR/CG services and reduce power consumption at the UE 102. Thus, the network 104 (e.g., RAN) may receive an indication of enhanced parameters, which may be directed to radio processing of XR/CG traffic for improved high-throughput URLLC awareness. [0066] High-throughput URLLC awareness may be enhanced for the network 104 to identify characteristic of both uplink and downlink XR/CG traffic, QoS metrics, and application layer attributes. High-throughput URLLC awareness may also allow for improved handling/processing of XR/CG-specific traffic. High-throughput URLLC-specific power saving techniques may be implemented to accommodate XR/CG service characteristics, such as periodicity, multiple flows, jitter, latency, reliability, etc. The power saving techniques may be based on improvements to 1143801610WO connected mode-DRX (C-DRX) and/or PDCCH monitoring procedures. High- throughput URLLC-related capacity improvements may provide a more efficient allocation of resources and scheduling for XR/CG service characteristics based on improvements to semi- persistent scheduling procedures and/or dynamic scheduling/grants. [0067] In some examples, the UE 102 may determine a size of a MAC PDU associated with an uplink grant when the UE 102 receives 410 the uplink grant from the network 104. Based on the size of the MAC PDU, the UE 102 may allocate resources (e.g., in bytes) to one or more logical channels according to bucket sizes of “token buckets” associated with the one or more logical channels as well as the priority levels of the one or more logical channels. The token buckets may be denoted as Bj, which refers to a bucket size of logical channel j. [0068] A token bucket refers to an algorithm executed in packet-switched and telecommunications networks that can be used to check whether data transmissions (e.g., in the form of packets) conform to predefined limits on bandwidth and burstiness, where burstiness is a measure of unevenness or variations in the traffic flow. Token buckets can also be used as a scheduling algorithm to determine a timing of transmissions that comply with the limits set for the bandwidth and the burstiness. The token bucket algorithm is based on an analogy to a fixed capacity bucket into which tokens (e.g., normally representing a unit of bytes or a single packet of predetermined size) are added to the bucket at a fixed rate. When a packet is to be checked for conformance with the predefined transmission limits, the bucket is inspected to determine whether the bucket includes a sufficient number of tokens for a transmission at that time. If so, the appropriate number of tokens (e.g., equivalent to a length of the packet in bytes) are removed from the bucket (e.g., "cashed in") and the packet is passed for transmission. The packet does not conform with the predefined limits for transmission if there is an insufficient number of tokens in the token bucket to perform the transmission. Non-conformant packets may be dropped, queued for subsequent transmission after sufficient tokens have accumulated in the bucket, or transmitted with an indication of non-conformance and possibly dropped at the network 104 if the network 104 is overloaded. [0069] For each logical channel j, the MAC entity may increment Bj by a product the PBR × T before each instance of a logical channel prioritization (LCP) procedure, where T corresponds to an elapsed time since Bj was last incremented. If a value of Bj is greater than the bucket size (e.g., greater than PBR × BSD), the value of Bj is set to the bucket size. A maximum size of a token bucket is equal to PBR × BSD. The UE 102 allocates a number of bytes to transmit an RLC SDU from a logical channel, if the value of Bj for the logical channel includes at least a number of bytes equal to a size of an RLC PDU. Hence, the number of bytes that can be allocated for a 1143801610WO logical channel may be based on Bj (e.g., of the token bucket). The UE 102 may not allocate a number of bytes that is larger than the Bj, except for certain predefined conditions. [0070] For example, the UE 102 may not segment an RLC SDU, a partially transmitted SDU, or a retransmitted RLC PDU, if the whole SDU, partially transmitted SDU, or retransmitted RLC PDU can fit within remaining resources of the MAC entity. If the UE 102 segments the RLC SDU from a logical channel, the UE 102 might maximize a size of the segment to fill, or mostly fill, the resources associated with the uplink grant. That is, UE 102 attempts to maximize each data transmission when possible. If the MAC entity receives 410 an uplink grant size that is equal to or greater than 8 bytes (e.g., when an enhanced logical channel identifier (eLCID) is not used) or 10 bytes (e.g., when eLCID is used) while having available data for transmission, the MAC entity may not transmit only padding or only a padding BSR. [0071] A value of Bj may be negative in some examples. In other words, a logical channel can “borrow” bytes that will be allocated to the logical channel in the future. Negative Bj values may occur in cases where the bucket size is smaller than a size of the RLC PDU, which may otherwise cause the UE 102 to segment the RLC PDU into two or more RLC PDUs. However, segmentation may result in additional overhead, such as through generation of additional RLC headers. To reduce/maintain the overhead, the UE 102 may transmit the whole RLC PDU, even if the value of Bj indicates that there are not enough bytes for the RLC PDU transmission. However, after including the RLC PDU in the MAC PDU, the value of Bj becomes negative. [0072] In XR/CG applications, a PDU set including one or more PDUs may be generated to carry a payload of one unit of information at an application level. A PDU set refers to one or more PDUs that convey an application-generated packet, such as a video frame or a video slice. Video slice refers to a video coding technique that divides a video frame into multiple slices. In examples, the unit of information may correspond to a frame or video slice for XR/CG services. In some implementations, all PDUs of the PDU set have to be received at the application layer to utilize the corresponding unit of information. In other implementations, the application layer can recover part of, or all of, the information unit when some PDUs are missing. A video frame may be divided into multiple IP packets communicated via PDUs of the PDU set. The PDU set may be assigned a delay budget, where the UE 102 and/or network 104 discards the whole PDU set if the whole PDU set is not delivered within a timeframe of the delay budget. [0073] The UE 102 determines, based on the uplink grant, both the size of the MAC PDU and the number of bytes that can be included in the MAC PDU for a logical channel. The number of bytes that can be included in the MAC PDU is based on the token bucket size for that logical channel. Each logical channel is associated with separate token buckets that may be of the same 1143801610WO or different sizes. The UE 102 transmits to the network 104, the MAC PDU including the number of bytes. In some examples, there may not be enough available tokens in the token bucket to include an entire PDU set (e.g., group of RLC PDUs from a same logical channel) in the MAC PDU, despite the MAC PDU being otherwise able to accommodate the entire PDU set. [0074] Since XR/CG applications might have to receive the entire PDU set to generate a video frame, the XR/CG applications may wait for a remainder of the PDUs in the PDU set to arrive at the UE 102 before the video frame can be displayed at the UE 102. Delays in receiving the remainder of the PDU set might increase a likelihood that a delivery deadline of the PDU set will be missed and that the video frame will be dropped as a result of not receiving the entire PDU set by the delivery deadline. [0075] To avoid segmenting a MAC SDU, the UE 102 may include the entire MAC SDU (e.g., RLC PDU) in a MAC PDU transmission 414, regardless of the token bucket size, to reduce overhead associated with the generation of RLC/MAC headers and sub-headers. Accordingly, similar techniques may be applicable to cases where there are not enough tokens in the token bucket to include an entire PDU set in the MAC PDU. In some instances, the UE 102 may include some PDUs of the PDU set in the MAC PDU, even if the MAC PDU can accommodate the entire PDU set. In other instances, the UE 102 may include the entire PDU set in the MAC PDU transmission 414, as long as the token bucket has enough available tokens to transmit at least one PDU from the PDU set. That is, when the UE 102 generates 412 the MAC PDU, if there are enough available tokens in the token bucket to include one PDU, or part of a PDU, (e.g., one RLC PDU or part of an RLC PDU) from a first PDU set in the MAC PDU, the UE 102 may include all other PDUs of the first PDU set in the MAC PDU, regardless of limitations associated with the token bucket. If the number of tokens in the token bucket is not large enough to transmit a whole PDU, the RLC layer 270 may segment the PDU. Likewise, if the network 104 has a PDU set in buffer to transmit to the UE 102, the network 104 may include all PDUs of the PDU set in the same MAC PDU transmission. [0076] Starting at the top of the signaling diagram 400, the UE 102 transmits 406 a first message to the network 104. The first message may correspond to a UE assistance information message that assists the network 104 with configuring the UE 102 for a MAC PDU transmission 414. The UE assistance information message may indicate a maximum size of the PDU set. In examples, the maximum size may be indicated in bytes. The UE assistance information message may also indicate a maximum burst size for the PDU set, which may be likewise indicated in bytes. A burst of PDU sets refers to transmission of one or more than one PDU sets communicated 1143801610WO between the network 104 and the UE a predefined time interval. In further examples, the UE assistance information message may be indicative of an average data rate at the UE 102. [0077] The network 104 transmits 408 a second message to the UE 102 corresponding to a UE configuration message that configures the UE 102 for the MAC PDU transmission 414. In examples, the network 104 transmits 408 the UE configuration message to the UE 102 in response to receiving 406 the UE assistance information message from the UE 102. In other examples, the network 104 transmits 408 the UE configuration message to the UE 102 independent of the UE assistance information message. The UE configuration message may be an RRC message, such as an RRCReconfiguration message, an RRCSetup message, an RRCReestablishment message, an RRCreestablishment message, an RRCResume message. In further examples, the UE configuration message may correspond to a MAC-CE or system information, such as a SIB. [0078] The UE configuration message configures the UE 102 with a first logical channel to transmit one or more PDU sets. The first logical channel may be configured based on parameters associated with the bucket size, the PBR, and/or a priority of the first logical channel. For example, the UE configuration message may configure a bucket size (e.g., in bytes) for the first logical channel that is greater than or equal to the maximum size of the PDU set indicated by the UE 102. In further examples, the parameter configures the bucket size for the first logical cannel to be greater than or equal to the maximum burst size of the PDU sets. The UE configuration message may similarly configure the PBR to be greater than or equal to the average data at the UE 102. The parameter that configures the PBR may be used to set a token generation rate for the token bucket associated with the first logical channel. [0079] In some implementations, the UE 102 may transmit 407a, 407b a scheduling request to the network 104 for a communications channel that the UE 102 may use to transmit 414 high- throughput URLLC traffic, such as the MAC PDU. The scheduling request may indicate resources for logical channel(s) based on a PDU or PDU set within the logical channel(s) having a remaining time to a deliver deadline at the network 104 that is less than a threshold, where the PDU set (e.g., unit of information, frame, video slice, etc.) is dropped if the network 104 does not receive the PDU set by the delivery deadline. The UE 102 may indicate, to the network 104, the remaining time to the delivery deadline. The scheduling request may trigger an uplink grant from the network 104 for transmitting 414 the MAC PDU. The network 104 may prioritize 409 uplink grant(s) to particular UEs based on a remaining time to a PDU or PDU set delivery deadline from the particular UEs. The UE 102 may transmit 407a the scheduling request to the network 104 prior to receiving 408 the UE configuration message from the network 104. Alternatively, the UE 102 may transmit 407b the scheduling request to the network 104 after receiving 408 the UE 1143801610WO configuration message from the network but before receiving 410 the uplink grant for the MAC PDU. [0080] The network 104 transmits 410 an uplink grant to the UE 102 for the MAC PDU transmission 414 based on the determined/indicated size of the MAC PDU or the determined/indicated maximum burst size of the PDU sets. The uplink grant may also be based on the average data rate at the UE 102. The network 104 might maintain a token bucket with the data rate and bucket size indicated by the UE 102. The network 104 allocates uplink resources for the MAC PDU transmission 414 via the uplink grant, where the uplink resources may correspond to a size that is equal to the number of tokens in the buckets. The uplink grant corresponds to downlink control information (DCI) transmitted from the network 104 to the UE 102. The DCI indicates time/frequency resources and a modulation and coding scheme (MCS). Based on the DCI, the UE 102 might determine a size of a MAC PDU that the UE 102 should generate. For example, the network 104 first determines the size of the MAC PDU that UE 102 can transmit 414 and then provides the uplink grant for the UE 102 to transmit 414 the MAC PDU based on the determined size. [0081] The uplink grant may be a dynamic uplink grant transmitted 410 to the UE 102 in DCI on a PDCCH addressed to a cell-radio network temporary identifier (C-RNTI) or a configured scheduling-radio network temporary identifier (CS-RNTI). In other implementations, the network 104 may transmit 410 a configured uplink grant for the MAC PDU. The uplink grant may be dedicated to the first logical channel. In other examples, the uplink grant may be dedicated to a logical channel group, which may include the first logical channel. The UE 102 may use the dedicated grant to transmit 414 data, in the MAC PDU, from the first logical channel or the logical channel group. [0082] The UE 102 generates 412 the MAC PDU based on the uplink grant and/or the UE configuration message. For each logical channel j, the MAC entity may increment a value of the bucket size (Bj) by the product of PBR × T before, where T corresponds to an elapsed time since Bj was last incremented. If the value of Bj is greater than the bucket size, Bj is set to the bucket size. [0083] The UE 102 selects one or more logical channels for incorporation of data into the MAC PDU. In a first example, the UE 102 may select a logical channel based on the data within the logical channel having a remaining time to the deliver deadline being less than a threshold. On uplink, the network 104 configures the UE 102 with a logical channel and indicates a packet delay deadline of the logical channel to the UE 102. Therefore, when a PDU set arrives in the buffer, the UE 102 can start a timer to track the remaining time to the delivery deadline. The 1143801610WO network 104 also configures a threshold the remaining time, so that if the MAC PDU is able to accommodate PDU sets with remaining time(s) less than the threshold, the UE 102 may include the PDU sets in the MAC PDU. The threshold may be indicated in the UE configuration message received 408 from the network 104. The UE 102 may include the data from the selected logical channel(s) into the MAC PDU for the logical channels where the remaining time to the delivery deadline is less than the threshold. In a second example, if the uplink grant is a dedicated grant, the UE 102 may select the logical channel(s) or logical channel group that corresponds to the dedicated grant. In a third example, the UE 102 may select all of the logical channels that include data for transmission. [0084] The UE 102 may allocate resources for logical channels with Bj > 0 in a decreasing order of priority. If the PBR of a logical channel is set to infinity, the MAC entity may allocate resources for all of the data that is available for transmission in the logical channel before satisfying the PBR of different/lower priority logical channel(s). If the UE 102 includes a MAC SDU (e.g., RLC PDU) from the first logical channel in the MAC PDU, and the MAC SDU is included in a first PDU set, the UE 102 includes all remaining MAC SDUs (e.g., RLC PDUs) of the first PDU set in the MAC PDU transmission 414, regardless of the value of Bj. The network 104 may indicate a second threshold to the UE 102 in the UE configuration message, so that if a total size of the remaining MAC SDUs (e.g., RLC PDUs) of the first PDU set is less than or equal to the second threshold, the UE 102 can include the remaining MAC SDUs (e.g., RLC PDUs) of the first PDU set in the MAC PDU. Otherwise, the UE 102 may not be permitted to include the remaining MAC SDUs in the MAC PDU. If the MAC entity is requested to simultaneously transmit 414 multiple MAC PDUs, or if the MAC entity receives 410 multiple uplink grants within one or more overlapping PDCCH occasions, such as for different serving cells, the UE 102 processes the uplink grant that allows the UE 102 to transmit 414 a MAC PDU with the largest size in comparison to other MAC PDUs associated with other uplink grants. [0085] The UE 102 may include information in the MAC PDU that indicates, to the network 104, a status of the PDU set included in the MAC PDU. The information may be associated with the first logical channel or the logical channel group that includes the first logical channel. In an example, the information may be a bit that is set to a first value or a second value. Setting the bit to the first value may indicate that the UE 102 has more data to transmit from the first PDU set, whereas setting the bit to the second value may indicate that the UE 102 has no more data in buffer from the first PDU set. In another example, the information corresponds to a field that indicates the number of bytes remaining in buffer from the first PDU set of the first logical channel. The field may indicate that there are zero bytes remaining in buffer when the UE 102 has no more data 1143801610WO to transmit from the first PDU set. In example, a MAC-CE is used to indicate the information, where the MAC-CE has higher priority than a padding BSR and a sidelink padding BSR. [0086] The UE 102 de-increments the value of Bj by a total size of the MAC SDUs served to logical channel j. If any resources remain in the MAC PDU, each of the logical channels are served in decreasing order of priority, regardless of the value of Bj, until either the data for the logical channels or the uplink grant is exhausted, whichever comes first. If a logical channel is served with the remaining resources and the value of Bj is negative, the UE 102 sets Bj to 0 for the logical channel. In other words, the “borrowed” tokens are “repaid” to the bucket. The UE 102 transmits 414 the MAC PDU to the network after generating 412 the MAC PDU based on the UE configuration message and/or uplink grant. FIGs. 2-4 illustrate procedures for MAC PDU transmissions. FIGs. 5-7 show methods for implementing one or more aspects of FIGs. 2-4. In particular, FIGs.5-6 shows an implementation by the UE 102 of the one or more aspects of FIGs. 2-4. FIG.7 shows an implementation by the network 104 of the one or more aspects of FIGs.2- 4. [0087] FIG.5 is a diagram 500 illustrating an algorithm for transmitting an entire PDU set in a MAC PDU. The diagram 500 starts 502 with tokens being added 504 to a token bucket for a logical channel at a fixed rate. That is, tokens may flow into the token bucket at a steady pace. However, removal of one or more tokens from the token bucket, which represents data being transmitting from the logical channel, may occur at a variable rate. An empty token bucket may indicate that data from the logical channel cannot be transmitted in a MAC PDU until after the token bucket is refilled with sufficient tokens to transmit the data from the logical channel. A UE might receive 506 an indication that a PDU set that includes one or RLC PDUs is available for transmission from the logical channel. The one or more RLC PDUs that comprise the PDU set may correspond to a video frame, where all of the PDUs in the PDU set may have to be communicated through MAC PDU(s) before the video frame can be assembled by a receiver. [0088] Based on the indication of the PDU set available for transmission from the logical channel, the UE determines 508 whether the token bucket has enough tokens for transmission of at least one RLC PDU from the PDU set in the MAC PDU. If so, the UE transmits 512 the entire PDU set in the MAC PDU regardless of a number of tokens in the token bucket for the logical channel, if the MAC PDU is large enough to carry the entire PDU set. Hence, the UE determines 510 whether the MAC PDU is large enough to carry the entire PDU set if the UE determines 508 that there are enough tokens in the token bucket to transmit at least one RLC PDU from the PDU set. 1143801610WO [0089] If the UE determines 510 MAC PDU is not large enough to carry the entire PDU set, the UE can segment the PDU set and include 514 a first segmentation of the PDU set in the MAC PDU for transmission. In examples, where the UE segments the PDU set, the UE might attempt to fill the MAC PDU with as much of the PDU set as will fit in the MAC PDU based on a size of the MAC PDU. The UE may then transmit a remaining segmentation of the PDU set in further MAC PDUs. If the UE 102 has a remaining segmentation to transmit, a next scheduling request (e.g., 407b) can include a time deadline for PDU set delivery completion to avoid a dropped unit. The next scheduling request (e.g., 407b) might indicate to the network 104 that a corresponding uplink grant has an “urgent” PDU delivery threshold. The diagram 500 can end 520 after transmitting 512 the entire PDU set in the MAC PDU or after including 514 a segmentation of the PDU set in the MAC PDU for transmission. [0090] If the UE determines 508 that the token bucket does not have enough tokens for transmission of at least one RLC PDU from the PDU set, the UE may skip 516 to a next logical channel to check for, and include, available data from the next priority logical channel into the MAC PDU. In further examples, if Bj is greater than or equal to 0, the UE may borrow tokens to transmit the PDU set. After skipping 516 to the next logical channel, the UE may check 518 the number of tokens in the token bucket for that logical channel until there are no further channels to check. If there are no further channels to check, the diagram ends 520 without including RLC PDUs from the PDU set in the MAC PDU transmission. If there are further channels to check, the UE again determines 508 whether the token bucket has enough tokens for transmission of at least one RLC PDU from the PDU set, prior to checking the further channels. If, upon a subsequent determination 508, the number of tokens in the token bucket has changed to include enough tokens for transmitting at least one RLC PDU from the PDU set, the UE can proceed with transmitting 512 the entire PDU set in the MAC PDU when the MAC PDU is large enough to carry the entire PDU set. [0091] FIG. 6 illustrates a flowchart 600 of a method of wireless communication at a UE. With reference to FIGs.1, 4, and 8, the method may be performed by the UE 102, the UE apparatus 802, etc., which may include the memory 826', 806', 816, and which may correspond to the entire UE 102 or the entire UE apparatus 802, or a component of the UE 102 or the UE apparatus 802, such as the wireless baseband processor 826 and/or the application processor 806. [0092] The UE 102 transmits 606, to a network, a message that indicates at least one of: a logical channel for transmitting a first MAC PDU, a first maximum size of a PDU set, a second maximum size of a burst of multiple PDU sets, or an average data rate associated with 1143801610WO communications between a UE and an server. For example, referring to FIG. 4, the UE 102 transmits 406 the UE assistance information message to the network 104. [0093] The UE 102 receives 608, from the network, a configuration to transmit the first MAC PDU including the PDU set when a number of available tokens in a token bucket is of the amount that allows for allocation of at least a portion of a PDU from the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU. For example, referring to FIG. 4, the UE 102 receives 408 a UE configuration message from the network 104 that configures the UE 102 for the MAC PDU transmission 414. [0094] The UE 102 receives 610, from a network, an uplink grant that indicates uplink resources for transmission of the first MAC PDU—individual PDUs of the PDU set are allocated to the first MAC PDU from a logical channel based on a number of available tokens in a token bucket dedicated to the logical channel. For example, referring to FIG. 4, the UE 102 receives 410 an uplink grant from the network 104 for transmission 414 of the MAC PDU. [0095] The UE 102 receives 611 a second uplink grant that schedules a simultaneous transmission of a second MAC PDU with the transmission of the first MAC PDU—the transmission of the first MAC PDU is based on the first MAC PDU having a larger size than the second MAC PDU. For example, referring to FIG. 4, the UE 102 receives 410 an uplink grant from the network 104 for transmission 414 of the MAC PDU. [0096] The UE 102 allocates 613 the PDU set to the first MAC PDU based on a delivery deadline of the PDU set being within a threshold time period. For example, referring to FIG. 2, the UE 102 may allocate the RLC PDU set 275 to the first MAC PDU 264a based on a delivery deadline of the PDU set. Referring to FIG. 4, the UE configuration message may configure the UE for the allocation of the PDU set to the MAC PDU. [0097] The UE 102 transmits 614, to the network, the first MAC PDU including the PDU set when the number of available tokens in the token bucket is of the amount that allows for the allocation of at least one PDU from the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU. For example, referring to FIG. 4, the UE 102 transmits 414 the MAC PDU to the network 104 based on the UE configuration message received 408 from the network that configures the token buckets for the logical channels. [0098] The UE 102 adjusts 616 the number of available tokens in the token bucket to zero available tokens after transmitting the first MAC PDU including the PDU set. For example, referring to FIG.4, the UE 102 may adjust the number of token in the token bucket based on the configuration received 408 in the UE configuration message from the network 104. FIG. 6 1143801610WO describe a method from a UE-side of a communication link, whereas FIG.7 describes a method from a network-side of the wireless communication link. [0099] FIG.7 is a flowchart 700 of a method of wireless communication at a network. With reference to FIGs.1, 4, and 9, the method may be performed by one or more network entities 104, which may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, the CU 110, an RU processor 906, a DU processor 926, a CU processor 946, etc. The one or more network entities 104 may include memory 906’/926’/946’, which may correspond to an entirety of the one or more network entities 104, or a component of the one or more network entities 104, such as the RU processor 906, the DU processor 926, or the CU processor 946. [0100] The network 104 receives 706, from a UE, a message that indicates at least one of: a logical channel for reception of a first MAC PDU, a first maximum size of a PDU set, a second maximum size of a burst of multiple PDU sets, or an average data rate associated with communications between the UE and an application server. For example, referring to FIG.4, the network 104 receives 406 the UE assistance information message from the UE 102. [0101] The network 104 transmits 708, to the UE, a configuration for including the PDU set in the first MAC PDU when a number of available tokens in a token bucket dedicated to the logical channel is of an amount that allows for allocation of at least a part of a PDU from the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU. For example, referring to FIG.4, the network 104 transmits 408 a UE configuration message to the UE 102 that configures the UE 102 for the MAC PDU transmission 414. [0102] The network 104 transmits 710, to the UE, an uplink grant that indicates uplink resources for reception of the first MAC PDU. For example, referring to FIG.4, the network 104 transmits 410 an uplink grant to the UE 102 for transmission 414 of the MAC PDU. [0103] The network 104 receives 714, from a UE, the first MAC PDU including the PDU set when the number of available tokens in the token bucket is of the amount that allows for the allocation of at least one PDU from the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU. For example, referring to FIG. 4, the network 104 receives 414 the MAC PDU from the UE 102 based on the UE configuration message transmitted 408 to the UE 102 that configures the token buckets for the logical channels. A UE apparatus 802, as described in FIG. 8, may perform the methods of flowcharts 500-600. The one or more network entities 104, as described in FIG.9, may perform the method of flowchart 700. [0104] FIG. 8 is a diagram 800 illustrating an example of a hardware implementation for a UE apparatus 802. The UE apparatus 802 may be the UE 102, a component of the UE 102, or may implement UE functionality. The UE apparatus 802 may include an application processor 1143801610WO 806, which may have on-chip memory In examples, the application processor 806 may be coupled to a secure digital (SD) card 808 and/or a display 810. The application processor 806 may also be coupled to a sensor(s) module 812, a power supply 814, an additional module of memory 816, a camera 818, and/or other related components. For example, the sensor(s) module 812 may control a barometric pressure sensor/altimeter, a motion sensor such as an inertial management unit (IMU), a gyroscope, accelerometer(s), a light detection and ranging (LIDAR) device, a radio-assisted detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and/or other technologies used for positioning. [0105] The UE apparatus 802 may further include a wireless baseband processor 826, which may be referred to as a modem. The wireless baseband processor 826 may have on-chip memory 826'. Along with, and similar to, the application processor 806, the wireless baseband processor 826 may also be coupled to the sensor(s) module 812, the power supply 814, the additional module of memory 816, the camera 818, and/or other related components. The wireless baseband processor 826 may be additionally coupled to one or more subscriber identity module (SIM) card(s) 820 and/or one or more transceivers 830 (e.g., wireless RF transceivers). [0106] Within the one or more transceivers 830, the UE apparatus 802 may include a Bluetooth module 832, a WLAN module 834, an SPS module 836 (e.g., GNSS module), and/or a cellular module 838. The Bluetooth module 832, the WLAN module 834, the SPS module 836, and the cellular module 838 may each include an on-chip transceiver (TRX), or in some cases, just a transmitter (TX) or just a receiver (RX). The Bluetooth module 832, the WLAN module 834, the SPS module 836, and the cellular module 838 may each include dedicated antennas and/or utilize antennas 840 for communication with one or more other nodes. For example, the UE apparatus 802 can communicate through the transceiver(s) 830 via the antennas 840 with another UE 102 (e.g., sidelink communication) and/or with a network entity 104 (e.g., uplink/downlink communication), where the network entity 104 may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, or the CU 110. [0107] The wireless baseband processor 826 and the application processor 806 may each include a computer-readable medium / memory 826', 806', respectively. The additional module of memory 816 may also be considered a computer-readable medium / memory. Each computer- readable medium / memory 826', 806', 816 may be non-transitory. The wireless baseband processor 826 and the application processor 806 may each be responsible for general processing, including execution of software stored on the computer-readable medium / memory 826', 806', 816. The software, when executed by the wireless baseband processor 826 / application processor 1143801610WO 806, causes the wireless baseband / application processor 806 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the wireless baseband processor 826 / application processor 806 when executing the software. The wireless baseband processor 826 / application processor 806 may be a component of the UE 102. The UE apparatus 802 may be a processor chip (e.g., modem and/or application) and include just the wireless baseband processor 826 and/or the application processor 806. In other examples, the UE apparatus 802 may be the entire UE 102 and include the additional modules of the apparatus 802. [0108] As discussed, the MAC PDU generation component 140 is configured to receive, from a network entity, an uplink grant that indicates uplink resources for transmission of a MAC PDU, where individual PDUs of a PDU set are allocated to the MAC PDU from a logical channel based on a number of available tokens in a token bucket dedicated to the logical channel; and transmit, to the network entity, the MAC PDU including the PDU set when the number of available tokens in the token bucket is of an amount that allows for allocation of at least one of the individual PDUs of the PDU set to the MAC PDU but not an entirety of the PDU set to the MAC PDU. The MAC PDU generation component 140 may be within the wireless baseband processor 826, the application processor 806, or both the wireless baseband processor 826 and the application processor 806. The MAC PDU generation component 140 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by the one or more processors, or a combination thereof. [0109] The UE apparatus 802 may include a variety of components configured for various functions. In examples, the UE apparatus 802, and in particular the wireless baseband processor 826 and/or the application processor 806, includes means for receiving, from a network entity, an uplink grant that indicates uplink resources for transmission of a first MAC PDU, where individual PDUs of a PDU set are allocated to the first MAC PDU from a logical channel based on a number of available tokens in a token bucket dedicated to the logical channel; and means for transmitting, to the network entity, the first MAC PDU including the PDU set when the number of available tokens in the token bucket is of an amount that allows for allocation of at least one of the individual PDUs of the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU. The UE apparatus 802 further includes means for receiving a second uplink grant that schedules a simultaneous transmission of a second MAC PDU with the transmitting the first MAC PDU, where the transmitting the first MAC PDU is based on the first MAC PDU having a larger 1143801610WO size than the second MAC PDU. The UE 802 further includes means for transmitting, to the network entity, a message that indicates at least one of: the logical channel for the transmitting the first MAC PDU, a first maximum size of the PDU set, a second maximum size of a burst of multiple PDU sets, or an average data rate associated with communications between the UE and an application server. The UE apparatus 802 further includes means for receiving, from the network entity, a configuration to transmit the first MAC PDU including the PDU set when the number of available tokens in the token bucket is of the amount that allows for the allocation of the at least one of the individual PDUs of the PDU set to the first MAC PDU but not the entirety of the PDU set to the first MAC PDU. The UE apparatus 802 further includes means for adjusting the number of available tokens in the token bucket to zero available tokens after the transmitting the first MAC PDU including the PDU set. [0110] The means for receiving the uplink grant is further configured to: receive a first indication of a threshold size, where the means for transmitting the first MAC PDU is based on the at least one of the first plurality of MAC SDUs or the second plurality of RLC PDUs being less than or equal to the threshold size. The means for receiving the configuration is further configured to: receive a second indication of a threshold time period, and the means for transmitting the first MAC PDU is further configured to: allocate the PDU set to the first MAC PDU based on a delivery deadline of the PDU set being within the threshold time period. The means may be the MAC PDU generation component 140 of the UE apparatus 802 configured to perform the functions recited by the means. [0111] FIG.9 is a diagram 900 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include, or may correspond to, at least one of the RU 106, the DU, 108, or the CU 110. The CU 110 may include a CU processor 946, which may have on-chip memory 946'. In some aspects, the CU 110 may further include an additional module of memory 956 and/or a communications interface 948, both of which may be coupled to the CU processor 946. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an F1 interface between the communications interface 948 of the CU 110 and a communications interface 928 of the DU 108. [0112] The DU 108 may include a DU processor 926, which may have on-chip memory 926'. In some aspects, the DU 108 may further include an additional module of memory 936 and/or the communications interface 928, both of which may be coupled to the DU processor 926. The DU 1143801610WO 108 can communicate with the RU 106 a fronthaul link 160 between the communications interface 928 of the DU 108 and a communications interface 908 of the RU 106. [0113] The RU 106 may include an RU processor 906, which may have on-chip memory 906'. In some aspects, the RU 106 may further include an additional module of memory 916, the communications interface 908, and one or more transceivers 930, all of which may be coupled to the RU processor 906. The RU 106 may further include antennas 940, which may be coupled to the one or more transceivers 930, such that the RU 106 can communicate through the one or more transceivers 930 via the antennas 940 with the UE 102. [0114] The on-chip memory 906', 926', 946' and the additional modules of memory 916, 936, 956 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 906, 926, 946 is responsible for general processing, including execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor(s) 906, 926, 946 causes the processor(s) 906, 926, 946 to perform the various functions described herein. The computer- readable medium / memory may also be used for storing data that is manipulated by the processor(s) 906, 926, 946 when executing the software. In examples, the MAC PDU configuration component 150 may sit at the one or more network entities 104, such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110, the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106. [0115] As discussed, the MAC PDU configuration component 150 is configured to transmit, to a UE, a configuration for including a PDU set in a MAC PDU when a number of available tokens in a token bucket dedicated to a logical channel is of an amount that allows for allocation of at least one PDU of the PDU set to the MAC PDU but not an entirety of the PDU set to the MAC PDU; and transmit, to the UE, an uplink grant that indicates uplink resources for reception of the MAC PDU. The MAC PDU configuration component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 906, the DU processor 926, and/or the CU processor 946. The MAC PDU configuration component 150 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors 906, 926, 946 configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by the one or more processors 906, 926, 946, or a combination thereof. [0116] The one or more network entities 104 may include a variety of components configured for various functions. In examples, the one or more network entities 104 include means for transmitting, to a UE, a configuration for including a PDU set in a first MAC PDU when a number 1143801610WO of available tokens in a token bucket to a logical channel is of an amount that allows for allocation of at least one PDU of the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU; and means for transmitting, to the UE, an uplink grant that indicates uplink resources for reception of the first MAC PDU. The one or more network entities 104 further include means for receiving, from the UE, a message that indicates at least one of: the logical channel for the reception of the first MAC PDU, a first maximum size of the PDU set, a second maximum size of a burst of multiple PDU sets, or an average data rate associated with communications between the UE and an application server. The means may be the MAC PDU configuration component 150 of the one or more network entities 104 configured to perform the functions recited by the means. [0117] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts. [0118] The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts. [0119] Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. [0120] An element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced 1143801610WO instruction set computing (RISC) systems-on-chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof. [0121] If the functionality described herein is implemented in software, the functions may be stored on, or encoded as, one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media includes computer storage media and can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer. [0122] Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end- user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, machine learning (ML)-enabled devices, etc. The aspects, implementations, and/or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein. [0123] Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor(s), 1143801610WO interleavers, adders/summers, etc. described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of varying configurations. [0124] The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims. [0125] Reference to an element in the singular does not mean “one and only one” unless specifically stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may”, “might”, and “can”, as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of). The phrase “For example” often carries a similar connotation to “may” and, therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases. [0126] Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C” or “one or more of A, B, or C” include any combination of A, B, and/or C, such as A and B, A and C, B and C, or A and B and C, and may include multiples of A, multiples of B, and/or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set of elements where the elements number one or more. [0127] Unless otherwise specifically indicated, ordinal terms such as “first” and “second” do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish between different instances of a term or phrase that follows each ordinal term. Reference numbers, as used in the specification and figures, are sometimes cross-referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbers that have different leading numbers, but have one or more of the same trailing numbers (e.g., 206, 306, 406, etc., may refer to similar features in the drawings). Sometimes an “X” is used to universally 1143801610WO denote multiple variations of a feature. “X06” can universally refer to all reference numbers that end in “06” (e.g., 206, 306, 406, etc.). [0128] Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A”, where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently. [0129] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation. [0130] Example 1 is a method of wireless communication at a UE, including: receiving, from a network, an uplink grant that indicates uplink resources for transmission of a first MAC PDU, where individual PDUs of a PDU set are allocated to the first MAC PDU from a logical channel based on a number of available tokens in a token bucket dedicated to the logical channel; and transmitting, to the network, the first MAC PDU including the PDU set when the number of available tokens in the token bucket is of an amount that allows for allocation of at least a portion of one of the individual PDUs of the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU. [0131] Example 2 may be combined with example 1 and includes that the PDU set included in the first MAC PDU corresponds to at least one of a first plurality of MAC SDUs or a second plurality of RLC PDUs. [0132] Example 3 may be combined with any of examples 1-2 and includes that the receiving the uplink grant includes: receiving a first indication of a threshold size, where the transmitting the first MAC PDU is based on the at least one of the first plurality of MAC SDUs or the second plurality of RLC PDUs being less than or equal to the threshold size. [0133] Example 4 may be combined with any of examples 2-3 and further includes receiving a second uplink grant that schedules a simultaneous transmission of a second MAC PDU with the transmitting the first MAC PDU, where the transmitting the first MAC PDU is based on the first MAC PDU having a larger size than the second MAC PDU. 1143801610WO [0134] Example 5 may be with any of examples 1-4 and further includes transmitting, to the network, a message that indicates at least one of: the logical channel for the transmitting the first MAC PDU, a first maximum size of the PDU set, a second maximum size of a burst of multiple PDU sets, an average data rate associated with communications between the UE and an application server, or a remaining time to a delivery deadline of the PDU set. [0135] Example 6 may be combined with example 5 and further includes receiving, from the network, a configuration to transmit the first MAC PDU including the PDU set when the number of available tokens in the token bucket is of the amount that allows for the allocation of the at least one of the individual PDUs of the PDU set to the first MAC PDU but not the entirety of the PDU set to the first MAC PDU. [0136] Example 7 may be combined with any of examples 5-6 and includes that the configuration includes a parameter that configures the token bucket dedicated to the logical channel to have a size that is greater than or equal to at least one of the first maximum size of the PDU set or the second maximum size of the burst of multiple PDU sets. [0137] Example 8 may be combined with any of examples 6-7 and includes that the receiving the configuration includes: receiving a second indication of a threshold time period for a remaining time to a delivery deadline of the PDU set, and includes that the transmitting the first MAC PDU includes: allocating the PDU set to the first MAC PDU based on the remaining time to the delivery deadline of the PDU set being within the threshold time period. [0138] Example 9 may be combined with any of examples 5-7 and includes that the uplink grant that indicates the uplink resources for the transmitting the first MAC PDU is dedicated to at least one of the logical channel or a logical channel group that includes the logical channel. [0139] Example 10 may be combined with example 9 and includes that the PDU set included in the first MAC PDU is from the at least one of the logical channel or the logical channel group indicated in the uplink grant. [0140] Example 11 may be combined with any of examples 1-10 and includes that the first MAC PDU includes a third indication that indicates a status of the PDU set included in the first MAC PDU. [0141] Example 12 may be combined with example 11 and includes that the third indication is a bit with a first value that indicates a quantity of non-transmitted data from the PDU set, a field with a second value that indicates a number of bytes in a buffer for the PDU set, or a MAC-CE that indicates a higher priority status than a padding BSR. 1143801610WO [0142] Example 13 may be with any of examples 1-12 and further includes adjusting the number of available tokens in the token bucket to zero available tokens after the transmitting the first MAC PDU including the PDU set. [0143] Example 14 is a method of wireless communication at a network, including: transmitting, to a UE, a configuration for including a PDU set in a first MAC PDU when a number of available tokens in a token bucket dedicated to a logical channel is of an amount that allows for allocation of at least a portion of one PDU of the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU; and transmitting, to the UE, an uplink grant that indicates uplink resources for reception of the first MAC PDU. [0144] Example 15 may be combined with example 14 and includes that the PDU set included in the first MAC PDU corresponds to at least one of a first plurality of MAC SDUs or a second plurality of RLC PDUs. [0145] Example 16 may be combined with any of examples 14-15 and further includes receiving, from the UE, a message that indicates at least one of: the logical channel for the reception of the first MAC PDU, a first maximum size of the PDU set, a second maximum size of a burst of multiple PDU sets, an average data rate associated with communications between the UE and an application server, or a remaining time to a delivery deadline of the PDU set. [0146] Example 17 may be combined with example 16 and includes that the network transmits the uplink grant to the UE after prioritizing the remaining time to the delivery deadline of the PDU set over other uplink grant transmissions. [0147] Example 18 may be combined with example 16 and includes that the configuration includes a parameter that configures the token bucket dedicated to the logical channel to have a size that is greater than or equal to at least one of the first maximum size of the PDU set or the second maximum size of the burst of multiple PDU sets. [0148] Example 19 may be combined with any of examples 16-18 and includes that an allocation of the uplink resources indicated in the uplink grant is based on the average data rate and at least one of the first maximum size of the PDU set or the second maximum size of the burst of multiple PDU sets. [0149] Example 20 is an apparatus for wireless communication for implementing a method as in any of examples 1-19. [0150] Example 21 is an apparatus for wireless communication including means for implementing a method as in any of examples 1-19. 1143801610WO [0151] Example 22 is a non- computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of examples 1-19. 1143801610WO

Claims

CLAIMS WHAT IS CLAIMED IS: 1. A method of wireless communication at a user equipment (UE) (102), comprising: receiving (410), from a network (104), an uplink grant that indicates uplink resources for transmission of a first medium access control (MAC) protocol data unit (PDU), individual PDUs of a PDU set being allocated to the first MAC PDU from a logical channel based on a number of available tokens in a token bucket dedicated to the logical channel; and transmitting (414), to the network (104), the first MAC PDU when the number of available tokens in the token bucket is of an amount that allows for allocation of at least a portion of one of the individual PDUs of the PDU set to the first MAC PDU but not an entirety of the PDU set to the first MAC PDU. 2. The method of claim 1, wherein the receiving (410) the uplink grant comprises: receiving (410) a first indication of a threshold size, wherein the transmitting the first MAC PDU is based on the at least one of a first plurality of MAC SDUs or a second plurality of RLC PDUs being less than or equal to the threshold size. 3. The method of claim 2, further comprising: receiving (410) a second uplink grant that schedules a simultaneous transmission of a second MAC PDU with the transmitting (414) the first MAC PDU, wherein the transmitting (414) the first MAC PDU is based on the first MAC PDU having a larger size than the second MAC PDU. 4. The method of any of claims 1-3, further comprising: transmitting (406), to the network (104), a message that indicates at least one of: the logical channel for the transmitting (414) the first MAC PDU, a first maximum size of the PDU set, a second maximum size of a burst of multiple PDU sets, an average data rate associated with communications between the UE (102) and an application server, or a remaining time to a delivery deadline of the PDU set. 5. The method of claim 4, further comprising: 1143801610WO receiving (408), from the network (104), a configuration to transmit the first MAC PDU when the number of available tokens in the token bucket is of the amount that allows for the allocation of the at least one of the individual PDUs of the PDU set to the first MAC PDU but not the entirety of the PDU set to the first MAC PDU. 6. The method of any of claims 4-5, wherein the configuration includes a parameter that configures the token bucket dedicated to the logical channel to have a size that is greater than or equal to at least one of: the first maximum size of the PDU set; or the second maximum size of the burst of multiple PDU sets. 7. The method of any of claims 5-6, wherein the receiving (408) the configuration comprises: receiving (408) a second indication of a threshold time period for a remaining time to a delivery deadline of the PDU set, and wherein the transmitting (414) the first MAC PDU comprises: allocating the PDU set to the first MAC PDU based on the remaining time to the delivery deadline of the PDU set being within the threshold time period. 8. The method of any of claims 4-6, wherein the uplink grant is dedicated to at least one of: the logical channel; or a logical channel group that includes the logical channel, and wherein the PDU set included in the first MAC PDU is from the at least one of the logical channel or the logical channel group. 9. The method of any of claims 1-8, wherein the first MAC PDU includes a third indication that indicates a status of the PDU set included in the first MAC PDU, the third indication being: a bit with a first value that indicates a quantity of non-transmitted data from the PDU set, a field with a second value that indicates a number of bytes in a buffer for the PDU set, or a medium access control-control element (MAC-CE) that indicates a higher priority status than a padding buffer status report (BSR). 10. The method of any of claims 1-9, further comprising: adjusting the number of available tokens in the token bucket to zero available tokens after the transmitting (414) the first MAC PDU. 1143801610WO 11. A method of wireless communication at a network (104), comprising: transmitting (408), to a user equipment (UE) (102), a configuration for a first medium access control (MAC) PDU that includes at least a portion of one PDU of a PDU set, but not an entirety of the PDU set, based on a number of available tokens in a token bucket dedicated to a logical channel; and transmitting (410), to the UE (102), an uplink grant that indicates uplink resources for reception of the first MAC PDU. 12. The method of claim 11, further comprising: receiving (406), from the UE (102), a message that indicates at least one of: the logical channel for the reception of the first MAC PDU, a first maximum size of the PDU set, a second maximum size of a burst of multiple PDU sets, an average data rate associated with communications between the UE (102) and an application server, or a remaining time to a delivery deadline of the PDU set. 13. The method of claim 12, wherein the transmitting (410) the uplink grant comprises prioritizing the remaining time to the delivery deadline of the PDU set over other uplink grant transmissions. 14. The method of claim 12, wherein the configuration includes a parameter that configures the token bucket dedicated to the logical channel to have a size that is greater than or equal to at least one of: the first maximum size of the PDU set or the second maximum size of the burst of multiple PDU sets. 15. An apparatus for wireless communication comprising a transceiver, a memory, and a processor coupled to the transceiver and the memory and configured to implement a method as in any of claims 1-14. 1143801610WO