Logical channel prioritization for data

Abstract

The UE receives a configuration indicating a priority level for each of a plurality of logical channels. The UE schedules one or more packets for uplink transmission according to priority levels of logical channels associated with respective ones of the one or more packets, and adjusts the scheduling in response to a residual delay budget of the packets exceeding a delay threshold. The UE transmits the uplink transmission.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 813,018, filed on July 15, 2022, entitled “LOGICAL CHANNEL PRIORITIZATION FOR DATA,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communications including logical channel prioritization. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects, nor to describe 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 a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus receives a configuration indicating a priority level for each of a plurality of logical channels. The apparatus schedules one or more packets for uplink transmission according to the priority level of the logical channel associated with a corresponding packet in one or more packets, and adjusts the scheduling in response to a residual delay budget of the packet exceeding a delay threshold. The apparatus transmits the uplink transmission.

[0008] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus configures a priority level for each of a plurality of logical channels and a delay threshold for each of the plurality of logical channels, the delay thresholds being based on a residual delay budget. The apparatus receives communications from a user equipment (UE) based on the priority levels and the delay thresholds.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 An example communication flow is illustrated in which a UE fills UL-SCH resources in a TB based on an LCP that includes switching between strict priority and delay-based prioritization.

[0017] Figure 5An example of moving packets to a higher level buffer in response to the residual delay budget falling below a delay threshold is illustrated.

[0018] Figure 6 An example communication flow is illustrated in which a UE moves packets to a higher level buffer in response to a residual delay budget falling below a delay threshold.

[0019] Figure 7 is a flow chart of a method of wireless communication at a UE in accordance with various aspects presented herein.

[0020] Figure 8 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or UE.

[0021] Fig. 9 is a flow chart of a method of wireless communication at a network node in accordance with various aspects presented herein.

[0022] Fig.10 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0023] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0024] Several aspects of the telecommunication system are also presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0025] For example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0026] Thus, in one or more example aspects, implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. For example, such computer-readable media 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 media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0027] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and / or use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be implemented from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including 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 of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0028] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0029] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0030] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0031] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0032] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals to one or more or both of the other units via a wireless transmission medium.

[0033] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0034] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0035] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0036] The SMO framework 105 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0037] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0038] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0039] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0040] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed via a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi, LTE, or NR based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard.

[0041] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0042] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) that is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0043] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0044] In view of the above, unless otherwise specifically stated, if the term "below 6 GHz" or the like is used in this document, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" or the like is used in this document, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0045] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and the best transmit direction for each of the base station 102 / UE 104. The transmit direction and the receive direction of the base station 102 may be the same, or may be different. The transmit direction and the receive direction of the UE 104 may be the same, or may be different.

[0046] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0047] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the positioning of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0048] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0049] Reference again Figure 1 In certain aspects, the UE 104 may include an LCP component 198 configured to: receive a configuration indicating a priority level for each of a plurality of logical channels; schedule one or more packets for uplink transmission according to the priority level of the logical channel associated with a respective packet in the one or more packets; and adjust the scheduling in response to a residual delay budget of the packet exceeding a delay threshold. The UE may also be configured to send an uplink transmission.

[0050] In certain aspects, the base station 102 may include a configuration component 199 that configures a priority level for each of a plurality of logical channels and a delay threshold for each of a plurality of logical channels, the delay thresholds being based on a residual delay budget. The base station may be further configured to receive communications from the UE based on the priority level and the delay threshold. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0051] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0052] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0053]

[0054] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a normal CP is provided, where there are 14 symbols per slot, and the parameter set μ=2, where there are 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0055] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0056] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0057] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0058] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0059] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0060] Figure 3 375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0061] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0062] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0063] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0064] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0065] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0066] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0067] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0068] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The LCP component 198 combines various aspects.

[0069] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The configuration component 199 combines various aspects.

