Allocating resources for multi-modal business of extended reality

Abstract

The present disclosure provides systems, apparatus, equipment, 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 comprising at least two logical channels. The configuration indicates that resources for MAC PDUs are to be allocated for the at least two logical channels using a token bucket size shared across the multi-logical channel group. The UE transmits (758), to the network entity (104), a MAC PDU comprising data from the multi-logical channel group. 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

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application Serial No. 63 / 568,881, filed on March 22, 2024, entitled “ALLOCATING RESOURCES TO MULTI-MODAL TRAFFIC FOR EXTENDED REALITY,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates generally to wireless communication, and more specifically to scheduling multimodal data transmission. Background Technology

[0004] The 3rd Generation Partnership Project (3GPP) specifies a radio interface known as Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), and user equipment (5G UE). Compared to previous generations of cellular communication systems, the 5G NR architecture aims to provide increased data rates, reduced latency, and / or increased capacity.

[0005] Generally, wireless communication systems provide various telecommunications services (e.g., telephony, video, data, messaging, etc.) based on multiple access technologies that support communication with multiple UEs (such as Orthogonal Frequency Division Multiple Access (OFDMA)). Improvements in mobile broadband have continued the development of these wireless communication technologies. For example, a User Equipment (UE) allocates resources to logical channels according to Logical Channel Priority (LCP) functionality. However, when a UE transmits a synchronization data group through a logical channel allocated resources according to LCP, the UE may not be able to transmit the entire synchronization data group within the synchronization deadline, which can degrade Quality of Service (QoS). Summary of the Invention

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all conceived aspects. It neither identifies key or important elements of all aspects nor describes 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 descriptions that follow.

[0007] The Logical Channel Prioritization (LCP) function allocates resources (e.g., multiple bytes to be sent to a network entity) to logical channels. For example, in the first round of LCP, the User Equipment (UE) allocates resources to logical channels in descending priority order, where the maximum amount of resources allocated is limited by the current size of the token bucket associated with the corresponding logical channel group. In the second round of LCP, if there are remaining resources from the first round, the UE allocates these remaining resources to individual logical channels in descending priority order, regardless of the token bucket size, until data from the logical channels is exhausted or all remaining resources are exhausted.

[0008] Multimodal data refers to input data from different devices (e.g., sensors) or output data destined for different destinations (e.g., different UE components) for the same task. In this example, multimodal data includes camera / video data, microphone / audio data, and haptic data, which the UE uses to present an extended reality (XR) experience to the user. In this example, the UE transmits audio data, video data, and haptic data through different logical channels. A satisfactory user experience can depend on each of the different types of multimodal data being transmitted by the UE within a specific time period. Therefore, a synchronization data group is defined as data generated on one or more logical channels that needs to be synchronized. In this example, the synchronization data group includes audio data, video data, and haptic data for the XR experience, where the audio data, video data, and haptic data are each assigned to different logical channels. If the UE transmits the first part of the synchronization data group, the UE should transmit the remaining part of the synchronization data group before a synchronization deadline. The synchronization deadline is the transmission time of the first part of the synchronization data group plus a synchronization threshold. The synchronization threshold refers to the maximum tolerable time separation between the transmission of the first data (e.g., video data) and the second data (e.g., audio data) in a synchronized data set.

[0009] When a UE uses the LCP function to schedule the transmission of a synchronization data group for multimodal data (e.g., in XR applications), the UE may not be able to send the entire synchronization data group. In an example, the 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 this example, the synchronization data group includes first data to be sent by the UE via the first logical channel, and second, third, and fourth data to be sent by the UE via the second logical channel. In this example, the UE schedules the first data for transmission on the first logical data channel, such that the first logical channel has two remaining tokens available. The UE schedules the second and third data for transmission on the second logical channel, such that the second logical channel has no remaining tokens available. Therefore, due to the bucket size (two) of the second logical channel, the UE cannot schedule the transmission of the fourth data on the second logical channel. Instead, the UE schedules other data for transmission on the first logical channel. Therefore, the UE cannot send the entire synchronization data group before the synchronization deadline, which may degrade the Quality of Service (QoS) of XR applications.

[0010] This disclosure addresses the aforementioned and other deficiencies by implementing a process for prioritizing and allocating logical channel groups (LCGs). An LCG includes at least one logical channel. A UE implementing LCG prioritization and resource allocation groups logical channels carrying multimodal services (e.g., multimodal services for XR applications) 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 based on the LCG's priority level (not the logical channel's priority level). If the UE determines that resources should be allocated to the LCG, it prioritizes data from the same synchronization data group within the logical channels of the LCG. The total amount of data transmitted from the LCG is based on the size of the LCG's token bucket (not the logical channel's token bucket size). Following the example given above, a UE implementing LCG prioritization and resource allocation can be configured with an LCG having a bucket size of five, enabling the UE to schedule the transmission of fourth data on a second logical channel, and thus allowing the UE to transmit the entire synchronization data group before the synchronization deadline, which can improve the QoS of XR applications.

[0011] According to some aspects, the UE receives (and the network entity sends to the UE) a configuration for a multi-logical channel group comprising at least two logical channels. This configuration instructs the allocation of resources for Media Access Control (MAC) Protocol Data Units (PDUs) for the at least two logical channels using a token bucket size shared across the multi-logical channel group. The UE sends (and the network entity receives from the UE) a MAC PDU comprising data from the multi-logical channel group. Resources are allocated to the multi-logical channel group such that first data from a first synchronization data group takes precedence over second data outside the first synchronization data group. Attached Figure Description

[0012] Figure 1 A diagram of a wireless communication system is shown, which includes multiple user equipment (UEs) and network entities communicating through one or more cells.

[0013] Figure 2 A diagram of the protocol stack is shown, which includes the Physical (PHY) layer, the Media Access Control (MAC) layer, and the Radio Link Control (RLC) layer.

[0014] Figure 3 This is a diagram showing the logical channel priority order.

[0015] Figure 4 A diagram of a multimodal interactive system is shown.

[0016] Figure 5 A diagram showing logical channel priority ordering and resource allocation is provided.

[0017] Figure 6 A diagram showing the priority ordering and resource allocation of Logical Channel Groups (LCGs) is provided.

[0018] Figure 7 The signaling diagram for LCG priority ordering and resource allocation is shown.

[0019] Figure 8 This is a flowchart of the wireless communication method at the UE.

[0020] Figure 9 This is a flowchart of a wireless communication method at a network entity.

[0021] Figure 10 A diagram illustrating the hardware implementation of an example UE device is shown.

[0022] Figure 11 A diagram illustrating the hardware implementation of one or more network entities is shown. Detailed Implementation

[0023] Figure 1Figure 100 illustrates a wireless communication system associated with multiple cells 190. This wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, and others may include a decomposed base station architecture. The aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may co-locate with CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).

[0024] The operation and / or network design of base station 104 can be based on the aggregation characteristics of base station functionality. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functionality among two or more units located in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. The various units of the decomposed base station architecture or decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication. For example, base stations 104d, 104e and / or RUs 106a, 106b, 106c, 106d can communicate with UEs 102a, 102b, 102c, 102d and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In the example, multiple RUs 106 and / or base stations 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RUs 106 / base stations 104.

[0025] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission medium—such as a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108 and CU 110 to transmit or receive information / signals between DU 108 and CU 110. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) may be configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and base station 104e in cell 190e via inter-cell communication beams 136-138 of RU 106a and base station 104e.

[0026] RU 106 can be configured to implement low-level functionality. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or low-level PHY functionality, such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.

[0027] RU 106 can transmit or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first set of communication beams 132 of RU 106b and a second set of communication beams 134b of UE 102b. These two sets of communication beams may correspond to inter-cell communication beams or, in some examples, inter-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third set of communication beams 134a of UE 102b and a fourth set of communication beams 136 of RU 106a. DU 108 can control both the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0028] Any combination of RU 106, DU 108, and CU 110, or a reference to them individually, may correspond to base station 104. Therefore, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to the core network. Base station 104 may relay communication between UE 102 and the core network (not shown). Base station 104 may be associated with macro cells of higher-power cellular base stations and / or small cells of lower-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network".

[0029] Transmissions from UE 102 to base station 104 / RU 106 are called uplink (UL) transmissions, while transmissions from base station 104 / RU 106 to UE 102 are called downlink (DL) transmissions. Uplink transmissions can also be called reverse link transmissions, and downlink transmissions can also be called forward link transmissions. For example, RU 106d uses the antenna of base station 104d in cell 190d to send downlink / forward link communication to UE 102d or receive uplink / reverse link communication from UE 102d based on the Uu interface associated with the access link between UE 102d and base station 104d / RU 106d.

[0030] The communication link between UE 102 and base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and base station 104 / RU 106 can utilize up to a total of Yx Each carrier allocated in MHz carrier aggregation Y Spectral bandwidths of MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.), where x Each component carrier (CC) is used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along the spectrum. In the example, uplink and downlink carriers may be allocated asymmetrically, with more or fewer carriers allocated for the uplink or downlink. A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carriers may be associated with secondary cells (SCells).

