Scheduling delay sensitive data transmissions
By prioritizing urgent data in the logical channel buffer during the second allocation phase of the MAC PDU, the problem of ineffective processing of urgent data during logical channel prioritization in the prior art is solved, enabling timely transmission of lower priority data and improving system capacity.
Patent Information
- Application Number
- CN202480024339.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-04-07
- Filing Date
- 2024-04-02
- Publication Date
- 2025-11-11
AI Technical Summary
In existing technologies, the logical channel prioritization process fails to effectively handle urgent data, which may cause urgent data in lower priority logical channels to miss the delivery deadline, increasing the data loss rate.
During the resource allocation process, an urgent data factor is introduced. By prioritizing urgent data in the logical channel buffer during the second allocation phase of the MAC PDU, it is ensured that urgent data takes precedence over non-urgent data in higher-priority logical channels during resource allocation.
It effectively reduces the probability of urgent data from lower-priority logical channels missing delivery deadlines, lowers data loss rates, and improves system capacity utilization.
Smart Images

Figure CN120937481A_ABST
Abstract
Description
Cross-reference to related applications
[0001] This application claims the benefit and priority of U.S. Provisional Application Serial No. 63 / 457,917, entitled “Scheduling a Delay Sensitive Data Transmission,” filed April 7, 2023, the entire contents of which are expressly incorporated herein by reference. Technical Field
[0002] This disclosure relates generally to wireless communications, and more specifically to scheduling delay-sensitive data transmission. Background Technology
[0003] The 3rd Generation Partnership Project (3GPP) specifies a radio interface called Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), user equipment (UE), and more. Compared to previous generation cellular communication systems, the 5G NR architecture seeks to provide increased data rates, reduced latency, and / or increased capacity.
[0004] Wireless communication systems typically provide various telecommunications services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple users (such as Orthogonal Frequency Division Multiple Access (OFDMA)). Improvements in mobile broadband have continued the development of these wireless communication technologies. For example, Media Access Control (MAC) entities implement techniques to balance resource allocation between higher-priority and lower-priority logical channels. However, in addition to logical channel priority, the resource allocation of logical channels can also be associated with other characteristics. Summary of the Invention
[0005] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.
[0006] A logical channel prioritization process includes allocating resources to logical channels in descending order of priority to construct Media Access Control (MAC) Protocol Data Units (PDUs) for transmission from a User Equipment (UE) to a network entity. Each MAC PDU includes data from logical channel buffers. The UE allocates data from the logical channel buffers to the MAC PDUs in multiple phases. For example, in a first phase, the UE allocates data to the MAC PDUs based on a Prioritized Bit Rate (PBR) (sometimes also called a Guaranteed Bit Rate (GBR)) for each logical channel, starting with the logical channel with the highest priority and continuing data allocation in descending order of logical channel priority, while waiting for available resources for the MAC PDUs to receive data from each logical channel to continue data allocation. The PBR provides an upper limit on the amount of data the UE can allocate from the logical channel buffers to the MAC PDUs during the first allocation phase.
[0007] If, after the first allocation phase, the MAC PDU has remaining resources available for carrying additional data, the UE executes a second allocation phase that can fill the remaining / residual resources of the MAC PDU. For example, in the second phase, the UE again allocates data to the MAC PDU from the logical channel buffer in descending order of logical channel priority. Data allocation to the MAC PDU during the second phase can be done without considering the logical channel's PBR / token bucket size. Therefore, if the highest priority logical channel has a large amount of data to be processed in its buffer during the second phase, the highest priority logical channel can consume the MAC PDU's residual resources without giving other logical channels the opportunity to further reduce the amount of data to be processed in their respective buffers.
[0008] In some examples, a lower-priority logical channel may have urgent data in its buffer when a higher-priority logical channel does not have any urgent data in its corresponding buffer. However, based on the logical channel prioritization process described above, the UE will allocate non-urgent data from the higher-priority logical channel to the MAC PDU during the second allocation phase before allocating urgent data from the lower-priority logical channel. This increases the probability of missing the delivery deadline for urgent data in the lower-priority logical buffer. "Urgent data" refers to data with a remaining valid time less than or equal to a first threshold, or data with a queuing delay greater than or equal to a second threshold, etc.
[0009] The aspects of this disclosure address the aforementioned and other deficiencies by implementing a process for adding an urgent data factor to existing factors regarding the priority of logical channels. For example, if the MAC PDU includes residual resources after the first round of allocation, the UE allocates the residual resources to pending urgent data so that the transmission of urgent data in those logical channel buffers is prioritized over non-urgent data in higher-priority logical channel buffers. The allocation of residual resources may occur in descending order of priority of logical channels with pending urgent data in the buffers or in descending order of data loss rate of logical channels with pending urgent data in the buffers. "Data loss rate" refers to the amount of data dropped from logical channel buffers over time.
[0010] According to some aspects, the UE receives an uplink grant from the network entity for transmitting a MAC PDU. The MAC PDU includes a first allocation of logical channel priority with PBR data and a second allocation of remaining resources for residual data. The UE transmits a MAC PDU with the second allocation of remaining resources to the network entity, which prioritizes urgent data in the logical channel buffer over logical channel priority.
[0011] According to some aspects, as described above, the network entity sends an uplink grant for the MAC PDU to the UE. The network entity receives a second allocation of MAC PDUs with remaining resources from the UE, which prioritizes urgent data in the logical channel buffer over logical channel priority. Attached Figure Description
[0012] Figure 1 A diagram is shown of a wireless communication system comprising multiple user equipment (UEs) and network entities communicating through one or more cells.
[0013] Figure 2 This is a diagram illustrating logical channel prioritization at the Media Access Control (MAC) layer.
[0014] Figure 3 A signaling diagram is shown for MAC protocol data unit (PDU) transmission based on resource allocation for latency-sensitive data.
[0015] Figure 4 A diagram showing the MAC PDU data allocation based on logical channels with different logical channel priorities is presented.
[0016] Figure 5 A diagram showing the MAC PDU data allocation based on a set of logical channels with the same logical channel priority is presented.
[0017] Figure 6 This is a flowchart of the wireless communication method at the UE.
[0018] Figure 7 This is a flowchart of a wireless communication method at a network entity.
[0019] Figure 8 This is a diagram illustrating the hardware implementation of an example UE (apparatus).
[0020] Figure 9 It is a diagram illustrating the hardware implementation of one or more example network entities. Detailed Implementation
[0021] Figure 1 Figure 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, and others may include a decomposed base station architecture. The aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may co-locate with CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).
[0022] The operation and / or network design of base station 104 can be based on the aggregation characteristics of base station functions. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functions among two or more units located in various physical locations, as well as virtually distributing the functions of at least one unit, which allows for flexibility in network design. Various units in the decomposed base station architecture or decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication. For example, DU 108a, 108b, 108d communicate with RU 106a-106d via fronthaul link 160. Base stations 104d / 104e and / or RU 106a-106d communicate with UE 102a-102d and 102s via one or more radio frequency (RF) access links based on the Uu interface. In the example, multiple RUs 106 and / or base stations 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RUs 106 / base stations 104.
[0023] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission media, such as a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. BBU 112 includes DU 108d and CU 110d, which may also have a wired interface (e.g., midhaul link 162) configured between DU 108d and CU 110d to transmit or receive information / signals between DU 108d and CU 110d. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) may be configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and base station 104e in cell 190e via inter-cell communication beams 136-138 of RU 106a and base station 104e.
[0024] DU 108 is a logical unit of base station 104, configured to perform one or more base station functions. DU 108 can control the operation of one or more RU 106. For example, DU 108b controls the operation of multiple RU 106b-106c, while DU 108a controls the operation of a single RU 106a. DU 108d also controls the operation of a single RU 106d. One or more of the following can be hosted at DU 108: Radio Link Control (RLC) layer, Media Access Control (MAC) layer, or one or more high physical (PHY) layers, such as forward error correction (FEC) modules for encoding / decoding, scrambling, modulation / demodulation, etc. DU 108 can host such functions based on the functional partitioning of DU 108. DU 108 can similarly host one or more low PHY layers, wherein each low PHY layer or module can be implemented based on an interface for communicating with other layers and modules hosted at DU 108.
[0025] RU 106 can be configured to implement low-level functions. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or low-level PHY functions such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.
[0026] RU 106 can send or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first set of communication beams 132 of RU 106b and a second set of communication beams 134b of UE 102b. These two sets of communication beams may correspond to inter-cell communication beams or, in some examples, inter-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third set of communication beams 134a of UE 102b and a fourth set of communication beams 136 of RU 106a. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.
[0027] Any combination of RU 106, DU 108, and CU 110, or a single reference thereto, can correspond to base station 104. Therefore, base station 104 can include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to the core network. Base station 104 can relay communication between UE 102 and the core network (not shown). Base station 104 can be associated with macro cells of high-power cellular base stations and / or small cells of low-power cellular base stations. For example, cell 190e can correspond to a macro cell, while cells 190a-190d can correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell can be called a "heterogeneous network".
[0028] Transmissions from UE 102 to base station 104 / RU 106 are called uplink (UL) transmissions, while transmissions from base station 104 / RU 106 to UE 102 are called downlink (DL) transmissions. Uplink transmissions can also be called reverse link transmissions, and downlink transmissions can also be called forward link transmissions. For example, RU 106d uses the antenna of base station 104d in cell 190d to send downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and base station 104d / RU 106d.
[0029] The communication link between UE 102 and base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and base station 104 / RU 106 can utilize a per-carrier Y MHz spectral bandwidth (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) allocated in carrier aggregation up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. Carriers can be adjacent to each other along the spectrum or can be non-adjacent. In the example, uplink and downlink carriers can be allocated asymmetrically, with more or fewer carriers allocated for the uplink or downlink. Component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be associated with the primary cell (PCell), and the secondary component carrier can be associated with the secondary cell (SCell).
[0030] Some UEs, such as UEs 102a and 102s, can perform device-to-device (D2D) communication via sidelinks. For example, sidelink communication / D2D links utilize the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems, such as Wi-Fi, Bluetooth, LTE, and NR systems.
[0031] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc., based on the different frequencies / wavelengths associated with it. Fifth-generation (5G) NR is generally associated with two operating frequency bands (FRs) called Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 ranges from 410 MHz to 7.125 GHz, and FR2 ranges from 24.25 GHz to 71.0 GHz, which includes FR2-1 (24.25 GHz to 52.6 GHz) and FR2-2 (52.6 GHz to 71.0 GHz). Although a portion of FR1 is actually greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. In contrast, FR2 is often referred to as the "millimeter wave" (mmW) band. FR2 is different from the "extremely high frequency" (EHF) band, but is an approximate subset of it, the EHF band which ranges from 30 GHz to 300 GHz, and is sometimes also referred to as the "millimeter wave" band. The frequencies between FR1 and FR2 are generally referred to as the "mid-band" frequencies. The operating frequency band of the mid-band can be referred to as Frequency Range 3 (FR3), ranging from 7.125 GHz to 24.25 GHz. The frequency bands within FR3 can include the characteristics of FR1 and / or FR2. Therefore, the characteristics of FR1 and / or FR2 can be extended to the mid-band frequencies. Higher operating frequency bands have been identified to extend 5G NR communication above 52.6 GHz, which is associated with the upper limit of FR2. Three of these higher operating frequency bands are FR2-2 (ranging from 52.6 GHz to 71.0 GHz), FR4 (ranging from 71.0 GHz to 114.25 GHz), and FR5 (ranging from 114.25 GHz to 300 GHz). The upper limit of FR5 corresponds to the upper limit of the EHF band. Therefore, unless otherwise expressly stated herein, the term "below 6 GHz" may refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include mid-band frequencies. Furthermore, unless otherwise expressly stated herein, the term "millimeter wave" or mmW refers to frequencies that may include mid-band frequencies, frequencies within FR2-1, FR4, FR2-2, and / or FR5, or frequencies within the EHF band.
[0032] UE 102 and base station 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b based on a first set of communication beams 132 in one or more transmit directions of RU 106b. UE 102b may receive downlink beamforming signals from RU 106b based on a second set of communication beams 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b based on a second set of communication beams 134b in one or more transmit directions of UE 102b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b.
[0033] UE 102b can perform beamforming to determine the optimal reception and transmission directions for the beamformed signal. The transmission and reception directions of UE 102b and base stations 104 / RU 106 can be the same or different. In a further example, the beamformed signal can be transmitted between a first base station / RU 106a and a second base station 104e. For example, base station 104e of cell 190e can transmit the beamformed signal to RU 106a based on communication beam 138 in one or more transmission directions of base station 104e. RU 106a can receive the beamformed signal from base station 104e of cell 190e based on RU communication beam 136 in one or more reception directions of RU 106a. In a further example, base station 104e transmits a downlink beamformed signal to UE 102e based on communication beam 138 in one or more transmission directions of base station 104e. UE 102e receives downlink beamforming signals from base station 104e based on UE communication beam 130 in one or more receiving directions of UE 102e. UE 102e can also transmit uplink beamforming signals to base station 104e based on UE communication beam 130 in one or more transmitting directions of UE 102e, so that base station 104e can receive uplink beamforming signals from UE 102e in one or more receiving directions of base station 104e.
[0034] Base station 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to base station 104 or at least one element of base station 104, such as RU 106, DU 108 and / or CU 110. Base station 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device or other related terms. Base station 104 or the entity at base station 104 may be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station with RU 106d and BBU 112 including DU 108d and CU 110d, or may be implemented as a decomposed base station including one or more RU 106, DU 108 and / or CU 110. An aggregated or decomposed set of base stations can be referred to as a Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In this case, base station 104e can be the primary node, and base station / RU 106a can be the secondary node. In other examples, UE 102b operates in DC with DU 108a and DU 108b. In this case, DU 108b can be the primary node, and DU 108a can be the secondary node.
[0035] Still referencing Figure 1 In some respects, any of the UEs in UE 102 may include an emergency data prioritization component 140, which is configured to: receive from a network entity an uplink grant for transmitting a Media Access Control (MAC) Protocol Data Unit (PDU), the MAC PDU including a first allocation of logical channel priority with priority bit rate (PBR) data and a second allocation of remaining resources for residual data; and transmit to the network entity a MAC PDU with the second allocation of remaining resources, the second allocation prioritizing emergency data in the logical channel buffer over the logical channel priority.
[0036] In some respects, any of the base stations 104 or the network entity of the base station 104 may include a resource allocation component 150 configured to: send a first uplink grant to the UE for a MAC PDU, the MAC PDU including a first allocation of logical channel priority with PBR data and a second allocation of remaining resources for residual data; and receive from the UE a MAC PDU with a second allocation of remaining resources, the second allocation prioritizing urgent data in the logical channel buffer over logical channel priority.
[0037] therefore, Figure 1 A wireless communication system that can be implemented in conjunction with one or more other figures described herein is described. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.
[0038] Figure 2 Figure 200 illustrates logical channel prioritization at the MAC layer. Data transmission can be based on multiple logical channels 210-213 carrying data via multiple MAC PDUs. If the amount of data in the buffers of logical channels 210-213 exceeds the transmission capacity of MAC PDU 216, then the data in the logical channel buffers will not be suitable (e.g., not suitable at all) within a single MAC PDU 216. Therefore, the scheduling entity can determine which logical channel data should be provided to MAC PDU 216 for transmission, and which other logical channel data can be reserved in the buffers of logical channels 210-213 for future transmission at different MAC PDU transmission times.
[0039] The UE generates MAC PDU 216 according to a predefined protocol that allows the UE to meet the Quality of Service (QoS) for each configured radio bearer. The UE determines the amount of data to be incorporated into the current MAC PDU 216 for each logical channel 210-213 based on the uplink resource grants signaled to the UE on the Physical Downlink Control Channel (PDCCH). The UE can also allocate resources for the MAC Control Elements (MAC-CEs) within the MAC PDU 216. The UE performs a logical channel prioritization process for each MAC PDU transmission. "Logical channel prioritization" refers to incorporating data from different logical channels 210-213 into the MAC PDU 216 based on the priority values of those channels.
[0040] If MAC resources are insufficient to accommodate logical channel data from all logical channel buffers, the UE allocates MAC resources based on the priority level of each logical channel 210-213. For example, Radio Resource Control (RRC) parameters indicate the priority level of each logical channel 210-213, where priority 0 is the highest priority, priority 1 is the second highest priority, and so on. Figure 200 includes four logical channels 210-213, which correspond to logical channel 0 210 with priority 0, logical channel 1 211 with priority 1, logical channel 2 212 with priority 2, and logical channel 3 213 with priority 3, respectively. Each logical channel 210-213 is associated with a logical channel buffer, which contains data waiting to be transmitted in MAC PDU 216.
[0041] In a first implementation of MAC PDU 216b, the UE incorporates logical channel data into MAC PDU 216b based on the descending priority order of logical channels 210-213, starting from priority 0 until all available MAC PDU resources are allocated. For example, MAC PDU 216b may hold data from logical channel buffers of logical channels 0 210, 1 211, and 2 212, but there may not be enough remaining resources to accommodate data from logical channel 3 213. Therefore, data from logical channel 3 213 may remain in its buffer until a future MAC PDU has available space to transmit data from logical channel 3 213. If no further data flows into the buffers of higher priority logical channels 0 210, 1 211, and 2 212, the data from logical channel 3 213 may be incorporated into the next MAC PDU transmission.
[0042] While strict logical channel prioritization may be sufficient in many cases, data held in the buffer of logical channel 3 213 may experience "starvation" if data continues to flow into higher-priority logical channels 0 210, 1 211, and 2 212 before each MAC PDU transmission instance. That is, data in logical channel 3 213 is repeatedly passed to be incorporated into MAC PDU transmissions to benefit higher-priority bearers. "Starvation" refers to lower-priority data that cannot be transmitted over an extended period because higher-priority data repeatedly consumes available MAC PDU transmission resources, preventing lower-priority data from being incorporated into subsequent versions of MAC PDU 216b for transmission.
[0043] To avoid starvation while still serving logical channels 210-213 based on priority levels, a second implementation of MAC PDU 216a uses a PBR 215 (e.g., configured via RRC) to set the data rate for higher-priority logical channels. This data rate limits the resources allocated to higher-priority logical channels before resources begin to be allocated to lower-priority logical channels. This technique reduces starvation for lower-priority data even as high-priority data continues to flow into the logical channel buffers of higher-priority logical channels. Therefore, this implementation uses a two-stage approach to allocate data from multiple logical channels. Each logical channel 210-213 can be configured with an independent PBR 215. For example, the PBR 215a for logical channel 0 210 with priority 0 can be greater than the PBR 215b for logical channel 1 211 with priority 1. In another example, the PBR 215b for logical channel 1 211 with priority 1 is equal to the PBR 215c for logical channel 2 212 with priority 2. Lower priority logical channels (such as logical channel 3 213) typically have PBR 215d that is less than or equal to that of higher priority logical channels (such as logical channels 0 210, 1 211, 2 212) in PBR 215a-215c.
[0044] In a second implementation of MAC PDU 216a, the UE serves each logical channel 210-213 in descending order of priority, taking into account both the PBR 215 and the priority value of each logical channel 210-213. The amount of data from each logical channel 210-213 included in MAC PDU 216a is initially limited based on the PBR 215 of each logical channel 210-213. If all logical channels 0 210, 1 211, 2 212, 3 213 have been served according to their respective PBR 215, then each logical channel 0 210, 1 211, 2 212, 3 213 can be served again in descending order of priority until there is no remaining data in the buffer of logical channels 210-213 or until all available MAC PDU resources are exhausted (as shown for MAC PDU 216a), whichever condition is satisfied first.
[0045] The RRC parameters can control the scheduling of uplink data from each logical channel 210-213 by setting parameters of PBR 215, setting the bucket size duration (BSD) of the data transmission token, and / or indicating that an increased priority value corresponds to a decreased priority level. The data transmission token and token bucket algorithm prioritizes transmissions on various logical channels, as further described below. The UE can maintain a variable token bucket size (Bj) for each logical channel j. When the corresponding logical channel is established, the token bucket size (Bj) is initialized to zero, and for each TTI, the token bucket size increases by the product of PBR × TTI duration, where PBR 215 corresponds to logical channel j. The value of Bj cannot exceed the token bucket size (e.g., more tokens than the bucket can hold), and is therefore limited by the token bucket size for each logical channel j. The bucket size for logical channels 210-213 is equal to PBR × BSD, where PBR and BSD are configured based on upper-layer parameters.
[0046] The MAC-CE included in MAC PDU 216 can have a higher priority than any logical channel in logical channels 210-213 because the MAC-CE controls the operation of the MAC entity. Therefore, when the UE generates MAC PDU 216, the MAC-CE can be included in MAC PDU 216 (not shown) first, allowing the UE to allocate the remaining space in MAC PDU 216 to data from the logical channel buffers of logical channels 210-213. An exception could be when the UE sends a first RRC message to the target cell during the handover process. In such cases, the MAC-CE (such as a Channel Buffer State Report (BSR)) can have a lower priority than a Signaling Radio Bearer (SRB), allowing the handover process to be completed earlier rather than later. Otherwise, due to delayed signaling, data transmission interruption time could be prolonged, and the probability of handover failure could increase.
[0047] Even in the example where a higher-priority logical channel is configured with PBR 215, lower-priority channels / data may still experience starvation if the higher-priority channel is associated with a large PBR 215 / mass of data that consumes available MAC PDU resources before all logical channels 210-213 have received allocations. Therefore, in the third implementation of MAC PDU 216, data from logical channels 210-213 can be incorporated into MAC PDU 216 based on a technique for balancing the starvation of PBR 215 with that of low-priority data.
[0048] In the example, priority 3 data for logical channel 3 213 can be included in MAC PDU 216 even if higher priority logical channels (e.g., 210-212) have data in the buffer. A third implementation of MAC PDU 216 can be based on the timing duration / limit of logical channels 210-213 according to their priorities. Each logical channel 210-213 can be associated with a countdown timer such that the timer is decremented by 1 whenever logical channel 210-213 transmits an amount of data equal to the PBR 215 of logical channel 210-213. If the countdown timer becomes negative, the higher priority logical channel yields its opportunity to transmit data in the upcoming MAC PDU to a lower priority logical channel. Therefore, the countdown timer prevents higher priority logical channels from monopolizing MAC PDU 216, even if the higher priority logical channel has data to transmit (e.g., with a large PBR). The countdown timer can be configured based on the RRC parameter of bucketSizeDuration. Figure 2 This describes how logical channel data is incorporated into the MAC PDU 216. Figure 3 This demonstrates how to grant resources to a UE for MAC PDU transmission.
[0049] Figure 3 Signaling diagram 300 is shown based on MAC PDU transmissions for resource allocation of delay-sensitive data. System capacity, such as that for extended reality (XR) systems, can be a performance indicator referring to the maximum number of UEs per cell, where at least Y% of all data streams from the UEs meet the Packet Error Rate (PER) and Packet Delay Budget (PDB). That is, the UEs transmit (i.e., do not drop) more than a certain percentage of packets over the air interface. An example percentage could be Y = 90%-95%. However, other values for Y can also be considered.
[0050] When UE 102 receives an uplink grant from network entity 104, UE 102 determines the size of the MAC PDU associated with that uplink grant. Based on the size of the MAC PDU, UE 102 allocates resources (e.g., in bytes) to one or more logical channels according to the bucket size of the "token bucket" of one or more logical channels and the priority level of one or more logical channels. The token bucket can be represented as Bj, which refers to the bucket size of logical channel j. For each logical channel j, the MAC entity increments Bj by the product of PBR × T before each instance of the Logical Channel Prioritization (LCP) process, where T corresponds to the time elapsed since the last increment of Bj. If the value of Bj is greater than the bucket size (e.g., greater than PBR × BSD), then the value of Bj is set to the bucket size. The maximum size of the token bucket is equal to PBR × BSD.
[0051] If the value of Bj for a logical channel includes at least a number of bytes equal to the size of the RLC PDU, then UE 102 allocates a certain number of bytes to transmit Radio Link Control (RLC) Service Data Units (SDUs) from the logical channel. Therefore, the number of bytes that UE 102 can allocate for a logical channel is based on Bj (e.g., the size of the token bucket). In the example, the MAC entity allocates resources to a logical channel for transmission in descending order of priority, based on logical channels with Bj > 0 selected for uplink grants. If the PBR of a logical channel is set to infinity, the MAC entity allocates resources for all data available for transmission on that logical channel before allocating resources for the PBRs of lower-priority logical channels. The MAC entity decrements Bj by the total size of the MAC SDU for logical channel j. If any resources remain for allocation, logical channels can be served in descending order of priority, regardless of the value of Bj, until either the data on the logical channel is exhausted or the uplink grant is exhausted, whichever comes first. Logical channels configured with equal priorities can be served equally.
[0052] The LCP procedure includes allocating resources (e.g., a certain number of bytes to be sent to network entity 104) to logical channels in descending order of priority for MAC PDU transmission. UE 102 may perform resource allocation in two phases, as previously described with reference to MAC PDU 216a.
[0053] However, if the highest priority logical channel has a large amount of pending data in its buffer during the second allocation phase, it can consume the remaining / residual resources of the MAC PDU without giving other / lower priority logical channels the opportunity to further reduce the amount of pending data in their respective buffers. In some examples, lower priority logical channels may have pending urgent data in their buffers when higher priority logical channels do not have any urgent data in their buffers. However, the UE may allocate non-urgent data for higher priority logical channels during the second allocation phase before allocating urgent data for lower priority logical channels, which can increase the probability of missing the delivery deadline for urgent data in the lower priority logical channels' buffers and potentially lead to a high data loss rate that does not meet system capacity protocols.
[0054] UE 102 can implement a technique such as that shown in Figure 300, which adds urgent data priority to the LCP procedure. "Urgent data," also known as "delay-sensitive data," refers to data with a remaining valid time less than or equal to a first threshold and / or data with a queuing delay greater than or equal to a second threshold. An example of the first threshold for the remaining valid time could be 20 ms. An example of the second threshold for the queuing delay could be used to apply control, gesture information, etc. For example, control information could have a larger threshold than data in different logical channels, which could result in control information having a higher priority than data with the same remaining valid time. UE 102 can send UE capability information (306) to network entity 104, indicating the UE capability for prioritizing delay-sensitive data for MAC PDU transmission.
[0055] Network entity 104 (e.g., based on UE capabilities) sends configuration 308 to UE 102 for prioritizing delay-sensitive data in MAC PDU transmissions. This configuration may indicate parameters such as the prioritizedBitRate for the PBR of a logical channel, the bucketSizeDuration for the BSD of a logical channel, and threshold criteria for determining which data in the buffer is urgent. This configuration may include an indication to enable or disable the UE from prioritizing delay-sensitive data. Network entity 104 may send this configuration 308 to UE 102 in an RRC message such as an RRC reconfiguration message, an RRC establishment message, an RRC re-establishment message, or an RRC recovery message. In a further example, network entity 104 may send this configuration 308 to the UE in a system information message. In other examples, the first threshold and / or the second threshold are predefined values.
[0056] Network entity 104 sends an uplink grant (310) to UE 102 for UE 102 to determine the size of the MAC PDU. For example, network entity 104 sends a first uplink grant (310a) to UE 102 for UE 102 to allocate resources (314) to the logical channel. UE 102 may receive the uplink grant (310) from network entity 104 in a downlink control information (DCI) on the PDCCH, in a random access response (RAR) message during a random access procedure, or in an RRC message such as an RRCReconfiguration message or an RRCRelease message. In a further example, the uplink grant is stored in the memory of UE 102, and UE 102 retrieves the uplink grant from this memory periodically according to a schedule configured by network entity 104.
[0057] UE 102 allocates 314 MAC PDU resources to logical channels in multiple phases. For example, as described above, UE 102 allocates 314 resources to logical channels in the first phase with a bucket size > 0, following the descending priority order of logical channels, and then reduces the bucket size by the amount of resources allocated to the logical channels (e.g., by the number of bits to be transmitted). For the LCP procedure of adding urgent data priority, UE 102 performs an intermediate allocation phase between the first and second phases previously described. During the intermediate phase, UE 102 allocates 314 resources based on a technique that prioritizes urgent data in lower-priority logical channel buffers over non-urgent data in higher-priority logical channel buffers. The intermediate allocation phase is described below regarding... Figures 4 to 5 To describe in more detail.
[0058] If, after the intermediate allocation phase (which can be considered the second allocation phase in the LCP process with added emergency data priority), the MAC PDU still has remaining resources available for carrying additional data, then UE 102 executes another allocation phase / third allocation phase to allocate the remaining resources 314 to logical channels in descending priority order (e.g., regardless of the value of Bj) until data for each logical channel is exhausted or remaining resources are exhausted, whichever comes first. The third allocation phase of the LCP process with added emergency data priority is similar to the second allocation phase of the LCP process described above with reference to MAC PDU 216a, which does not include the intermediate phase with emergency data priority.
[0059] UE 102 sends 316 MACPDUs to network entity 104 based on resource allocation 314 to logical channels. The MAC PDU may include delay information and / or data volume information indicating the amount of urgent data currently pending in the logical channel buffer. If the remaining valid time of data in the logical channel buffer is less than or equal to a first threshold (e.g., 20 ms), UE 102 prioritizes that data for transmission in the MAC PDU. Similarly, if the queuing delay for the same or different data currently pending in the logical channel buffer is greater than or equal to a second threshold, UE 102 also prioritizes that data for transmission in the MAC PDU. In some examples, the second threshold corresponds to the time between the delay information of UE 102 transmitting data and the time between UE 102 transmitting the data. UE 102 may determine / calculate data volume information for channels, channel groups, and / or PDU sets (i.e., sets of data). Data within the same PDU set has the same delay budget and the same delivery deadline. "Data volume" refers to the total size of the data in the buffers of all logical channels that will be included in the MAC PDU transmission while waiting for available space in the MAC PDU, based on the LCP process of adding urgent data priority.
[0060] Network entity 104 can process the information included in the MAC PDU to allocate 318 resources to UE 102. For example, network entity 104 sends 310b a second uplink grant to UE 102, which grants UE 102 sufficient resources to send a second MAC PDU (not shown), which is large enough to carry all urgent data currently pending processing in the logical channel buffers of all logical channels, as indicated by the first MAC PDU 316. Network entity 104 also maintains and updates the token buckets of the logical channels in a manner similar to that of UE 102. The size of the second MAC PDU may correspond to the sum of the current token bucket sizes of all logical channels plus the sum of the differences between the current token bucket size of the logical channel and the amount of data in the logical channel. That is, the size of the second MAC PDU may be equal to (or greater than) the sum of the data associated with the first allocation phase and the intermediate allocation phase. Figure 3 The MAC PDU transmission based on the LCP procedure with urgent data priority is described. Figures 4 to 5 The data allocation within a MAC PDU is shown according to an LCP process with emergency data priority.
[0061] Figures 4 to 5Figures 400-500 show the data allocation from the logical channel buffers (410-412, 510-512b) of logical channels to MAC PDUs 416 / 516 414a-414b / 514a-514b. (Reference) Figure 4 Figure 400 illustrates three logical channel buffers for three logical channels 410-412 with different priorities. Specifically, Figure 400 shows a high-priority logical channel 410 with priority 0, a medium-priority logical channel 411 with priority 1, and a low-priority logical channel 412 with priority 2. Logical channels 410-412 are associated with corresponding PBRs 415, wherein the first PBR 415a of the high-priority logical channel 410 is greater than the second PBR 415b of the medium-priority logical channel 411 and the third PBR 415c of the low-priority logical channel 412.
[0062] In the first allocation phase 414a, the UE allocates data from the logical channel buffer to the MAC PDU 416 according to the PBR 415 in descending order of priority of logical channels 410-412. Therefore, the first allocation phase 414a begins with the first PBR 415a of the high-priority logical channel 410, where the UE allocates data packets 1, 2, and 3 to the MAC PDU 416. After satisfying the first PBR 415a, the UE allocates data packets 4 and 5 to the MAC PDU 416 according to the second PBR 415b of the medium-priority logical channel 411. To conclude the first allocation phase 414a, the UE allocates data packets 6 and 7 to the MAC PDU 416 according to the third PBR 415c of the low-priority logical channel 412. The UE allocates data packets from the logical channel buffer in the first allocation phase 414a regardless of whether the data packets correspond to urgent data 420 or non-urgent data 422.
[0063] In the second allocation phase 414b (also referred to herein as the intermediate allocation phase of the LCP procedure for adding urgent data priority), if there are remaining resources in the MAC PDU 416 to carry additional data after the first allocation phase 414a, the UE can allocate the remaining resources to the urgent data 420 still pending in the logical channel buffers of logical channels 410-412 in descending order of priority (e.g., regardless of token bucket size). Therefore, the second allocation phase 414b begins with the urgent data 420 of the medium-priority logical channel 411, because the high-priority logical channel 410 does not have any remaining urgent data 420 in its logical channel buffer after the first allocation phase 414a. Following the descending priority order, the medium-priority logical channel 411 has one data packet (i.e., data packet 8) of remaining urgent data 420 in its logical channel buffer during the second allocation phase 414b. Therefore, UE 102 allocates data packet 8 to MAC PDU 416 and leaves data packet 13 in the buffer for processing, as data packet 13 is non-urgent data 422. To conclude the second allocation phase 414b, the UE allocates urgent data 420 data packet 9 from the low-priority logical channel 412 to MAC PDU 416, because data packet 9 is the next head-of-line data packet to be allocated from the logical channel buffer. Although the low-priority logical channel 412 has another urgent data packet (i.e., data packet 10) in the buffer, MAC PDU 416 has no available space to carry another urgent data packet, and therefore, data packet 10 is not included in MAC PDU 416 during the second allocation phase 414b.
[0064] In an alternative implementation (not shown), if the MAC PDU 416 is large enough to carry all 13 data packets shown in Figure 400 in the logical channel buffers of the three different logical channels 410-412, then data packet 10 (which is urgent data 420) will be included in the MAC PDU 416 during the second allocation phase 414b. The LCP procedure then proceeds to the third allocation phase (not shown), where the UE allocates the remaining non-urgent data 422 in the logical channel buffers, such as in descending order of priority of logical channels 410-412. That is, the UE allocates data packets 11 and 12 from the high-priority logical channel 410 to the MAC PDU 416, followed by data packet 13 from the medium-priority logical channel 411.
[0065] The UE can also transmit MAC-CE (not shown) in MAC PDU 416 / 516. The UE can prioritize the transmission of emergency data 420 over non-emergency MAC-CE. For example, the UE prioritizes emergency data 420 over non-emergency MAC-CE for at least one of the following: (enhanced) beam failure recovery (BFR), authorization confirmation for (sidelink / multi-entry) configuration, listen-before-speak (LBT) failure, timing advance report, sidelink / extended BSR, (enhanced) single-entry / multi-entry power headroom report (PHR), location measurement gap activation / deactivation request, desired number of protection symbols, timing request, (extended) preemptive BSR, IAB-Mobile Terminal (MT) recommended beam indication, desired IAB-MT power spectral density (PSD) range, desired downlink transmit (Tx) power adjustment, recommended bit rate query, or padding BSR. In some examples, the UE prioritizes the transmission of data volume information over the transmission of emergency data 420. In other words, the transmission of delayed information has a higher priority than the transmission of emergency data 420.
[0066] refer to Figure 5 Figure 500 shows three logical channel buffers for three logical channels 510-512b, where two of the logical channels are low-priority logical channels 512a-512b with the same priority level. The high-priority logical channel 510 with priority 0 has a first PBR 415a, the first low-priority logical channel 512a with priority 2 has a second PBR 415c, and the second low-priority logical channel 512b with priority 2 also has a low-priority PBR 515c similar to the second PBR 415c.
[0067] In the first allocation phase 514a, the UE, with regard to Figure 4 In a similar manner, data is allocated from the logical channel buffer to the MAC PDU 516 according to the decreasing priority order of logical channels 510-512b, based on PBRs 415a, 415c, and 515c. The first allocation phase 514a is independent of whether the data being allocated to the MAC PDU 516 is urgent data 420 or non-urgent data 422.
[0068] When logical channels (such as two low-priority logical channels 512a-512b) have the same logical channel priority, the UE may consider other criteria to determine which logical channel among logical channels 512a-512b should be allocated resources first during the second allocation phase 514b. For example, if two logical channels have the same priority level and both logical channels have remaining urgent data 420 in the buffer during the second allocation phase 514b, the UE may first allocate resources to the logical channel 512a-512b with the shortest remaining valid time for the line-start data. Therefore, if data packet 8 (i.e., the line-start data packet of the first low-priority logical channel 512a during the second allocation phase 514b) has a shorter remaining valid time than data packet 10 (i.e., the line-start data packet of the second low-priority logical channel 512b during the second allocation phase 514b), the UE will prioritize the urgent data 420 of the first low-priority logical channel 512a over the urgent data 420 of the second low-priority logical channel 512b.
[0069] In a further example, the UE allocates resources to logical channels 512a-512b that have a larger amount of urgent data 420 remaining in the buffer. In Figure 500, the first low-priority logical channel 512a has a larger amount of urgent data 420 (i.e., two data packets) in the buffer during the second allocation phase 514b than the second low-priority logical channel 512b (i.e., one data packet). Therefore, the UE can prioritize resource allocation for the first low-priority logical channel 512a over the second low-priority logical channel 512b. Conversely, in another example, the UE allocates resources to logical channels 512a-512b that have a smaller amount of urgent data 420 remaining in the buffer.
[0070] In other examples, the UE implements a round-robin method for resource allocation. For instance, if the UE allocates N bytes to the first low-priority logical channel 512a, then the UE also allocates N bytes to the second low-priority logical channel 512b, and so on. The techniques described above for the logical channels 512a-512b of the same priority in Figure 500 can also be applied to the logical channels 410-412 of different priorities described in Figure 400.
[0071] Referring to Figures 400-500, the UE may alternatively allocate resources during the second round of allocation 414b / 514b to logical channels 411-412 and 512a-512b that have urgent data 420 in the logical channel buffer, in descending order of the measured data loss rate of logical channels 411-412 and 512a-512b. That is, the UE may first allocate resources to logical channels 512a-512b that have the highest amount of data / total number of bytes dropped from the logical channel buffer over time (e.g., compared to the amount of data / total number of bytes entering the buffer). The data loss rate may correspond to the ratio of the number of bytes dropped from the logical channel buffer to the total number of bytes entering the buffer, or to the ratio of the number of SDUs dropped from the logical channel buffer to the total number of SDUs entering the buffer. The UE allocates resources in descending order of priority and / or in descending order of data loss rate until the urgent data 420 in the logical channel buffer is exhausted or the remaining MAC PDU resources are exhausted, whichever condition is met first. Figures 3 to 5 The transmission of a MAC PDU is shown, which prioritizes the transmission of emergency data 420. Figures 6 to 7 The following diagram illustrates the implementation. Figures 3 to 5 One or more aspects of the method. Specifically, Figure 6 The UE 102 is shown to be paired with Figures 3 to 5 The implementation of one or more aspects. Figure 7 104 pairs of network entities are shown. Figures 3 to 5 The implementation of one or more aspects.
[0072] Figure 6 A flowchart 600 illustrates a method for wireless communication at the UE. (Reference) Figure 1 , Figure 3 and Figure 8 The method can be executed by UE 102, UE equipment 802, etc. UE 102, UE equipment 802, etc. may include memories 826', 806', 816 and may correspond to the entire UE 102 or the entire UE equipment 802, or components of UE 102 or UE equipment 802, such as wireless baseband processor 826 and / or application processor 806.
[0073] UE 102 sends UE capability information (606) to the network entity. This UE capability information indicates the UE's ability to allocate remaining resources, prioritizing urgent data in the logical channel buffer over logical channel priorities. For example, refer to... Figure 3 UE102 sends 306 to network entity 104 to enable UE capabilities to prioritize latency-sensitive data.
[0074] UE 102 receives a 608 indication that emergency data includes at least one of the following: a remaining valid time less than or equal to a first threshold, or a queuing delay greater than or equal to a second threshold. For example, refer to Figure 3 UE 102 receives 308 from network entity 104 for prioritizing latency-sensitive data.
[0075] UE 102 receives 610 uplink grants for a MAC PDU from a network entity—this MAC PDU includes a first allocation of logical channel priority with PBR data and a second allocation of remaining resources for residual data. For example, refer to... Figures 3 to 5 UE 102 receives uplink grants of 310a / 310b from network entity 104. Figures 400 to 500 illustrate MAC PDU 416 / 516, which has a first allocation phase 414a / 514a of PBR 415 / 515 based on logical channels 410-412, 510-512b and a second allocation phase 414b / 514b for the remaining resources of MAC PDU 416 / 516.
[0076] UE 102 skips the second allocation of remaining resources for logical channels for which there is no remaining urgent data in the logical channel buffer, as per 612. For example, refer to... Figures 4 to 5 The second allocation phase 414b / 514b of MAC PDU 416 / 516 does not include data allocated from the logical channel buffer of high-priority logical channels 410 / 510 because during the second allocation phase 414b / 514b, high-priority logical channels 410 / 510 do not have urgent data 420 in their logical channel buffers. In other words, the logical channel buffers of high-priority logical channels 410 / 510 only have non-urgent data (i.e., data packets 11 and 12) to be processed in their logical channel buffers during the second allocation phase 414b / 514b.
[0077] UE 102 allocates 614 emergency data points from multiple logical channel buffers, including emergency data, to the MAC PDU. For example, refer to... Figures 3 to 5During the second round of allocation 414b / 514b, UE 102 allocates 314 urgent data 420 from multiple logical channel buffers to MAC PDUs 416 / 516. In some implementations, UE 102 may perform a fixed allocation between logical channels 510-512b in a polling manner. That is, UE 102 may provide a fixed allocation of two data packets, wherein UE 102 allocates two data packets (i.e., data packets 8 and 9) from the first low-priority logical channel 512a, two data packets (i.e., data packets 10 and 13) from the second low-priority logical channel 512b, and so on, until the data in the logical channels or the available resources of MAC PDU 516 are exhausted.
[0078] UE 102 sends a MAC PDU with a second allocation of remaining resources (616) to the network entity. This second allocation prioritizes urgent data in the logical channel buffer over logical channel priorities. For example, refer to... Figures 3 to 5 UE 102 sends MAC PDU 416 to network entity 104. MAC PDU 416 / 516 includes a second allocation phase 414b / 514b for emergency data 420. Figure 6 The method from the UE side of the wireless communication link is described, while Figure 7 A method from the network side of a wireless communication link is described.
[0079] Figure 7 This is flowchart 700, which describes a method for wireless communication at a network entity. (Reference) Figure 1 , Figure 3 and Figure 9 The method can be executed by one or more network entities 104, which may correspond to a base station or a unit of a base station, such as RU 106, DU 108, CU 110, RU processor 906, DU processor 926, CU processor 946, etc. One or more network entities 104 may include memories 906' / 926' / 946', which may correspond to the entirety of one or more network entities 104, or components of one or more network entities 104, such as RU processor 906, DU processor 926, or CU processor 946.
[0080] Network entity 104 receives UE capability information 706 from the UE. This UE capability information indicates the UE's ability to allocate remaining resources, prioritizing urgent data in the logical channel buffer over logical channel priorities. For example, refer to... Figure 3 Network entity 104 receives UE capability 306 from UE 102 for prioritizing latency-sensitive data.
[0081] Network entity 104 sends a 708 configuration to the UE, which indicates that the emergency data includes at least one of the following: a remaining valid time less than or equal to a first threshold, or a queuing delay greater than or equal to a second threshold. For example, refer to Figure 3 Network entity 104 sends 308 to UE 102 for prioritizing latency-sensitive data.
[0082] Network entity 104 sends a 710a first uplink grant to the UE for a MAC PDU, which includes a first allocation of logical channel priority with PBR data and a second allocation of remaining resources for residual data. For example, refer to Figure 3 Network entity 104 sends a first uplink grant (310a) to UE 102. Figures 400 to 500 show MAC PDU 416 / 516, which has a first allocation phase 414a / 514a of PBR 415 / 515 based on logical channels 410-412, 510-512b and a second allocation phase 414b / 514b for the remaining resources of MAC PDU 416 / 516.
[0083] Network entity 104 receives from the UE 716 a second allocation of MAC PDUs with remaining resources, which prioritizes urgent data in the logical channel buffer over logical channel priorities. For example, refer to... Figure 3 Network entity 104 receives MAC PDU 416 from UE 102. MAC PDU 416 / 516 includes a second allocation phase 414b / 514b for emergency data 420.
[0084] Network entity 104 allocates 718 uplink resources to the UE based on the indication of the amount of urgent data in the logical channel buffer in the MAC PDU. For example, refer to Figure 3 Network entity 104 may receive 316 MAC PDUs from UE 102 with MAC-CE indicating the amount of urgent data in the logical channel buffer, such that network entity 104 may allocate 318 resources to UE 102 to accommodate that amount of urgent data in the next MAC PDU transmission.
[0085] Network entity 104 sends 710b to the UE a second uplink grant for the allocated uplink resources associated with the amount of urgent data indicated in the logical channel buffer. For example, refer to Figure 3 Based on the indication received in the MACPDU 316 regarding the amount of urgent data in the logical channel buffer, network entity 104 sends 310b to UE 102 for a second uplink grant of resources allocated 318 to UE 102. Figure 8The described UE equipment 802 can execute the method of flowchart 600. For example... Figure 9 One or more network entities 104 described may execute the methods of flowchart 700.
[0086] Figure 8 Figure 800 illustrates an example of a hardware implementation of UE equipment 802. UE equipment 802 may be UE 102, a component of UE 102, or may implement UE functions. UE equipment 802 may include an application processor 806, which may have on-chip memory 806'. In the example, application processor 806 may be coupled to a secure digital (SD) card 808 and / or a display 810. Application processor 806 may also be coupled to a sensor module 812, a power supply 814, an additional memory module 816, a camera 818, and / or other related components. For example, sensor module 812 may control a barometer / altimeter, motion sensors (such as an inertial management unit (IMU)), a gyroscope, an accelerometer, a light detection and ranging (LIDAR) device, a radio-assisted detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies for positioning.
[0087] The UE equipment 802 may further include a wireless baseband processor 826, which may be referred to as a modem. The wireless baseband processor 826 may have on-chip memory 826'. Together with and similar to the application processor 806, the wireless baseband processor 826 may also be coupled to a sensor module 812, a power supply 814, an additional memory module 816, a camera 818, and / or other related components. The wireless baseband processor 826 may additionally couple to one or more Subscriber Identity Module (SIM) cards 820 and / or one or more transceivers 830 (e.g., wireless RF transceivers).
[0088] Within one or more transceivers 830, the UE equipment 802 may include a Bluetooth module 832, a wireless local area network (WLAN) module 834, a satellite positioning system (SPS) module 836 (e.g., a Global Navigation Satellite System (GNSS) module), and / or a cellular module 838. The Bluetooth module 832, WLAN module 834, SPS module 836, and cellular module 838 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 832, WLAN module 834, SPS module 836, and cellular module 838 may each include a dedicated antenna and / or communicate with one or more other nodes using an antenna 840. For example, UE equipment 802 can communicate with another UE (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 830 and antenna 840, where network entity 104 may correspond to a base station or a unit of a base station, such as RU 106, DU 108 or CU 110.
[0089] The wireless baseband processor 826 and application processor 806 may each include computer-readable media / memory 826', 806' respectively. Additional modules of memory 816 may also be considered as computer-readable media / memory. Each computer-readable medium / memory 826', 806', 816 may be non-transitory. The wireless baseband processor 826 and application processor 806 may each be responsible for general processing, including executing software stored on computer-readable media / memory 826', 806', 816. This software, when executed by the wireless baseband processor 826 / application processor 806, causes the wireless baseband processor 826 / application processor 806 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the wireless baseband processor 826 / application processor 806 during software execution. The wireless baseband processor 826 / application processor 806 may be a component of UE 102. UE equipment 802 may be a processor chip (e.g., a modem and / or application) and includes only the wireless baseband processor 826 and / or application processor 806. In other examples, UE equipment 802 may be the entire UE 102 and may include additional modules of equipment 802.
[0090] like Figure 1 The discussion and about Figure 6The implemented emergency data prioritization component 140 is configured to: receive from a network entity an uplink grant for transmitting a MAC PDU, the MAC PDU including a first allocation of logical channel priority with PBR data and a second allocation of remaining resources for residual data; and transmit to the network entity a MAC PDU with the second allocation of remaining resources, the second allocation prioritizing emergency data in the logical channel buffer over the logical channel priority. The emergency data prioritization component 140 may be located within an application processor 806 (e.g., at 140a), a wireless baseband processor 826 (e.g., at 140b), or both application processor 806 and wireless baseband processor 826. Emergency data prioritization components 140a-140b may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof.
[0091] Figure 9 Figure 900 illustrates an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functions. The one or more network entities 104 may include or correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 946, which may have on-chip memory 946'. In some aspects, CU 110 may further include an additional memory module 956 and / or a communication interface 948, both of which may be coupled to the CU processor 946. CU 110 may communicate with DU 108 via a midhaul link 162 (such as an F1 interface between the communication interface 948 of CU 110 and the communication interface 928 of DU 108).
[0092] DU 108 may include a DU processor 926, which may have on-chip memory 926'. In some aspects, DU 108 may further include an additional memory module 936 and / or a communication interface 928, both of which may be coupled to the DU processor 926. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 928 and RU 106's communication interface 908.
[0093] RU 106 may include an RU processor 906, which may have on-chip memory 906'. In some aspects, RU 106 may further include an additional memory module 916, a communication interface 908, and one or more transceivers 930, all of which may be coupled to the RU processor 906. RU 106 may further include an antenna 940, which may be coupled to one or more transceivers 930, such that RU 106 can communicate with UE 102 via the antenna 940 through one or more transceivers 930.
[0094] On-chip memories 906', 926', 946' and additional memory modules 916, 936, 956 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 906, 926, 946 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 906, 926, 946, the software causes the processor 906, 926, 946 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processors 906, 926, 946 during software execution. In the example, the resource allocation component 150 may be located at any one of the network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.
[0095] like Figure 1 The discussion and about Figure 7The resource allocation component 150 is configured to: send a first uplink grant to the UE for a MAC PDU, the MAC PDU including a first allocation of logical channel priority with PBR data and a second allocation of remaining resources for residual data; and receive from the UE a MAC PDU with a second allocation of remaining resources, the second allocation prioritizing urgent data in the logical channel buffer over logical channel priority. The resource allocation component 150 may be located within one or more processors of one or more network entities 104, such as an RU processor 906 (e.g., at 150a), a DU processor 926 (e.g., at 150b), and / or a CU processor 946 (e.g., at 150c). Resource allocation components 150a-150c may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors 906, 926, 946 configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors 906, 926, 946, or a combination thereof.
[0096] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is an example of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes can also be combined or deleted. Dashed lines may indicate optional elements of the diagram. The appended method claims present the elements of each box in the exemplary order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.
[0097] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not represent the only configurations in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.
[0098] Various aspects of wireless communication systems, such as telecommunications systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.
[0099] An element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.
[0100] If the functions described herein are implemented in software, these functions may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. Storage media can be any available medium that is computer-accessible.
[0101] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more technologies described herein.
[0102] The apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.
[0103] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.
[0104] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used in this disclosure generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that is likely to occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.
[0105] Unless otherwise expressly stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set should be interpreted as a collection of elements having one or more elements.
[0106] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term. As used in the specification and figures, reference numerals are sometimes cross-referenced between figures to indicate identical or similar features. Features that are identical in multiple figures may be labeled with the same reference numerals in multiple figures. Features that are similar but not identical in multiple figures may be labeled with reference numerals that have different leading numerals but share one or more trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the figures). Sometimes, “X” is used generally to indicate multiple variations of a feature. For example, “X06” may generally refer to all reference numbers ending in “06” (e.g., 206, 306, 406, etc.).
[0107] Structural and functional equivalents of the various aspects described throughout this disclosure that are known or subsequently learned by those skilled in the art are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element shall be construed as means plus function unless the phrase “component for…” is explicitly used herein. As used herein, the phrase “based on” should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) shall be construed as “at least based on A.”
[0108] The following examples are merely illustrative and can be combined without limitation with other examples or teachings described herein.
[0109] Example 1 is a method for wireless communication at a UE, comprising: receiving from a network entity an uplink grant for transmitting a MAC PDU, the MAC PDU including a first allocation of logical channel priority with PBR data and a second allocation of remaining resources for residual data; and transmitting to the network entity a MAC PDU with the second allocation of remaining resources, the second allocation prioritizing urgent data in the logical channel buffer over the logical channel priority.
[0110] Example 2 can be combined with Example 1 and includes: the second allocation further prioritizes urgent data in a first logical channel buffer having a first logical channel priority over non-urgent data in a second logical channel buffer having a second logical channel priority that is higher than the first logical channel priority.
[0111] Example 3 may be combined with any of Examples 1 to 2, and further includes: receiving an indication that the emergency data includes at least one of the following: the remaining valid time that meets a first threshold criterion, or the queuing delay that meets a second threshold criterion.
[0112] Example 4 can be combined with Example 3 and includes: the indication includes threshold information indicating at least one of the following: a first threshold criterion or a second threshold criterion for emergency data.
[0113] Example 5 can be combined with any of Examples 1 to 4 and includes: multiple logical channel buffers containing urgent data that is allocated from the multiple logical channel buffers to a MAC PDU based on a descending order of logical channel priorities associated with the multiple logical channel buffers.
[0114] Example 6 can be combined with Example 5 and includes: a set of logical channels having the same logical channel priority, and each logical channel having urgent data in multiple logical channel buffers.
[0115] Example 7 can be combined with Example 6 and includes the following: the set of logical channels is prioritized based on the shortest remaining valid time of the next urgent data to be allocated from the multiple logical channel buffers of the set of logical channels.
[0116] Example 8 can be combined with any of Examples 5 to 7, and includes the second allocation comprising: allocating urgent data to a MAC PDU based on prioritizing the first logical channel buffer over the second logical channel buffer when the first logical channel buffer has more urgent data than the second logical channel buffer.
[0117] Example 9 can be combined with any of Examples 5 to 8, and includes the following: the second allocation includes allocating urgent data to the MAC PDU based on prioritizing the first logical channel buffer over the second logical channel buffer when the first logical channel buffer has more discarded data than the second logical channel buffer in the same amount of time.
[0118] Example 10 can be combined with any of Examples 5 to 6, and includes, the second allocation comprising: allocating up to a fixed amount of emergency data from each of the plurality of logical channel buffers, which includes emergency data, in a cyclical order of logical channels associated with the plurality of logical channel buffers.
[0119] Example 11 can be combined with any of Examples 1 to 4 and includes: multiple logical channel buffers containing urgent data, and a second allocation of the urgent data from the multiple logical channel buffers based on a decreasing data loss rate.
[0120] Example 12 can be combined with Example 11 and includes: the data loss rate is the amount of data dropped from the logical channel buffer over time.
[0121] Example 13 can be combined with any of Examples 1 to 12 and includes: when the residual data is urgent data, a second allocation of the remaining resources for the residual data is independent of the token bucket size for the logical channel.
[0122] Example 14 can be combined with any of Examples 1 to 4, and further includes: skipping a second allocation of the remaining resources from the logical channel buffer when the logical channel buffer does not contain urgent data.
[0123] Example 15 may be combined with any of Examples 1 to 14, and further includes: sending UE capability information to a network entity, the UE capability information indicating the UE's ability to allocate remaining resources, the capability of prioritizing urgent data in the logical channel buffer over logical channel priority.
[0124] Example 16 is a method of wireless communication at a network entity, comprising: sending a first uplink grant to a UE for a MAC PDU, the MAC PDU including a first allocation of logical channel priority with PBR data and a second allocation of remaining resources for residual data; and receiving from the UE a MAC PDU with a second allocation of remaining resources, the second allocation prioritizing urgent data in the logical channel buffer over the logical channel priority.
[0125] Example 17 can be combined with Example 16 and includes: the second allocation further prioritizes urgent data in a first logical channel buffer having a first logical channel priority over non-urgent data in a second logical channel buffer having a second logical channel priority that is higher than the first logical channel priority.
[0126] Example 18 may be combined with any of Examples 16 to 17, and further includes: sending a configuration to the UE indicating that the emergency data includes at least one of the following: the remaining valid time that meets a first threshold criterion, or the queuing delay that meets a second threshold criterion.
[0127] Example 19 can be combined with Example 18 and includes: the indication includes threshold information indicating at least one of the following: a first threshold criterion or a second threshold criterion for emergency data.
[0128] Example 20 may be combined with any of Examples 16 to 19 and includes: the MAC PDU includes an indication of the amount of urgent data in the logical channel buffer, and further includes: sending a second uplink grant to the UE, the second uplink grant allocating uplink resources for at least that amount of urgent data in the logical channel buffer.
[0129] Example 21 can be combined with any of Examples 16 to 20 and includes: multiple logical channel buffers containing urgent data, the MAC PDU having an allocation of urgent data from the multiple logical channel buffers based on a descending order of logical channel priorities associated with the multiple logical channel buffers.
[0130] Example 22 can be combined with Example 21 and includes: a set of logical channels having the same logical channel priority, and each logical channel having urgent data in multiple logical channel buffers.
[0131] Example 23 can be combined with Example 22 and includes that the set of logical channels is prioritized based on the shortest remaining valid time of the next urgent data in the multiple logical channel buffers for the set of logical channels.
[0132] Example 24 can be combined with any of Examples 21 to 23 and includes: based on the fact that the first logical channel has more urgent data in the logical channel buffer than the second logical channel, and the first logical channel has a higher priority than the second logical channel.
[0133] Example 25 can be combined with any of Examples 21 to 24 and includes: the first logical channel having a higher priority than the second logical channel based on the fact that the first logical channel has more data dropped from the logical channel buffer than the second logical channel in the same amount of time.
[0134] Example 26 can be combined with any of Examples 21 to 22, and includes a second allocation based on a cyclical order of allocations from logical channels associated with a plurality of logical channel buffers, the allocation of up to a fixed amount of urgent data from each of the plurality of logical channel buffers including urgent data.
[0135] Example 27 can be combined with any of Examples 16 to 20 and includes: multiple logical channel buffers containing urgent data, and a second allocation of the urgent data from the multiple logical channel buffers based on a decreasing data loss rate.
[0136] Example 28 can be combined with Example 27 and includes: the data loss rate is the amount of data dropped from the logical channel buffer over time.
[0137] Example 29 can be combined with any of Examples 16 to 28 and includes: when the residual data is urgent data, a second allocation of the remaining resources for the residual data is independent of the token bucket size for the logical channel.
[0138] Example 30 may be combined with any of Examples 16 to 29, and further includes: receiving UE capability information from the UE, the UE capability information indicating the UE's ability to allocate remaining resources, the capability of prioritizing urgent data in the logical channel buffer over logical channel priority.
[0139] Example 31 is an apparatus for implementing wireless communication as described in any one of Examples 1 to 30.
[0140] Example 32 is an apparatus for wireless communication, including components for implementing the method as described in any one of Examples 1 to 30.
[0141] Example 33 is a non-transitory computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to implement the method as described in any one of Examples 1 to 30.
Claims
1. A method for wireless communication at a user equipment (UE) (102), comprising: Uplink grants for transmitting Media Access Control (MAC) Protocol Data Units (PDUs) (416 / 516) are received from network entity (104) (310a / 310b), the MAC PDUs (416 / 516) including a first allocation (414a / 514a) with logical channel priority of priority bit rate (PBR) data and a second allocation (414b / 514b) for remaining resources for residual data. as well as Send (316) the MAC PDU (416 / 516) with the second allocation (414b / 514b) of the remaining resources to the network entity (104), the second allocation prioritizing urgent data (420) in the logical channel buffer over the logical channel priority.
2. The method as described in claim 1, wherein, The second allocation (414b / 514b) further prioritizes the urgent data (420) in the first logical channel buffer with the first logical channel priority over the non-urgent data (422) in the second logical channel buffer with the second logical channel priority which is higher than the first logical channel priority.
3. The method according to any one of claims 1 to 2, further comprising: Receive (308) an instruction, the instruction being the emergency data (420) including at least one of the following: The remaining valid time to meet the first threshold criterion, or Queuing delay that meets the second threshold criterion.
4. The method of claim 3, wherein, The indication includes threshold information indicating at least one of the following: the first threshold standard or the second threshold standard for the emergency data (420).
5. The method according to any one of claims 1 to 4, wherein, Multiple logical channel buffers include the emergency data (420), which is allocated from the multiple logical channel buffers to the MAC PDU (416 / 516) based on the descending order of the logical channel priorities associated with the multiple logical channel buffers.
6. The method of claim 5, wherein, The set of logical channels (512a-512b) has the same logical channel priority, and each logical channel has urgent data (420) in the plurality of logical channel buffers.
7. The method of claim 6, wherein, The set of logical channels (512a-512b) is prioritized based on the shortest remaining valid time of the next urgent data to be allocated from the multiple logical channel buffers of the set of logical channels (512a-512b).
8. The method according to any one of claims 5 to 7, wherein, The second allocation (414b / 514b) includes: When the first logical channel has more urgent data (420) than the second logical channel buffer, the urgent data (420) is allocated (314) to the MAC PDU (416 / 516) based on prioritizing the first logical channel buffer over the second logical channel buffer.
9. The method according to any one of claims 5 to 8, wherein, The second allocation (414b / 514b) includes: When the first logical channel buffer has more discarded data than the second logical channel buffer in the same time period, the urgent data (420) is allocated (314) to the MAC PDU (416 / 516) based on prioritizing the first logical channel buffer over the second logical channel buffer.
10. The method according to any one of claims 5 to 6, wherein, The second allocation (414b / 514b) includes: In accordance with the cyclical order of the logical channels (410-412, 510-512b) associated with the plurality of logical channel buffers, up to a fixed amount of the emergency data (420) is allocated (314) from each of the plurality of logical channel buffers that includes the emergency data (420).
11. The method according to any one of claims 1 to 4, wherein, Multiple logical channel buffers include the emergency data (420), and the second allocation (414b / 514b) is an allocation of the emergency data (420) from the multiple logical channel buffers based on a decreasing data loss rate.
12. The method of claim 11, wherein, The data loss rate is the amount of data discarded from the logical channel buffer over time.
13. The method according to any one of claims 1 to 12, wherein, When the residual data is the emergency data (420), the second allocation (414b / 514b) of the remaining resources for the residual data is independent of the token bucket size for the logical channels (410-412, 510-512b).
14. The method of any one of claims 1 to 4, further comprising: When the logical channel buffer does not include the urgent data (420), the second allocation (414b / 514b) of the remaining resources is skipped from the logical channel buffer.
15. The method of any one of claims 1-14, further comprising: Send (306) UE capability information to the network entity (104), the UE capability information indicating the UE's ability to allocate (314) the remaining resources, the capability prioritizing the urgent data (420) in the logical channel buffer over the logical channel priority.
16. A method for wireless communication at a network entity (104), comprising: Sending (310a) a first uplink grant to the user equipment (UE) for a Media Access Control (MAC) Protocol Data Unit (PDU) (416 / 516), the MAC PDU including a first allocation (414a / 514a) with logical channel priority of priority bit rate PBR data and a second allocation (414b / 514b) for remaining resources for residual data; and The MACPDU (416 / 516) with the second allocation (414b / 514b) having the remaining resources is received (316) from the UE (102), the second allocation prioritizing urgent data (420) in the logical channel buffer over the logical channel priority.
17. The method of claim 16, further comprising: Send (308) configuration to the UE (102), the configuration indicating that the emergency data (420) includes at least one of the following: The remaining valid time to meet the first threshold criterion, or Queuing delay that meets the second threshold criterion.
18. The method of any one of claims 16 to 17, wherein, The MAC PDU (416 / 516) includes an indication of the amount of urgent data (420) in the logical channel buffer, and the method further includes: Send (310b) a second uplink grant to the UE (102), the second uplink grant allocating (318) uplink resources for at least the amount of emergency data (420) in the logical channel buffer.
19. An apparatus for wireless communication, comprising a memory, a transceiver, and a processor, the processor being coupled to the memory and the transceiver, the apparatus being configured to implement the method as claimed in any one of claims 1-18.