Logical channel priority for delay sensitive traffic communications

Abstract

Aspects of the present disclosure relate to an apparatus and a method that incorporates and provides wireless communication for jitter reduction of delay sensitive data. The method includes receiving a control message including a logical channel configuration of logical channels, each logical channel including an associated priority value, and an uplink resource allocation grant. The method includes tracking a respective remaining delay budget for each packet data unit (PDU) in uplink buffer (s) allocated to corresponding logical channel (s). The method includes determining a multiplexing order of PDUs of a logical channel according to an associated remaining delay budget on a media access control layer by increasing the remaining delay budget. The method includes allocating resources allocated by the uplink grant to the logical channel by increasing the remaining delay budget. The method includes generating an uplink signal by multiplexing a PDU of a logical channel according to the allocated resources.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 367,773, filed on July 6, 2022, the contents of which are incorporated herein in their entirety. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to wireless communications scheduling that accommodates data delays for video frame transmissions. Background Art

[0004] A wireless communication system may include one or more network communication devices (including base stations), which may be referred to as eNodeB (eNB), next generation NodeB (gNB) or other suitable terms. Each network communication device (such as a base station) may support wireless communication of one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. A wireless communication system may utilize resources of a wireless communication system to support wireless communication with one or more user communication devices, such as time resources (e.g., symbols, time slots, sub-time slots, mini-time slots, aggregated time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies other than 5G.

[0005] The UE can communicate with the gNB to support extended reality (XR) features. XR refers to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices. XR is an umbrella term for different types of reality (including virtual reality (VR), augmented reality (AR) and mixed reality (MR)), as well as the areas inserted between them. The level of virtuality ranges from partial sensory input to fully immersive VR. A key aspect of XR is the extension of human experience, especially related to presence (represented by VR) and cognitive acquisition (represented by AR). Summary of the invention

[0006] The present disclosure relates to methods, apparatus, and systems for supporting wireless communications for jitter-reduced wireless communications by user equipment for delay-sensitive data, such as extended reality (XR) services. The present disclosure provides different solutions described in various embodiments for enhancing a logical channel prioritization (LCP) process to address the quality of service (QoS) issues of XR applications. The user equipment considers the remaining delay budget associated with the data of the logical channel and available for initial transmission. Specifically, the user equipment determines the order in which the allocated resources of the uplink media access channel (MAC) are multiplexed into transport blocks (TBs). For situations where the remaining delay budgets of more than one logical channel are the same or there is no delay-sensitive data awaiting initial transmission, logical channel priority may be considered.

[0007] Some implementations of the methods and apparatus described herein may also include: receiving, on a downlink, one or more control messages from a network device via a transceiver, the one or more control messages containing: (i) a logical channel configuration for more than one logical channel, including a priority value associated with each logical channel; and (ii) an uplink resource allocation grant. The method includes: tracking a corresponding remaining delay budget for each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel in more than one logical channel. The method includes: determining, at a media access control layer, a multiplexing order of the PDUs of more than one logical channel in ascending order based on the associated remaining delay budgets, starting with the PDU with the smallest remaining delay budget. The method includes: allocating resources allocated by the uplink grant to the logical channel based on the determined multiplexing order, starting with the logical channel with the PDU, the PDU having the smallest remaining delay budget. The method includes: generating an uplink signal by multiplexing the PDUs of more than one logical channel based on the allocated resources.

[0008] Some implementations of the methods and apparatus described herein may also include a network device or a method that incorporates or provides: wireless communication for jitter reduction of delay-sensitive data in an uplink signal from a user device. The method includes: sending one or more control messages to the user device via a transceiver of the network device on a downlink, the one or more control messages containing: (i) a logical channel configuration of more than one logical channel, including a priority value associated with each logical channel; and (ii) an uplink resource allocation grant. The one or more control messages prompt the user device to track the corresponding remaining delay budget of each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel in the more than one logical channel. In addition, the one or more control messages prompt the user device to determine, at a media access control layer, a multiplexing order of the PDUs of more than one logical channel in ascending order based on the associated remaining delay budgets, starting from the PDU with the smallest remaining delay budget. The one or more control messages prompt the user device to allocate resources allocated by the uplink grant to the logical channel based on the determined multiplexing order, starting from the logical channel with the PDU, and the PDU has the smallest remaining delay budget. The method includes: receiving an uplink signal from a user equipment via a transceiver on a medium access control layer, the uplink signal including: PDUs of more than one logical channel multiplexed by the user equipment according to allocated resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example of a wireless communication system capable of wireless communication according to aspects of the present disclosure is presented, the wireless communication system supporting a logical channel procedure (LCP) enhanced for delay-sensitive services, such as extended reality (XR) services.

[0010] Figure 2 A downlink and uplink communication diagram is presented that illustrates aspects of a logical channel prioritization (LCP) process that takes into account residual delay budget (RDB) and / or packet delay budget (PDB) according to aspects of the present disclosure.

[0011] Figure 3 A graphical diagram of the amount of traffic or data buffered in corresponding logical channels at different assigned priorities according to aspects of the present disclosure is presented.

[0012] Figure 4 An example graphical diagram of an implementation of an LCP process that addresses stringent delay requirements of logical channels carrying delay-sensitive data is presented in accordance with aspects of the present disclosure.

[0013] Figure 5Graphical diagrams of first, second, and third configuration grants for early, on-time, and late uplink Media Access Channel (MAC) packet data units, respectively, are presented in accordance with aspects of the present disclosure.

[0014] Figure 6 An example graphical diagram is presented in which a logical channel prioritization process is used to initiate allocation of traffic or data in accordance with aspects of the present disclosure.

[0015] Figure 7 An example graphical diagram is presented in which a logical channel prioritization process is used to accomplish allocation of traffic or data in accordance with aspects of the present disclosure.

[0016] Figure 8 Examples of information elements that implement configuration authorization configuration according to aspects of the present disclosure are presented.

[0017] Fig. 9 An example of a block diagram of a user equipment that supports wireless communication with a network device by multiplexing delay sensitive data in an uplink signal according to aspects of the present disclosure is presented.

[0018] Fig.10 An example of a block diagram of a network device supporting scheduling and receiving wireless communications including uplink signals from user equipment multiplexing delay-sensitive data is presented in accordance with aspects of the present disclosure.

[0019] Fig.11 A flow chart of a method performed by a user equipment supporting wireless communications that multiplex uplink signals to meet delay requirements applicable to a portion of delay sensitive data is presented in accordance with aspects of the present disclosure.

[0020] Fig.12 A flow chart of a method performed by a network device supporting wireless communications that multiplex uplink signals to meet delay requirements applicable to portions of delay sensitive data is presented in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0021] As an example of delay-sensitive traffic, the extended reality (XR) traffic between the radio access network (RAN) and the user equipment (UE) over the air interface is modeled as a packet delay budget (PDB). The PDB is a finite time budget for data packets sent over the air from a base node to a UE or from a UE to a base node. A delay budget can also be defined for an application data unit (ADU). An ADU is the smallest data unit that can be processed independently by an application, such as for processing out-of-order traffic data.

[0022] Virtual reality (VR) is a rendered version of a delivered visual and audio scene. The rendering is intended to mimic as naturally as possible the visual and auditory stimuli of the real world as the observer or user moves within a range defined by the application. Augmented reality (AR) provides the user with additional information, artificially generated items, or content overlaid on their current environment. Mixed reality (MR) is an advanced form of AR in which some virtual elements are inserted into the physical scene with the goal of providing the illusion that these elements are part of the real scene.