[0031] Some UEs, such as UEs 102a and 102s, can perform device-to-device (D2D) communication via a sidelink. For example, the sidelink / D2D communication link utilizes the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems such as Wi-Fi, Bluetooth, LTE, and NR systems.

[0032] UE 102 and base station 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b based on a first set of communication beams 132 in one or more transmit directions of RU 106b. UE 102b may receive downlink beamforming signals from RU 106b based on a second set of communication beams 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b based on a second set of communication beams 134b in one or more transmit directions of UE 102b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b. UE 102b can perform beamforming to determine the optimal reception and transmission directions for the beamformed signal. The transmission and reception directions of UE 102 and base station 104 / RU 106 can be the same or different.

[0033] In a further example, the beamforming signal can be transmitted between the first base station / RU 106a and the second base station 104e. For example, base station 104e of cell 190e can transmit the beamforming signal to RU 106a based on communication beam 138 in one or more transmit directions of base station 104e. RU 106a can receive the beamforming signal from base station 104e of cell 190e based on RU communication beam 136 in one or more receive directions of RU 106a. In a further example, base station 104e transmits a downlink beamforming signal to UE 102e based on communication beam 138 in one or more transmit directions of base station 104e. UE 102e receives the downlink beamforming signal from base station 104e based on UE communication beam 130 in one or more receive directions of UE 102e. UE 102e can also transmit uplink beamforming signals to base station 104e based on UE communication beam 130 in one or more transmission directions of UE 102e, so that base station 104e can receive uplink beamforming signals from UE 102e in one or more reception directions of base station 104e.

[0034] Base station 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to base station 104 or at least one element of base station 104, such as RU 106, DU 108, and / or CU 110. Base station 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Base station 104 or entities at base station 104 may be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station, or a decomposed base station including one or more RU 106, DU 108, and / or CU 110. An aggregated or decomposed set of base stations may be referred to as a Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In such cases, base station 104e can be the primary node, and base station / RU 106a can be the secondary node.

[0035] Continue to refer to Figure 1In some respects, any UE in UE 102 may include a Logical Channel Group (LCG) component 140 configured to receive configuration from a network entity for a multi-logical channel group comprising at least two logical channels, the configuration indicating the use of a token bucket size shared across the multi-logical channel group to allocate resources for Media Access Control (MAC) Protocol Data Units (PDUs) for the at least two logical channels; and to send a MAC PDU to the network entity, the MAC PDU comprising data from the multi-logical channel group, the resources being allocated to the multi-logical channel group such that first data from a first synchronization data group takes precedence over second data outside the first synchronization data group.

[0036] In some aspects, base station 104 or any of its network entities may include LCG configuration component 150, which is configured to send to the UE a configuration for a multi-logical channel group comprising at least two logical channels, the configuration indicating that a token bucket size shared across the multi-logical channel group should be used to allocate resources for MAC PDUs for the at least two logical channels; and to receive from the UE a MAC PDU comprising data from the multi-logical channel group, the resources being allocated to the multi-logical channel group according to the configuration such that first data from a first synchronization data group takes precedence over second data outside the first synchronization data group.

[0037] therefore, Figure 1 A wireless communication system that can be implemented in conjunction with one or more other figures described herein is described. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.

[0038] Figure 2 Figure 200 illustrates a protocol stack including PHY layer 250, MAC layer 260, and RLC layer 270. PHY layer 250 corresponds to layer 1 (L1). MAC layer 260 and RLC layer 270, along with the PDCP layer (not shown) located above RLC layer 270, can also be referred to as sublayers of layer 2 (L2). That is, the L2 protocol stack includes the PDCP sublayer, RLC sublayer, and MAC sublayer. Both the UE and network entities such as base stations perform transmissions using the protocol stack of Figure 200.

[0039] The PHY layer 250 provides a transport channel to the MAC layer 260 for downlink / uplink transmission. The transport channel may carry one or more transport blocks (TBs) 252a, 252b. The MAC layer 260 includes scheduling and / or priority handling functions for downlink and uplink transmissions. The MAC layer 260 also includes multiplexing and demultiplexing functions for downlink / uplink transmissions. The MAC layer 260 can perform a Hybrid Automatic Repeat Request (HARQ) procedure for each downlink / uplink transmission on a specific downlink / uplink CC associated with a specific UE. The RLC layer 270 includes segmentation and Automatic Repeat Request (ARQ) functions for downlink / uplink data transmitted to / from one or more UEs. In LTE applications, the RLC layer 270 can perform concatenation of RLC SDU 272 to RLC PDU 274. For example, RLC PDU 274a concatenates the first RLC SDU 272a and the second RLC SDU 272b. In NR applications, RLC layer 270 may not perform concatenation. Instead, RLC layer 270 may perform (re)segmentation of RLC SDU 272.

[0040] Internet Protocol (IP) packets may include data transmitted through layers 250-270 of the protocol stack. In the example, the PDCP layer (not shown) performs IP header compression using Robust Header Compression (ROHC) technology, followed by encryption, resulting in one or more RLC Service Data Units (SDUs) 272. ROHC technology can reduce the size of upper-layer headers, including static information such as Voice over Internet Protocol (VoIP) packet headers, which, without compression, could be more than half the packet size. In the example, the reduced PDCP header size may be between 1 and 3 bytes. The PDCP header also includes information for packet decryption at the mobile terminal.

[0041] The output from the PDCP layer (e.g., one or more RLC SDUs 272) is input to the RLC layer 270. In addition to adding RLC headers 276a, 276b, and 276c to the RLC PDU 274, the RLC layer 270 can also perform concatenation and / or segmentation of the RLC SDUs 272 to produce the RLC PDU 274. For example, the RLC layer 270 can concatenate the first RLC SDU 272a and the second RLC SDU 272b into a first RLC PDU 274a associated with a first logical channel, and segment the 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 can form a set 275 of RLC PDUs associated with the same logical channel. A PDU set (e.g., a PDCP PDU set, an RLC PDU set 275, or a MAC PDU set) comprises one or more PDUs carrying the payload of an information element (e.g., a frame or video slice for Extended Reality (XR) services) generated at the application level. In some implementations, the application layer recovers all PDUs in the PDU set for use of the information element. In other implementations, the application layer may recover part or all of the information element when some PDUs in the PDU set are lost. RLC PDU 274 includes RLC headers 276a, 276b, and 276c for in-order delivery in a mobile terminal (e.g., per logical channel) and for identifying individual RLC PDU 274 in the event of retransmission. Additional RLC subheaders may be added to RLC PDU 274 in the case of packet segmentation and / or concatenation. RLC PDU 274 may include part or all of a PDU packet, or several PDU packets (e.g., RLC SDU 272), depending on the size allocated to the UE.

[0042] RLC PDU 274 is forwarded to MAC layer 260, where it becomes MAC SDU 262 according to 3GPP nomenclature. In addition to adding MAC headers 266a and 266b to MAC PDU 264, MAC layer 260 can similarly perform concatenation and / or fragmentation of MAC SDU 262 to MAC PDU 264. For example, MAC layer 260 can concatenate the first MAC SDU 262a and the second MAC SDU 262b into the first MAC PDU 264a, and can incorporate the third MAC SDU 272c into the second MAC PDU 264b (e.g., without concatenation or fragmentation). MAC layer 260 appends MAC header 266 to the MAC PDU payload to form TBs 252a and 252b.

[0043] MAC layer 260 includes a radio resource scheduler that determines how much data is currently in the buffer awaiting transmission from the logical channel. MAC layer 260 can also determine information about the radio link quality of different UEs, whether any packets are being retransmitted, UE state (e.g., whether the UE is in scan / monitor mode or power-saving / sleep mode), scheduling of system information transmissions (e.g., synchronization signals, Master Information Block (MIB) and / or System Information Block (SIB)), etc. The resource scheduler can allocate radio resources to one or more UEs and indicate transmission parameters for each TTI. The resource scheduler can further indicate the amount of data (e.g., in bits) that can be transmitted within a TTI (e.g., 1 ms), which may correspond to a TB size.

[0044] The size of each TB 252 can be based on the instantaneous data rate selected for link adaptation. Therefore, link adaptation may affect both MAC and RLC processing. The PHY layer 250 further includes a Cyclic Redundancy Check (CRC) utilizing the TB 252 for error detection. The CRC size can be 24 bits and is used to distinguish between successful and failed packet decoding at the receiver. PHY layer processing is performed before signals are sent to the air interface. Inverse functionality can be similarly performed for downlink communication when the UE receives one or more TB 252s from the base station on the downlink.

[0045] Figure 3 It is shown Figure 2Figure 300 shows the logical channel priority ordering at the MAC layer of the protocol stack. Data transmission can be based on multiple logical channels 336a-336d carrying data through multiple physical paths. A single transmission path among the multiple physical paths can send a limited amount of data / resources per transmission time interval (TTI). If the amount of data in the buffers of logical channels 336a-336d exceeds the transmission capacity of the MAC PDU 364, then the data in the logical channel buffers will not fit (not fit at all) within a single MAC PDU 364. Therefore, the scheduling entity can determine which logical channel data to provide to the MAC PDU 364 for transmission, and which other logical channel data can be retained in the buffers of logical channels 336a-336d for future transmission at different MAC PDU transmission times.