[0070] When the UE receives an uplink grant from the network (e.g., from a base station), the UE determines how to use (e.g., split) the granted resources for data from different logical channels. The UE may be configured with multiple logical channels (LCHs) and may have data associated with one or more of the LCHs to be sent when the UE has uplink resource allocations. The UE may use a logical channel prioritization (LCP) procedure to share resources for uplink transmissions between LCHs. For example, the LCP procedure may control how UL-SCH resources are shared between LCHs. The LCHs may be served based on different priorities between LCHs. Each LCH in the LCH may be configured with a scheduling priority, and data packets from different LCHs may be scheduled in uplink resources based on the scheduling priority of the corresponding LCH associated with the data packet. For example, packets for a higher priority LCH may be scheduled before packets from a lower priority LCH. In some aspects, a priority-based LCP may be referred to as being based on strict priority, e.g., where the LCH with the highest priority is served first, and the LCH with the second highest priority is not served until the LCH with the highest priority no longer has buffered data. Similarly, an LCH with a priority lower than the second highest priority is not served until the LCH with the highest priority and the LCH with the second highest priority no longer have buffered data.

[0071] Some applications may generate multiple types of uplink data streams. Different streams may have different timing deadlines. For example, different data streams of the same application may have different packet delay budgets. Non-limiting examples of such applications are extended reality (XR) applications (e.g., or similarly, virtual reality (VR) applications or augmented reality applications) or different types of cloud-type gaming applications. In the XR example, the XR application may generate a gesture or control packet of information that may have a packet delay budget of 4ms, and the gesture or control packet of information may arrive for transmission (e.g., generation) in a period of 10ms. Such gesture data may be based on the movement of the user's head, the user's field of view, etc. For example, the application may sample the head positioning every 10ms and generate updates to transmit to the other end of the application (such as a cloud-based server). The XR application may also generate hand gesture tracking information to track the movement of the player's hands, and the hand gesture tracking information may have a longer packet delay budget of 10ms and may arrive every 40ms (e.g., in a period of 40ms) for transmission. The XR application may generate voice or audio for transmission, which may have a longer delay budget of 15ms and may arrive at a period of 20ms for transmission. In this example, the XR application may generate different traffic flows that may have different packet delay budgets and different generation periods.

[0072] If a single LCH has a shorter deadline, e.g., a shorter packet delay budget, a priority-based LCP (e.g., a strict priority-based LCP) may enable transmission within the deadline. For example, if an LCH is used for audio and web data or for URLLC and eMBB, a scheduling priority-based LCP may be used, where the highest priority is assigned to the LCH for data with a shorter time deadline.

[0073] However, the XR application example shows that there may be multiple flows with various levels of packet delay budgets. The aspects presented herein enable the use of priority-based scheduling while also serving PDUs in a lower priority LCH that have been buffered so that their delay is close to their deadline, so that the lower priority LCH can be served before packets of a higher priority LCH. The aspects presented herein provide scheduling priorities for LCHs of different priorities that take into account residual delay budgets, rather than scheduling based on fixed priorities. As an example, the scheduling priority of an XR service may be based on a residual packet delay budget, rather than a fixed priority assigned to a flow.

[0074] Figure 4 An example communication flow 400 is illustrated with an LCP based at least in part on a time deadline. The LCP may be referred to as a deadline-based LCP. The network may configure at least one LCH subset for deadline-based scheduling. Figure 4It is illustrated that the base station 404 may configure the UE 402 at 406 with a priority level for each of the multiple LCHs, and may further configure a delay threshold for at least one LCH subset. The network may configure each of the LCH subsets, which may be configured with a delay threshold for a residual delay budget (RDB) to be applied to the PDU. The UE 402 may compare the residual delay budget for each PDU buffered by the LCH with the delay threshold. Each LCH (e.g., including the LCH subset and any additional LCH) may be configured with an LCH scheduling priority to be used for the LCP. Then, as shown in 408 and 412, the UE may schedule data transmission from different LCHs based on priority and based on a delay deadline.

[0075] For example, if no packets in the deadline-based LCH subset have a residual delay budget that exceeds the corresponding delay threshold, each LCH in the LCH (e.g., including the deadline-based LCH and any priority-based LCH) may be scheduled using a strict priority scheme (e.g., a priority-based scheme that is not scheduled based on delay). For example, UE 402 may fill the UL-SCH resources of the TB with packets from one or more LCHs based on the strict priority procedure, as shown at 408.

[0076] If at least one packet in the deadline-based LCH subset has a residual delay budget exceeding the corresponding delay threshold, the UL-SCH resources in the available TBs may be filled according to a procedure in which the LCHs with packets exceeding their delay threshold are scheduled first. Figure 4 In the embodiment, at 410, at least one PDU has a residual delay budget below a threshold amount of time, and at 412, the UE may switch to a UL-SCH resource that fills a TB based on the shortest residual delay budget.