[0023] In the field of video compression, video frames are compressed using different algorithms with different advantages and disadvantages, mainly around the amount of data compression. These different algorithms for video frames are called picture types or frame types. The three main picture types used in different video algorithms are I, P, and B. Picture types differ in the following characteristics: (i) Intra-coded (I) frames are the least compressible, but do not require other video frames to decode; (ii) Predicted (P) frames can use data from previous frames for decompression and are more compressible than I frames; and (iii) Bidirectionally predicted (B) frames can use both previous and forward frames as data references to obtain the highest amount of data compression. XR services have many characteristics: (i) variable packet arrival rate: packets arrive at 30-120 frames / second with some jitter; (ii) packets with variable and large packet sizes; (iii) B / P frames are dependent on I frames, and (iv) there are multiple services / data streams in the uplink, such as gestures and video scenes. The delay budget of the video frame ADU is particularly important in XR services due to the decoding requirements of the video content. A video frame can be an I-frame, a P-frame, or can be composed of I-slices and / or P-slices. I-frames / I-slices are more important and larger than P-frames / P-slices. The importance is related to the impact of late services on the ability to successfully decode and use the service.

[0024] The current specific logical channel prioritization (LCP) process is based on statically configured parameters, such as logical channel priority. However, these static priority rules may not be sufficient to meet the strict delay requirements of XR applications. For example, currently, the LCP process does not take into account the remaining delay budget for the data to be transmitted when allocating uplink resources to logical channels (LCH). After the remaining delay budget expires, the delay-sensitive services that arrive may not be available, for example, which will reduce the quality of content presentation and thus reduce the user experience. "User experience" refers to the overall sense of performance experienced by users of communication devices or peripherals when using products, applications, systems or services. In the context of the present disclosure, user experience is a broad term that can cover the user's ability to navigate a product, the ease of use of a device or product, the relevance of the displayed content, etc. Some immersive user interfaces (such as XR displays) have demanding communication requirements. The user experience is reduced when the presentation of images is significantly reduced due to insufficient data throughput or excessive data delays.

[0025] The present disclosure provides solutions that can be used alone or in combination to enhance the LCP process for delay-sensitive services (such as for XR applications). The enhanced LCP process maintains the quality of service (QoS) required for delay-sensitive services while retaining the ability to revert to logical channel priority sorting. The user equipment considers the remaining delay budget associated with the service or data of the logical channel (LCH) available for initial transmission to determine the order of multiplexing priorities in the transport block (TB) at the media access control (MAC) layer. For delay-sensitive data, logical channel priority is only considered if the remaining delay budget of more than one LCH is the same.

[0026] In one embodiment, the user equipment implements an enhanced LCP process for multiplexing data on physical uplink shared channel (PUSCH) resources allocated or reserved for XR services. The MAC entity / UE considers the remaining delay budget (RDB) of the LCH data available for transmission to determine the order in which the LCH data is multiplexed on the uplink resources. The service or data with the strictest remaining delay budget (i.e., the lowest remaining RDB) is prioritized and therefore multiplexed first on the PUSCH resources.

[0027] In another embodiment, the present disclosure introduces a new field in the downlink control information (DCI) for allocating uplink (UL) resources (UL DCI) for initial transmission. The new field indicates whether the MAC should use an enhanced LCP process for delay-sensitive data or should revert to allocation based on LCH priority. When the field indicates the previous prioritization of delay-sensitive traffic, the remaining delay budget (RDB) or packet delay budget (PDB) is then used to prioritize traffic during the LCP process and multiplex traffic to the allocated resources of the MAC layer. In one example, the new DCI field is a 1-bit flag.

[0028] In another embodiment, the present disclosure introduces a configuration grant (CG) optimized for delay-sensitive services or data (e.g., XR services) by allocating multiple CG resource allocations within each CG period. According to one implementation of this embodiment, a new parameter within the CG configuration indicates the timing of additional CG resources within the CG period. In one example, the new parameter is a field for indicating the maximum jitter expected for delay-sensitive services or data mapped to the CG configuration. According to one example, the CG configuration allocates additional configuration grant resources 'x' time slots before the CG resources and 'y' time slots after the CG resources. The user device uses the next available resource in the additional configuration grant resources, and any remaining resources thereafter are available for rescheduling by the network device. The CG configuration reduces delay by accommodating jitter within a single CG period, and does not have to potentially wait too long to reschedule uplink transmissions in subsequent CG periods.

[0029] Figure 1 An example of a wireless communication system 100 according to aspects of the present disclosure is presented, which implements wireless communication that supports LCP enhanced for delay-sensitive services (such as XR services). The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as a new radio (NR) network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0030] One or more base stations 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the base stations 102 described herein may be, may include, or may be referred to as a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), a network device, or other suitable terms. The base station 102 and the UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, the base station 102 and the UE 104 may wirelessly communicate via a user-to-user (Uu) interface.