[0046] The UE may generate MAC PDU 364 according to a predefined protocol that allows the UE to meet the Quality of Service (QoS) of the radio bearer for each configuration. The UE may determine the amount of data to be incorporated into the current MAC PDU 364 from each logical channel 336a-336d based on uplink resource grants signaled to the UE on the Physical Downlink Control Channel (PDCCH). The UE may also allocate resources for the MAC Control Element (MAC-CE) within the MAC PDU 364. The UE may perform a logical channel priority ordering process for each MAC PDU transmission. Logical channel priority ordering refers to incorporating data from different logical channels 336a-336d into the MAC PDU 364 based on their priority values.

[0047] If MAC resources are insufficient to accommodate logical channel data from all logical channel buffers, MAC resources can be allocated based on the priority level of each logical channel 336a-336d. For example, the RRC parameter indicates the priority level of each logical channel 336a-336d, where priority 1 is the highest priority, priority 2 is the second highest priority, and so on. Figure 300 includes four logical channels 336a-336d, corresponding to logical channel 1 336a with priority 1, logical channel 2 336b with priority 2, logical channel 3 336c with priority 3, and logical channel 4 336d with priority 4. Each logical channel 336a-336d includes data for transmission in MAC PDU 364.

[0048] In a first implementation of MAC PDU 364b, logical channel data can be incorporated into MAC PDU 364b based on a descending priority order (starting from priority 1) until all available MAC PDU resources are allocated. For example, MAC PDU 364b may contain data from logical channels 1 (336a), 2 (336b), and 3 (336c), but there may not be enough remaining resources to accommodate data from logical channel 4 (336d). Therefore, data from logical channel 4 (336d) can be retained in its buffer until a future MAC PDU has available space to transmit data from logical channel 4 (336d). If no other data flows into the buffers of logical channels (1, 2, 3) (336a-336c), the data from logical channel 4 (336d) can be incorporated into the next MAC PDU transmission.

[0049] While strict logical channel priority ordering may be sufficient in many cases, data held by the buffer in logical channel 4 336d may experience “starvation” if data continues to flow into logical channels (1, 2, 3) 336a-336c before each MAC PDU transmission instance. That is, data in logical channel 4 336d is repeatedly skipped without being incorporated into the MAC PDU transmission to favor higher-priority bearers. Starvation refers to lower-priority data that cannot be transmitted for an extended period because higher-priority data repeatedly consumes available MAC PDU transmission resources, preventing lower-priority data from being incorporated into subsequent versions of MAC PDU 364b for transmission.

[0050] To avoid starvation while still serving logical channels 336a-336d based on priority levels, a second implementation of MAC PDU 364a uses a prioritized bit rate (PBR) 337 configured via RRC to set the data rate for higher-priority logical channels. This data rate limits the resources allocated to higher-priority logical channels before resources begin to be allocated to lower-priority logical channels. This approach reduces starvation for lower-priority data even as high-priority data continues to flow into higher-priority logical channels. Each logical channel 336a-336d can be configured with an independent PBR 337. For example, although in Figure 3 It is not shown in the figure, but the PBR 337a of logical channel 1 336a can be greater than or less than the PBR 337b of logical channel 2 336b.

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