[0077] For example, among the buffered PDUs for one or more LCHs, the UE first selects the PDU with the smallest residual delay budget to fill the available TB. If resources are still available in the TB after the first PDU, the UE selects the PDU with the second smallest residual delay budget to fill the remaining resources in the TB. The UE continues to select PDUs to fill the TB based on the PDU with the next smallest residual delay budget until each PDU has a residual delay budget that exceeds the corresponding delay threshold for the LCH of the PDU (e.g., until no PDU has a residual delay budget less than its delay threshold) or until the TB is completely filled with PDUs.

[0078] If there are remaining UL-SCH resources in the TB after each PDU with a residual delay budget exceeding the corresponding delay threshold has been applied to the TB, the UE schedules the remaining PDUs of the LCH based on a strict priority procedure, for example, without considering the residual delay budget. For example, the UE 402 can switch between strict priority-based TB filling and delay budget-based TB filling based on whether the PDU has a residual delay budget less than a threshold delay. At 414, the UE sends an uplink transmission, for example, a TB in the UL-SCH resources.

[0079] Figure 5 An example 500 of dynamic LCH priority used in the LCP procedure is illustrated. Figure 5 In the example in , the UE may use a strict priority procedure to fill PDUs in the UL-SCH resources of a TB, where if the residual delay budget of the packet drops below a threshold, an adjustment is made to upgrade the packet to a different buffer. Queuing, for example, the buffer may be used for the MAC layer, RLC layer, PDCP, or HARQ buffer. The PHY priority associated with the packet may also be upgraded (e.g., for a new DRB).

[0080] Figure 5 Packets buffered for data radio bearer (DRB) #2 (which has a lower priority than DRB #1) are shown. Once the residual delay budget of a packet reaches a threshold (e.g., 506), the UE may move (or upgrade) the packet from DRB #2 504 to a higher priority DRB #1 502.

[0081] Figure 6 An example communication flow 600 between a UE 602 and a base station 604 is illustrated. Figure 6 It is illustrated that the base station 604 may configure the UE 602 with a priority level for each of the plurality of LCHs at 606, and may further configure a delay threshold for at least one LCH subset. As shown at 608 and 616, the UE may use a strict priority procedure to fill the TB with the PDU. At 612, the residual delay budget of the PDU drops below the delay threshold of its default data radio bearer (DRB) (e.g., at 610), the UE may change the PDU to a different buffer, for example, to a DRB with a higher priority, instead of filling the TB without considering the priority at 616. The PDU may be queued in the new DRB according to its residual delay budget.

[0082] In some aspects, the change of the PDU to a different buffer (eg, “upgrade” to a higher priority DRB) may be a triggering condition for the UE to send a delay status report at 614 .

[0083] In response to the transmission of the packet at 618, the UE may update the token count at 620 based on the default LCH of the packet (eg, of the PDU) instead of the upgraded buffer, e.g., B associated with a leaky bucket procedure, a token bucket procedure, etc. j . For example, as part of a traffic conditioner operation, or as part of logical channel prioritization, the UE may maintain a token count. As an example, the UE may accumulate tokens based on factors such as the amount of time that has passed, for example, increasing or incrementing a count value. The UE (e.g., a MAC entity of the UE) may maintain a token count value, for example, which may be referred to as Bj. When a logical channel is established, the UE may initialize Bj for the logical channel to zero. For each logical channel j, the UE may increment Bj by the product of prioritized bit rate (PBR)×T before each instance of the LCP procedure, where T is the time elapsed since Bj was last incremented. In some aspects, once the token count value reaches a maximum number, the UE may stop increasing the count. For example, if the value of Bj is greater than the bucket size (i.e., PBR×BSD), the UE may set Bj to the bucket size. When the UE has a transmission, the UE may determine whether the current count value of the logical channel meets a threshold. If so, the UE may allocate uplink resources (e.g., in a priority order and / or residual delay budget order as described herein) and may decrement the token count. If the current count value of the logical channel does not meet the threshold, the UE may not allocate uplink resources for the logical channel. When performing a new transmission, the UE (e.g., the MAC entity of the UE) may allocate resources to these logical channels in descending priority order for the logical channels selected by UL grant and with Bj>0. The UE may then decrement Bj by the total size of the MAC SDU serving logical channel j. Using the token count to determine whether to allocate resources to a logical channel can help regulate traffic between logical channels.