[0031] The base station 102 may provide a geographic coverage area 110, and the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110. For example, the base station 102 and the UE 104 may support wireless communications of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) in accordance with one or more radio access technologies. In some implementations, the base station 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 110 may be associated with different base stations 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0032] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0033] One or more UEs 104 may be devices of different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated in FIG. Figure 1As shown, UE 104 can communicate with various types of devices, such as base station 102, other UE 104, or network equipment (e.g., core network 106, relay equipment, integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally or alternatively, UE 104 can support communications with other base stations 102 or UEs 104 (which can act as relays in the wireless communication system 100).

[0034] In the following description, the timing of transmission and retransmission of control channels and data channels supports the delay and / or error rate requirements of portions of video frames and may be referred to as time units. Time units such as symbols, time slots, sub-time slots, and transmission time intervals (TTIs) may have specific durations. In one example, a symbol may be a certain fraction or percentage of an orthogonal frequency division multiplexing (OFDM) symbol length associated with a specific subcarrier spacing (SCS). In another example, an uplink (UL) transmission burst may consist of multiple transmissions. Multiple transmissions may have the same priority, different priorities, or no associated priorities. Multiple transmissions may include intervals between transmissions that are short enough in duration without the need to perform channel sensing or listen-before-transmit (LBT) operations between transmissions.

[0035] UE 104 may also be capable of supporting wireless communications directly with other UEs 104 via a communication link 112. For example, UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 112 may be referred to as a sidelink. For example, UE 104 may support wireless communications directly with another UE 104 via a PC5 interface. PC5 refers to a reference point where UE 104 communicates directly with another UE 104 via a direct channel without the need to communicate with base station 102.

[0036] The base station 102 may support communication with the core network 106, or with another base station 102, or both. For example, the base station 102 may interface with the core network 106 via one or more backhaul links 114 (e.g., via S1, N2, or another network interface). The base stations 102 may communicate with each other via the backhaul links 114 (e.g., via X2, Xn, or another network interface). In some implementations, the base stations 102 may communicate directly with each other (e.g., between the base stations 102). In some other implementations, the base stations 102 may communicate with each other indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmission reception points (TRPs).

[0037] The core network 106 may support user authentication, access authorization, tracking, connection, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of one or more UEs 104 served by one or more base stations 102 associated with the core network 106.

[0038] Some implementations of the methods and apparatus described herein may also include signaling or handshaking between a base node (such as base station 102) and a user device (such as UE 104) indicating which transport blocks (TBs) are associated with packets and / or application data units (ADUs). In one example, the signaling or handshaking may be a downlink control information (DCI) indication, or a media access control (MAC) control element (CE) indication. In one or more embodiments, the base node and the device may use a priority indication of the priority of a particular type of video transmission. In one example, an I frame / slice may have a high priority, while a P frame / slice may have a low priority.

[0039] Figure 2A communication diagram 200 of a downlink 201 and an uplink 202 is presented, illustrating aspects of a logical channel prioritization (LCP) process that takes into account a residual delay budget (RDB) and / or a packet delay budget (PDB). The downlink 201 includes a logical channel configuration message 204 and a medium access control (MAC) main configuration message 206 as part of a radio resource control (RRC) protocol 208 that establishes data communications. The uplink 202 includes a periodic buffer status report 210 that indicates the amount of traffic or data that requires uplink allocation. The buffer status report 210 may indicate a multiplexing capacity to prompt authorization to prioritize multiplexing traffic or data on the uplink 202 based on the residual delay budget of delay sensitive data such as XR traffic. When delay sensitive data is not buffered, the buffer status report 210 may alternatively not indicate a multiplexing capacity to prompt resumption of multiplexing traffic or data on the uplink 202 based on logical channel priority. The control message(s) 212 on the uplink 202 may include uplink (UL) downlink control information (DCI) 214, such as a UL PUSCH grant 216, which defines an allocated UL amount MAC PDU 218 to carry portions of a first logical channel (LCH1) 221, a second logical channel (LCM2) 222, and a third logical channel (LCD3) 223. In one or more embodiments, the UL PUSCH grant 216 provides a configuration grant to enable selection of two or more allocated UL amount MAC PDUs 218 to accommodate jitter in the availability of buffered data for the uplink signal.

[0040] Figure 3 A graphical diagram 300 of the amount of traffic or data buffered in corresponding logical channels of different assigned priorities is presented. Portions of the traffic or data are allocated to the allocated uplink amount MAC PDU 304. For clarity, three LCHs are depicted, each with an assigned priority: (i) a first logical channel (LCH1) 301 is assigned the highest priority (e.g., priority = 1); (ii) a second logical channel (LCH2) 302 is assigned a medium priority (e.g., priority = 2); and (iii) a third logical channel (LCH3) 303 is assigned the lowest priority (e.g., priority = 3). The traffic or data buffered in LCH1 301, LCH2 302, and LCH3 303 are allocated to the MAC PDU allocated by the uplink grant 304. Specifically, depending on the presence of delay-sensitive data (e.g., XR traffic), the traffic or data is allocated according to the lowest RDB priority 306 or according to the LCH priority 308.

[0041] Figure 4An example graphical diagram 400 of an implementation of an LCP process is presented that addresses the strict delay requirements of (multiple) LCHs / (multiple) DRBs carrying delay sensitive data (such as XR services / applications, also referred to as XR bearers / LCHs). LCH1 301 caches a first PDU 411 with an RDB of 20ms, and a second PDU 412 with an RDB of 10ms. LCH2 302 caches a third PDU 413 with an RDB of 40ms, and a fourth PDU 414 with an RDB of 5ms. LCH3 303 caches a fifth PDU 415 with an RDB of 50ms. The fourth PDU 414, the second PDU 412, and the first PDU 411 are allocated to the allocated uplink resources defined by the MAC PDU grant 304 based on the lowest RDB.

[0042] Figure 5 A graphical diagram 500 is presented of a first configuration grant 501, a second configuration grant 502, and a third configuration grant 503 of early, on-time, and late UL MAC PDUs 506a, 506b, and 506c, respectively, that may be utilized on the uplink 202. The spacing between the UL MAC PDUs 506a, 506b, and 506c is based on an expected amount of jitter in receiving traffic or data to be transmitted on the uplink 202.

[0043] In one or more embodiments, the LCP process retains the ability to revert to LCH priority based on LCH priority when delay sensitive data is not present. In particular, when the LCP process is operated in this recovery mode, "normal" data that is less delay sensitive than XR traffic is cached and available for uplink transmission. The LCP process reverts to the priority of considering LCHs that are entitled to multiplex data onto uplink resources allocated by an uplink resource allocation (grant). The set of LCHs that are allowed to map data to UL resources is determined by the configured LCH restrictions. In particular, only LCHs that meet all configured LCH restrictions will be considered for subsequent multiplexing by the LCP process. UL resources are allocated to LCHs in strict priority order, starting with the highest priority LCH.

[0044] For this recovery in the LCP procedure, the UE shares UL resources between the configured LCHs based on the LCH priority and the priority bit rate configured for the LCH. The idea behind the priority bit rate is to support a minimum bit rate for each logical channel, including low priority non-GBR (guaranteed bit rate) bearers, to avoid potential starvation. Each bearer should at least acquire enough resources to achieve the priority bit rate (PBR). The LCP procedure includes an initial step of selecting the LCH for TB generation based on the configured LCH restrictions. Thereafter, the LCP procedure is generally specified as a "two-step" procedure. In the first step, the LCHs are served (in descending priority order, starting with the highest priority logical channel) until their configured PBR (implemented by a token bucket model). In the second step of the LCP, if any uplink resources still exist (after the PBR of the first round of LCHs has been met), all logical channels are served in strict descending priority order (regardless of the value of the bucket) until the data or UL grant for that logical channel is exhausted.

[0045] According to one embodiment, when delay budget considerations are not applicable to a particular PDU or are the same for a particular PDU, the UE may revert to using a preset priority order classification when performing the LCP procedure. In one example, logical channels may be prioritized according to the following order, with the highest priority first:

[0046] (a) C-RNTI MAC CE or data from UL-CCCH;

[0047] (b) Configuring the authorization confirmation MAC CE or BFR MAC CE or multiple entries

[0048] Authorization confirmation MAC CE;

[0049] (c) Sidelink Configuration Authorization Confirmation MAC CE;

[0050] (d) LBT fault MAC CE;

[0051] (e) The MAC CE of the SL-BSR that is prioritized according to clause 5.22.1.6;

[0052] (f) MAC CE of BSR, except BSR used for padding;

[0053] (g) Single-entry PHR MAC CE or multi-entry PHR MAC CE;

[0054] (h) MAC CE of the desired number of protection symbols;

[0055] (i) MAC CE of preemptive BSR;

[0056] (j) MAC CE of SL-BSRs, except for SL-BSRs that are prioritized according to clause 5.22.1.6 and SL-BSRs used for padding;

[0057] (k) data from any logical channel, except data from UL-CCCH;

[0058] (l) MAC CE for recommended bit rate query;

[0059] (m) MAC CE for the padded BSR; and

[0060] (n) MAC CE of SL-BSR used for padding.

[0061] Note that the priority ordering between the Configuration Authorization Confirmation MAC CE, the Multiple-Entry Configuration Authorization Confirmation MAC CE, and the MAC CE for BFR depends on the UE implementation.

[0062] Figure 6 An example graphical diagram 600 is presented in which the logical channel prioritization process is used to begin the allocation of traffic or data. The selection process includes first selecting the first data / PDU 611 from LCH1 301 as the first allocation 621 of the UL MAC PDU 304. Then, the second data / PDU 612 from LCH2 302 is selected as the second allocation 622 of the UL MAC PDU 304. Then, the third data / PDU 613 from LCH3 303 is selected as the third allocation 623 of the UL MAC PDU 304, leaving the remaining allocation 624.

[0063] Figure 7 An example graphical diagram 700 is presented in which a logical channel prioritization process is used to complete the allocation of traffic or data. In a second round of the selection process after selecting the first PDU 611, the second PDU 612, and the third PDU 613, the LCH priority is used to select a corresponding number of LCH1 301 as the fourth data / PDU 614 to fill the remaining allocation 624 (i.e., the "fourth" allocation).

[0064] Many XR and cloud computing use cases are characterized by quasi-periodic traffic (possibly with jitter) with high data rates in the DL (i.e., video streaming), combined with frequent UL (i.e., attitude / control updates) and / or UL video streaming. Both DL and UL traffic are characterized by relatively tight packet delay budgets (PDBs). In order to support sufficiently high capacity, i.e., the number of served UEs that meet the service requirements, it is important to ensure that packets are received within the expected delay budget (e.g., PDB or ADU delay budget). Since the application layer does not benefit from packets received outside its PDB, i.e., packets are dropped, it is critical that packets are successfully received within the relevant delay bounds.

[0065] According to one embodiment, the gNB allocates to the UE UL resources reserved for XR bearer data, i.e., data of the LCH configured for the XR service / application. These uplink resources are reserved specifically for the XR bearer / LCH. That is, data of other LCHs that are not configured for XR services / applications are scheduled on other UL-SCH resources. According to one implementation of this embodiment, those uplink resources reserved for XR data are configured uplink grant resources (CG PUSCH resources). The configured grant can be applicable to the UL service of the XR application. In one example, the XR application can generate uplink data for quasi-periodic services, such as posture or control updates. Through the existing LCH restrictions, i.e., the LCH to CG mapping configuration, it can be ensured that only specific LCHs (e.g., XR bearers / LCHs) are allowed to multiplex data on the CG PUSCH resources allocated for the XR service.

[0066] According to one embodiment, the UE uses a new LCP process to multiplex data on PUSCH resources allocated / reserved for XR services. According to one implementation of this embodiment, the UE uses the remaining delay budget (RDB) of the data of the LCH that can be used to transmit i to determine the order in which the LCH data is multiplexed on the UL resources. When determining the order and number of resources allocated to XR LCHs or bearers, the UE does not revert to considering LCH priorities. One principle of these new LCP multiplexing rules is that data with the strictest remaining delay budget (e.g., the lowest remaining RDB) should be prioritized and multiplexed on PUSCH resources first. Specifically, LCHs are sorted according to their remaining delay budgets (RDBs) or delay bounds, starting with the LCH with the data with the lowest remaining delay budget or shortest delay bound, and arranged in ascending order. In essence, the remaining delay budget or delay bound is used as the main parameter of the LCP process, rather than the logical channel priority.

[0067] One advantage of this scheme is that during the LCP process, the "multiplexing priority" of the LCH is not static, just like the logical channel priority, which is a parameter associated with the LCH. Instead, the multiplexing priority changes depending on the time data of the LCH to be transmitted in the UE. During the LCP process, the lower the remaining delay budget, the higher the "multiplexing priority" of the data. In essence, the mechanism adapts the multiplexing priority depending on the remaining delay budget. Therefore, the multiplexing priority essentially reflects the urgency of the data. Different data packets (e.g., (multiple) radio link control (RLC) PDUs) of one LCH can have different associated residual delay budgets and therefore different multiplexing priorities. Therefore, during the LCP process, different data packets of the same LCH are processed with different multiplexing priorities. According to one implementation of this embodiment, each RLC SDU of the LCH is associated with a parameter representing the remaining delay budget.

[0068] According to one implementation of this embodiment, for the case where the data of multiple LCHs to be transmitted in the buffer have the same remaining delay budget, the UE / MAC uses logical channel priority. In this case, when allocating resources to different LCHs, that is, during the LCP process, the UE can give priority to data with higher LCH priority. In this implementation, the LCH priority is used as a second-level parameter for determining the multiplexing priority.

[0069] According to some alternative implementations of this embodiment, when data of multiple LCHs to be transmitted in the buffer have the same remaining delay budget, the UE determines which LCH to prioritize during the LCP process. As an alternative or supplement, for the case where data of multiple LCHs to be transmitted in the buffer have the same remaining delay budget, the UE may prioritize the LCH with a larger amount of data. The motivation for this implementation is maximization of data transmission.

[0070] According to one embodiment, a MAC control element ((multiple) MAC CEs) is configured with an upper limit delay, also referred to as a delay budget, for example. When multiplexing data in the MAC layer on scheduled uplink resources, the UE enforces the upper limit delay specified for the MAC CE during the LCP procedure. In particular, the UE treats the MAC CE as an LCH. As described in the previous embodiment, the remaining delay budget of the MAC CE is regarded as a criterion for determining the multiplexing priority. The delay budget of the MAC CE can be fixed in the standard or configured by a higher layer (such as a radio resource control (RRC) layer). According to one implementation of this embodiment, a default delay budget is assumed for the MAC CE during the LCP procedure.

[0071] According to one embodiment, the UE uses a different relative priority order when performing an LCP procedure for initial UL transmission on UL resources allocated for XR services than the relative priority order currently specified. According to one implementation of this embodiment, the UE / MAC prioritizes LCH data that is allowed to be multiplexed on UL resources allocated for XR services / data over MAC CE. That is, LCH has a higher multiplexing priority than MAC CE and is granted UL resources before MAC CE.

[0072] In one embodiment, the UE uses the LCH priority during LCP to determine the order and amount of resources allocated to each LCH. For the case where two LCHs have the same LCH priority, the UE / MAC uses the RDB of the data to determine the multiplexing priority, i.e. which data to put into the TB first. According to this embodiment, the UE uses the traditional LCP process for UL authorization, and in addition to the logical channel priority, it also uses the RDB of the data to determine the order in which the data of the LCH is multiplexed into the TB.

[0073] According to one embodiment, the grant configuration configured for UL transmission is specifically configured for XR data / service. A new information element (IE) is introduced that configures semi-persistent UL resources, such as CG-PUSCH resources, for XR services. Some parameters of this new IE may be similar to the traditional configuration grant configuration. In one example, new XR-specific parameters (e.g., new periodicity, jitter parameters, delay parameters, etc.) may be included in the XR-specific CG configuration IE. Figure 8 An example code snippet for a new IE 800 is provided that implements a configured grant configuration ("ConfiguredGrantConfig") in addition to configuring other aspects of the LCP process.

[0074] According to one embodiment, a newly introduced CG configuration (e.g., a CG configuration optimized for XR data / services) allocates multiple CG resource allocations within each CG period. According to one implementation of this embodiment, a new parameter within the CG configuration indicates the timing of additional CG resources within the CG period. In one example, the new parameter is a field indicating the maximum jitter expected for data mapped to the CG configuration. According to one example, the CG configuration allocates additional configuration authorization resources 'x' time slots before the CG resources and 'y' time slots after the CG resources, which time slots are determined according to well-known formulas given in traditional specifications.

[0075] After configuring uplink grants for grant type 1, when managing the MAC layer, the UE identifies the sequence of available uplink grants 1-N that appear sequentially in the symbol according to the following calculation:

[0076] (System Frame Number (SFN) × Number of slots per frame × Number of symbols per slot) + (Number of slots in a frame × Number of symbols per slot) + (Number of symbols in a slot) = (Time Reference SFN × Number of slots per frame × Number of symbols per slot + Time Domain Offset × Number of symbols per slot + S + N × Period) modulo (1024 × Number of slots per frame × Number of symbols per slot)

[0077] After configuring uplink grants for Grant Type 2, when managing the MAC layer, the UE identifies the sequence of available uplink grants 1-N that appear sequentially in a symbol according to the following calculation:

[0078] (SFN x number of slots per frame x number of symbols per slot) + (number of slots in a frame x number of symbols per slot) + number of symbols in a slot = (SFN start time × number of slots per frame × number of symbols per slot + slot start time ×Number of symbols per time slot+symbol start time )+N×cycle]modulo(1024×number of slots per frame×number of symbols per slot)