[0052] RRC parameters control the scheduling of uplink data from each logical channel 336a-336d, such as parameters of PBR 337, the bucket size duration (BSD) of the data transmission token, and / or indicating that an increasing priority value corresponds to a decreasing priority level. The data transmission token and token bucket algorithm prioritizes transmissions on various logical channels, as described further below. The UE can prioritize data transmissions on each logical channel. j Maintain a variable token bucket size (B j When the corresponding logical channel is established, the token bucket size (B) j The token bucket size is initialized to zero, and for each TTI, it increases by the product of PBR × TTI duration, where PBR 337 corresponds to the logical channel. j B j The value cannot exceed the token bucket size (e.g., more tokens than the bucket can hold), and is therefore limited to each logical channel. j The token bucket size. The bucket size for logical channels 336a-336d is equal to PBR × BSD, where PBR and BSD are configured based on upper-layer parameters.

[0053] The MAC-CE included in MAC PDU 364 can have a higher priority than any logical channel in logical channels 336a-336d because the MAC-CE controls the operation of the MAC entity. Therefore, when the UE generates MAC PDU 364, the MAC-CE can be included in MAC PDU 364 first (not shown), allowing the remaining space in MAC PDU 364 to be used for data allocation from logical channels 336a-336d. An exception could be when the UE sends a first RRC message to the target cell during the handover process. In such cases, MAC-CEs such as Buffer State Reports (BSRs) can have a lower priority than Signaling Radio Bearers (SRBs), allowing the handover process to be completed earlier rather than later. Otherwise, due to delayed signaling, data transmission interruption time may be prolonged, and the probability of handover failure may increase.

[0054] Even in the example where a higher-priority channel is configured with a PBR 337, lower-priority channels / data may still experience starvation if the higher-priority channel is associated with a large PBR 337 that consumes available MAC PDU resources before all logical channels 336a-336d have been allocated. Therefore, in the third implementation of MAC PDU 364a (which can be considered an extension of the second implementation), data from logical channels 336a-336d can be incorporated into MAC PDU 364a based on a technique that balances the starvation of PBR 337 with that of low-priority data.

[0055] In the example, priority 4 data from logical channel 4 336d might be included in MAC PDU 364a even if higher priority logical channels (e.g., 336a-336c) have data in the buffer. A third implementation of MAC PDU 364a could be based on a timing duration / limit for logical channels 336a-336d according to their priority. Each logical channel 336a-336d could be associated with a countdown timer, such that the timer decrements by 1 whenever a logical channel 336a-336d transmits an amount of data equal to the PBR 337 of that logical channel. If the countdown timer becomes negative, a higher priority logical channel can yield its opportunity to transmit data in the upcoming MAC PDU to a lower priority logical channel. Therefore, the countdown timer prevents a higher priority logical channel from monopolizing MAC PDU 364a, even if the higher priority logical channel has data to transmit (e.g., with a high PBR 337). The countdown timer could be based on RRC parameters. bucketSizeDuration Configure it. Figure 3 It describes the logical channel priority ordering at the MAC layer, while Figure 4 A multimodal interactive system is described that transmits data according to the logical channel priority order at the MAC layer.

[0056] Figure 4 Figure 400 illustrates a multimodal interactive system 401. The multimodal interactive system 401 is configured to process multimodal data. Multimodal data refers to input data from different types of devices / sensors and / or output data destined for different types of destinations (e.g., UE 102a-102e) for the same task or application (e.g., an XR application). Multimodal data includes more than one type of unimodal data. Strong dependencies may exist between the different types of unimodal data included in multimodal data. Unimodal data can be considered as one type of data. In the example, multimodal data includes audio data, video data, and haptic data for an XR application.

[0057] Multimodal interactive system 401 can enable or facilitate haptic and multimodal communication services. Haptic and multimodal communication services (which may be referred to as the "Haptic Internet") refer to networks that combine ultra-low latency with high availability, reliability, and security. The Haptic Internet enables real-time control of the Internet of Things (IoT). IoT refers to a collection of network-connected devices and technologies that facilitate communication between devices and the cloud, as well as between devices themselves. The Haptic Internet can be applied in multiple fields, such as industry, robotics and telepresence, virtual reality, augmented reality, healthcare, road transportation, gaming, education and culture, and / or smart grids. Multimodal interactive system 401 combines multiple modalities (described in more detail below) in the service to provide complementary technologies that may convey redundant information but effectively convey information. Multimodal interactive system 401 combines inputs from more than one source and / or combines outputs destined for more than one destination. Therefore, multimodal interactive system 401 enables communication services to be more accurate, faster, smoother, and more natural, and also allows for faster response times.

[0058] As indicated above, the multimodal interactive system 401 can enable or facilitate haptic and multimodal communication services (or applications). Haptic and multimodal communication services / applications include different modalities that influence the user experience. In the example, haptic and multimodal communication services / applications include video / audio media, information about the environment perceived by sensors (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, tension, positional awareness).

[0059] The multimodal interactive system 401 can process environmental information (e.g., information about the environment perceived by sensors) to generate IoT control commands as feedback. Tactile data has specific characteristics based on physiological perception. These specific characteristics include, for example, frequency and latency. Therefore, periodic, deterministic, and reliable communication paths can be used to transmit tactile data. In the example, the tactile device samples at a rate of one thousand times per second, and transmits the samples individually at one thousand times per second. In the example, the video frame rate could be sixty or ninety frames per second. Therefore, wireless communication systems (e.g., 5G NR) may face challenges in transmitting small packets over long distances at high frequencies.

[0060] The multimodal interactive system 401 can simultaneously send multiple modalities to multiple application servers for coordinated further processing in terms of Quality of Service (QoS) coordination, service synchronization, and power saving. Multiple application servers can generate multiple results as feedback. In an example concerning a real-time remote virtual reality service, a virtual reality (VR) user uses multiple independent devices to collect video data, audio data, environmental data, and haptic data from an individual. These independent devices also receive video data, audio data, environmental data, and haptic feedback from one or more application servers for use in the same VR application. In this example, the VR user wears VR glasses to receive images and sound, haptic gloves to receive haptic sensations, a camera to collect video input, a microphone to collect audio input, and multiple wearable sensors to provide haptic and environmental information associated with the user. In another example, a real-time remote virtual reality service can facilitate a session between two user devices (e.g., two VR devices) worn by two users.

[0061] In the example, the application / service experience depends on multiple results arriving at the distributed UE simultaneously (or nearly simultaneously). In the sound field reproduction example, the application / service sends sounds from different channels to distributed speakers to simulate sound from a specific direction. Small time differences between the arrival times of sounds from different channels can lead to large directional errors that negatively impact the user experience. In the example, a 1 ms time difference can result in an angular error exceeding 30°.

[0062] Multimodal applications may involve a large number of UEs (102a-102e) located relatively far apart from each other. In examples involving multimodal telepresence, dozens of UEs can be synchronized with each other in terms of time, control signals, and visual signals.

[0063] In another example, a device associated with the same haptic and multimodal communication service detects a haptic and multimodal UE within a certain proximity of the device. Upon detecting the haptic and multimodal UE, the device can wake up. As the UE moves, different groups of haptic and multimodal devices can serve the user. Other scenarios utilizing synchronized control of visual-haptic feedback can include industrial manufacturing and real-time drone applications.

[0064] The multimodal interactive system 401 includes an input device 414 that generates multimodal input 413 based on user information 422 and / or environmental information 423. In the multimodal interactive system 401, a modality is a type or representation of information in a particular interactive system. Multimodal interaction is a process of exchanging information in multiple modalities during its occurrence. Modal types may include motion, emotion, and gesture. Modal representations may include video, audio, and haptic feedback (i.e., vibrations or other movements that provide a tactile or sensory experience to the user). In this example, the input device 414 includes 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 the example, the multimodal input 413 includes biometrics 402 from speech, text 403 from speech, emotion 404 from speech, biometrics 405 from face, emotion 406 from face, lip movement 407, emotion from wearable device 408, gesture 409, user's relative position 410, environmental information 411, and tactile information 412.

[0065] Different services can utilize multimodal input 413 to perform functions. In the example, biometric service 424a uses biometrics 402 from speech and biometrics 405 from the face to provide biometric identification of a user. Some services can also utilize multimodal input 413 and outputs from other services to perform functions. In the example, intent-aware service 424b utilizes text 403 from speech, lip movements 407, gestures 409, emotion from speech 404, emotion from the face 406, emotion from wearable devices 408, tactile information 412, and the output of biometric service 424a to provide multimodal natural language processing (NLP) functionality, multimodal emotion functionality, and multimodal tactile functionality. In yet another example, presence service 424c uses relative position 410, environmental information 411, and the output of intent-aware service 424b to provide audio / video services and / or IoT control.

[0066] The multimodal interactive system 401 includes an output device 421 that generates a multimodal output 420 based on multimodal input 413 and / or output from a service (e.g., presence service 426). A user can perceive the multimodal output 420. In an example, the output device 421 includes at least one of a display 421a, an audio speaker 421b, a piezoelectric actuator 421c, a temperature changing device 421d, a lamp 421e, and a vibration device 421f. In an example, the multimodal output 420 includes haptic feedback 415, brightness 416, temperature 417, video 418, and audio 419.

[0067] In XR applications, users can perceive multiple senses (e.g., visual, auditory, tactile) in a virtual environment involving the exchange of information across multiple modalities between the XR device and a base station. Modal representations include video, audio, vibration, or other movements that provide a tactile or sensory experience to the individual. When the synchronicity between different modalities decreases, the user's sense of presence and realism diminishes. Therefore, the multimodal synchronization threshold is defined as the maximum tolerable time interval between the onset of a first stimulus and a second stimulus, where one stimulus is presented to the first sense and the other to the second sense, such that the user perceives the accompanying sensory objects as synchronized. Figure 5 Example 530 of logical channel priority ordering and resource allocation is shown, which can be used to allocate resources for transmitting multimodal data, such as... Figure 4 The multimodal input 413 of the multimodal interactive system shown in the figure.

[0068] Figure 5 Figure 500 illustrates an example 530 of Logical Channel Prioritization (LCP) and resource allocation. A synchronization data group (also referred to as a "sync data group") includes data generated on at least one logical channel (e.g., PDCP SDU, PDCP PDU, MAC PDU, or RLC PDU). In this example, the synchronization data group includes first data generated on a first logical channel and second data generated on a second logical channel. In this example, the first data includes audio data for an XR application, and the second data includes video data for an XR application. If a UE (e.g., UE 102) transmits the first portion of the synchronization data group, the UE should transmit the remaining portion of the synchronization data group before a synchronization deadline. The synchronization deadline is the transmission time of the first portion of the synchronization data group plus a synchronization threshold. The synchronization threshold is the maximum tolerable separation between the transmission of the first portion of the synchronization data group and the transmission of the remaining portion of the synchronization data group.

[0069] In the example, if UE 102 is in timet If the first part of the synchronization data group is sent, the synchronization deadline is ( t +Synchronization threshold). UE 102 should send the remainder of the synchronization data group before the synchronization deadline. The time period from the start of the synchronization deadline to the synchronization deadline after UE 102 sends the first part of the synchronization data group is called the remaining synchronization time. Data in the same synchronization data group has the same remaining synchronization time.

[0070] When UE 102 uses LCP and allocation to schedule the transmission of synchronization data groups for multimodal data, UE 102 may be unable to transmit the entire synchronization data group within the synchronization deadline due to the lack of a token for component modes. When UE 102 is unable to transmit the entire synchronization data group within the synchronization deadline, QoS may be degraded.

[0071] In relation to Figure 5 In the example, UE 102 needs to send 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, network entity 104 configures logical channels 1 536a, 2 536b, 3 536c, and 4 536d for UE 102. UE 102 generates data and transmits it on logical channels 1 536a, 2 536b, 3 536c, and 4 536d. In the example, each of logical channels 536a-536d has a corresponding bucket size 534a-534d. In this example, logical channel 1 536a has a bucket size of two (534a), logical channel 2 536b has a bucket size of three (534b), logical channel 3 536c has a bucket size of two (534c), and logical channel 4 536d has a bucket size of two (534d). Each of logical channels 536b-536d can carry different forms of multimodal data. In this 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 logical channels 536a-536d has a priority level. In this example, logical channel 1 536a has a high priority (e.g., priority level 3), logical channel 2 536b has a medium priority (e.g., priority level 2), and logical channels 3 536c and 4 536d have low priorities (e.g., priority level 1).

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

[0073] Then, UE 102 begins another round of allocation, where UE 102 allocates resources to logical channel 1 536a to transmit data 3 and data 4 in MAC PDU 564. Therefore, although data 12 426 and data 17 427 belong to synchronization data group 1532a, the UE fails to allocate resources to logical channels 2 536b and 3 536c due to insufficient bucket sizes 534c and 534d, and thus fails to include data 12 426 and data 17 427 in MAC PDU 564. If the synchronization deadline for synchronization data group 532a expires before UE 102 receives the next uplink grant, the UE may fail to transmit data 12 and data 17 before the synchronization deadline. Therefore, failure to transmit data 12 426 and data 17 527 may degrade the QoS of XR applications. Figure 5 The priority ordering and resource allocation for each logical channel are shown, while Figure 6 An example of logical channel group priority ordering and resource allocation is shown.

[0074] Figure 6Figure 600 illustrates LCG priority ranking and resource allocation. Figure 6 In Example 630, which depicts LCG prioritization and resource allocation, network entity 104 prioritizes resources in a manner similar to... Figure 5 The method described herein is to configure logical channels 1536a, 1536b, 1536c, and 1536d for UE 102. Network entity 104 further configures the priority level of each of logical channels 536a-536d for UE 102. In this example, logical channel 1536a has a high priority level, logical channel 2536b has a medium priority level, and logical channels 3536c and 4536d have similar priority levels. Figure 5 The lower priority level described in the text.

[0075] Network entity 104 further configures LCG 1 638 and LCG 2 641 for the UE. LCG 1 638 includes a single logical channel: logical channel 1 536a. Therefore, LCG 1 638 is referred to as a single LCG. LCG 2 641 includes multiple logical channels: logical channel 2 536b, logical channel 3 536c, and logical channel 4 536d. Therefore, LCG 1 638b is referred to as a multi-LCG. Because LCG 1 638 includes a single logical channel, LCG 1 638 has a high priority from logical channel 1 536a, and LCG 1 638 has a bucket size of two, 634A, of bucket size 534a from logical channel 1 536a. However, the network entity configures LCG 2 641 with a medium priority and a bucket size of seven, 634b. In this example, synchronization data group 1532a has a minimum remaining synchronization timer (or minimum remaining delivery timer). The priority of the LCG can be configured by network entity 104, set to be equal to the highest priority of the logical channels in the LCG, set to be equal to the medium priority level of the logical channels in the LCG, set to be equal to the lowest priority of the logical channels in the LCG, or determined in a different manner. The LCG token bucket size can be configured by network entity 104, equal to the sum of the token buckets of the logical channels in the LCG, equal to the sum of the token buckets of the logical channels in the LCG but capped by a given value, or determined in another manner.

[0076] In the resource allocation of round 1639a, UE 102 allocates resources to LCG 1638 (i.e., logical channel 1536a) based on LCG 1638 having high priority and based on an LCG bucket size of 2 (634a) to send data 1 and data 2 in MAC PDU 664 (remaining tokens of LCG 1638 = 0). Subsequently, and still in the resource allocation of round 1639a, UE 102 allocates resources to LCG 2641 to send synchronization data group 1532a. In this example, synchronization data group 1532a has the shortest remaining synchronization time timer (or the shortest remaining delivery time timer), that is, synchronization data group 1532a has a shorter remaining synchronization time timer (or the shorter remaining delivery time timer) compared to the remaining synchronization time timer (or the shorter remaining delivery time timer) of synchronization data group 1532b.

[0077] Since logical channel 2536b has the highest priority within LCG 2641, UE 102 allocates resources in round 1639a to transmit data 5 in MAC PDU 664 (remaining tokens in LCG 2641 = 6). Because there is no remaining data from synchronization data group 1532a on logical channel 2536b, UE 102 allocates resources to logical channel 3536c to transmit data 10, data 11, and data 12 in MAC PDU 664 (remaining tokens in LCG 2641 = 3). Because there is no remaining data from synchronization data group 1532a on logical channel 2536c, UE 102 allocates resources to logical channel 4536d to transmit data 15, data 16, and data 17 in MAC PDU 664 (remaining tokens in LCG 2641 = 0).

[0078] In round 2 639b, UE 102 allocates resources to LCG 1 638 (i.e., logical channel 1 536a) to transmit data 3 and data 4 in MACPDU 664. Alternatively, if data 6 and data 7 belong to synchronization data group 1 532a (instead of synchronization data group 2 532b), then in round 1 639a, UE 102 will allocate resources to logical channel 2 536b to transmit data 6 and data 7 in MACPDU 664. Therefore, with Figure 5 Compared to Example 530, which describes logical channel priority ordering and resource allocation, Figure 6 Example 630 of logical channel group priority ordering and resource allocation helps ensure that MAC PDU 664 includes data of synchronization data group 1532a and ensures that UE 102 can send data of synchronization data group 1532a before the synchronization deadline, which can improve QoS. Figure 7 The signaling diagram associated with logical channel group priority ordering and resource allocation is shown above. Figure 6 As stated above.

[0079] Figure 7 This is a signaling diagram 700 illustrating communication between UE 102 and network entity 104 for allocating resources for wireless communication. Network entity 104 may correspond to a base station or a base station unit such as RU 106, DU 108, CU 110, etc.

[0080] UE 102 sends 742 UE capability information to network entity 104. The UE capability information indicates that the UE supports LCG priority ordering and / or LCG resource allocation. In LCG priority ordering, UE 102 performs priority ordering between LCGs and logical channels to allocate resources (e.g., bytes to be transmitted in a MAC PDU). In LCG resource allocation, UE 102 allocates resources to an LCG to transmit data from that LCG.

[0081] The network entity receives UE capability information 742 sent by UE 102. Based on the UE capability information, network entity 104 sends RRC configuration (or LCG configuration) 744 for LCG to UE 102. The RRC configuration configures at least one LCG for UE 102. An LCG includes at least one logical channel. Multiple LCGs refer to LCGs that include multiple logical channels. A single LCG refers to LCGs that include one logical channel. The RRC configuration can also configure logical channels for UE 102 that do not belong to a logical channel group. In the example, the RRC configuration can configure logical channels for UE 102 that do not belong to a logical channel group, logical channels belonging to a single LCG, or logical channels belonging to multiple LCGs. In the example, the network entity sends the RRC configuration 744 in an RRC message such as an RRC reconfiguration message, RRC establishment message, RRC reconstruction message, or RRC recovery message. In other aspects, network entity 104 sends the LCG configuration in a system information message.

[0082] The RRC configuration indicates the priority level (which may also be referred to as priority order), priority bit rate (PBR), and / or bucket size duration (BSD) of the logical channel. The UE maintains a bucket size (i.e., a variable token bucket size) for each logical channel based on the RRC configuration, denoted as B. j Bucket size B j = PBR × T, where T corresponds to the value of B since the last increment of UE. j The elapsed time. The maximum bucket size is given by PBR × BSD. If B j If the value is greater than the maximum bucket size, then UE 102 will move B. jSet to maximum bucket size. BS 104 can configure the PBR value to infinity. In this case, the bucket size of the logical channel is infinity.

[0083] In each respect, the RRC configuration indicates the logical channel belonging to the LCG, as well as the priority level, prioritized bit rate (PBR), and bucket size duration (BSD) of that LCG. In each respect, the RRC configuration indicates the synchronization threshold of the LCG. In other respects, the synchronization threshold is predefined. In each respect, UE 102 derives the priority level, prioritized bit rate, and maximum size from the logical channels in the LCG (described in more detail below).

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

[0085] Network entity 104 receives a 746 scheduling request from UE 102. Based on the scheduling request, network entity 104 sends a 748 uplink grant to UE 102. The uplink grant indicates the radio resources (e.g., time resources and frequency resources) for UE 102 to transmit uplink transmissions (e.g., MAC PDU transmissions). In various aspects, the RRC configuration configures uplink grant and periodicity for UE 102. The UE is to transmit uplink transmissions according to the periodicity indicated by the uplink grant. In this example, network entity 104 includes this in the downlink control information (DCI) on the PDCCH, in the random access response (RAR) message during the random access procedure, or in other contexts such as... RRCReconfiguration Message or RRCRelease The RRC message sends an uplink grant of 748 to UE102.

[0086] UE 102 receives uplink grant 748 from network entity 104. In the example, UE 102 receives it in the DCI on the PDCCH, in the RAR message during the random access procedure, or in other contexts such as... RRCReconfiguration Message or RRCReleaseThe RRC message of the message receives uplink grant 748. When UE 102 receives uplink grant 748, UE 102 determines the size of the MAC PDU associated with that uplink grant. Based on the size of the MAC PDU, UE 102 allocates resources (e.g., bytes in the MAC PDU) to the logical channel and / or LCG respectively, according to the bucket size of the logical channel and / or the bucket size of the LCG. UE 102 multiplexes data from the logical channel or LCG into the MAC PDU based on the resource allocation results.

[0087] In each aspect, UE 102 derives the priority level, prioritized bit rate, and maximum bucket size from the logical channels in the LCG. In one embodiment, UE 102 calculates the priority level of the LCG as 750, representing the highest priority level among the logical channels in the LCG. In another embodiment, UE 102 calculates the priority level of the LCG as 750, representing the lowest priority level among the logical channels in the LCG. UE 102 calculates the prioritized bit rate as 752, representing the sum of the prioritized bit rates of the logical channels in the LCG. In one embodiment, UE 102 calculates the maximum bucket size as 754, representing the sum of the maximum bucket sizes of the logical channels in the LCG. UE 102 calculates the LCG based on PBR × T. j Bucket size B j Where T corresponds to B increasing since UE 102 j The elapsed time. Network entity 104 can (in the RRC configuration) configure the PBR value to infinity. In this case, UE102 calculates the LCG bucket size as infinity.

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

[0089] UE 102 allocates resource 756 to LCG in both the first and second rounds. In the first round, UE 102 allocates resource 756 to LCG according to the descending priority order of LCGs.

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

[0091] In other aspects, in the first round, UE 102 allocates the first resource 756 in the resources to the LCG (e.g., a single LCG or multiple LCGs) according to the descending priority order of the LCGs indicated by the RRC configuration. Subsequently, UE 102 allocates the second resource 756 in the resources to the logical channel according to the descending priority order of the logical channels indicated by the RRC configuration.

[0092] In a further aspect, in the first round, if UE 102 has already allocated resources to an LCG to transmit a portion of the synchronization data group (e.g., in the last uplink grant), then UE 102 allocates resources to that LCG to transmit the remaining portion of the synchronization data group. If UE 102 has already allocated resources to more than one LCG to transmit that portion of the synchronization data group, then UE 102 may allocate resources to these LCGs in any order. In all respects, UE 102 allocates resources to LCGs in descending priority order. After UE 102 allocates resources to an LCG that UE 102 has already partially transmitted that portion of the synchronization data group, UE 102 allocates resources to other LCGs and logical channels in descending priority order.

[0093] In the example, UE 102 has allocated resource 756 (first resource) to transmit a portion of synchronization data group 1 from LCG 1, and UE 102 has allocated resource 756 (second resource) to transmit a portion of synchronization data group 2 in LCG 2. In this example, the RRC configuration indicates that LCG 1 has a higher priority than LCG 2. If UE 102 receives uplink grant 748, then because LCG 1 has a higher priority, UE 102 first allocates resources to LCG 1 to transmit the remaining portion of synchronization data group 1. Then, UE 102 allocates resources to LCG 2 to transmit the remaining portion of synchronization data group 2.

[0094] In UE 102, resources are allocated to the LCG. j(As mentioned above, it may include a single logical channel or multiple logical channels) After that, UE 102 enables LCG j Bucket size B j Decrease the amount of allocated resources (e.g., the number of bytes). If network entity 104 will use the logical channel j If the PBR is configured to infinity, then UE 102 allocates resources to transmit the logical channel before allocating resources to a lower priority logical channel group. j All data that can be used for transmission.

[0095] When UE 102 allocates resources to an LCG, that LCG may have more than one synchronization data group waiting to be transmitted within that LCG. In each respect, UE 102 allocates resources (e.g., bytes in a MAC PDU) to transmit the synchronization data group with the shortest remaining synchronization time. In each respect, if the synchronization data group includes data from more than one logical channel, UE 102 may allocate resources to the logical channels in any order. In other respects, if the synchronization data group includes data from more than one logical channel, UE 102 allocates resources to the logical channels in descending order of logical channel priority.

[0096] In other respects, if the LCG has more than one synchronization data group waiting to be transmitted in the LCG, the UE 102 allocates resources to transmit the synchronization data group that includes data with the shortest remaining delivery time. In other respects, if the synchronization data group includes data from more than one logical channel, the UE 102 may allocate resources to the logical channels in any order. In other respects, if the synchronization data group includes data from more than one logical channel, the UE 102 allocates resources to the logical channels in descending order of their priority.

[0097] As described above, UE 102 allocates resources 756 to the LCG in the first and second rounds. After the UE performs the first round of resource allocation, if there are remaining resources available for allocation, UE 102 performs the second round of resource allocation. In the second round of resource allocation, if UE 102 has already allocated resources to transmit a portion of the synchronization data group of the LCG (e.g., for another uplink grant different from the received uplink grant or as part of the first round), UE 102 allocates resources to that LCG to transmit the remaining portion of that synchronization data group. Similar to the first round, if there are more than one LCG, the UE can allocate resources to these LCGs in any order. Alternatively, UE 102 can allocate resources to LCGs in descending order of their priority.

[0098] Regarding the second round of resource allocation, if an LCG includes a synchronization data group with a remaining synchronization time below a threshold, UE 102 allocates resources to the LCG to transmit that synchronization data group. In other respects, if there is more than one LCG, UE 102 may allocate resources to these LCGs in any order. In still other respects, if there is more than one LCG, UE 102 allocates resources to logical channels in descending order of LCG priority.

[0099] If resources remain unallocated after the first and second rounds, UE 102 can allocate resources to LCGs in a third round that occurs after the first and second rounds. In the third round, UE 102 allocates resources to logical channels or LCGs in descending order of priority (e.g., single LCG or multiple LCGs) until the UE exhausts data from the LCGs or until the UE uses up all resources, whichever occurs first. Therefore, if the highest priority logical channel or the highest priority LCG has a relatively large amount of data to be processed in its buffer in the third round, the highest priority logical channel or the highest priority LCG can consume the remaining resources without giving lower priority logical channels or lower priority LCGs the opportunity to reduce the amount of data to be processed in their respective buffers. To allocate resources to LCGs... j UE 102 allocates resources to LCGs in descending order of logical channel priority. j Logical channels.

[0100] After UE 102 allocates resources to the logical channel and LCG, UE 102 constructs a MAC PDU based on the resource allocation. UE 102 sends 758 MAC PDUs to network entity 104. After UE 102 sends the MAC PDU, UE 102 starts a remaining synchronization timer for the synchronization data group sent in the MAC PDU. UE 102 initially sets the remaining synchronization timer to the synchronization threshold provided in the RRC configuration. Network entity 104 receives 758 MAC PDUs from UE 102. Figures 6 to 7 The logical channel priority ordering and resource allocation are shown. Figures 8 to 9 The following diagram illustrates the implementation. Figures 6 to 7 One or more aspects of the method. Specifically, Figure 8 The UE 102 is shown to be paired with Figures 6 to 7 The implementation of one or more aspects. Figure 11 104 pairs of network entities are shown. Figures 6 to 7 The implementation of one or more aspects.

[0101] Figure 8 A flowchart 800 illustrating a wireless communication method at the UE is shown. (Reference) Figure 1 , Figure 7 and Figure 10 The method can be executed by UE 102, UE equipment 1002, etc., which may include memory 1026', 1006', 1016, and may correspond to the entire UE 102 or the entire UE equipment 1002, or components of UE 102 or UE equipment 1002 (such as wireless baseband processor 1026 and / or application processor 1006).

[0102] UE 102 sends UE capability information (842) to network entity 104. This UE capability information indicates that UE 102 supports logical channel group priority ordering and resource allocation, wherein the receive configuration is based on this UE capability information. For example, refer to... Figure 7 UE 102 sends 742 UE capability information to the network entity. This UE capability information indicates that UE 102 supports logical channel group priority ordering and resource allocation, and the receiving RRC configuration is based on this UE capability information. In the example, Figure 6 The multi-LCG 641 corresponding to the multi-logical channel group is shown.

[0103] UE 102 receives configuration 844 from network entity 104 for a multi-logical channel group comprising at least two logical channels. This configuration indicates that a token bucket size shared across the multi-logical channel group is used to allocate resources for MAC PDUs to the at least two logical channels. For example, refer to... Figure 7 UE 102 receives configuration 744 from network entity 104 for a multi-logical channel group comprising at least two logical channels. This configuration indicates that resources for MAC PDUs will be allocated to the at least two logical channels using a token bucket size shared across the multi-logical channel group. In the example, Figure 6 Logical channels 2 536b, 3 536c, and 4 536d, corresponding to at least two channels, are shown. In another example, Figure 6 The LCG bucket size of 634b is shown, corresponding to the token bucket size shared across multiple logical channel groups. In yet another example, Figure 6 The MAC PDU 664 corresponding to the MAC PDU is shown.

[0104] UE 102 sends scheduling request 846 to network entity 104. For example, refer to Figure 7 UE 102 sends a scheduling request 746 to network entity 104.

[0105] UE 102 receives uplink grant 848 from network entity 104 based on a scheduling request, wherein the transmission of a MAC PDU is further based on this uplink grant. For example, refer to Figure 7UE 102 receives uplink grant 748 from network entity 104 based on a scheduling request, wherein a MAC PDU is sent further based on the uplink grant.

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

[0107] UE 102 calculates the priority order of the 852 multi-logical channel groups based on the first priority order. For example, refer to Figure 7 UE 102 calculates the priority order of the 752 multi-logic channel groups based on the first priority order.

[0108] UE 102 calculates the 854-way logical channel group PBR based on the first PBR, and the transmitted MAC PDU is based on the token bucket size, the priority order of the multi-way logical channel groups, and the multi-way logical channel group PBR. For example, refer to Figure 7 UE 102 calculates the 854 multi-logical channel group PBR based on the first PBR, and the transmitted 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.

[0109] UE 102 allocates resources to the multiple logical channel groups based on their priority order, which is indicated by the configuration. For example, refer to... Figure 7 UE 102 allocates resources to the multi-logical channel group based on the priority order of the multi-logical channel group, which is indicated by the configuration.

[0110] UE 102 sends 858 MAC PDU to network entity 104. This MAC PDU includes data from multiple logical channel groups, whose resources are allocated to these groups to prioritize first data from a first synchronization data group over second data outside that first synchronization data group. For example, refer to... Figure 7 UE 102 sends a 758 MAC PDU to network entity 104. This MAC PDU includes data from multiple logical channel groups, whose resources are allocated to the multiple logical channel groups to prioritize first data from a first synchronization data group over second data outside of that first synchronization data group. In the example, Figure 6 Synchronization data group 1 532a and synchronization data group 2 532b, which correspond to the first synchronization data group and the second synchronization data group, are shown respectively. Figure 7A method is described from the UE side of the wireless communication link, while Figure 8 A method is described from the network side of the wireless communication link.

[0111] Figure 9 This is flowchart 900, which describes a method for wireless communication at a network entity. (Reference) Figure 1 , Figure 7 and Figure 11 The method can be performed by one or more network entities 104, which may correspond to a base station or a base station unit such as RU 106, DU108 and / or CU 110.

[0112] Network entity 104 receives 942 UE capability information from UE 102. This UE capability information indicates that the UE supports logical channel group priority ordering and resource allocation, and the transmission configuration is based on this UE capability information. For example, refer to... Figure 7 Network entity 104 receives 742 UE capability information from UE 102. This UE capability information indicates that the UE supports logical channel group priority ordering and resource allocation, and the transmission configuration is based on this UE capability information. In the example, Figure 6 The multi-LCG 641 corresponding to the multi-logical channel group is shown.

[0113] Network entity 104 sends 944 to UE 102 for a configuration of a multi-logical channel group comprising at least two logical channels. This configuration indicates that a token bucket size shared across the multi-logical channel group should be used to allocate resources for MAC PDUs to the at least two logical channels. For example, refer to... Figure 7 Network entity 104 sends 744 to UE 102 for configuration of a multi-logical channel group, which includes at least two logical channels. This configuration indicates that a token bucket size shared across the multi-logical channel group should be used to allocate resources for MAC PDUs for the at least two logical channels. In the example, Figure 6 Logical channels 2 536b, 3 536c, and 4 536d, corresponding to at least two channels, are shown. In another example, Figure 6 The LCG bucket size of 634b is shown, corresponding to the token bucket size shared across multiple logical channel groups. In yet another example, Figure 6 The MAC PDU 664 corresponding to the MAC PDU is shown.

[0114] Network entity 104 receives scheduling request 946 from UE 102. For example, refer to Figure 7 Network entity 104 receives scheduling request 746 from UE 102.

[0115] Network entity 104 sends uplink grant 948 to UE 102 based on a scheduling request, wherein the received MAC PDU is further based on this uplink grant. For example, refer to Figure 7 Network entity 104 sends uplink grant 748 to UE 102 based on a scheduling request, and the received MAC PDU is further based on this uplink grant.

[0116] Network entity 104 receives 958 MAC PDUs from UE 102. These MAC PDUs include data from multiple logical channel groups, whose resources are allocated according to a configuration such that first data from a first synchronization data group takes precedence over second data outside that first synchronization data group. For example, refer to... Figure 7 Network entity 104 receives 758 MACPDUs from UE 102. These MAC PDUs include data from multiple logical channel groups, whose resources are allocated according to a configuration such that first data from a first synchronization data group takes precedence over second data outside that first synchronization data group. In the example, Figure 6 Synchronization data group 1 532a and synchronization data group 2 532b, corresponding to the first and second synchronization data groups, are shown respectively. For example... Figure 10 The UE equipment 1002 described herein can execute the method of flowchart 800. For example... Figure 11 One or more network entities 104 described may execute the methods of flowchart 900.

[0117] Figure 10 Figure 1000 illustrates an example of a hardware implementation of UE device 1002. UE device 1002 may be UE 102, a component of UE 102, or may implement UE functionality. UE device 1002 may include an application processor 1006, which may have on-chip memory 1006'. In the example, application processor 1006 may be coupled to a secure digital (SD) card 1008 and / or a display 1010. Application processor 1006 may also be coupled to a sensor module 1012, a power supply 1014, an additional memory module 1016, a camera 1018, and / or other related components.

[0118] The UE equipment 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'. Together with and similarly to the application processor 1006, the wireless baseband processor 1026 may also be coupled to a sensor module 1012, a power supply 1014, an additional memory module 1016, a camera 1018, and / or other related components. The wireless baseband processor 1026 may additionally be coupled to one or more subscriber identity module (SIM) cards 1020 and / or one or more transceivers 1030 (e.g., wireless RF transceivers).

[0119] Within one or more transceivers 1030, the UE equipment 1002 may include a Bluetooth module 1032, a WLAN module 1034, an SPS module 1036 (e.g., a GNSS module), and / or a cellular module 1038. The Bluetooth module 1032, WLAN module 1034, SPS module 1036, and cellular module 1038 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1032, WLAN module 1034, SPS module 1036, and cellular module 1038 may each include a dedicated antenna and / or utilize an antenna 1040 to communicate with one or more other nodes. For example, UE equipment 1002 can communicate with another UE (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1030 and antenna 1040, wherein network entity 104 may correspond to a base station or a base station unit such as RU 106, DU108 or CU 110.

[0120] The wireless baseband processor 1026 and application processor 1006 may each include computer-readable media / memory 1026', 1006' respectively. An additional memory module 1016 may also be considered as computer-readable media / memory. Each computer-readable medium / memory 1026', 1006', 1016 may be non-transitory. The wireless baseband processor 1026 and application processor 1006 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1026', 1006', 1016. This 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 media / memory may also be used to store data manipulated by the wireless baseband processor 1026 / application processor 1006 during software execution. The wireless baseband processor 1026 / application processor 1006 may be a component of UE 102. UE equipment 1002 may be a processor chip (e.g., a modem and / or an application) and includes only a wireless baseband processor 1026 and / or an application processor 1006. In other examples, UE equipment 1002 may be the entire UE 102 and may include additional modules for equipment 1002.

[0121] like Figure 1 The discussion and about Figure 8 Implemented, LCG component 140 is configured to receive configuration from a network entity for a multi-logical channel group comprising at least two logical channels, the configuration indicating the allocation of resources for MAC PDUs to the at least two logical channels using a token bucket size shared across the multi-logical channel group; and to send a MAC PDU to the network entity, the MAC PDU comprising data from the multi-logical channel group, the resources being allocated to the multi-logical channel group such that first data from a first synchronization data group takes precedence over second data outside the first synchronization data group. LCG component 140 may be within application processor 1006 (e.g., at 140a), wireless baseband processor 1026 (e.g., at 140b), or both application processor 1006 and wireless baseband processor 1026. LCG components 140a-140b may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0122] Figure 11Figure 1100 illustrates an example of a hardware implementation of 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 functions. The one or more network entities 104 may include or correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1146, which may have on-chip memory 1146'. In some aspects, CU 110 may further include an additional memory module 1156 and / or a communication interface 1148, both of which may be coupled to the CU processor 1146. CU 110 may communicate with DU 108 via a midhaul link 162 (such as an F1 interface between the communication interface 1148 of CU 110 and the communication interface 1128 of DU 108).

[0123] DU 108 may include a DU processor 1126, which may have on-chip memory 1126'. In some aspects, DU 108 may further include an additional memory module 1136 and / or a communication interface 1128, both of which may be coupled to the DU processor 1126. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1128 and RU 106's communication interface 1108.

[0124] RU 106 may include an RU processor 1106, which may have on-chip memory 1106'. In some aspects, RU 106 may further include an additional memory module 1116, a communication interface 1108, and one or more transceivers 1130, all of which may be coupled to the RU processor 1106. RU 106 may further include an antenna 1140, which may be coupled to one or more transceivers 1130, enabling RU 106 to communicate with UE 102 via the antenna 1140 through one or more transceivers 1130.

[0125] On-chip memories 1106', 1126', 1146' and additional memory modules 1116, 1136, 1156 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1106, 1126, 1146 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1106, 1126, 1146, the software causes the processor 1106, 1126, 1146 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processors 1106, 1126, 1146 during software execution. In the example, the LCG configuration component 150 may be located at any of the network entities in one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0126] like Figure 1 The discussion and about Figure 9 The implemented LCG configuration component 150 is configured to send a configuration to the UE for a multi-logical channel group comprising at least two logical channels, the configuration indicating that resources for MAC PDUs should be allocated for the at least two logical channels using a token bucket size shared across the multi-logical channel group; and to receive a MAC PDU from the UE, the MAC PDU comprising data from the multi-logical channel group, the resources being allocated to the multi-logical channel group according to the configuration such that first data from a first synchronization data group takes precedence over second data outside the first synchronization data group. The LCG configuration component 150 may be located within one or more processors of one or more network entities 104—such as RU processor 1106 (e.g., at 150a), DU processor 1126 (e.g., at 150b), and / or CU processor 1146 (e.g., at 150c). LCG configuration components 150a to 150c may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors 1106, 1126, 1146 configured to execute the stated process / algorithm, and stored in a computer-readable medium for use by one or more processors 1106, 1126, 1146, or a combination thereof.

[0127] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is illustrative of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes can also be combined or deleted. Dashed lines may indicate optional elements of the diagram. The appended method claims present the elements of the various boxes in the exemplary order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0128] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not represent the only configurations in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0129] Various aspects of wireless communication systems, such as telecommunications systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such an element is implemented as hardware or software depends on the specific application and design constraints imposed on the system as a whole.