[0084] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, 350, 402, 602; device 804). The method may enable the UE to process flows with various delay budgets and priority levels through LCP based on priority and considering residual delay budget.

[0085] At 702, the UE receives a configuration indicating a priority level for each of a plurality of logical channels. Receiving the configuration may be performed, for example, by the LCP component 198, the transceiver 822, and / or the antenna 880. In some aspects, the configuration may also include delay thresholds for each of the at least a subset of the plurality of logical channels, the delay thresholds being based on the residual delay budget.

[0086] At 704, the UE schedules the one or more packets for uplink transmission according to the priority level of the logical channel associated with a corresponding packet of the one or more packets. The scheduling may be performed by the LCP component 198, for example.

[0087] At 706, the UE adjusts scheduling in response to the residual delay budget of the packet exceeding the delay threshold. The scheduling may be performed, for example, by the LCP component 198. In some aspects, adjusting scheduling may include switching scheduling decisions among the plurality of logical channels from priority-based to residual delay budget-based in response to the residual delay budget of at least one packet exceeding the delay threshold. Figure 4 An example of switching between priority-based scheduling to delay-based scheduling is illustrated. Adjusting the scheduling may also include scheduling at least one delayed packet with a residual delay budget that has exceeded the delay threshold before scheduling the remaining packets with residual delay budgets within the delay threshold. Scheduling at least one delayed packet with a residual delay budget that has exceeded the delay threshold may include scheduling a first packet with a smaller residual delay budget before scheduling a second packet with a longer residual delay budget. In some aspects, the UE may return to priority-based scheduling in response to the residual delay budget of each packet being within the delay threshold.

[0088] In some aspects, adjusting the schedule may include moving the buffered packets from a first buffer to a second buffer in response to a residual delay budget of the buffered packets exceeding a delay threshold, the first buffer having a higher priority than the second buffer. Figure 5 and Figure 6 Example aspects of a UE moving a packet to a higher priority buffer in response to a residual delay budget of the packet falling below a delay threshold are illustrated. The UE may queue the buffered packets in a second buffer based on the residual delay budget of the packet. The first buffer and the second buffer may be used for a MAC layer, an RLC layer, or a PDCP buffer. In some aspects, the UE may send a delay status report in response to moving the packet to the second buffer. The UE may update a token count used in a traffic conditioner configured for a logical channel associated with the first buffer in response to the sending of the packet.

[0089] At 708, the UE transmits an uplink transmission. The transmission may be performed, for example, by the LCP component 198, the transceiver 822, and / or the antenna 880. Figure 4 and Figure 6 Example aspects of a UE sending an uplink transmission are illustrated.

[0090] Figure 8800 is a diagram illustrating an example of a hardware implementation for an apparatus 804. The apparatus 804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 804 may include a cellular baseband processor 824 (also referred to as a modem) coupled to one or more transceivers 822 (e.g., a cellular RF transceiver). The cellular baseband processor 824 may include on-chip memory 824'. In some aspects, the apparatus 804 may also include one or more subscriber identity module (SIM) cards 820 and an application processor 806 coupled to a secure digital (SD) card 808 and a screen 810. The application processor 806 may include on-chip memory 806'. In some aspects, the device 804 may also include a Bluetooth module 812, a WLAN module 814, an SPS module 816 (e.g., a GNSS module), one or more sensor modules 818 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 826, a power supply 830, and / or a camera 832. The Bluetooth module 812, the WLAN module 814, and the SPS module 816 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 812, the WLAN module 814, and the SPS module 816 may include their own dedicated antennas and / or communicate using an antenna 880. The cellular baseband processor 824 communicates with the UE 104 and / or with the RU associated with the network entity 802 through the transceiver 822 via one or more antennas 880. The cellular baseband processor 824 and the application processor 806 may each include a computer-readable medium / memory 824', 806', respectively. The additional memory module 826 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 824', 806', 826 may be non-transitory. The cellular baseband processor 824 and the application processor 806 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 824 / application processor 806, enables the cellular baseband processor 824 / application processor 806 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 824 / application processor 806 when executing the software. The cellular baseband processor 824 / application processor 806 may be a component of the UE 350 and may include the memory 360 , and / or at least one of the TX processor 368 , the RX processor 356 , and the controller / processor 359 .In one configuration, the device 804 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 824 and / or the application processor 806, while in another configuration, the device 804 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 804.