[0079] SFN start time 、slot start time , and symbol start time are, respectively, the SFN, timeslot, and symbol of the first transmission opportunity of the PUSCH, where the uplink grant is (re)initialized.

[0080] According to one implementation of this embodiment, 'x' and 'y' are configured within the CG Configuration IE and correspond to the minimum and maximum jitter, respectively. Additional CG resources are configured to cope with variations in packet arrival times due to jitter effects.

[0081] In another example, the new GG configuration introduced for XR traffic allocates additional CG resources / grants 'x' slots or ms after the CG opportunity, which is defined according to the traditional formula. The additional CG resources allocated 'x' slots / ms after the "traditional" CG resources solves the problem of late packet arrival.

[0082] According to one implementation of this embodiment, after the UE performs UL transmission on one of the CG resources, it deactivates / skips the remaining CG resources (if any) allocated in the same CG period. For example, if the UE has been allocated three CG resources in the CG period to handle early and late packet arrivals, and the UE sends an early arrival packet on the first CG resource of the 3 CG resources, such as a CG resource allocated 'x' slots / ms before the CG resource determined by the formula, the UE will not perform UL transmission on the remaining 2 CG resources. The UE can explicitly inform the gNB that it will not use the remaining CG resources in the CG period so that the gNB can allocate (multiple) resources to other UEs.