[0130] Any element, any part of an element, or any combination of elements can be implemented as a "processing system" including 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, system-on-a-chip (SoCs), 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 various functionalities described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0131] If the functionality described herein is implemented in software, such functionality 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 include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer. The storage medium can be any available medium accessible by a computer.

[0132] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0133] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.

[0134] The description herein is provided to enable those skilled in the art to practice the aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.

[0135] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" 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 the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used herein generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that is likely to occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0136] Unless otherwise expressly stated, the term "some" means 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 multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set should be interpreted as a collection of elements in which the number of elements is one or more. Terms or articles such as "a," "an," and / or "the / said" may refer to one of the items, features, elements, etc., following that term or article, or may refer to more than one of the items, features, elements, etc., following that term or article. For example, the expression "a small component" does not exclude references to multiple components, because "multiple components" necessarily includes "a small component." Therefore, the expression "a small component" can be interpreted as "at least one component," or similarly, as "one or more components."

[0137] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase that follows each ordinal term.

[0138] As used in the specification and drawings, reference numerals are sometimes cross-referenced across drawings to indicate the same or similar features. Features that are identical in multiple drawings may be labeled with the same reference numerals in multiple drawings. Features that are similar but not identical across multiple drawings may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the drawings). Therefore, the same numerals may indicate the same action.