[0091] As discussed above, component 198 is configured to: receive a configuration indicating a priority level for each of a plurality of logical channels; schedule one or more packets for uplink transmission according to the priority level of the logical channel associated with a corresponding packet in one or more packets; adjust the scheduling in response to the residual delay budget of the packet exceeding the delay threshold; and send the uplink transmission. The LCP component 198 may be further configured to: switch the scheduling decision among the plurality of logical channels from priority-based to residual delay budget-based in response to the residual delay budget of at least one packet exceeding the delay threshold. The LCP component 198 may be further configured to: schedule at least one delayed packet having a residual delay budget that has exceeded the delay threshold before scheduling the remaining packets having a residual delay budget within the delay threshold. The LCP component 198 may be further configured to: return to priority-based scheduling in response to the residual delay budget of each packet being within the delay threshold. The LCP component 198 may be further configured to: move the buffered packets from the first buffer to the second buffer in response to the residual delay budget of the buffered packets exceeding the delay threshold, the first buffer having a higher priority than the second buffer. The LCP component 198 may be further configured to queue the buffered packets in the second buffer based on the residual delay budget of the packets. The LCP component 198 may be further configured to send a delay status report in response to moving the packets to the second buffer. The LCP component 198 may be further configured to update a token count used in a traffic conditioner configured for a logical channel associated with the first buffer in response to the sending of the packets. The component 198 may be within the cellular baseband processor 824, the application processor 806, or both the cellular baseband processor 824 and the application processor 806. The component 198 may be one or more hardware components that are 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 some combination thereof. As shown, the device 804 may include a variety of components configured for various functions. In one configuration, the apparatus 804 (and specifically the cellular baseband processor 824 and / or the application processor 806) includes means for receiving a configuration indicating a priority level for each of a plurality of logical channels; means for scheduling one or more packets for uplink transmission according to the priority level of the logical channel associated with a corresponding packet in the one or more packets; means for adjusting the scheduling in response to a residual delay budget of the packet exceeding a delay threshold; and means for transmitting the uplink transmission. The apparatus 804 may also include means for switching a scheduling decision among the plurality of logical channels from priority-based to residual delay budget-based in response to a residual delay budget of at least one packet exceeding the delay threshold.The apparatus 804 may also include: a component for scheduling at least one delayed packet having a residual delay budget that has exceeded the delay threshold before scheduling the remaining packets having a residual delay budget within the delay threshold. The apparatus 804 may also include: a component for returning to priority-based scheduling in response to the residual delay budget of each packet being within the delay threshold. The apparatus 804 may also include: a component for moving the buffered packets from the first buffer to the second buffer in response to the residual delay budget of the buffered packets exceeding the delay threshold, the first buffer having a higher priority than the second buffer. The apparatus 804 may also include: a component for queuing the buffered packets in the second buffer based on the residual delay budget of the packets. The apparatus 804 may also include: a component for sending a delay status report in response to moving the packets to the second buffer. The apparatus 804 may also include: a component for updating a token count used in a traffic regulator configured for a logical channel associated with the first buffer in response to the sending of the packets. The component may be a component 198 of the apparatus 804 configured to perform the functions recited by the component. As described above, the apparatus 804 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the components.

[0092] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102, 310, 404, 604; network entity 802). The method may enable processing of flows with various delay budgets and priority levels through LCP based on priority and considering residual delay budget.

[0093] At 902 , the network node configures a priority level for each logical channel of a plurality of logical channels. The configuration may be performed, for example, by the configuration component 199 . Figure 4 and Figure 6 An example of a network node configuring a priority level for an LCH is illustrated.

[0094] At 904 , the network node configures delay thresholds for each of the plurality of logical channels, the delay thresholds being based on the residual delay budget. The configuration may be performed, for example, by the configuration component 199 . Figure 4 and Figure 6 An example of a network node configuring a delay threshold for an LCH is illustrated.

[0095] At 906, the network node receives a communication from the UE based on the priority level and the delay threshold. The receiving may be performed, for example, by the communication interface 1018, 1038, or 1048. Figure 4 and Figure 6An example of a network node receiving communications from a UE based on a priority level and a delay threshold is illustrated.