[0083] According to one embodiment, the LCH is configured as an LCH carrying XR services / data. The new field / IE in the IE "logicalchannelconfig" indicates whether the LCH carries data / services for XR applications. According to one implementation of this embodiment, the UE / MAC is only allowed to multiplex the data of the LCH configured as an LCH carrying XR services / data onto the UL resources allocated for the XR data / services. In one implementation, the UE is only allowed to multiplex the data of the LCH configured as an LCH carrying XR services / data onto the CG PUSCH resources configured for the XR data / services.

[0084] According to one implementation of this embodiment, in addition to allowing the UE to multiplex the data of the LCH configured for XR data / service, the UE is also allowed to multiplex the data of the LCH that is not configured for XR data / service. According to this implementation of this embodiment, a new LCH restriction is introduced. The LCH with the highest multiplexing priority (i.e., the LCH whose data is first multiplexed in the TB) determines whether only XR services or other services can be multiplexed in the TB. In one example, the UE is allowed to multiplex the data of the LCH configured for the XR service onto UL resources that are not specifically allocated / reserved for XR data / service.

[0085] According to one embodiment, the LCH / radio bearer is configured with a new field / IE that indicates whether the UE / MAC uses the residual delay budget (RDB) of the LCH's data to determine the order in which the LCH data is multiplexed on the UL resources during the LCP, such as the multiplexing priority. In one example, the field is a Boolean parameter that, if set to true, indicates that the RDB should be used to determine the multiplexing priority. If the field / IE is set to false or does not exist, the UE / MAC should use the logical channel priority in the traditional LCP process to determine the multiplexing order.

[0086] According to one aspect, the highest priority logical channel determines the type of priority mechanism used during LCP, such as RDB-based or priority-based. In addition, on the other hand, Grant indicates the type of priority mechanism to be used during the LCP process, and the UE only considers the LCH of the corresponding configured LCP.

[0087] According to one embodiment, a new IE / field is introduced in the MAC configuration, eg, MAC main configuration, which indicates whether the UE should use RDB or logical channel priority to determine the multiplexing order.

[0088] According to one embodiment, the DCI (UL DCI) that allocates UL resources for the initial transmission indicates within a field whether the MAC should use the RDB to use the new LCP mechanism to determine the order in which the LCH allocates resources, or whether the MAC should use the logical channel priority during the LCP process (as traditionally). In one example, the field is a 1-bit flag. In response to receiving the UL DCI, where the flag indicates that the RDB should be used as a parameter for determining the multiplexing priority, the UE / MAC only considers those LCHs that are allowed to multiplex data on the resources allocated for the XR service / data, and the UE / MAC performs the LCP process outlined in the previous embodiment, i.e., considering the RDB of the data of the LCH to determine the multiplexing order. In one example, the UE only considers those LCHs configured by the network for multiplexing order from the RDB to the MAC according to the currently proposed LCP process. In another example, the UE only considers those LCHs configured as XR LCH / bearers for multiplexing order from the RDB to the MAC according to the currently proposed LCP process. In another example, the UE may multiplex only the data of the LCHs configured with the same LCP multiplexing rule in the TB, for example, based on the RDB or based on the LCH priority.

[0089] According to one implementation of this embodiment, a 2-bit field is signaled within the DCI allocated UL resources for initial transmission. Four (4) different combinations are signaled within the new 2-bit field. In one example, the following combinations are signaled:

[0090] 00: Use normal / legacy LCP for all data types

[0091] 01: Authorized only for XR LCH and using RDB

[0092] 10: Authorized only for XR LCH, but using LCP

[0093] 11: Not authorized for use in XR LCH

[0094] According to one implementation of this embodiment, for the case where the data of multiple LCHs to be transmitted in the buffer have the same remaining delay budget, the UE / MAC uses logical channel priority. In this case, when allocating resources to different LCHs, that is, during the LCP process, the UE can give priority to data with higher LCH priority. In this implementation, the LCH priority is used as a second-level parameter for determining the multiplexing priority.

[0095] Fig. 9 An example of a block diagram 900 of a user device 902 according to aspects of the present disclosure is presented, which provides wireless communication with a network device by multiplexing delay-sensitive services (such as XR services) in an uplink signal. The user device 902 can be an example of a UE 104, as described herein. The user device 902 can support wireless communication with one or more base stations 102, UE 104, or any combination thereof. The user device 902 may include components for two-way communication, including components for sending and receiving communications (such as a communication manager 904, a processor 906, a memory 908, a receiver 910, a transmitter 912, and an I / O controller 914). These components can be electronically communicated or otherwise coupled (e.g., operationally, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus). The receiver 910 and the transmitter 912 can exist on the same chip and are collectively referred to as a transceiver 915.

[0096] The communication manager 904, the receiver 910, the transmitter 912, or various combinations thereof, or various components thereof may be examples of components for performing various aspects of the present disclosure described herein. For example, the communication manager 904, the processor 906, the receiver 910, the transmitter 912, or various combinations thereof, or components may support methods for performing one or more functions described herein. In one example, the processor 906 executes a dynamic RGB prioritization application that configures the communication manager 904 to perform an enhanced LCP process for prioritizing delay-sensitive data for allocation to uplink signals, or reverting to LCH prioritization for other services or data.

[0097] In some implementations, the communication manager 904, the receiver 910, the transmitter 912, or various combinations thereof, or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some implementations, the processor 906 and a memory 908 coupled to the processor 906 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 908 by the processor 906).

[0098] Additionally or alternatively, in some implementations, the communication manager 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be implemented in code executed by the processor 906 (e.g., as communication management software or firmware). If implemented in code executed by the processor 906, the functionality of the communication manager 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0099] In some implementations, the communication manager 904 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 910, the transmitter 912, or both. For example, the communication manager 904 may receive information from the receiver 910, send information to the transmitter 912, or combine with the receiver 910, the transmitter 912, or both to receive information, send information, or perform various other operations described herein. Although the communication manager 904 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communication manager 904 may be supported or performed by the processor 906, the memory 908, or any combination thereof. For example, the memory 908 may store code that may include instructions executable by the processor 906 to cause the user device 902 to perform various aspects of the present disclosure as described herein, or the processor 906 and the memory 908 may be configured to perform or support such operations.