[0139] Structural and functional equivalents of elements throughout the aspects described herein, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element shall be construed as a component plus a function unless the phrase “component for…” is explicitly used herein. As used herein, the phrase “based on” should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) shall be construed as “at least based on A.”

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

[0141] Example 1 is a method for wireless communication at a user equipment (UE), comprising: receiving from a network entity a configuration for a multi-logical channel group, the multi-logical channel group comprising at least two logical channels, the configuration indicating the allocation of resources for Media Access Control (MAC) Protocol Data Units (PDUs) for the at least two logical channels using a token bucket size shared across the multi-logical channel group; and sending the MAC PDU 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 such that first data from a first synchronization data group takes precedence over second data outside the first synchronization data group.

[0142] Example 2 is the method according to Example 1, further comprising: allocating the resources to the multiple logical channel groups based on the priority order of the multiple logical channel groups, the priority order being indicated by the configuration.

[0143] Example 3 is the method according to Example 2, wherein allocating the resources to the multiple logical channel group includes: allocating a first resource among the resources to the multiple logical channel group based on the priority order; and allocating a second resource among the resources to a single logical channel group comprising only one logical channel after allocating the first resource based on the priority order.

[0144] Example 4 is the method according to Example 2, wherein allocating the resources to the multiple logical channel groups includes: allocating the resources to the multiple logical channel groups and a single logical channel group comprising only one logical channel based on the priority order.

