Allocating resources to multi-modal traffic for extended reality

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for allocating resources to multi-modal XR traffic. A UE receives (744), from a network entity (104), a configuration for a multi-logical channel group including at least two logical channels. The configuration indicates that the at least two logical channels are to be allocated resources for a MAC PDU using a token bucket size that is shared across the multi-logical channel group. The UE transmits (758), to the network entity (104), the MAC PDU including data from the multi-logical channel group. The resources are allocated (756) to the multi-logical channel group to prioritize first data from a first synchronization data group over second data outside of the first synchronization data group.

Description

ALLOCATING RESOURCES TO MULTI-MODAL TRAFFIC FOR EXTENDED REALITYCROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit and priority to U.S. Provisional Application Serial No. 63 / 568,881, entitled “ALLOCATING RESOURCES TO MULTIMODAL TRAFFIC FOR EXTENDED REALITY” and filed on March 22, 2024, 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 scheduling a multi-modal data transmission.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 (5G 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, provide various telecommunication services (e g., telephony, video, data, messaging, 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, a user equipment (UE) allocates resources to logical channels according to a logical channel prioritization (LCP) function. However, when the UE transmits a synchronization data group over a logical channel having resources allocated according to the LCP function, the UE might not be able to transmit an entirety of the synchronization data group within a synchronization deadline, which might degrade a quality of service (QoS).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 delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] A logical channel prioritization (LCP) function allocates resources (e.g., a number of bytes to transmit to a network entity) to logical channels. For example, in a first round of the LCP function, a user equipment (UE) allocates resources to logical channels in a decreasing priority order, where a maximum number of allocated resources is bounded by a current size of a token bucket associated with respective group of logical channels. In a second round of the LCP function, if there are remaining resources left over from the first round, the UE allocates the remaining resources to individual logical channels in the decreasing priority order regardless of a token bucket size until data from the logical channels is exhausted or all of the remaining resources are exhausted.

[0007] Multi-modal data refers to input data from different devices (e.g., sensors) or output data to different destinations (e.g., different UE components) that are used for the same task. In an example, multi-modal data includes camera / video data, microphone / audio data, and haptic data that the UE uses to present a user with an extended reality (XR) experience. In the example, the UE transmits the audio data, the video data, and the haptic data over different logical channels. A satisfactory user experience may depend on each of the different types of multi-modal data being transmitted by a UE within a certain time period. As such, a synchronization data group is defined as data that is generated on one or more logical channels that needs to be synchronized. In an example, a synchronization data group includes audio data, video data, and haptic data for an XR experience, where the audio data, the video data, and the haptic data are each assigned to a different logical channel. If a UE transmits a first part of a synchronization data group, the UE should transmit the remainder of the synchronization data group before a synchronization deadline. The synchronization deadline refers to a transmit time of the first part of the synchronization data group plus a synchronization threshold. A synchronization threshold refers to a maximum tolerable temporal separation of transmission of firstdata (e.g., video data) and second data (e.g.. audio data) in a synchronization data group.

[0008] When a UE uses the LCP function to schedule a transmission of a synchronization data group of multi-modal data (e.g., of an XR application), the UE might not be able to transmit an entirety of the synchronization data group. In an example, a UE is configured with a first logical channel and a second logical channel, where the first logical channel is configured with a bucket size of three and the second logical channel is configured with a bucket size of two. In the example, a synchronization data group includes first data that the UE is to transmit via the first logical channel and second data, third data, and fourth data that the UE is to transmit via the second logical channel. In the example, the UE schedules the first data for transmission on the first logical data channel, leaving two remaining tokens of the first logical channel available. The UE schedules the second data and the third data for transmission on the second logical channel, leaving no remaining tokens of the second logical channel available. As such, the UE is unable to schedule transmission of the fourth data on the second logical channel due to the bucket size (two) of the second logical channel. Instead, the UE schedules other data for transmission on the first logical channel. As a result, the UE is not able to transmit the entirety of the synchronization data group before a synchronization deadline, which might degrade a quality of service (QoS) of the XR application.

[0009] Aspects of the present disclosure address the above-noted and other deficiencies by implementing a procedure that adds logical channel group (LCG) prioritization and resource allocation. An LCG includes at least one logical channel. A UE that implements the LCG prioritization and resource allocation groups logical channel(s) earn ing multi-modal traffic (e.g., multi-modal traffic of an XR application) into an LCG. The LCG is configured with a priority level and a priority bit rate, and has a token bucket. The UE determines how to allocate LCG resources to according to a priority level of the LCG(s) (as opposed to a priority level of a logical channel). If the UE determines that resources are to be allocated to an LCG, the UE prioritizes data from the same synchronization data group within the logical channels in an LCG. A total amount of data transmitted from an LCG is based on a size of a token bucket of the LCG (as opposed to a size of a token bucket of a logical channel). Following the example given above, a UE that implements LCG prioritization and resource allocation may be configured with an LCG with a bucket size of five, such that theUE is able to schedule transmission of the fourth data on the second logical channel, and hence enable the UE to transmit the entirety of the synchronization data group before the synchronization deadline, which can improve the QoS of the XR application.

[0010] According to some aspects, a UE receives from a network entity (and the network entity transmits to the UE) a configuration for a multi-logical channel group that includes at least two logical channels. The configuration indicates that the at least two logical channels are allocated resources for a medium access control (MAC) protocol data unit (PDU) using a token bucket size that is shared across the multi- logical channel group. The UE transmits to the network entity (and the network entity receives from the UE), the MAC PDU including data from the multi-logical channel group. The resources are allocated to the multi-logical channel group to prioritize first data from a first synchronization data group over second data outside of the first synchronization data group.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 illustrates a diagram of 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 illustrates a diagram of a multi-modal interactive system.

[0015] FIG. 5 illustrates a diagram of logical channel prioritization and resource allocation.

[0016] FIG. 6 illustrates a diagram of logical channel group (LCG) prioritization and resource allocation.

[0017] FIG. 7 illustrates a signaling diagram for LCG prioritization and resource allocation.

[0018] FIG. 8 is a flowchart of a method of wireless communication at a UE.

[0019] FIG. 9 is a flowchart of a method of wireless communication at a network entity.

[0020] FIG. 10 illustrates a diagram of a hardware implementation for an example UE apparatus.

[0021] FIG. 11 illustrates a diagram of a hardware implementation for one or more network entities.DETAILED DESCRIPTION

[0022] 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 / network entities 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within 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., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, a CU 1 10 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. Any 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). The base station / network entity 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108), may be referred to as a transmission reception point (TRP).

[0023] Operations of the base station 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 base stations 104d, 104e and / or the RUs 106a, 106b, 106c, 106d may communicate with the UEs 102a, 102b, 102c, 102d, and / or 102s via one or moreradio 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 by intracell and / or inter-cell access links between the UEs 102 and the RUs 106 / base stations 104.

[0024] The RU 106. the DU 108, and the CU 110 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. For example, a wired interface can be configured to transmit or receive the information / signals over a wired transmission medium, such as via the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 1 12 of the base station 104d associated with the cell 190d. The BBU 112 includes a DU 108 and a CU 110, which may also have a wired interface (e.g., midhaul link) configured between the DU 108 and the CU 110 to transmit or receive the information / signals between the DU 108 and the CU 110. In further examples, a wireless interface, which may include a receiver, a transmitter, or a transceiver, such as an RF transceiver, configured to transmit and / 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 104e of the cell 190e via cross-cell communication beams 136-138 of the RU 106a and the base station 104e.

[0025] 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 RU 106 may be based on the functional split, such as a functional split of lower layers.

[0026] 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, in some examples, cross-cell communication beams. For instance, 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 a fourth set of communication beams 136 of the RU 106a. DUs 108 cancontrol both real-time and non-real-time features of control plane and user plane communications of the RUs 106.

[0027] 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 a core network. The base stations 104 may relay communications between the UEs 102 and the core network (not shown). The base stations 104 may be associated with macrocells for higher-power cellular base stations and / or small cells for lower-power cellular base stations. For example, the cell 190e may correspond to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network.”

[0028] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as 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 104d 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 104d / RU 106d.

[0029] 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 earner 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, with more or fewer carriers allocated to either the uplink or the downlink. A primary component carrier and one or more secondary7component carriers may be included in the componentearners. The primary component earner may be associated with a primary cell (PCell) and a secondary component carrier may be associated with a secondary cell (SCell).

[0030] 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. 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.

[0031] 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 communication 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 communication 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 (e.g.. sounding reference signal (SRS)) to the RU 106b based on the second set of communication 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 beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104 / RUs 106 may or may not be the same.