[0100] The processor 906 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 906 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 906. The processor 906 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 908) so that the user device 902 is configured to perform various functions of the present disclosure.

[0101] The memory 908 may include a random access memory (RAM) and a read-only memory (ROM). The memory 908 may store computer-readable computer executable code, which includes instructions that, when executed by the processor 906, cause the user device 902 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 906, but may cause the computer / configure the computer to (e.g., when the code is compiled and executed) perform the functions described herein. In some implementations, the memory 908 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0102] The I / O controller 914 can manage input and output signals for the device 902. The I / O controller 914 can also manage peripheral devices that are not integrated into the user device 902. In some implementations, the I / O controller 914 can represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 914 can use an operating system, such as MS Or other known operating systems. In some implementations, I / O controller 914 can be implemented as part of a processor such as processor 906. In some implementations, a user can interact with user device 902 via I / O controller 914 or via hardware components controlled by I / O controller 915.

[0103] In some implementations, the user device 902 may include a single antenna 916. However, in some other implementations, the user device 902 may have more than one antenna 916, which may be capable of concurrently sending or receiving multiple wireless transmissions. The receiver 910 and the transmitter 912 may communicate bidirectionally via one or more antennas 916, wired or wireless links described herein. For example, the receiver 910 and the transmitter 912 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem for modulating packets, providing the modulated packets to one or more antennas 916 for transmission, and demodulating packets received from one or more antennas 916.

[0104] In one example, according to examples disclosed herein, the communication manager 904 can support wireless communication at a first device (e.g., user equipment 902). The communication manager 904 can be configured to or otherwise support communication with a network device (such as a base station 102 ( Figure 1 )) of wireless communication. The transceiver 915 includes at least one receiver 910 and at least one transmitter 912 that enable the user equipment 902 to communicate with the network device. The communication manager 904 is communicatively coupled to the transceiver 915. The processor 906 executes a dynamic RDB prioritization application 909 that configures the communication manager 904 to perform aspects of the present disclosure. In one or more embodiments, the communication manager 904 receives one or more control messages from the network device via the transceiver 915 on a downlink, the one or more control messages containing: (i) a logical channel configuration of more than one logical channel, including a priority value associated with each logical channel; and (ii) an uplink resource allocation grant. The communication manager 904 tracks the corresponding remaining delay budget of each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel in the more than one logical channels. The communication manager 904 determines the multiplexing order of the PDUs of more than one logical channel in ascending order based on the associated remaining delay budgets at the media access control layer, starting from the PDU with the smallest remaining delay budget. The communication manager 904 allocates resources allocated by the uplink grant to the logical channels according to the determined multiplexing order, starting from the logical channel with the PDU having the minimum remaining delay budget. The communication manager 904 generates an uplink signal by multiplexing the PDUs of more than one logical channel according to the allocated resources.

[0105] Fig.10An example of a block diagram 1000 of a network device 1002 is presented that implements wireless communications that support LCP procedures enhanced for delay-sensitive services (such as XR services) according to aspects of the present disclosure. The network device 1002 can be an example of a base station 102 or base node, as described herein. The network device 1002 can support communication with Figure 1 The network device 1002 may include components for bidirectional communication, including components for sending and receiving communications (such as a scheduler 1004, a processor 1006, a memory 1008, a receiver 1010, a transmitter 1012, and an I / O controller 1014). These components may be in electronic communication or otherwise coupled (e.g., operationally, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus). The receiver 1010 and the transmitter 1012 may be located on a single chip and are collectively referred to as a transceiver 1015.

[0106] The scheduler 1004, the receiver 1010, the transmitter 1012, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the scheduler 1004, the receiver 1010, the transmitter 1012, or various combinations thereof, or components thereof may support methods for performing one or more functions described herein.

[0107] In some implementations, the scheduler 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports components for performing the functions described in the present disclosure. In some implementations, the processor 1006 and a memory 1008 coupled to the processor 1006 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 1008 by the processor 1006). In one example, the processor 1006 executes a dynamic RGB prioritization application 1009 that configures the scheduler 1004 to perform an enhanced LCP process that schedules a UE 104 ( Figure 1 ) and other user equipment to prioritize delay-sensitive data for allocation to uplink signals, or to revert to LCH prioritization for other services or data.

[0108] Additionally or alternatively, in some implementations, the scheduler 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be implemented in code executed by the processor 1006 (e.g., as communication management software or firmware). If implemented in code executed by the processor 1006, the functions of the scheduler 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0109] In some implementations, the scheduler 1004 may be configured to perform various operations (e.g., receive, monitor, send) using or otherwise cooperating with the receiver 1010, the transmitter 1012, or both. For example, the scheduler 1004 may receive information from the receiver 1010, send information to the transmitter 1012, or combine with the receiver 1010, the transmitter 1012, or both to receive information, send information, or perform various other operations described herein. Although the scheduler 1004 is illustrated as a separate component, in some implementations, one or more functions described with reference to the scheduler 1004 may be supported or performed by the processor 1006, the memory 1008, or any combination thereof. For example, the memory 1008 may store code that may include instructions executable by the processor 1006 so that the network device 1002 configures it to perform various aspects of the present disclosure as described herein, or the processor 1006 and the memory 1008 may be configured to perform or support such operations.

[0110] Processor 1006 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, processor 1006 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into processor 1006. Processor 1006 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1008) to cause network device 1002 to perform various functions of the present disclosure.

[0111] Memory 1008 may include random access memory (RAM) and read-only memory (ROM). Memory 1008 may store computer-readable computer executable code, which includes instructions that, when executed by processor 1006, cause network device 1002 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 1006, but may cause a computer / configure a computer to (e.g., when compiled and executed) perform the functions described herein. In some implementations, memory 1008 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0112] I / O controller 1014 can manage input and output signals of network device 1002. I / O controller 1014 can also manage peripheral devices that are not integrated into network device 1002. In some implementations, I / O controller 1014 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 1014 can use an operating system, such as MS Or other known operating systems. In some implementations, I / O controller 1014 can be implemented as part of a processor such as processor 1006. In some implementations, a user can interact with network device 1002 via I / O controller 1014 or via hardware components controlled by I / O controller 1015.

[0113] In some implementations, the network device 1002 may include a single antenna 1016. However, in some other implementations, the network device 1002 may have more than one antenna 1016, which may be capable of concurrently sending or receiving multiple wireless transmissions. The receiver 1010 and the transmitter 1012 may communicate bidirectionally via one or more antennas 1016, wired or wireless links described herein. For example, the receiver 1010 and the transmitter 1012 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1016 for transmission, and demodulating packets received from one or more antennas 1016.