[0145] Example 5 is a method according to any one of Examples 2 to 4, wherein allocating the resources to the multiple logical channel group comprises: allocating the resources to the at least two logical channels based on the priority order and the total number of available tokens for the at least two logical channels.

[0146] Example 6 is a method according to any one of Examples 2 to 5, wherein allocating the resources to the multiple logical channel group comprises: allocating a first resource for the first data from the first synchronization data group to the at least two logical channels based on the token bucket size.

[0147] Example 7 is a method according to any one of Examples 2 to 6, wherein allocating the resources to the multiple logical channel groups comprises: allocating a second resource for the first data from the first synchronization data group based on the priority order and at least one of the first data from the first synchronization data group having the shortest remaining synchronization time or the shortest remaining delivery time.

[0148] Example 8 is a method according to any one of Examples 1 to 7, wherein the configuration indicates the token bucket size, the priority order of the multiple logical channel groups, and the priority bit rate (PBR), and wherein the MAC PDU is sent based on the token bucket size, the priority order of the multiple logical channel groups, and the PBR.

[0149] Example 9 is a method according to any one of Examples 1 to 7, wherein the configuration indicates a first token bucket size, a first priority order of the at least two logical channels of the multi-logical channel group, and a first priority bit rate (PBR), the method further comprising: calculating the token bucket size based on the first token bucket size; calculating the priority order of the multi-logical channel group based on the first priority order; and calculating the multi-logical channel group PBR based on the first PBR, and wherein sending 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.