[0032] In further examples, beamformed signals may be communicated between a first base station / RU 106a and a second base station 104e. For instance, the base station 104e of the cell 190e may transmit a beamformed signal to the RU 106a based on the communication beams 138 in one or more transmit directions of the base station 104e. The RU 106a may receive the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the downlink beamformed signal from the base station 104e based on UE communicationbeams 130 in one or more receive directions of the UE 102e. The UE 102e may also transmit an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e may receive the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.

[0033] 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 next 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, or a disaggregated base station including one or more RUs 106, DUs 108, and / or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN). In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station / RU 106a. In such cases, the base station 104e can be a master node and the base station / RU 160a can be a secondary node.

[0034] Still referring to FIG. 1, in certain aspects, any of the UEs 102 may include a logical channel group (LCG) component 140 configured to receive, from a network entity, a configuration for a multi-logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are allocated resources for a medium access control (MAC) protocol data unit (PDU) using a token bucket size that is shared across the multi-logical channel group; and transmit, to the network entity, the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi-logical channel group to prioritize first data from a first synchronization data group over second outside of the first synchronization data group.

[0035] In certain aspects, any of the base stations 104 or a network entity of the base stations 104 may include an LCG configuration component 150 configured to transmit, to a UE, a configuration for a multi-logical channel group including at leasttwo logical channels, the configuration indicating that the at least two logical channels are to be allocated resources for a MAC PDU using a token bucket size that is shared across the multi-logical channel group; and receive, from the UE, the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi-logical channel group according to the configuration to prioritize first data from a first synchronization data group over second data outside the first synchronization data group.

[0036] Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. 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.

[0037] 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 (LI). 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.

[0038] 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 (TBs) 252a, 252b. The MAC layer 260 includes 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 asecond 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.

[0039] 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.

[0040] 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 w ith 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. A PDU set (e.g., a PDCP PDU set, the RLC PDU set 275, a MAC PDU set) includes one or more PDUs that carry a payload of a unit of information generated at an application level (e.g., a frame or a video slice for extended reality (XR) services). In some implementations, an application layer recovers all PDUs in a PDU set in order to use the unit of information. In other implementations, the application layer can recover parts or all of the information unit when some PDUs in the PDU set are missing. 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 identification 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 includepart 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.

[0041] The RLC PDUs 274 are forwarded 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.

[0042] 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 TTL The resource scheduler may further indicate an amount of data (e.g., in bits) that can be transmitted within aTTI (e.g., 1 ms), which may correspond to a TB size.

[0043] 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.

[0044] 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 336a-336d that carry data through multiple physical paths. A single transmission path of the multiple physical paths may transmit a finite amountof data / resources per transmission time interval (TT1). If the amount of data in buffer(s) of the logical channels 336a-336d 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 logical channel data may remain in the buffer(s) of the logical channel(s) 336a- 336d for future transmission at a different MAC PDU transmission occasion.

[0045] 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 336a-336d 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 aMAC-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 336a-336d based on priority values of the different logical channels 336a-336d.

[0046] 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 336a-336d. For example, an RRC parameter indicates the priority level of each logical channel 336a-336d, where priority' 1 is a highest priority, priority 2 is a next highest priority, and so on. The diagram 300 includes four logical channels 336a-336d that correspond to logical channel 1 336a having priority 1, logical channel 2 336b having priority' 2, logical channel 3 336c having priority 3, and logical channel 4 336d having priority 4. Each logical channel 336a-336d includes data for transmission in the MAC PDU 364.

[0047] 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 1, until all of the available MAC PDU resources are allocated. For instance, the MAC PDU 364b accommodates the data from logical channel 1 336a, logical channel 2 336b, and logical channel 3 336c, but does not have enough remaining resources available to accommodate the data from logical channel 4 336d. Hence, the data from logical channel 4 336d may remain in the buffer of logical channel 4336d until a future MAC PDU has available space to transmit the data fromlogical channel 4 336d. If no further data flows into the buffers for logical channels (1, 2, 3) 336a-336c, the data from logical channel 4 336d may be incorporated into a next MAC PDU transmission.

[0048] While strict logical channel prioritization may be sufficient in many instances, if data continues to flow into logical channels (1, 2, 3) 336a-336c before each MAC PDU transmission instance, the data held by the buffer for logical channel 4 336d may experience “starvation”. That is, the data in logical channel 4 336d 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 consumes the available MAC PDU transmission resources without allowing the lower priority data to be incorporated into subsequent versions of the MAC PDU 364b for transmission.

[0049] To avoid starvation while still serving the logical channels 336a-336d based on priority levels, a second implementation of the MAC PDU 364a uses a prioritized bit rate (PBR) 337 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 336a-336d may be configured with an independent PBR 337. For example, although not illustrated as such in FIG. 3, the PBR 337a of logical channel 1 336a may be larger or smaller than the PBR 337b of logical channel 2 336b.

[0050] In the second implementation of the MAC PDU 364a, each logical channel 336a- 336d is served in decreasing order of priority to account for both the PBR 337 and the priority value, and the amount of data from each logical channel 336a-336d included in the MAC PDU 364a is initially limited based on the PBR 337 of each logical channel 336a-336d. If all of the logical channels (1, 2, 3, 4) 336a-336d have been served up to their respective PBRs 337, then each logical channel (1, 2, 3, 4) 336a- 336d can be served again in decreasing priority' until the logical channels 336a-336d have no more data remaining in their buffers or until all of the available MAC PDU resources are exhausted, whichever comes first.

[0051] RRC parameters may control the scheduling of uplink data from each logical channel 336a-336d, such as parameters for the PBRs 337, a bucket size duration (BSD) for data transmission tokens, and / or indicating that increasing priority valuescorrespond to decreasing levels of priority. Data transmission tokens and a token buckets algonthm prioritizes various logical channel transmissions as described further below. The UE can maintain variable token bucket sizes (B / ) for each logical channel j. The token bucket size (By) is initialized to zero when the corresponding logical channel is established, and incremented by a product of PBR x TTI duration for each TTI, where the PBR 337 corresponds to logical channel j. A value of By 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 336a-336d is equal to PBR x BSD, where PBR and BSD are configured based on upper layer parameters.

[0052] A MAC-CE included in the MAC PDU 364 may have a higher pnority than any of the logical channels 336a-336d, 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 336a-336d. An exception may be when the UE transmits a first RRC message to a target cell during a handover procedure. In such 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.

[0053] Even in examples where higher priority channels are configured with a PBR 337, the lower priority channels / data may still experience starvation if the higher priority channels are associated with large PBRs 337 that consume the available MAC PDU resources before all of the logical channels 336a-336d 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 336a-336d may be incorporated into the MAC PDU 364a based on techniques that balance the PBRs 337 against instances of starvation of low priority data.

[0054] In an example, the priority 4 data from logical channel 4 336d might be included in the MAC PDU 364a even if higher priority logical channels (e.g., 336a-336c) have data in buffers. The third implementation of the MAC PDU 364a may be based on a timing duration / restriction for the logical channels 336a-336d according to priority. Each logical channel 336a-336d may be associated with a countdown timer, such thateach time a logical channel 336a-336d transmits an amount of data equal in size to the PBR 337 for the logical channel 336a-336d, 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 337). The countdown timer may be configured based on an RRC parameter bucketSizeDuration. FIG. 3 describes logical channel prioritization at the MAC layer, whereas FIG. 4 describes a multi-modal interactive system that transmits data according to the logical channel prioritization at the MAC layer.

[0055] FIG. 4 illustrates a diagram 400 of a multi-modal interactive system 401. The multi-modal interactive system 401 is configured to process multi-modal data. Multimodal data refers to input data from different kinds of devices / sensors and / or output data to different kinds of destinations (e g., the UEs 102a-102e) used for the same task or application (e.g., an XR application). Multi-modal data includes more than one type of single-modal data. Strong dependenc(ies) may exist betw een different ty pes of single-modal data included in multi-modal data. Single-modal data can be considered to be one type of data. In an example, multi-modal data includes audio data, video data, and haptic data for an XR application.