[0114] In one example, according to examples disclosed herein, scheduler 1004 can support wireless communication at a first network device (e.g., network device 1002). Network device 1002 includes a transceiver 1015 that includes: enabling network device 1002 to communicate with a UE 104 ( Figure 1) and at least one receiver 1010 and at least one transmitter 1012 for communicating with a user equipment such as a scheduler 1004. The scheduler 1004 is communicatively coupled to a transceiver 1015. According to aspects of the present disclosure, the scheduler 1004 sends one or more control messages to the user equipment via the transceiver 1015 on a downlink, the one or more control messages comprising: (i) a logical channel configuration of more than one logical channel, including a priority value associated with each logical channel; and (ii) an uplink resource allocation grant. The one or more control messages prompt the user equipment to track the corresponding remaining delay budget of each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel in the more than one logical channels. In addition, the one or more control messages prompt the user equipment to determine the multiplexing order of the PDUs of more than one logical channel in an ascending order based on the associated remaining delay budgets, starting from the PDU with the smallest remaining delay budget, at a media access control layer. In addition, the one or more control messages prompt the user equipment to allocate resources allocated by the uplink grant to the logical channels starting from the logical channels with the PDUs according to the determined multiplexing order, and the PDUs have the minimum remaining delay budget. In addition, the one or more control messages prompt the user equipment to receive an uplink signal from the user equipment via the transceiver 1015 on the media access control layer, the uplink signal comprising: PDUs of more than one logical channel multiplexed by the user equipment according to the allocated resources.

[0115] Fig.11 A flowchart of a method 1100 for supporting wireless communication between a user device and a network device according to aspects of the present disclosure is presented, the method enhancing an LCP process for delay-sensitive services or data (such as XR services). The operations of the method 1100 may be implemented by a user device or components thereof as described herein. For example, the operations of the method 1100 may be implemented by reference to Figures 1 to 9 The UE 114 described herein performs. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.

[0116] At 1105, method 1100 may include: receiving, on a downlink, one or more control messages from a network device via a transceiver of a user device, the one or more control messages comprising: (i) a logical channel configuration of more than one logical channel, including a priority value associated with each logical channel; and (ii) an uplink resource allocation grant. The operations of 1105 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1105 may be provided by reference to Figure 1 or Fig. 9 The device is used to perform the above.

[0117] At 1110, method 1100 may include tracking a respective remaining delay budget for each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel of more than one logical channel. The operations of 1110 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1110 may be described with reference to Figure 1 or Fig. 9 The device is used to perform the above.

[0118] At 1115, method 1100 may include: determining, at a media access control layer, a multiplexing order of PDUs of more than one logical channel in ascending order, starting from a PDU with a minimum residual delay budget, based on the associated residual delay budgets. The operations of 1115 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1115 may be described with reference to Figure 1 or Fig. 9 The device is used to perform the above.

[0119] At 1120, method 1100 may include allocating resources allocated by the uplink grant to the logical channel starting with the logical channel having the PDU according to the determined multiplexing order, the PDU having the smallest remaining delay budget. The operations of 1120 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1120 may be described with reference to Figure 1 or Fig. 9 The device is used to perform the above.

[0120] At 1125, method 1100 may include: generating an uplink signal by multiplexing PDUs of more than one logical channel according to the allocated resources. The operations of 1125 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1125 may be described by reference to Figure 1 or Fig. 9 The device is used to perform the above.

[0121] In one or more embodiments, the method 1100 includes: in response to determining that one or more uplink buffers contain delay-sensitive data, sending a buffer status report to a network device, the buffer status report indicating the ability to multiplex uplink signals. The method 1100 also includes: in response to receiving logical channel priority configuration information indicated by the buffer status report from the network device, generating an uplink signal by multiplexing the PDU.

[0122] In one or more specific embodiments, the method 1100 includes: determining that the one or more uplink buffers contain delay-sensitive data by identifying extended reality (XR) data within the one or more uplink buffers. In one or more specific embodiments, the method 1100 includes: in response to determining that the one or more uplink buffers no longer contain delay-sensitive data, reverting to allocating PDUs to the uplink signal according to a priority value associated with each of the more than one logical channels.

[0123] In one or more embodiments, the one or more control messages include: downlink control information (DCI). In one or more embodiments, the PDU is a radio link control (RLC) PDU. The method 1100 also includes: determining the residual delay budget of a particular RLC PDU by identifying a parameter of each RLC service data unit (SDU) of a logical channel associated with a corresponding residual delay budget.

[0124] In one or more embodiments, method 1100 includes: in response to receiving a configuration uplink grant for two or more uplink resources separated in time within a configuration grant period, sending a multiplexed uplink signal scheduled to occur next in one of the two or more uplink resources, so that the network device can reschedule any subsequent unused uplink resources in the two or more uplink resources.

[0125] Fig.12 A flowchart of a method 1200 for supporting wireless communication between a network device and a user device according to aspects of the present disclosure is presented, the method enhancing an LCP process for delay-sensitive services or data (such as XR services). The operations of the method 1200 may be implemented by a device or component thereof as described herein. For example, the operations of the method 1200 may be implemented by reference to Figures 1 to 10 The network device, base node, or base station 102 described herein performs. In some implementations, the network device may execute a set of instructions to control the functional elements of the network device to perform the described functions. Additionally or alternatively, the network device may use dedicated hardware to perform various aspects of the described functions.

[0126] At 1205, the method may include: sending, on a downlink, one or more control messages to a user equipment via a transceiver of a network device, the one or more control messages comprising: (i) a logical channel configuration of more than one logical channel, including a priority value associated with each logical channel; and (ii) an uplink resource allocation grant. The operations of 1205 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1205 may be provided by reference to Figure 1 or Fig.10 The device is used to perform the above.

[0127] One or more control messages prompt a user equipment to: (i) track a corresponding residual delay budget for each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel among more than one logical channels; (ii) determine, at a media access control layer, a multiplexing order of the PDUs of the more than one logical channels in ascending order based on the associated residual delay budgets, starting from the PDU with the smallest residual delay budget; and (iii) allocate resources allocated by an uplink grant to the logical channels based on the determined multiplexing order, starting from the logical channel with the PDU with the smallest residual delay budget.

[0128] At 1210, the method may include: receiving an uplink signal from a user equipment via a transceiver on a media access control layer, the uplink signal including: PDUs of more than one logical channel multiplexed by the user equipment according to the allocated resources. The operations of 1210 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1210 may be described with reference to Figure 1 or Fig.10 The device is used to perform the above.

[0129] In one or more embodiments, the method 1200 includes: receiving a buffer status report from a user equipment. The buffer status report indicates: an ability to multiplex uplink signals based on one or more uplink buffers of the user equipment containing delay sensitive data. The method 1200 also includes: sending one or more control messages in response to the buffer status report to configure the user equipment to multiplex the PDUs in the uplink signals.

[0130] In one or more specific embodiments, the delay-sensitive data includes extended reality (XR) data. In one or more specific embodiments, the method 1000 includes: in response to receiving a second buffer status report indicating that the one or more uplink buffers no longer contain delay-sensitive data, sending one or more second control messages, the second control messages configuring the user equipment to: resume allocating PDUs to the second uplink signal according to a priority value associated with each of the more than one logical channels.

[0131] In one or more embodiments, the one or more control messages include: downlink control information (DCI). In one or more embodiments, the PDU is a radio link control (RLC) PDU. The method 1200 also includes: determining the residual delay budget of a particular RLC PDU by identifying a parameter of each RLC service data unit (SDU) of a logical channel associated with a corresponding residual delay budget.

[0132] In one or more embodiments, the method 1200 includes: sending a configuration uplink grant for two or more uplink resources separated in time within a configuration grant period to a user equipment. The method 1200 includes: receiving a multiplexed uplink signal scheduled to occur next from the user equipment in one of the two or more uplink resources. The method 1200 includes: rescheduling any subsequent unused uplink resource in the two or more uplink resources.

[0133] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0134] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0135] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations.