[0096] In some aspects, the network node may receive a delay status report in response to a packet being moved from a first buffer to a second buffer in response to a residual delay budget of the packet exceeding a delay threshold configured for a logical channel associated with the packet, the first buffer having a higher priority than the second buffer. The receiving may be performed, for example, by communication interface 1018, 1038, or 1048.

[0097] Fig.10 1000 is a diagram illustrating an example of a hardware implementation for a network entity 1002. The network entity 1002 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1002 may include at least one of a CU 1010, a DU 1030, or a RU 1040. For example, depending on the layer functionality handled by the component 199, the network entity 1002 may include a CU 1010; both a CU 1010 and a DU 1030; each of the CU 1010, the DU 1030, and the RU 1040; the DU 1030; both the DU 1030 and the RU 1040; or the RU 1040. The CU 1010 may include a CU processor 1012. The CU processor 1012 may include an on-chip memory 1012'. In some aspects, the CU 1010 may also include an additional memory module 1014 and a communication interface 1018. CU 1010 communicates with DU 1030 via a midhaul link, such as an F1 interface. DU 1030 may include a DU processor 1032. DU processor 1032 may include on-chip memory 1032'. In some aspects, DU 1030 may also include an additional memory module 1034 and a communication interface 1038. DU 1030 communicates with RU 1040 via a fronthaul link. RU 1040 may include a RU processor 1042. RU processor 1042 may include on-chip memory 1042'. In some aspects, RU 1040 may also include an additional memory module 1044, one or more transceivers 1046, an antenna 1080, and a communication interface 1048. RU 1040 communicates with UE 104. On-chip memory 1012', 1032', 1042' and additional memory modules 1014, 1034, 1044 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1012, 1032, 1042 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0098] As discussed above, component 199 is configured to: configure a priority level for each of a plurality of logical channels; configure a delay threshold for each of a plurality of logical channels, the delay thresholds being based on a residual delay budget; and receive communications from a UE based on the priority level and the delay threshold. Configuration component 199 may be further configured to: receive a delay status report in response to a packet being moved from a first buffer to a second buffer in response to a residual delay budget of the packet exceeding a delay threshold configured for a logical channel associated with the packet, the first buffer having a higher priority than the second buffer. Component 199 may be within one or more processors of one or more of CU 1010, DU 1030, and RU 1040. Component 199 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 some combination thereof. Network entity 1002 may include a variety of components configured for various functions. In one configuration, the network entity 1002 includes a component for configuring a priority level for each of a plurality of logical channels; a component for configuring a delay threshold for each of a plurality of logical channels, the delay thresholds being based on a residual delay budget; and a component for receiving communications from a UE based on the priority level and the delay threshold. The network entity 1002 may also include a component for performing the following operations: receiving a delay status report in response to a packet being moved from a first buffer to a second buffer in response to a residual delay budget of the packet exceeding a delay threshold configured for a logical channel associated with the packet, the first buffer having a higher priority than the second buffer. The component may be a component 199 of the network entity 1002 configured to perform the functions recited by the component. As described above, the network entity 1002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the component.

[0099] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

[0100] The foregoing description is provided to enable any person 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 various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0101] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0102] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0103] Aspect 1 is a method for wireless communication at a UE, comprising: receiving a configuration indicating a priority level for each of a plurality of logical channels; scheduling one or more packets for uplink transmission according to the priority level of the logical channel associated with a corresponding packet in the one or more packets; adjusting the scheduling in response to a residual delay budget of the packet exceeding a delay threshold; and sending the uplink transmission.

[0104] In aspect 2, the method according to aspect 1 further includes: the configuration, the configuration also includes a delay threshold for each logical channel in at least one subset of the multiple logical channels, and the delay threshold is based on the residual delay budget.

[0105] In aspect 3, the method according to aspect 1 or aspect 2 further includes: switching the scheduling decision among the multiple logical channels from priority-based to residual delay budget-based in response to the residual delay budget of at least one packet exceeding the delay threshold.

[0106] In aspect 4, the method according to aspect 3 further includes: scheduling at least one delayed packet having the residual delay budget that has exceeded the delay threshold before scheduling the remaining packets having the residual delay budget within the delay threshold.

[0107] In aspect 5, according to the method of aspect 4, further comprising: scheduling the at least one delayed packet having the residual delay budget that has exceeded the delay threshold comprises: scheduling a first packet having a smaller residual delay budget before scheduling a second packet having a longer residual delay budget.