[0056] The multi-modal interactive system 401 may enable or facilitate tactile and multimodal communication services. Tactile and multi-modal communication services (which may be referred to as the "Tactile Internet”) refers to a network that combines ultra-low latency with high availability', reliability, and security. The Tactile Internet enables control of the Internet of Things (loT) in real time. The loT refers to a collective of network connected devices and the technology that facilitates communication between the devices and the cloud, as well as between the devices themselves. Multiple fields may apply the Tactile Internet, such as industry, robotics and telepresence, virtual reality7, augment reality7, healthcare, road traffic, gaming, education and culture, and / or smart grids. The multi-modal interactive system 401 utilizes multiple modalities (described in greater detail below) in combination in a service to provide complementary techniques that may convey redundant information, but that conveys information effectively. The multi-modal interactive system 401 combines inputs from more than one source and / or combines outputs to more thanone destination. As such, the multi-modal interactive system 401 enables communication services to be more accurate, faster, smoother, and more natural, and allows responses to be faster as well.

[0057] As indicated above, the multi-modal interactive system 401 may enable or facilitate a tactile and multi-modal communication service (or application). A tactile and multi-modal communication service / application includes different modalities that affect a user experience. In an example, a tactile and multi-modal communication service / application includes video / audio media, information perceived by sensors about an environment (e.g., brightness, temperature, humidity), and haptic data. Haptic data includes sensations when touching a surface (e.g., pressure, texture, vibration, temperature) or kinesthetic sensations (e.g., gravity, pull forces, sense of position awareness).

[0058] The multi-modal interactive system 401 may process ambient information (e.g., information perceived by sensors about an environment) to generate loT control instructions as feedback. Haptic data, according to physiological perception, has specific characteristics. For example, the specific characteristics include frequency and latency. As such, a periodic, deterministic, and reliable communication path may be used for transmission of the haptic data. In an example, a haptic device samples at a rate of one thousand times per second and the haptic device transmits the samples individually at one thousand times per second. In an example, a video frame rate may be sixty or ninety frames per second. Thus, a wireless communication system (e.g., 5G NR) may be challenged in the high frequency transmission of small packets over a long distance.

[0059] The multi-modal interactive system 401 can transmit multiple modalities at the same time to multiple application servers for further processing in a coordinated manner in terms of quality of service (QoS) coordination, traffic synchronization, and power saving. The multiple application servers may generate multiple outcomes as feedback. In an example pertaining to a real-time remote virtual reality service, a virtual reality' (VR) user uses a plurality' of independent devices to separately collect video data, audio data, ambient data, and haptic data from a person. The plurality' of independent devices also receives video data, audio data, ambient data, and haptic feedback from one or multiple application servers for a same VR application. In the example, the VR user wears VR glasses to receive images and sounds, a touch glove to receive touch sensations, a camera to collect video inputs, a microphone to collectaudio inputs, and multiple wearable sensors to provide haptic information and environmental information associated to the user. In another example, a real time remote virtual reality service can conduct a session between two user devices (e.g., two VR devices) worn by two users.

[0060] In an example, an experience of an application / service depends on multiple outcomes reaching distributed UEs at the same time (or near the same time). In an example of a sound field reappearing, the application / service sends different channels of sounds to distributed sound boxes in order to simulate sound from a particular direction. A small time difference between arrival times of the different channels of sounds may cause a large direction error that impacts a user experience. In an example, a time difference of 1 ms may cause more than a 30° angle error.

[0061] Multi-modal applications may involve a large number of UEs (102a-102e) located at relatively long distances from one another. In an example involving multi-modal telepresence, tens of UEs may synchronize with one another for time, a control signal, and a visual signal.

[0062] In another example, devices associated to the same tactile and multi-modal communication service discover a tactile and multi -modality' capable UE within a certain proximity of the devices. Upon discovering the tactile and multi-modality capable UE, the devices may wake up. As a UE moves, a different group of tactile and multi-modality' capable devices can service the user. Other scenarios that utilize synchronous control of visual-haptic feedback may include industrial manufacturing and real-time drone applications.

[0063] The multi-modal interactive system 401 includes input devices 414 that generate multi -modality input 413 based on user information 422 and / or ambient information 423. In the multi-modal interactive system 401, a modality' is a type or a representation of information in a specific interactive system. Multi-modal interaction is the process during which multiple modalities exchange information. Modal types may include motion, sentiment, and gesture. Modal representations may include video, audio, and tactile (i.e., vibrations or other movements which provide haptic or tactile sensations to a user). In an example, the input devices 414 include at least one of a camera 414a, a microphone 414b. a gyroscope 414c, a pressure sensor 414d, a temperature sensor 414e, and a haptic sensor 414f. In an example, the multimodality input 413 includes biometrics from voice 402, words from voice 403, emotion from voice 404, biometrics from face 405, emotion from face 406, lipmovements 407, emotion from wearables 408, a gesture 409. a relative location 410 of the user, ambient information 411, and haptic information 412.

[0064] Different services may utilize the multi -modality input 413 to perform functions. In an example, a biometric recognition service 424a uses the biometrics from voice 402 and the biometrics from face 405 to provide biometric recognition of a user. Some services may also utilize the multi -modality input 413 and output(s) from other services to perform functions. In an example, an intention perception service 424b utilizes the words from voice 403, the lip movements 407, the gesture 409, the emotion from voice 404, the emotion from face 406, the emotion from wearables 408. the haptic information 412, and the output of the biometric recognition service 424a to provide multi -modality natural language processing (NLP) functionality, multimodality7emotion functionality, and multi-modality haptic functionality. In yet another example, a presence service 424c uses the relative location 410, the ambient information 411. and output(s) of the intention perception service 424b to provide audio / video services and / or loT control.

[0065] The multi-modal interactive system 401 includes input devices 421 that generate multi-modality output 420 based on the multi-modality input 413 and / or outputs from services (e.g., the presence service 426). The user may perceive the multi-modality output 420. In an example, the output devices 421 include at least one of a display 421a, an audio speaker 421b, a piezoelectric actuator 421c, a temperature changing device 42 Id, lights 42 le, and a vibration device 42 If. In an example, the multimodality output 420 includes haptic feedback 415, brightness 416, temperature 417, video 418, and audio 419.

[0066] In an XR application, a user may perceive multiple sensations (e g., vision, sound, touch) in a virtual environment that involves an information exchange of multiple modalities between an XR device and a base station. Modal representations include video, audio, vibrations, or other movements which provide haptic or tactile feelings to a person. When synchronicity between different modalities decreases, a sense of presence and realism of the user decreases. As such, a multi-modal synchronization threshold is defined as a maximum tolerable temporal separation of the onset of a first stimulus and a second stimulus, one of which is presented to a first sense and the other to another sense, such that the user perceives accompanying sensory objects as being synchronous. FIG. 5 illustrates an example 530 of logical channel prioritization and resource allocation that may be used to allocate resources for the transmission ofmulti-modal data, such as the multi-modal input 413 of the multi-modal interactive system illustrated in FIG. 4.

[0067] FIG. 5 illustrates a diagram 500 of an example 530 of logical channel prioritization (LCP) and resource allocation. A synchronization data group (which may also be referred to as a sync data group) includes data (e.g., a PDCP SDU, a PDCP PDU. a MAC PDU, or an RLC PDU) that is generated on at least one logical channel. In an example, a synchronization data group includes first data generated on a first logical channel and second data generated on a second logical channel. In the example, the first data includes audio data of an XR application and the second data includes video data of the XR application. If a UE (e.g., the UE 102) transmits a first part of a synchronization data group, the UE should transmit the remainder of the synchronization data group before a synchronization deadline. A synchronization deadline is the transmit time of the first part of the synchronization data group plus a synchronization threshold. The synchronization threshold is the maximum tolerable separation of the transmission of the first part of the synchronization data group and the remainder of the synchronization data group.

[0068] In an example, if the UE 102 transmits a first part of a synchronization data group at time t, the synchronization deadline is (t + synchronization threshold). The UE 102 should transmit the rest of the synchronization data group before the synchronization deadline. After the UE 102 transmits the first part of the synchronization data group, a time period from a time before the synchronization deadline began to the synchronization deadline is referred to as remaining synchronization time. Data in the same synchronization data group has the same remaining synchronization time.

[0069] When the UE 102 uses the LCP and allocation to schedule transmission of a synchronization data group of multi-modal data, the UE 102 may be unable to transmit an entirety of a synchronization data group within a synchronization deadline due to a lack of tokens for a component modality. When the UE 102 is unable to transmit the entirety of the synchronization data group within the synchronization deadline, a QoS may be degraded.

[0070] In an example pertaining to FIG. 5, the UE 102 is to transmit synchronization data group 1 532a, synchronization data group 2 532b. and other data 532c. To facilitate the transmission of synchronization data group 1 532a, synchronization data group 2 532b, and other data 532c, the network entity 104 configures the UE 102 with logical channel 1 536a, logical channel 2 536b, logical channel 3 536c, and logical channel 4536d. The UE 102 generates data and transmits the data on logical channel 1 536a. logical channel 2 536b, logical channel 3 536c, and logical channel 4 536d. In an example, each of the logical channels 536a-536d has a respective bucket size 534a- 534d. In the example, the bucket size 534a of logical channel 1 536a is two, the bucket size 534b of logical channel 2 536b is three, the bucket size 534c of logical channel 3 536c is two, and the bucket size 534d of logical channel 4 536d is two. Each of the logical channels 536b-536d may cany' different forms of multi-modal data. In an example, logical channel 2 536b carries audio data, logical channel 3 536c carries video data, and logical channel 4 536d carries haptic data. Each of the logical channels 536a-536d has a priority level. In an example, logical channel 1 536a has a high priority (e.g., priority level 3), logical channel 2536b has a medium priority (e.g., priority level 2), and logical channel 3 536c and logical channel 4 536d have a low priority (e.g., priority level 1).

[0071] The UE 102 schedules transmission of data on each of the logical channels 536a- 536d based on the bucket sizes 534a-534d, respectively. In the example depicted in FIG. 5, the UE 102 is unable to schedule transmission of data 12 426 and data 17 427 because there are not enough tokens in token buckets of logical channel 3 536c and logical channel 4536d. Instead, the UE 102 schedules transmission of data 6 and data 7 425, because logical channel 2 536b has tokens remaining in its bucket. For instance, as depicted in FIG. 5, the UE 102 allocates resources to logical channel 1 536a to transmit data 1 and data 2 in a MAC PDU 564 based on the bucket size 534a of two and based on logical channel 1 536a having a high priority (remaining tokens of logical 536a = 0). The UE 102 allocates resources to logical channel 2 536b to transmit data 5, data 6, and data 7 in the MAC PDU 564 based on the bucket size 534b of three and based on the logical channel 2 536b having a medium priority' (remaining tokens of logical channel 2 536b = 0). The UE 102 allocates resources to logical channel 3 536c to transmit data 10 and data 11 in the MAC PDU 564 based on the bucket size 534c of two and based on logical channel 3 536c having a low priority (remaining tokens of logical channel 3 536c = 0). The UE 102 allocates resources to logical channel 4 536d to transmit data 15 and data 16 in the MAC PDU 564 based on the bucket size 534d of two and based on logical channel 3 536d having the low priority (remaining tokens of logical channel 4 536d = 0).

[0072] The UE 102 then begins another round of allocation in which the UE 102 allocates resources to logical channel 1 536a to transmit data 3 and data 4 in the MAC PDU564. Thus, while data 12 426 and data 17 427 belong to synchronization data group1 532a, the UE fails to allocate resources to logical channel 2536b and logical channel 3 536c due to bucket size 534c and bucket size 534d being insufficiently large, and hence the UE fails to include data 12 426 and data 17 427 in the MAC PDU 564. If a synchronization deadline of synchronization data group 532a expires before the UE 102 receives a next uplink grant, the UE may fail to transmit data 12 and data 17 by the synchronization deadline. Failing to transmit data 12 426 and data 17 527 may thus degrade a QoS of an XR application. FIG. 5 illustrates per-logical channel prioritization and resource allocation, whereas FIG. 6 illustrates an example of logical channel group prioritization and resource allocation.

[0073] FIG. 6 illustrates a diagram 600 of LCG prioritization and resource allocation. In an example 630 of ECG prioritization and resource allocation depicted in FIG. 6, the network entity 104 configures the UE 102 with logical channel 1 536a, logical channel2 536b. logical channel 3 536c. and logical channel 4 536d similar to the manner described in FIG. 5. The network entity 104 further configures the UE 102 with priority levels for each of the logical channels 536a-536d. In the example, logical channel 1 536a has a high priority level, logical channel 2 536b has a medium priority, and logical channel 3 536c and logical channel 4 536d have low priorities similar to the priority levels described in FIG. 5.

[0074] The network entity 104 further configures the UE with LCG 1 638 and LCG 2 641. LCG 1 638 includes a single logical channel: logical channel 1 536a. As such, LCG 1 638 is referred to a mono-LCG. LCG 2641 includes multiple logical channels: logical channel 2 536b. logical channel 3 536c, and logical channel 4 536d. As such. LCG 1 638b is referred to as a multi-LCG. Because LCG 1 638 includes a single logical channel, LCG 1 638 has the high priority from logical channel 1 536a and LCG 1 638 has an LCG bucket size 634 A of two from the bucket size 534a of logical channel 1 536a. However, the network entity configures LCG 2 641 with a medium priority and an LCG bucket size 634b of seven. In the example, synchronization data group 1 532a has a shortest remaining synchronization time timer (or a shortest remaining delivery time timer). A priority of the LCG may be configured by the network entity 104, set as equivalent to the highest priority logical channel in the LCG, set as equivalent to a median priority level of the logical channels in the LCG, set as equivalent to the lowest priority logical channel in the LCG, or determined in a different manner. An LCG token bucket size may be configured by the network entity104, be equivalent to the sum of logical channel token buckets within the LCG, be equivalent to the sum of logical channel token buckets within the LCG as capped at a given value, or determined in another manner.

[0075] In round 1 639a of resource allocation, the UE 102 allocates resources to LCG 1 638 (i.e., logical channel 1 536a) to transmit data 1 and data 2 in a MAC PDU 664 based on LCG 1 638 having the high priority and based on the LCG bucket size 634a of two (remaining tokens of LCG 1 638 = 0). Subsequently, and still in round 1 639a of resource allocation, the UE 102 allocates resources to LCG 2 641 to transmit synchronization data group 1 532a. In the example, synchronization data group 1 532a has a shortest remaining synchronization time timer (or a shortest remaining delivery time timer), that is, synchronization data group 1 532a has a shorter remaining synchronization time timer (or a shorter remaining delivery7time timer) compared to a remaining synchronization time timer (or a remaining delivery time timer) of synchronization data group 1 532b.

[0076] Because logical channel 2 536b has a highest priority within LCG 2 641, the UE 102 allocates resources to transmit data 5 in the MAC PDU 664 in round 1 639a (remaining tokens of LCG 2 641 = 6). As no data remains from synchronization data group 1 532a on logical channel 2 536b, the UE 102 allocates resources to logical channel 3 536c to transmit data 10, data 11, and data 12 in the MAC PDU 664 (remaining tokens of LCG 2 641 = 3). As data no remains from synchronization data group 1 532a on logical channel 2 536c, the UE 102 allocates resources to logical channel 4 536d to transmit data 15, data 16, and data 17 in the MAC PDU 664 (remaining tokens of LCG 2 641 = 0).

[0077] In round 2 639b, the UE 102 allocates resources to LCG 1 638 (i.e., logical channel 1 536a) to transmit data 3 and data 4 in the MAC PDU 664. Alternatively, if data 6 and data 7 belonged to synchronization data group 1 532a (as opposed to synchronization data group 2 532b), in round 1 639a. the UE 102 would allocate resources to logical channel 2 536b to transmit data 6 and data 7 in the MAC PDU 664. Thus, in comparison to the example 530 of logical channel prioritization and resource allocation in FIG. 5, the example 630 of logical channel group prioritization and resource allocation in FIG. 6 helps to ensure that the MAC PDU 664 includes data of synchronization data group 1 532a and that the UE 102 is able to transmit the data of synchronization data group 1 532a before a synchronization deadline, which may improve a QoS. FIG. 7 illustrates a signaling diagram associated with logicalchannel group prioritization and resource allocation, as described above with respect to FIG. 6.

[0078] FIG. 7 is a signaling diagram 700 illustrating communications between a UE 102 and a network entity 104 for allocating resources for wireless communication. The network entity 104 may correspond to a base station or a unit of a base station, such as the RU 106, the DU 108, the CU 110, etc.

[0079] The UE 102 transmits 742 UE capability information to the network entity 104. The UE capability information indicates that the UE supports LCG prioritization and / or LCG resource allocation. In LCG prioritization, the UE 102 performs prioritizations among LCGs and logical channels to allocate resources (e.g., bytes to transmit in a MAC PDU). In LCG resource allocation, the UE 102 allocates resources to an LCG to transmit data of the LCG.

[0080] The network entity receives 742 the UE capability information transmitted by the UE 102. Based on the UE capability information, the network entity 104 transmits 744 an RRC configuration for an LCG (or an LCG configuration) to the UE 102. The RRC configuration configures the UE 102 with at least one LCG. An LCG includes at least one logical channel. A multi-LCG refers to an LCG that includes a plurality of logical channels. A mono-LCG refers to an LCG that includes one logical channel. The RRC configuration may configure the UE 102 with logical channel(s) that do not belong to a logical channel group as well. In an example, the RRC configuration may configure the UE 102 with a logical channel that does not belong to a logical channel group, a logical channel that belongs to a mono-LCG, or a logical channel that belongs to a multi-LCG. In an example, the network entity transmits 744 the RRC configuration in an RRC message such as an RRC reconfiguration message, an RRC setup message, an RRC reestablishment message, or an RRC resume message. In aspects, the network entity 104 transmits an LCG configuration in a system information message.

[0081] The RRC configuration indicates a priority level (which may also be referred to as a priority order), a prioritized bit rate (PBR), and / or a bucket size duration (BSD) for a logical channel. The UE maintains, based on the RRC configuration, a bucket size (i.e., a variable token bucket size) for each logical channel, denoted as By. The bucket size B / = PBR x T, where T corresponds to an elapsed time since the UE last incremented By. The maximum bucket size is given by PBR x BSD. If By is greater than the maximum bucket size, the UE 102 sets By to the maximum bucket size. TheBS 104 can configure the value of the PBR to be infinity. In that case, the bucket size of the logical channel is infinity.

[0082] In aspects, the RRC configuration indicates logical channels that belong to an LCG and a priority level, a prioritized bit rate (PBR), and a bucket size duration (BSD) for the LCG. In aspects, the RRC configuration indicates a synchronization threshold for the LCG. In other aspects, the synchronization threshold is predefined. In aspects, the UE 102 derives the priority level, the prioritized bit rate, and the maximum size from logical channels in an LCG (described in greater detail below).

[0083] When the UE 102 has new data to transmit, the UE 102 transmits 746. based on the RRC configuration, a scheduling request to the network entity 104 to notify the network entity 104 of the new data. The RRC configuration indicates a radio resource (e.g., a time resource and a frequency resource) on which the UE is to transmit 746 the scheduling request. When the UE 102 has new data to transmit, the UE 102 also starts a remaining delivery time timer for the new data in order to monitor a remaining delivery time for the new data. The RRC configuration indicates the length of the remaining delivery time. If the remaining delivery' time timer expires, the UE 102 discards the new data. The UE 102 initially sets the remaining delivery time timer to a delay budget indicated by the RRC configuration.

[0084] The network entity 104 receives 746 the scheduling request from the UE 102. The network entity 104 transmits 748, based on the scheduling request, an uplink grant to the UE 102. The uplink grant indicates radio resources (e.g., time resources and frequency resources) for the UE 102 to transmit an uplink transmission (e.g., a transmission of a MAC PDU). In aspects, the RRC configuration configures the UE 102 with the uplink grant and a periodicity. The UE is to transmit the uplink transmission according to periodicity indicated by the uplink grant. In an example, the network entity 104 transmits 748 the uplink grant to the UE 102 in downlink control information (DCI) on aPDCCH, in a random-access response (RAR) message during a random-access procedure, or in an RRC message, such as an RRCReconfiguration message or an RRCRelease message.

[0085] The UE 102 receives 748 the uplink grant from the network entity 104. In an example, the UE 102 receives 748 the uplink grant in DCI on a PDCCH, in a RAR message during a random-access procedure, or in an RRC message, such as an RRCReconfiguration message or an RRCRelease message. When the UE 102 receives 748 the uplink grant, the UE 102 determines a size of a MAC PDU associatedwith the uplink grant. Based on the size of the MAC PDU. UE 102 allocates resources (e.g., bytes in the MAC PDU) to a logical channel and / or an LCG according to bucket sizes of the logical channel and / or the LCG, respectively. The UE 102 multiplexes data from the logical channels or the LCGs into the MAC PDU according to the resource allocation result.

[0086] In aspects, the UE 102 derives the priority level, the prioritized bit rate, and the maximum bucket size from logical channels in the LCG. The UE 102 calculates 750 the priority level of the LCG as the highest priority level among logical channels in the LCG in one embodiment. In another embodiment, the UE 102 calculates 750 the priority level of the LCG as the lowest priority level among logical channels in the LCG. The UE 102 calculates 752 the prioritized bit rate as a sum of prioritized bit rates of logical channels in the LCG. The UE 102 calculates 754 the maximum bucket size as a sum of maximum bucket sizes of the logical channels in the LCG in one embodiment. The UE 102 calculates the bucket size Bj of the LCG j according to PBR x T, where T corresponds to an elapsed time since the UE 102 incremented B / incremented. The network entity 104 can configure (in the RRC configuration) a value of PBR to be infinity. In such a case, the UE 102 calculates the bucket size of the LCG as infinity.

[0087] Based on the size of determined size of the MAC PDU, the UE 102 allocates 756 resources (e.g., bytes in the MAC PDU) to a LCG (or LCGs) according to a bucket size of the LCG (which, as described above, may include one logical channel or multiple logical channels).

[0088] The UE 102 allocates 756 the resources to LCGs in a first round and a second round. In the first round, the UE 102 allocates 756 the resources to the LCGs according to a descending priority order of the LCGs.

[0089] In aspects, in the first round, the UE 102 allocates 756 the resources to the LCGs and logical channels that do not belong to any LCG according to the descending priority order of the LCGs and logical channels. In one example, if the RRC configuration indicates that an LCG has a higher priority than a logical channel, the UE 102 prioritizes allocating the resources to the LCG. In another example, if the RRC configuration indicates that a logical channel has a higher priority than a LCG. the UE 102 prioritizes allocating the resources to the logical channel. In a further example, if the RRC configuration indicates that a mono-LCG has a higher priority than a multi-LCG, the UE 102 prioritizes allocating the resources to the mono-LCG.

[0090] In other aspects, in the first round, the UE 102 allocates 756 first resources in the resources to LCGs (e.g., mono-LCGs or multi-LCGs) according to a descending priority order of the LCGs indicated by the RRC configuration. Subsequently, the UE 102 allocates 756 second resources in the resources to logical channels according to a descending priority order of the logical channels indicated by the RRC configuration.

[0091] In further aspects, in the first round, if the UE 102 has allocated resources to an LCG to transmit a part of a synchronization data group (e.g., in a last uplink grant), the UE 102 allocates resources to the LCG to transmit the remainder of the synchronization data group. If the UE 102 has allocated resources to more than one LCG to transmit the part of the synchronization data group, the UE 102 can allocate resources to the LCGs in any order. In aspects, the UE 102 allocates resources to the LCGs in a descending priority order. After the UE 102 allocates resources to the LCGs that the UE 102 has partially transmitted the part of the synchronization data group, the UE 102 allocates resources to other LCGs and logical channels in a descending priority order.

[0092] In an example, the UE 102 has allocated 756 first resources to transmit a part of synchronization data group 1 from LCG 1 and the UE has allocated 756 second resources to transmit a part of synchronization data group 2 in LCG 2. In the example, the RRC configuration indicates that LCG 1 has a higher priority than LCG 2. If the UE 102 receives 748 an uplink grant, the UE 102 first allocates resources to LCG 1 to transmit a remaining part of synchronization data group 1 due to LCG 1 having a higher priority. The UE 102 then allocates resources to LCG 2 to transmit the remaining part of synchronization data group 2.

[0093] After the UE 102 allocates resources to an LCG j (which, as noted above, may include a single logical channel or multiple logical channels), the UE 102 decrements a bucket size By for the LCG / by an amount of allocated resources (e.g., a number of bytes). If the network entity 104 configures the PBR of the logical channel j to be infinity, the UE 102 allocates resources to transmit all data that is available for transmission in the logical channel j before allocating resources to lower priority logical channel group(s).

[0094] When the UE 102 allocates resources to an LCG, the LCG may have more than one synchronization data group pending for transmission in the LCG. In aspects, the UE 102 allocates resources (e.g., bytes in a MAC PDU) to transmit a synchronizationdata group with a shortest remaining synchronization time. In aspects, if a synchronization data group includes data from more than one logical channel, the UE 102 can allocate resources to logical channels in any order. In other aspects, if the synchronization data group includes data from more than one logical channel, the UE 102 allocates resources to logical channels in a descending priority of the logical channels.

[0095] In other aspects, if an LCG has more than one synchronization data group pending for transmission in the LCG, the UE 102 allocates resources to transmit a synchronization data group that includes data with a shortest remaining delivery time. In aspects, if a synchronization data group includes data from more than one logical channel, the UE 102 can allocate resources to logical channels in any order. In other aspects, if the synchronization data group includes data from more than one logical channel, the UE 102 allocates resources to logical channels in a descending priority of the logical channels.

[0096] As noted above, the UE 102 allocates 756 the resources LCGs in a first round and a second round. After the UE performs the first round of resource allocation, the UE 102 performs the second round of resource allocation if remaining resources exist for allocation. In the second round of resource allocation, if the UE 102 has allocated resources to transmit a part of a synchronization data group (e.g., for another uplink grant different from the uplink grant received or as part of the first round) for an LCG, the UE 102 allocates resources to the LCG to transmit the remainder of the synchronization data group. Similar to the first round, if more than one LCG exists, the UE may allocate resources to the LCGs in any order. Alternatively, the UE 102 may allocate resources to LCGs in a descending priority order of the LCGs.

[0097] In aspects pertaining to the second round of resource allocation, if an LCG includes a synchronization data group with a remaining synchronization time below a threshold, the UE 102 allocates resources to the LCG to transmit the synchronization data group. In aspects, if more than one LCG exists, the UE 102 can allocate resources to LCGs in any order. In other aspects, if more than one LCG exists, the UE 102 allocates resources to logical channels in a descending priority order of the LCGs.

[0098] The UE 102 may also allocate 756 the resources to LCGs in a third round that occurs after the first round and the second round if resources remain unallocated after the first round and the second round. In the third round, the UE 102 allocates resources to logical channels or LCGs (e.g., mono-LCGs or multi-LCGs) in adecreasing priority order of the logical channels or LCGs until the UE exhausts data from the LCGs or until the UE uses all of the resources, whichever occurs first. Accordingly, if a highest priority logical channel or a highest priority LCG has a relatively large amount of data pending in a buffer in the third round, the highest priority logical channel or the highest priority LCG can consume remaining resources without giving lower priority’ logical channels or lower priority LCGs an opportunity to reduce amounts of data pending in their respective buffers. To allocate resources to an LCG j, the UE 102 allocates resources to the logical channel(s) of the LCG j in a descending priority order of the logical channels.

[0099] After the UE 102 allocates resources to logical channels and LCGs, the UE 102 builds a MAC PDU according to the resource allocation. The UE 102 transmits 758 the MAC PDU to the network entity’ 104. After the UE 102 transmits the MAC PDU, the UE 102 starts a remaining synchronization time timer for synchronization data group(s) transmitted in the MAC PDU. The UE 102 initially sets the remaining synchronization time timer to a synchronization threshold provided in the RRC configuration. The network entity 104 receives 758 the MAC PDU from the UE 102. FIGs. 6-7 illustrate logical channel prioritization and resource allocation. FIGs. 8-9 show methods for implementing one or more aspects of FIGs. 6-7. In particular, FIG. 8 shows an implementation by the UE 102 of the one or more aspects of FIGs. 6-7. FIG. 11 shows an implementation by the network entity 104 of the one or more aspects of FIGs. 6-7.

[0100] FIG. 8 illustrates a flowchart 800 of a method of wireless communication at a UE. With reference to FIGs. 1. 7, and 10, the method may be performed by the UE 102. the UE apparatus 1002, etc., which may include the memory 1026', 1006', 1016, and which may correspond to the entire UE 102 or the entire UE apparatus 1002, or a component of the UE 102 or the UE apparatus 1002, such as the wireless baseband processor 1026 and / or the application processor 1006.

[0101] The UE 102 transmits 842, to the network entity 104, UE capability information indicating that the UE 102 supports logical channel group prioritization and resource allocation, wherein receiving the configuration is based on the UE capability information. For example, referring to FIG. 7, the UE 102 transmits 742, to the network entity, UE capability information indicating that the UE 102 supports logical channel group prioritization and resource allocation, wherein receiving the RRCconfiguration is based on the UE capability information. In an example. FIG. 6 shows a multi-LCG 641 corresponding to a multi-logical channel group.

[0102] The UE 102 receives 844, from the network entity 104, the configuration for the multi-logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are allocated resources for a MAC PDU using a token bucket size that is shared across the multi-logical channel group. For example, referring to FIG. 7, the UE 102 receives 744, from the network entity 104, the configuration for the multi-logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are allocated resources for a MAC PDU using a token bucket size that is shared across the multi-logical channel group. In an example, FIG. 6 shows logical channel 2536b, logical channel 3 536c, and logical channel 4 536d corresponding to the at least two channels. In another example, FIG. 6 shows an LCG bucket size 634b corresponding to the token bucket size that is shared across the multi-logical channel group. In a further example, FIG. 6 shows a MAC PDU 664 corresponding to the MAC PDU.

[0103] The UE 102 transmits 846, to the network entity 104, a scheduling request. For example, referring to FIG. 7, the UE 102 transmits 746, to the network entity 104, a scheduling request.

[0104] The UE 102 receives 848, from the network entity 104 based on the scheduling request, an uplink grant, wherein transmitting the MAC PDU is further based on the uplink grant. For example, referring to FIG. 7, the UE 102 receives 748, from the network entity 104 based on the scheduling request, an uplink grant, wherein transmitting the MAC PDU is further based on the uplink grant.

[0105] In aspects, the configuration indicates, for the at least two logical channels of the multi-logical channel group, a first token bucket size, a first priority order of the at least two logical channels, and a first prioritized bit rate (PBR). The UE 102 calculates 850. based on the first token bucket size, the token bucket size. For example, referring to FIG. 7, the UE 102 calculates 750, based on the first token bucket size, the token bucket size.

[0106] The UE 102 calculates 852, based on the first priority order, a priority order of the multi-logical channel group. For example, referring to FIG. 7, the UE 102 calculates 752, based on the first priority order, a priority order of the multi-logical channel group.

[0107] The UE 102 calculates 854, based on a first PBR. a multi-logical channel group PBR, and wherein transmitting the MAC PDU is based on the token bucket size, the priority order of the multi-logical channel group, and the multi-logical channel group PBR. For example, referring to FIG. 7, the UE 102 calculates 854, based on a first PBR. a multi-logical channel group PBR, and wherein transmitting the MAC PDU is based on the token bucket size, the priority order of the multi-logical channel group, and the multi-logical channel group PBR.

[0108] The UE 102 allocates 856, based on the priority' order of the multi-logical channel group, the resources to the multi-logical channel group, the priority order being indicated by the configuration. For example, referring to FIG. 7, the UE 102 allocates 756, based on the priority order of the multi-logical channel group, the resources to the multi-logical channel group, the priority order being indicated by the configuration.

[0109] The UE 102 transmits 858, to the network entity 104, the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi- logical channel group to prioritize first data from a first synchronization data group over second data outside of the first synchronization data group. For example, referring to FIG. 7, the UE 102 transmits 758, to the network entity 104, the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi-logical channel group to prioritize first data from a first synchronization data group over second data outside of the first synchronization data group. In an example, FIG. 6 shows a synchronization data group 1 532a and a synchronization data group 2 532b corresponding to the first synchronization data group and the second synchronization data group, respectively. FIG. 7 describes a method from a UE-side of a wireless communication link, whereas FIG. 8 describes a method from a network-side of the wireless communication link.

[0110] FIG. 9 is a flowchart 900 of a method of wireless communication at a network entity. With reference to FIGs. 1, 7, and 1 1, 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, and / or the CU 110.

[0111] The network entity 104 receives 942, from a UE 102. UE capability information indicating that the UE supports logical channel group prioritization and resource allocation, wherein transmitting a configuration is based on the UE capability information. For example, referring to FIG. 7, the network entity' 104 receives 742,from a LIE 102, UE capability information indicating that the UE supports logical channel group prioritization and resource allocation, wherein transmitting a configuration is based on the UE capability information. In an example, FIG. 6 shows a multi-LCG 641 corresponding to a multi-logical channel group.

[0112] The network entity 104 transmits 944, to the UE 102. the configuration for a multi- logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are to be allocated resources for a MAC PDU using a token bucket size that is shared across the multi-logical channel group. For example, referring to FIG. 7. the network entity 104 transmits 744, to the UE 102, the configuration for a multi -logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are to be allocated resources for a MAC PDU using a token bucket size that is shared across the multi-logical channel group. In an example, FIG. 6 shows logical channel 2 536b. logical channel 3 536c, and logical channel 4 536d corresponding to the at least two channels. In another example, FIG. 6 shows an LCG bucket size 634b corresponding to the token bucket size that is shared across the multi-logical channel group. In a further example, FIG. 6 shows a MAC PDU 664 corresponding to the MAC PDU.

[0113] The network entity 104 receives 946, from the UE 102, a scheduling request. For example, referring to FIG. 7, the network entity 104 receives 746, from the UE 102, a scheduling request.

[0114] The network entity 104 transmits 948, to the UE 102 based on the scheduling request, an uplink grant, wherein receiving the MAC PDU is further based on the uplink grant. For example, referring to FIG. 7, the network entity7104 transmits 748, to the UE 102 based on the scheduling request, an uplink grant, wherein receiving the MAC PDU is further based on the uplink grant.

[0115] The network entity 104 receives 958, from the UE 102, the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi- logical channel group according to the configuration to prioritize first data from a first synchronization data group over second data outside the first synchronization data group. For example, referring to FIG. 7, the network entity 104 receives 758. from the UE 102, the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi-logical channel group according to the configuration to prioritize first data from a first synchronization data group oversecond data outside the first synchronization data group. In an example. FIG. 6 shows a synchronization data group 1 532a and a synchronization data group 2 532b corresponding to the first synchronization data group and the second synchronization data group, respectively. A UE apparatus 1002, as described in FIG. 10, may perform the method of flowchart 800. The one or more network entities 104. as described in FIG. 11, may perform the method of flowchart 900.

[0116] FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for a UE apparatus 1002. The UE apparatus 1002 may be the UE 102, a component of the UE 102. or may implement UE functionality. The UE apparatus 1002 may include an application processor 1006, which may have on-chip memory 1006’. In examples, the application processor 1006 may be coupled to a secure digital (SD) card 1008 and / or a display 1010. The application processor 1006 may also be coupled to a sensor(s) module 1012, a power supply 1014, an additional module of memory 1016, a camera 1018. and / or other related components.

[0117] The UE apparatus 1002 may further include a wireless baseband processor 1026, which may be referred to as a modem. The wireless baseband processor 1026 may have on-chip memory 1026'. Along with, and similar to, the application processor 1006. the wireless baseband processor 1026 may also be coupled to the sensor(s) module 1012, the power supply 1014, the additional module of memory 1016, the camera 1018, and / or other related components. The wireless baseband processor 1026 may be additionally coupled to one or more subscriber identity module (SIM) card(s) 1020 and / or one or more transceivers 1030 (e.g.. wireless RF transceivers).

[0118] Within the one or more transceivers 1030. the UE apparatus 1002 may include a Bluetooth module 1032, a WLAN module 1034, an SPS module 1036 (e.g., GNSS module), and / or a cellular module 1038. The Bluetooth module 1032, the WLAN module 1034, the SPS module 1036. and the cellular module 1038 may each include an on-chip transceiver (TRX), or in some cases, just a transmitter (TX) or just a receiver (RX). The Bluetooth module 1032, the WLAN module 1034, the SPS module 1036, and the cellular module 1038 may each include dedicated antennas and / or utilize antennas 1040 for communication with one or more other nodes. For example, the UE apparatus 1002 can communicate through the transceiver(s) 1030 via the antennas 1040 with another UE (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlink communication), where the network entity104 may correspond to a base station or a unit of the base station, such as the RU 106. the DU 108, or the CU 1 10.

[0119] The wireless baseband processor 1026 and the application processor 1006 may each include a computer-readable medium / memory 1026', 1006', respectively. The additional module of memory 1016 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1026', 1006', 1016 may be non-transitory. The wireless baseband processor 1026 and the application processor 1006 may each be responsible for general processing, including execution of software stored on the computer-readable medium / memory 1026'. 1006', 1016. The software, when executed by the wireless baseband processor 1026 / application processor 1006, causes the wireless baseband processor 1026 / application processor 1006 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 1026 / application processor 1006 when executing the software. The wireless baseband processor 1026 / application processor 1006 may be a component of the UE 102. The UE apparatus 1002 may be a processor chip (e.g., modem and / or application) and include just the wireless baseband processor 1026 and / or the application processor 1006. In other examples, the UE apparatus 1002 may be the entire UE 102 and include the additional modules of the apparatus 1002.

[0120] As discussed in FIG. 1 and implemented with respect to FIG. 8, the LCG component 140 is configured to receive, from a network entity, a configuration for a multi-logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are allocated resources for a MAC PDU using a token bucket size that is shared across the multi-logical channel group; and transmit, to the network entity, the MAC PDU including data from the multi- logical channel group, the resources being allocated to the multi -logical channel group to prioritize first data from a first synchronization data group over second outside of the first synchronization data group. The LCG component 140 may be within the application processor 1006 (e.g., at 140a), the wireless baseband processor 1026 (e.g., at 140b), or both the application processor 1006 and the wireless baseband processor 1026. The LCG component 140a-140b 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, storedwithin a computer-readable medium for implementation by the one or more processors, or a combination thereof.

[0121] FIG. 11 is a diagram 1100 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 1146, which may have on-chip memory 1146'. In some aspects, the CU 110 may further include an additional module of memory’ 1156 and / or a communications interface 1148, both of which may be coupled to the CU processor 1146. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an Fl interface between the communications interface 1148 of the CU 110 and a communications interface 1128 of the DU 108.

[0122] The DU 108 may include a DU processor 1126, which may have on-chip memory 1126'. In some aspects, the DU 108 may further include an additional module of memory’ 1136 and / or the communications interface 1128, both of which may be coupled to the DU processor 1126. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1128 of the DU 108 and a communications interface 1108 of the RU 106.

[0123] The RU 106 may include an RU processor 1106, which may have on-chip memory’ 1106'. In some aspects, the RU 106 may further include an additional module of memory 1116, the communications interface 1108, and one or more transceivers 1130. all of which may be coupled to the RU processor 1106. The RU 106 may further include antennas 1140, which may be coupled to the one or more transceivers 1130, such that the RU 106 can communicate through the one or more transceivers 1130 via the antennas 1140 with the UE 102.

[0124] The on-chip memory 1106', 1126'. 1146' and the additional modules of memory 1116, 1136, 1156 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1106, 1126, 1146 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) 1106, 1 126, 1146 causes the processor(s) 1106, 1126, 1146 to perform the various functions described herein. The computer-readable medium / memory’ may also be used for storing data that ismanipulated by the processor(s) 1106. 1126, 1146 when executing the software. In examples, the LCG configuration component 150 may sit at any of 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.

[0125] As discussed in FIG. 1 and implemented with respect to FIG. 9, the LCG configuration component 150 is configured to transmit, to a UE, a configuration for a multi-logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are to be allocated resources for a MAC PDU using a token bucket size that is shared across the multi-logical channel group; and receive, from the UE, the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi-logical channel group according to the configuration to prioritize first data from a first synchronization data group over second data outside the first synchronization data group. The LCG configuration component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 1106 (e.g., at 150a), the DU processor 1126 (e.g., at 150b), and / or the CU processor 1146 (e.g., at 150c). The LCG configuration component 150a-150c may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1106, 1126, 1146 configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors 1106, 1126. 1146, or a combination thereof.

[0126] 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.

[0127] 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.

[0128] 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.

[0129] 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 instruction set computing (RISC) processors, 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.

[0130] 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 instructionsor data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer.

[0131] 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 (Al)-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.

[0132] 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), interleavers, adders / summers, etc. Techniques 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.