[0136] Computer-readable media include both non-transient computer storage media and communication media, and communication media include any medium that facilitates the transfer of computer programs from one place to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, non-transient computer-readable media may include: RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to carry or store desired program code devices in the form of instructions or data structures and can be accessed by a general or special-purpose computer, or any other non-transient medium of a general or special-purpose processor.

[0137] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0138] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of" or "one or more of") represents an inclusive list, so that, for example, a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on." In addition, as used herein, including in the claims, a "set" may include one or more elements.

[0139] The descriptions described herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." The detailed description includes specific details to facilitate understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid confusing the concepts of the described examples.

[0140] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be clear to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment for wireless communication, the user equipment comprising: a transceiver comprising at least one transmitter and at least one receiver enabling the user equipment to communicate with a network device; as well as a communications manager communicatively coupled to the transceiver, and the manager: receiving, via the transceiver, one or more control messages from the network device on a downlink, the one or more control messages comprising: (i) a logical channel configuration for more than one logical channel, including a priority value associated with each logical channel; and (ii) uplink resource allocation grant; tracking a respective remaining delay budget for each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel of the more than one logical channels; determining, at a medium access control layer, a multiplexing order of the PDUs of the more than one logical channels in ascending order starting from the PDU with the smallest remaining delay budget according to the associated remaining delay budgets; allocating resources allocated by the uplink grant to the logical channel according to the determined multiplexing order, starting from the logical channel having the PDU having the minimum remaining delay budget; as well as An uplink signal is generated by multiplexing the PDUs of the more than one logical channels according to the allocated resources.

2. The user equipment according to claim 1, wherein the communication manager: In response to determining that the one or more uplink buffers contain delay sensitive data, sending a buffer status report to the network device, the buffer status report indicating a capability to multiplex uplink signals; and In response to receiving the logical channel priority configuration information indicated by the buffer status report from the network device, the uplink signal is generated by multiplexing the PDUs.

3. The user device of claim 2, wherein the communication manager determines that the one or more uplink buffers contain delay-sensitive data based on identifying extended reality (XR) data within the one or more uplink buffers.

4. A user equipment according to claim 2, wherein in response to determining that the one or more uplink buffers no longer contain delay-sensitive data, the communication manager reverts to allocating PDUs to uplink signals based on the priority value associated with each of the more than one logical channels.

5. The user equipment according to claim 1, wherein the one or more control messages include: Downlink Control Information (DCI).

6. The user equipment of claim 1 , wherein the PDU is a radio link control (RLC) PDU, and the communication manager determines the residual delay budget of a specific RLC PDU by identifying parameters of each RLC service data unit (SDU) of a logical channel associated with a corresponding residual delay budget.

7. The user equipment of claim 1, wherein the communication manager: In response to receiving a configuration uplink grant for two or more uplink resources separated in time within a configuration grant period, sending a multiplexed uplink signal scheduled to occur next in one of the two or more uplink resources, enabling the network device to reschedule any subsequent unused uplink resource in the two or more uplink resources.

8. A network device for wireless communication, the network device comprising: a transceiver comprising at least one transmitter and at least one receiver enabling the network device to communicate with a user device; as well as a scheduler communicatively coupled to the transceiver, and the scheduler: On a downlink, one or more control messages are sent to the user equipment via the transceiver, the one or more control messages comprising: (i) a logical channel configuration of more than one logical channel, including a priority value associated with each logical channel; and (ii) an uplink resource allocation grant, the control message being used to prompt the user equipment: tracking a respective remaining delay budget for each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel of the more than one logical channels; determining, at a medium access control layer, a multiplexing order of the PDUs of the more than one logical channels in ascending order starting from the PDU with the smallest remaining delay budget according to the associated remaining delay budgets; as well as allocating resources allocated by the uplink grant to the logical channel according to the determined multiplexing order, starting from the logical channel having the PDU having the minimum remaining delay budget; as well as An uplink signal is received from the user equipment via the transceiver on the medium access control layer, the uplink signal including the PDUs of the more than one logical channels multiplexed by the user equipment according to the allocated resources.

9. The network device according to claim 8, wherein the scheduler: receiving a buffer status report from the user equipment, the buffer status report indicating: a capability to multiplex uplink signals based on one or more uplink buffers of the user equipment containing delay sensitive data; and In response to the buffer status report, the one or more control messages are sent to configure the user equipment to multiplex the PDUs in the uplink signal.

10. The network device of claim 9, wherein the delay-sensitive data comprises: Extended reality (XR) data within the one or more uplink buffers.

11. A network device according to claim 9, wherein in response to receiving a second buffer status report indicating that the one or more uplink buffers no longer contain delay-sensitive data, the scheduler sends one or more second control messages, and the second control message configures the user equipment to: resume allocating PDUs to the second uplink signal based on the priority value associated with each of the more than one logical channels.

12. The network device of claim 8, wherein the scheduler sends downlink control information (DCI) within the one or more control messages.

13. The network device of claim 8, wherein the PDU is a radio link control (RLC) PDU, and the user equipment determines the residual delay budget of a specific RLC PDU by identifying a parameter of each RLC service data unit (SDU) of a logical channel associated with a corresponding residual delay budget.

14. The network device according to claim 8, wherein the scheduler: sending to the user equipment a configuration uplink grant of two or more uplink resources separated in time within a configuration grant period; receiving, in one uplink resource of the two or more uplink resources, a multiplexed uplink signal scheduled to occur next from the user equipment; and Any subsequently unused uplink resource of the two or more uplink resources is rescheduled.

15. A method for wireless communication by a user equipment, the method comprising: On a downlink, receiving one or more control messages from a network device via a transceiver of a user device, the one or more control messages comprising: (i) a logical channel configuration of more than one logical channel, including a priority value associated with each logical channel; and (ii) uplink resource allocation grant; tracking a respective remaining delay budget for each packet data unit (PDU) in one or more uplink buffers allocated to a corresponding logical channel of the more than one logical channels; determining, at a medium access control layer, a multiplexing order of the PDUs of the more than one logical channels in ascending order starting from the PDU with the smallest remaining delay budget according to the associated remaining delay budgets; allocating resources allocated by the uplink grant to the logical channel according to the determined multiplexing order, starting from the logical channel having the PDU having the minimum remaining delay budget; as well as An uplink signal is generated by multiplexing the PDUs of the more than one logical channels according to the allocated resources.

16. The method according to claim 15, further comprising: in response to determining that the one or more uplink buffers contain delay sensitive data, sending a buffer status report to the network device, the buffer status report indicating a capability to multiplex uplink signals; as well as In response to receiving the logical channel priority configuration information indicated by the buffer status report from the network device, the uplink signal is generated by multiplexing the PDUs.

17. The method of claim 16, wherein determining that the one or more uplink buffers contain delay sensitive data comprises: Extended reality (XR) data within the one or more uplink buffers is identified.

18. The method according to claim 16, further comprising: In response to determining that the one or more uplink buffers no longer contain delay sensitive data, reverting to allocating PDUs to uplink signals according to the priority value associated with each of the more than one logical channels.

19. The method of claim 15, wherein the PDU is a radio link control (RLC) PDU, the method further comprising: The residual delay budget for a particular RLC PDU is determined by identifying a parameter for each RLC service data unit (SDU) of a logical channel associated with a corresponding residual delay budget.

20. The method of claim 15, further comprising: In response to receiving a configuration uplink grant for two or more uplink resources separated in time within a configuration grant period, sending a multiplexed uplink signal scheduled to occur next in one of the two or more uplink resources, enabling the network device to reschedule any subsequent unused uplink resource in the two or more uplink resources.

Images