[0108] In aspect 6, the method according to any one of aspects 3 to 5 further comprises: returning to the priority-based scheduling in response to the residual delay budget of each packet being within the delay threshold.

[0109] In aspect 7, the method according to aspect 1 further includes: moving the buffered packets from a first buffer to a second buffer in response to the residual delay budget of the buffered packets exceeding the delay threshold, the first buffer having a higher priority than the second buffer.

[0110] In aspect 8, the method according to aspect 7 further comprises: queuing the buffered packets in the second buffer based on the residual delay budget of the packets.

[0111] In aspect 9, the method according to aspect 7 or aspect 8 further includes: the first buffer and the second buffer are used for at least one of a MAC layer, an RLC layer, or a PDCP buffer.

[0112] In aspect 10, the method according to any one of aspects 7 to 9 further comprises sending a delay status report in response to moving the packet to the second buffer.

[0113] In aspect 11, the method according to any one of aspects 7 to 10 further comprises: updating a token count used in a traffic conditioner configured for the logical channel associated with the first buffer in response to the sending of the packet.

[0114] Aspect 12 is an apparatus for wireless communication at a UE, the apparatus comprising means for performing the method according to any one of aspects 1 to 11.

[0115] Aspect 13 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to implement the method according to any one of aspects 1 to 11.

[0116] In aspect 14, the apparatus according to aspect 12 or aspect 13 further comprises at least one of a transceiver or an antenna.

[0117] Aspect 15 is a non-transitory computer-readable medium storing computer-executable code for wireless communication at a UE, which, when executed by a processor, causes the processor to implement the method according to any one of aspects 1 to 11.

[0118] Aspect 16 is a method for performing wireless communications at a network node, comprising: configuring a priority level for each of a plurality of logical channels; configuring a delay threshold for each of the plurality of logical channels, the delay threshold being based on a residual delay budget; and receiving communications from a UE based on the priority level and the delay threshold.

[0119] In aspect 17, the method according to aspect 16 further includes: receiving a delay status report in response to a packet being moved from a first buffer to a second buffer in response to the residual delay budget of the packet exceeding a delay threshold configured for a logical channel associated with the packet, the first buffer having a higher priority than the second buffer.

[0120] Aspect 18 is an apparatus for wireless communication at a network node, comprising: means for performing the method according to aspect 16 or 17.

[0121] Aspect 19 is an apparatus for wireless communication at a network node, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to implement the method according to aspect 16 or 17.

[0122] In aspect 20, the apparatus according to aspect 18 or 19 further comprises at least one of a transceiver or an antenna.

[0123] Aspect 21 is a non-transitory computer readable medium storing computer executable code for wireless communication at a network node, which, when executed by a processor, causes the processor to implement the method according to aspect 16 or 17.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving a configuration indicating a priority level for each of a plurality of logical channels; scheduling the one or more packets for uplink transmission according to a priority level of a logical channel associated with a respective packet of the one or more packets; adjusting scheduling in response to a residual delay budget of the packet exceeding a delay threshold; as well as The uplink transmission is transmitted.

2. The method of claim 1, wherein the configuration further comprises a delay threshold for each logical channel in at least a subset of the plurality of logical channels, the delay threshold being based on the residual delay budget.

3. The method of claim 1 , wherein adjusting the schedule comprises: Scheduling decisions among the plurality of logical channels are switched from priority-based to residual delay budget-based in response to the residual delay budget of at least one packet exceeding the delay threshold.

4. The method according to claim 3, further comprising: At least one delayed packet having the residual delay budget that has exceeded the delay threshold is scheduled before scheduling the remaining packets having the residual delay budget within the delay threshold.

5. The method of claim 4, wherein scheduling the at least one delayed packet having the residual delay budget that has exceeded the delay threshold comprises: A first packet having a smaller residual delay budget is scheduled before a second packet having a longer residual delay budget is scheduled.

6. The method according to claim 3, further comprising: Returning to the priority-based scheduling is performed in response to the residual delay budget for each packet being within the delay threshold.

7. The method of claim 1 , wherein adjusting the schedule comprises: In response to the residual delay budget of a buffered packet exceeding the delay threshold, the buffered packet is moved from a first buffer to a second buffer, the first buffer having a higher priority than the second buffer.

8. The method according to claim 7, further comprising: The buffered packets are queued within the second buffer based on the residual delay budget of the packets.