[0133] 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.

[0134] 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. Theterms “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.

[0135] 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. Terms or articles such as “a”, “an”, and / or “the” may refer to one of an item, feature, element, etc., that the term or article precedes, or may refer to more than one of said item, feature, element, etc. that the term or article precedes. For example, the recitation “a widget” does not preclude reference to multiples of said widget, as “multiple widgets” necessarily includes “a widget”. Hence, the recitation “a widget” may be interpreted as “at least one widget” or, similarly, interpreted as “one or more widgets”.

[0136] 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.

[0137] 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 draw ings 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). Hence, like numbers may refer to like actions.

[0138] 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.

[0139] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.

[0140] Example 1 is a method of wireless communication at a user equipment (UE) including: receiving, from a network entity, a configuration for a multi-logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are allocated resources for a medium access control (MAC) protocol data unit (PDU) using a token bucket size that is shared across the multi-logical channel group; and transmitting, to the network entity', the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi-logical channel group to prioritize first data from a first synchronization data group over second data outside of the first synchronization data group.

[0141] Example 2 is the method of example 1, further including: allocating, based on a priority order of the multi-logical channel group, the resources to the multi-logical channel group, the priority order being indicated by the configuration.

[0142] Example 3 is the method of example 2, where the allocating the resources to the multi-logical channel group includes: allocating, based on the priority order, first resources in the resources to the multi-logical channel group; and allocating, based on the priority order subsequent to the allocating the first resources, second resources in the resources to a mono-logical channel group including only one logical channel.