[0150] Example 10 is a method according to any one of Examples 1 to 9, wherein each logical channel of the multi-logical channel group corresponds to a different mode of multi-modal data.

[0151] Example 11 is a method according to any one of Examples 1 to 10, further comprising: sending UE capability information to the network entity, the UE capability information indicating that the UE supports logical channel group priority ordering and resource allocation, wherein receiving the configuration is based on the UE capability information.

[0152] Example 12 is a method according to any one of Examples 1 to 11, further comprising: sending a scheduling request to the network entity; and receiving an uplink grant from the network entity based on the scheduling request, wherein sending the MACPDU is further based on the uplink grant.

[0153] Example 13 is a method for wireless communication at a network entity, comprising: sending to a user equipment (UE) a configuration for a multi-logical channel group, the multi-logical channel group comprising at least two logical channels, the configuration indicating that resources for Media Access Control (MAC) Protocol Data Units (PDUs) should be allocated for the at least two logical channels using a token bucket size shared across the multi-logical channel group; and receiving from the UE the MAC PDU, the MAC PDU comprising data from the multi-logical channel group, the resources being allocated to the multi-logical channel group according to the configuration such that first data from a first synchronization data group takes precedence over second data outside the first synchronization data group.

[0154] Example 14 is the method according to Example 13, wherein the configuration indication allocates the resources based on the priority order of the multiple logical channel groups, the priority order being determined by the configuration indication.

[0155] Example 15 is the method according to Example 14, wherein the configuration indicates that a first resource of the resources is to be allocated to the multi-logical channel group based on the priority order, and wherein a second resource of the resources is to be allocated to a single logical channel group comprising only one logical channel after the first resource is allocated, based on the priority order.

[0156] Example 16 is the method according to Example 14, wherein the configuration indicates that the resources are to be allocated to the multi-logical channel group and the single logical channel group including only one logical channel based on the priority order.

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

[0158] Example 18 is a method according to any one of Examples 14 to 17, wherein the configuration indicates that a first resource for the first data from the first synchronization data group is to be allocated to the at least two logical channels.

[0159] Example 19 is a method according to any one of Examples 14 to 18, wherein the configuration indicates that a second resource for the first data from the first synchronization data group shall be allocated based on the priority order and at least one of the first data having the shortest remaining synchronization time or the shortest remaining delivery time.

[0160] Example 20 is a method according to any one of Examples 13 to 19, wherein the configuration indicates the token bucket size, priority order, and priority bit rate (PBR), and wherein receiving the MAC PDU is based on the token bucket size, the priority order, and the PBR.

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

[0162] Example 22 is a method according to any one of Examples 13 to 21, wherein each logical channel of the multi-logical channel group corresponds to a different mode of multi-modal data.

[0163] Example 23 is a method according to any one of Examples 13 to 22, further comprising: receiving UE capability information from the UE, the UE capability information indicating that the UE supports logical channel group priority ordering and resource allocation, wherein the configuration is sent based on the UE capability information.

[0164] Example 24 is a method according to any one of Examples 13 to 23, further comprising: receiving a scheduling request from the UE; and sending an uplink grant to the UE based on the scheduling request, wherein receiving the MAC PDU is further based on the uplink grant.

[0165] 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 the method as described in any one of Examples 1 to 24.

[0166] Example 26 is an apparatus for wireless communication, including components for implementing the method as described in any one of Examples 1 to 24.

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

Claims

1. A method for wireless communication at a user equipment (UE) (102), comprising: Receive (744) configuration from network entity (104) for a multi-logical channel group (641) comprising at least two logical channels (536), the configuration indicating the use of a token bucket size (634) shared across the multi-logical channel group (641) to allocate resources for Media Access Control MAC Protocol Data Units (PDUs) (664) for the at least two logical channels (536); as well as The MAC PDU (664) is sent (758) to the network entity (104), the MAC PDU including data (532) from the multiple logical channel group (641), the resources being allocated to the multiple logical channel group (641) such that first data (532a) from the first synchronization data group takes precedence over second data (532b-532c) outside the first synchronization data group.

2. The method according to claim 1, further comprising: Based on the priority order of the multiple logical channel groups (641), the resources are allocated (756) to the multiple logical channel groups (641), the priority order being indicated by the configuration.

3. The method of claim 2, wherein allocating the resources (756) to the multiple logical channel group (641) comprises: Based on the priority order, the first resource in the resources is allocated to the multi-logical channel group (641); as well as Based on the priority order, after allocating the first resource, the second resource in the resource is allocated to a single logical channel group (638) that includes only one logical channel (536).

4. The method of claim 2, wherein allocating the resources (756) to the multiple logical channel group (641) comprises: Based on the priority order, the resources are allocated to the multi-logical channel group (641) and the single logical channel group (638) which includes only one logical channel (536).

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

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

7. The method according to any one of claims 2 to 6, wherein allocating the resources (756) to the multiple logical channel group (641) comprises: Based on the priority order and the fact that the first data (532a) from the first synchronization data group has at least one of the shortest remaining synchronization time or the shortest remaining delivery time, a second resource is allocated for the first data (532a) from the first synchronization data group.

8. The method according to any one of claims 1 to 7, wherein the configuration indicates the token bucket size (634), the priority order of the multiple logical channel groups (641) and the priority bit rate PBR, and wherein the transmission (758) of the MAC PDU (664) is based on the token bucket size (634), the priority order of the multiple logical channel groups and the PBR.

9. The method according to any one of claims 1 to 7, wherein the configuration indicates a first token bucket size, a first priority order of the at least two logical channels (536) in the multi-logical channel group (641), and a first priority bit rate PBR, the method further comprising: The token bucket size is calculated (754) based on the size of the first token bucket; The priority order of the multiple logical channel group (641) is calculated based on the first priority order (752); as well as (753) The multi-logical channel group PBR is calculated based on the first PBR, and (758) the MAC PDU is sent based on the token bucket size, the priority order of the multi-logical channel group, and the multi-logical channel group PBR.

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

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

12. The method according to any one of claims 1 to 11, further comprising: Send a scheduling request (746) to the network entity (104); as well as Based on the scheduling request, receive (748) uplink grant from the network entity (104), wherein send (758) the MAC PDU (664) further based on the uplink grant.

13. A method for wireless communication at a network entity (104), comprising: Send (744) to the user equipment (UE) (102) a configuration for a multi-logical channel group (641) comprising at least two logical channels (536), the configuration indicating that a token bucket size (634) shared across the multi-logical channel group (641) is to be used to allocate resources for Media Access Control (MAC) Protocol Data Units (PDUs) (664) for the at least two logical channels (536); as well as The MAC PDU (664) is received (758) from the UE (102), the MAC PDU including data (532) from the multiple logical channel group (641), the resources being allocated to the multiple logical channel group (641) according to the configuration such that first data (532a) from the first synchronization data group takes precedence 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), the priority order of the multiple logical channel groups (641), and the priority bit rate PBR, and wherein receiving (758) the MAC PDU (664) is based on the token bucket size (634), the priority order of the multiple logical channel groups, and the PBR.

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

Images