9. The method of claim 7, wherein the first buffer and the second buffer are used for at least one of a medium access control (MAC) layer, a radio link control (RLC) layer, or a packet data convergence protocol (PDCP) buffer.

10. The method according to claim 7, further comprising: A delay status report is sent in response to moving the packet to the second buffer.

11. The method according to claim 7, further comprising: A token count used in a traffic conditioner configured for the logical channel associated with the first buffer is updated in response to the sending of the packet.

12. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; and at least one processor coupled to the memory and configured to: receiving a configuration indicating a priority level for each of a plurality of logical channels; scheduling the one or more packets for uplink transmission according to a priority level of a logical channel associated with a respective packet of the one or more packets; adjusting scheduling in response to a residual delay budget of the packet exceeding a delay threshold; as well as The uplink transmission is transmitted.

13. The apparatus of claim 12, wherein the configuration further comprises a delay threshold for each logical channel of at least a subset of the plurality of logical channels, the delay threshold being based on the residual delay budget.

14. The apparatus of claim 12, wherein to adjust the schedule, the at least one processor is further configured to: Scheduling decisions among the plurality of logical channels are switched from priority-based to residual delay budget-based in response to the residual delay budget of at least one packet exceeding the delay threshold.

15. The apparatus of claim 14, wherein the at least one processor is further configured to: At least one delayed packet having the residual delay budget that has exceeded the delay threshold is scheduled before scheduling the remaining packets having the residual delay budget within the delay threshold.

16. An apparatus according to claim 15, wherein, in order to schedule the at least one delayed group having the residual delay budget that has exceeded the delay threshold, the at least one processor is configured to: schedule a first group having a smaller residual delay budget before scheduling a second group having a longer residual delay budget.

17. The apparatus of claim 14, wherein the at least one processor is further configured to: Returning to the priority-based scheduling is performed in response to the residual delay budget for each packet being within the delay threshold.

18. The apparatus of claim 12, wherein to adjust the schedule, the at least processor is further configured to: In response to the residual delay budget of a buffered packet exceeding the delay threshold, the buffered packet is moved from a first buffer to a second buffer, the first buffer having a higher priority than the second buffer.

19. The apparatus of claim 18, wherein the at least one processor is further configured to: The buffered packets are queued within the second buffer based on the residual delay budget of the packets.

20. The apparatus of claim 18, wherein the first buffer and the second buffer are used for at least one of a medium access control (MAC) layer, a radio link control (RLC) layer, or a packet data convergence protocol (PDCP) buffer.

21. The apparatus of claim 18, wherein the at least one processor is further configured to: A delay status report is sent in response to moving the packet to the second buffer.

22. The apparatus of claim 18, wherein the at least one processor is further configured to: A token count used in a traffic conditioner configured for the logical channel associated with the first buffer is updated in response to the sending of the packet.

23. The apparatus according to claim 12, further comprising: At least one transceiver is coupled to the at least one processor and configured to receive the configuration and to transmit the uplink transmission.

24. A method for wireless communication at a network node, comprising: configuring a priority level for each logical channel of the plurality of logical channels; configuring a delay threshold for each of the plurality of logical channels, the delay threshold being based on a residual delay budget; as well as A communication is received from a user equipment (UE) based on the priority level and the delay threshold.

25. The method according to claim 24, further comprising: In response to receiving a delay status report, a packet is moved from a first buffer to a second buffer in response to the residual delay budget of the packet exceeding a delay threshold configured for a logical channel associated with the packet, the first buffer having a higher priority than the second buffer.

26. An apparatus for wireless communication at a network node, comprising: Memory; and at least one processor coupled to the memory and configured to: configuring a priority level for each logical channel of the plurality of logical channels; configuring a delay threshold for each of the plurality of logical channels, the delay threshold being based on a residual delay budget; as well as A communication is received from a user equipment (UE) based on the priority level and the delay threshold.

27. The apparatus of claim 26, wherein the at least one processor is further configured to: In response to receiving a delay status report, a packet is moved from a first buffer to a second buffer in response to the residual delay budget of the packet exceeding a delay threshold configured for a logical channel associated with the packet, the first buffer having a higher priority than the second buffer.

28. The apparatus of claim 26, further comprising: At least one transceiver is coupled to the at least one processor and configured to transmit the configuration and receive the communication from the UE.

Images