[0143] Example 4 is the method of example 2, where the allocating the resources to the multi-logical channel group includes: allocating, based on the priority' order, the resources to the multi-logical channel group and a mono-logical channel group including only one logical channel.

[0144] Example 5 is the method of any of examples 2-4, where the allocating the resources to the multi-logical channel group includes: allocating, based on the priorityorder and a total number of available tokens for the at least two logical channels, the resources to the at least two logical channels.

[0145] Example 6 is the method of any of examples 2-5, where the allocating the resources to the multi-logical channel group includes: allocating, based on the token bucket size, first resources for the first data from the first synchronization data group to the at least two logical channels.

[0146] Example 7 is the method of any of examples 2-6, where the allocating the resources to the multi-logical channel group includes: allocating second resources for the first data from the first synchronization data group based on the priority order and the first data from the first synchronization data group having at least one of: a shortest remaining synchronization time or a shortest remaining delivery time.

[0147] Example 8 is the method of any of examples 1 -7, where the configuration indicates the token bucket size, the priority order of the multi-logical channel group, and a prioritized bit rate (PBR) and where the transmitting the MAC PDU is based on the token bucket size, the priority order of the multi-logical channel group, and the PBR.

[0148] Example 9 is the method of any of examples 1-7, where the configuration indicates, for the at least two logical channels of the multi-logical channel group, a first token bucket size, a first priority order of the at least two logical channels, and a first prioritized bit rate (PBR) the method further including: calculating, based on the first token bucket size, the token bucket size; calculating, based on the first priority order, a priority order of the multi-logical channel group; and calculating, based on the first PBR, a multi-logical channel group PBR. and where the transmitting the MAC PDU is based on the token bucket size, the priority order of the multi-logical channel group, and the multi-logical channel group PBR.

[0149] Example 10 is the method of any of examples 1-9, where each logical channel of the multi-logical channel group corresponds to a different modality of multi-modality data.

[0150] Example 11 is the method of any of examples 1-10, further including: transmitting, to the network entity, UE capability information indicating that the UE supports logical channel group prioritization and resource allocation, where the receiving the configuration is based on the UE capability information.

[0151] Example 12 is the method of any of examples 1-11, further including: transmitting, to the network entity, a scheduling request; and receiving, from thenetwork entity based on the scheduling request, an uplink grant, where the transmitting the MAC PDU is further based on the uplink grant.

[0152] Example 13 is a method of wireless communication at a network entity, including: transmitting, to a user equipment, UE, a configuration for a multi-logical channel group including at least two logical channels, the configuration indicating that the at least two logical channels are to be allocated resources for a medium access control (MAC) protocol data unit (PDU) using a token bucket size that is shared across the multi-logical channel group; and receiving, from the UE, the MAC PDU including data from the multi-logical channel group, the resources being allocated to the multi- logical channel group according to the configuration to prioritize first data from a first synchronization data group over second data outside the first synchronization data group.

[0153] Example 14 is the method of example 13, where the configuration indicates to allocate the resources based on a priority order of the multi-logical channel group, the priority order being indicated by the configuration.

[0154] Example 15 is the method of example 14, where the configuration indicates that first resources in the resources are to be allocated to the multi-logical channel group based on the priority order, and where second resources in the resources are to be allocated to a mono-logical channel group including only one logical channel based on the priority order subsequent to the first resources being allocated.

[0155] Example 16 is the method of example 14, where the configuration indicates that the resources are to be allocated to the multi-logical channel group and a mono-logical channel group including only one logical channel based on the priority order.

[0156] Example 17 is the method of any of examples 14-16, where the configuration indicates that the resources are to be allocated to the multi-logical channel group based on the priority order and a total number of available tokens for the multi-logical channel group.

[0157] Example 18 is the method of any of examples 14-17, where the configuration indicates that first resources for the first data from the first synchronization data group are to be allocated to the at least two logical channels.

[0158] Example 19 is the method of any of examples 14-18, where the configuration indicates that second resources for the first data from the first synchronization data group are to be allocated based on the priority order and the first data having at leastone of: a shortest remaining synchronization time or a shortest remaining delivery time.

[0159] Example 20 is the method of any of examples 13-19, where the configuration indicates the token bucket size, a priority order, and a prioritized bit rate (PBR) and where the receiving the MAC PDU is based on the token bucket size, the priority order, and the PBR.

[0160] Example 21 is the method of any of examples 13-19, where the configuration indicates, for the at least two logical channels of the multi-logical channel group, a first token bucket size, a first priority order, and a first prioritized bit rate (PBR) and where receiving the MAC PDU is based on the first token bucket size, the first priority order, and the first PBR.

[0161] Example 22 is the method of any of examples 13-21, where each logical channel of the multi-logical channel group corresponds to a different modality of multimodality data.

[0162] Example 23 is the method of any of examples 13-22, further including: receiving, from the UE, UE capability information indicating that the UE supports logical channel group prioritization and resource allocation, where the transmitting the configuration is based on the UE capability information.

[0163] Example 24 is the method of any of examples 13-23, further including: receiving, from the UE, a scheduling request; and transmitting, to the UE based on the scheduling request, an uplink grant, where the receiving the MAC PDU is further based on the uplink grant.

[0164] Example 25 is an apparatus for wireless communication including a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of examples 1-24.

[0165] Example 26 is an apparatus for wireless communication including means for implementing a method as described in any of examples 1-24.

[0166] Example 27 is a non-transitory computer-readable medium storing computer executable code, the computer executable code, when executed by a processor, causes the processor to implement a method as in any of examples 1 -24.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. A method of wireless communication at a user equipment, UE, (102) comprising: receiving (744), from a network entity- (104), a configuration for a multi-logical channel group (641) including at least two logical channels (536), the configuration indicating that the at least two logical channels (536) are allocated resources for a medium access control, MAC, protocol data unit, PDU, (664) using a token bucket size (634) that is shared across the multi-logical channel group (641); and transmitting (758), to the network entity (104), the MAC PDU (664) including data (532) from the multi-logical channel group (641), the resources being allocated to the multi-logical channel group (641) to prioritize first data (532a) from a first synchronization data group over second data (532b-532c) outside of the first synchronization data group.

2. The method of claim 1, further comprising: allocating (756), based on a priority order of the multi -logical channel group (641), the resources to the multi-logical channel group (641). the priority order being indicated by the configuration.

3. The method of claim 2, wherein the allocating (756) the resources to the multi- logical channel group (641) comprises: allocating, based on the priority- order, first resources in the resources to the multi- logical channel group (641); and allocating, based on the priority order subsequent to the allocating the first resources, second resources in the resources to a mono-logical channel group (638) including only one logical channel (536).

4. The method of claim 2, wherein the allocating (756) the resources to the multi- logical channel group (641) comprises: allocating, based on the priority order, the resources to the multi-logical channel group (641) and a mono-logical channel group (638) including only one logical channel (536).

5. The method of any of claims 2-4. wherein the allocating (756) the resources to the multi-logical channel group (641) comprises: allocating, based on the priority order and a total number of available tokens for the at least two logical channels (536b-536d), the resources to the at least two logical channels (536).

6. The method of any of claims 2-5, wherein the allocating (756) the resources to the multi-logical channel group (641) comprises: allocating, based on the token bucket size (634), first resources for the first data (532a) from the first synchronization data group to the at least two logical channels (536).

7. The method of any of claims 2-6, wherein the allocating (756) the resources to the multi-logical channel group (641) comprises: allocating second resources for the first data (532a) from the first synchronization data group based on the priority order and the first data (532a) from the first synchronization data group having at least one of: a shortest remaining synchronization time or a shortest remaining delivery time.

8. The method of any of claims 1-7, wherein the configuration indicates the token bucket size (634), the priority order of the multi-logical channel group (641), and a prioritized bit rate, PBR, and wherein the transmitting (758) the MAC PDU (664) is based on the token bucket size (634), the priority order of the multi-logical channel group, and the PBR.

9. The method of any of claims 1-7, wherein the configuration indicates, for the at least two logical channels (536) of the multi-logical channel group (641). a first token bucket size, a first priority order of the at least two logical channels (536). and a first prioritized bit rate, PBR, the method further comprising: calculating (754), based on the first token bucket size, the token bucket size; calculating (752), based on the first priority order, a priority order of the multi- logical channel group (641); and calculating (753), based on the first PBR, a multi-logical channel group PBR, and wherein the transmitting (758) the MAC PDU is based on the token bucket size, thepriority order of the multi-logical channel group, and the multi-logical channel group PBR.

10. The method of any of claims 1 -9, wherein each logical channel of the multi-logical channel group (641) corresponds to a different modality of multi-modality data.

11. The method of any of claims 1-10, further comprising: transmitting (742), to the network entity (104), UE capability information indicating that the UE (102) supports logical channel group prioritization and resource allocation, wherein the receiving (744) the configuration is based on the UE capability information.

12. The method of any of claims 1-11, further comprising: transmitting (746), to the network entity (104), a scheduling request; and receiving (748), from the network entity (104) based on the scheduling request, an uplink grant, wherein the transmitting (758) the MAC PDU (664) is further based on the uplink grant.

13. A method of wireless communication at a network entity (104), comprising: transmitting (744), to a user equipment, UE (102), a configuration for a multi- logical channel group (641) including at least two logical channels (536), the configuration indicating that the at least two logical channels (536) are to be allocated resources for a medium access control. MAC. protocol data unit. PDU, (664) using a token bucket size (634) that is shared across the multi-logical channel group (641); and receiving (758), from the UE (102), the MAC PDU (664) including data (532) from the multi-logical channel group (641), the resources being allocated to the multi- logical channel group (641) according to the configuration to prioritize first data (532a) from a first synchronization data group over second data (532b-532c) outside the first synchronization data group.

14. The method of claim 13, wherein the configuration indicates the token bucket size (634), a priority order of the multi-logical channel group (641), and a prioritized bit rate, PBR, and wherein the receiving (758) the MAC PDU (664) is based on the token bucket size (634), the priority' order of the multi-logical channel group, and the PBR.

15. An apparatus for wireless communication comprising a memory. a transceiver, and a processor coupled to the memon' and the transceiver, the apparatus being configured to implement a method as in any of claims 1-14.

Images