Delayed status reporting for deadline-based scheduling

Abstract

Methods, systems, and devices for wireless communication are described. A network can configure a packet delay budget for wireless communication over a logical channel and a delay status report for a user equipment (UE) according to a trigger condition for sending the delay status report. If the UE identifies that a logical channel has satisfied the trigger condition, the UE can send a delay status report indicating a remaining delay budget for the logical channel. The UE can send the delay status report via a physical uplink shared channel resource or via a physical uplink control channel resource.

Description

[0001] Cross-references

[0002] This patent application claims priority to Chinese PCT patent application No. PCT / CN2022 / 100349, entitled “DELAY STATUSREPORTING FOR DEADLINE-BASED SCHEDULING”, filed by He et al. on June 22, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including delay status reporting for deadline-based scheduling. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting delay status reporting for deadline-based scheduling. For example, the described technology provides a network to configure a delay status report for a user equipment (UE) according to a trigger condition for sending a delay status report. The network can be configured with a packet delay budget for wireless communication over a logical channel, and a delay status report for a protocol data unit (PDU) associated with the logical channel can be enabled according to a trigger. If the UE identifies that the logical channel has met the trigger condition, the UE can send a delay status report indicating the remaining delay budget for the logical channel. The UE can send a delay status report via a physical uplink shared channel (PUSCH) resource or via a physical uplink control channel (PUCCH) resource. Compared with PUSCH resources, PUCCH resources can provide faster reports, but PUCCH resources may not include as much data as PUSCH resources. PUCCH resources can be configured for more urgent delay status reports (e.g., based on the priority level of the logical channel).

[0006] A method for wireless communication at a UE is described. The method may include: receiving first control information that identifies a packet delay budget for wireless communication over a logical channel; receiving second control information that enables a delay status report for a PDU associated with the logical channel based on a trigger; and sending a delay status report indicating a remaining delay budget associated with the PDU associated with the logical channel based on satisfying the trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include: at least one processor; a memory coupled to the at least one processor (e.g., operatively, communicatively, functionally, electronically, or electrically); and instructions stored in the memory. The instructions may be executable by the at least one processor (e.g., directly, indirectly, after preprocessing, without preprocessing) to cause the UE to: receive first control information identifying a packet delay budget for wireless communication over a logical channel; receive second control information enabling a delay status report for a PDU associated with the logical channel based on a trigger; and send a delay status report indicating a remaining delay budget associated with a PDU associated with the logical channel based on satisfying the trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving first control information identifying a packet delay budget for wireless communication over a logical channel; means for receiving second control information enabling a delay status report for a PDU associated with the logical channel based on a trigger; and means for sending a delay status report indicating a remaining delay budget associated with a PDU associated with the logical channel based on satisfying the trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by at least one processor (e.g., directly, indirectly, after preprocessing, without preprocessing) to perform the following operations: receiving first control information that identifies a packet delay budget for wireless communication over a logical channel; receiving second control information that enables a delay status report for a PDU associated with the logical channel based on a trigger; and sending a delay status report indicating a remaining delay budget associated with a PDU associated with the logical channel based on satisfying the trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a remaining delay budget threshold for a logical channel together with the second control information, wherein the trigger can be satisfied based on the remaining delay budget satisfying the remaining delay budget threshold.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the remaining delay budget indicated in the delay status report can be a remaining delay budget for a medium access control sub-PDU, a radio link control sub-PDU, or a packet data convergence protocol sub-PDU associated with a logical channel.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the remaining delay budget indicated in a delay status report can be the minimum remaining delay budget of a set of multiple buffered PDUs in a logical channel, and the logical channel can have the highest priority among the set of multiple logical channels for which delay status reporting can be enabled and which can have non-empty buffers.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a delay status report may include operations, features, components, or instructions for periodically sending a delay status report, where the trigger may be satisfied based on a periodic parameter of the delay status report.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a delay status report may include operations, features, components, or instructions for sending a delay status report in portions of a PUSCH allocated for filling a PUSCH payload.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a delay status report may include operations, features, components, or instructions for sending a delay status report in conjunction with a buffer status report triggered for a logical channel, where the trigger may be satisfied based on the buffer status report being triggered.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a delay status report may include operations, features, components, or instructions for sending a delay status report via available PUSCH resources in a medium access control (MAC) control element.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving an indication of a PUCCH resource for delay status reporting for a logical channel.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a delay status report may include operations, features, components, or instructions for sending a delay status report via a code point value included in a PUCCH resource, where the code point value may indicate a remaining delay budget.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the trigger may be associated with sending a delay status report via a PUCCH resource.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a delay status report may include operations, features, components, or instructions for sending a delay status report via PUCCH resources over multiple transmission instances based on one of the first control information or the second control information.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the packet delay budget includes at least one of a packet delay budget for a quality of service (QoS) flow associated with a logical channel or a PDU set delay budget for a QoS flow associated with the logical channel. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 An example of a wireless communication system supporting delay status reporting for deadline-based scheduling in accordance with one or more aspects of the present disclosure is illustrated.

[0023] Figure 2 An example of a wireless communication system supporting delay status reporting for deadline-based scheduling in accordance with one or more aspects of the present disclosure is illustrated.

[0024] Figure 3 An example of a process flow to support delay status reporting for deadline-based scheduling in accordance with one or more aspects of the present disclosure is illustrated.

[0025] Figure 4 and Figure 5 A block diagram of an apparatus supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is shown.

[0026] Figure 6 A block diagram of a communication manager supporting delay status reporting for deadline-based scheduling is shown in accordance with one or more aspects of the present disclosure.

[0027] Figure 7 A diagram of a system including a device supporting delay status reporting for deadline-based scheduling is shown in accordance with one or more aspects of the present disclosure.

[0028] Figures 8 to 10 A flow chart illustrating a method of supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0029] In some wireless communication systems, some applications may require high reliability and low latency transmission. For example, extended reality (XR) services may require high reliability and low latency transmission. For example, a network entity may send a video frame to an XR user (e.g., a user equipment (UE)), or a UE may send a video frame to a network entity. The limited (e.g., minimum) amount of data that an application software can process at one time (e.g., the granularity of data processed by the application software) may be referred to as an application data unit (ADU). Due to the strict latency requirements associated with the ADU, some packets may become obsolete for the application if the packet is not received within the packet delay budget (e.g., the packet is not received within the duration to be processed with other packets of the same ADU). Some uplink services (e.g., small-sized constant data streams, such as poses) can be sent using configured grants, but dynamic grants can be used for busy high data rate streams (such as video) to efficiently use radio resources.

[0030] An end-to-end packet delay budget may be defined between a UE and an application server. An end-to-end packet delay budget may provide a packet delay budget guide, but it may not be practical to apply it to a UE for a layer 2 procedure for uplink transmissions. For layer 2 procedures, for downlink transmissions, the UE may not be aware of the routing delay through the core network and the scheduling delay for each individual packet at the serving base station. For layer 2 procedures, for uplink transmissions, the network (e.g., a serving network entity) may not be aware of the delay of each packet before the packet is sent on a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH). The remaining delay budget refers to the remaining delay budget of a protocol data unit (PDU) before the PDU becomes obsolete (e.g., is discarded). Currently, there is no signaling for the UE to indicate the remaining delay budget for a given PDU. Thus, the network may send an uplink grant (e.g., based on hybrid automatic repeat request (HARQ) feedback) for transmission of a PDU or retransmission of a PDU even when transmission of the PDU or retransmission of the PDU would be overdue (e.g., because the transmission or retransmission would be outside the packet delay budget associated with the ADU for the PDU).

[0031] The network may configure a delay status report for the UE based on a trigger condition for sending a delay status report. For example, the network may configure a packet delay budget for wireless communication over a logical channel, and may enable a delay status report for a protocol data unit associated with the logical channel based on a trigger. If the UE identifies that a PDU associated with the logical channel has met the trigger condition, the UE may send a delay status report indicating the remaining delay budget for the PDU associated with the logical channel.

[0032] In some cases, each buffered PDU in a logical channel may have a corresponding remaining delay budget, and the UE may send a delay status report based on the minimum remaining delay budget in the buffered PDU for the logical channel satisfying the trigger condition. In some cases, the UE may report the remaining delay budget for each buffered PDU in the logical channel. In some cases, the UE may report the remaining delay budget for the PDU associated with multiple logical channels based on satisfying the trigger condition in the PDU associated with the highest priority logical channel among the multiple logical channels. In some cases, the UE may be configured to periodically send a delay status report to the network. In some cases, the UE may be configured to send a delay status report for the logical channel whenever the UE is triggered to send a buffer status report for the logical channel. The UE may send a delay status report via a PUSCH resource (e.g., a PUSCH resource of a medium access control (MAC) control element (MAC-CE) or via portions of a PUSCH resource used to fill a PUSCH payload) or via a PUCCH resource. Compared with PUSCH resources, PUCCH resources can provide faster reports, but PUCCH resources may not include as much data as PUSCH resources. Therefore, PUCCH resources may be configured for more urgent delay status reporting (eg, based on the priority level of the logical channel).

[0033] Aspects of the disclosure are first described in the context of a wireless communication system. Aspects of the disclosure are further illustrated and described by and with reference to process flows, apparatus diagrams, system diagrams, and flow diagrams related to delay status reporting for deadline-based scheduling.

[0034] Figure 1 An example of a wireless communication system 100 supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0035] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0036] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Other UEs 115 or network entities 105 are shown communicating.

[0037] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0038] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other through the backhaul communication link 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0039] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0040] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0041] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within a protocol layer (e.g., some functions of a protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate over those communication links.

[0042] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0043] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0044] The IAB node 104 may refer to a RAN node that provides IAB functions (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward a child node associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, the IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay transmissions to the UE through one or more other IAB nodes 104). Additionally or alternatively, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and the DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0045] For example, the IAB node 104 may be referred to as a parent node supporting child IAB node communications and as a child node associated with the IAB donor. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmission to the UE 115 through the IAB node 104, and may directly signal the UE 115 of the transmission. The CU 160 of the IAB donor may signal the IAB node 104 of the communication link establishment via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling through the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0046] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support delay status reporting for deadline-based scheduling as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0047] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, a client, or the like. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, an MP3 player, or a video device), a camera, a gaming device, a navigation / positioning device (e.g., a GNSS (Global Navigation Satellite System) device based on, for example, GPS (Global Positioning System), BeiDou system, GLONASS or Galileo system, ground-based equipment, etc.), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot / robotic device, a vehicle, a vehicle's equipment, a meter (e.g., a parking meter, an electricity meter, a gas meter, a water meter), a monitor, a gas pump, an appliance (e.g., a kitchen appliance, a washing machine, a dryer), a location tag, a medical / health care device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, and the like.

[0048] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0049] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0050] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0051] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0052] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth, or may be configured to support communication over one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0053] The signal waveform transmitted by the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0054] One or more numerologies of a carrier may be supported, where the numerologies may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP of a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0055] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·Nf ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0056] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0057] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0058] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0059] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., via a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0060] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0061] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0062] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0063] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0064] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging. In one aspect, the technology disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UE may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UE, NB-IoT (also known as CAT NB1) UE, and other types of UE. eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), and mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT) and FeNB-IoT (further enhanced NB-IoT).

[0065] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed with a reduced peak rate. Other energy-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0066] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0067] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0068] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units) using vehicle-to-network (V2N) communications, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0069] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0070] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0071] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of a spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, RU170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0072] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0073] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0074] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to the same receiving device and in which multiple spatial layers are sent to multiple devices.

[0075] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0076] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0077] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0078] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0079] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0080] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reorganization to communicate through logical channels. The MAC layer can perform priority processing and multiplexing of logical channels into transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration, and maintenance of the RRC connection that supports the radio bearer of user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, the transport channel can be mapped to the physical channel.

[0081] UE 115 and network entity 105 may support retransmission of data to increase the possibility of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0082] In some examples, some applications supported by the wireless communication system 100 may require high reliability and low latency transmission. For example, the wireless communication system 100 may support XR services, which may require high reliability and low latency transmission. For example, the network entity 105 may send video frames to an XR user (e.g., UE 115), or the UE 115 may send video frames to the network entity 105. A delay budget (e.g., a packet delay budget) may be defined as an end-to-end packet delay budget between the UE 115 and an application server (e.g., the network entity 105). The network entity 105 may establish one or more PDU sessions for the UE 115, and each PDU session may be associated with one or more quality of service (QoS) flows. QoS may be defined as a measurement of the performance that the UE 115 or the network entity 115 can achieve for an associated service (e.g., a flow, such as a QoS flow). Therefore, different QoS flows in a PDU session may be associated with data packets, logical channels, etc., each of which has different QoS parameters or requirements (e.g., bit rate, packet loss rate, throughput, or transmission delay, etc.). That is, services with the same or similar QoS requirements can be assigned to the same QoS flow. For example, in an XR application, a QoS flow may correspond to a logical channel that carries data packets (e.g., ADU) with relatively high reliability and relatively low latency requirements. Each QoS flow can be associated with a unique QoS flow identifier (QFI).

[0083] A PDU set may be defined as a group of data packets (e.g., PDUs) from an application (e.g., an XR application) carrying a payload of one or more ADUs, where the one or more ADUs are processed together by the application. In some examples, QoS may be processed on a per-PDU set basis. That is, QoS parameters may be PDU set specific. For example, each PDU set may be associated with a corresponding QoS flow for a logical channel, and each QoS flow may be associated with a corresponding PDU set delay budget, a PDU set error rate, PDU set integrated processing information, or a combination thereof. In such examples, a packet delay budget for a PDU set (e.g., a PDU set delay budget) may be defined as an upper limit on the delay that the PDU set may experience (e.g., the time period between the receipt of the first PDU in the PDU set at its destination and the time when all PDUs in the PDU set have been successfully received at that destination).

[0084] Alternatively, when QoS is not handled on a per-PDU-aggregation basis, a delay budget (e.g., a packet delay budget) may be defined as a packet delay budget for a QoS flow associated with a logical channel. Here, the packet delay budget may be an upper limit on the time that a packet may be delayed between UE115 and UPF.

[0085] In order to support high reliability and low latency transmission in the wireless communication system 100, the network (e.g., the serving network entity 105) may configure a delay status report for the UE 115 according to a trigger condition for sending a delay status report. For example, the network may configure a packet delay budget (e.g., a PDU set delay budget, a packet delay budget) for wireless communication through a logical channel, and may enable a delay status report for a PDU associated with the logical channel according to a trigger. If the UE 115 identifies that the PDU associated with the logical channel has met the trigger condition, the UE 115 may send a delay status report indicating the remaining delay budget for the PDU associated with the logical channel.

[0086] In some cases, each buffered PDU in a logical channel may have a corresponding remaining delay budget, and the UE may send a delay status report based on the minimum remaining delay budget in the buffered PDU for the logical channel satisfying the trigger condition. In some cases, the UE 115 may report the remaining delay budget for each buffered PDU in the logical channel. In some cases, the UE may report the remaining delay budget for the PDU associated with multiple logical channels based on satisfying the trigger condition in the PDU associated with the highest priority logical channel among the multiple logical channels. In some cases, the UE 115 may be configured to periodically send a delay status report to the network. In some cases, the UE 115 may be configured to send a delay status report for the logical channel whenever the UE is triggered to send a buffer status report for the logical channel. The UE 115 may send a delay status report via a PUSCH resource (e.g., a PUSCH resource of a MAC-CE or via portions of a PUSCH resource used to fill a PUSCH payload) or via a PUCCH resource. PUCCH resources may provide faster reporting compared to PUSCH resources, but PUCCH resources may not include as much data as PUSCH resources. Therefore, PUCCH resources may be configured for more urgent delay status reporting (eg, based on the priority level of the logical channel).

[0087] Figure 2 An example of a wireless communication system 200 that supports delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. The wireless communication system 200 can include a UE 115-a, which can be an example of a UE 115 as described herein. The wireless communication system 200 can include a network entity 105-a, which can be an example of a network entity 105 as described herein.

[0088] UE 115-a may communicate with network entity 105-a using communication link 125-a, which may be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a may include a bidirectional link that implements both uplink communication and downlink communication. For example, UE 115-a may send uplink signal 205 (such as uplink control signal or uplink data signal) to network entity 105-a using communication link 125-a, and network entity 105-a may send downlink signal 210 (such as downlink control signal or downlink data signal) to UE 115-a using communication link 125-a.

[0089] The network entity 105-a may send one or more uplink grants 215 to the UE 115-a, the one or more uplink grants scheduling one or more uplink transmissions 220 through one or more logical channels. In some cases, the one or more uplink transmissions 220 may be associated with one or more packet delay budgets. For example, the network entity 105-a may send first control information 225, the first control information identifying a packet delay budget for wireless communication through a logical channel. The packet delay budget may be based on a QoS flow associated with the logical channel. When the QoS flow is based on PDU set QoS processing, the packet delay budget may include a PDU set delay budget for the QoS flow associated with the logical channel, or an example of the PDU set delay budget. Alternatively, when the QoS flow is not based on a PDU set, the packet delay budget may include a packet delay budget for the QoS flow associated with the logical channel, or an example of the packet delay budget. In some cases, the first control information 225 may identify a corresponding packet delay budget for wireless communication through a set of corresponding logical channels (e.g., based on a corresponding QoS flow set for the set of corresponding logical channels).

[0090] The network entity 105-a may not be aware of the remaining packet delay budget for the logical channel, where the remaining delay budget is part of the packet delay budget (e.g., PDU aggregate delay budget, packet delay budget) for the logical channel. Therefore, the network entity 105-a may send second control information 230 that enables delay status reporting for PDUs associated with the logical channel based on a trigger. The UE 115-a may send a delay status report 235 indicating the remaining delay budget associated with the logical channel based on satisfying the trigger. Once triggered, the delay status report 235 may remain pending until sent by the UE 115-a.

[0091] In some examples, when a MAC sub-PDU, a radio link control (RLC) sub-PDU, or a packet data convergence protocol (PDCP) sub-PDU for a logical channel configured with a remaining delay budget report is sent in a PUSCH resource, if the remaining delay budget of the MAC sub-PDU, RLC sub-PDU, or PDCP sub-PDU has exceeded a configured threshold (e.g., where the configured threshold is indicated in the second control information 230), the UE 115-a may trigger a delay status report 235. In some cases, the delay status report 235 may be sent in a MAC-CE when there are available PUSCH resources. In some cases, the delay status report 235 triggered by the remaining delay budget of the MAC sub-PDU, RLC sub-PDU, or PDCP sub-PDU for a logical channel configured with a remaining delay budget report exceeding the configured threshold may include only the remaining delay budget for the MAC sub-PDU, RLC sub-PDU, or PDCP sub-PDU.

[0092] In some examples, logical channel m can have the highest priority among all logical channels configured with delay status reporting. For example, the second control information can enable delay status reporting for multiple logical channels including logical channel m. If logical channel m has a non-empty buffer and Zm (i.e., the minimum remaining delay budget in the buffered protocol data units in logical channel m) has exceeded a configured threshold (e.g., where the configured threshold is indicated in the second control information 230), UE 115-a can trigger delay status reporting 235.

[0093] In some examples, the network entity 105-a may configure the UE 115-a to periodically send the delay status report 235 (e.g., the second control information 230 may indicate a periodicity parameter). In some examples, the network entity 105-a may configure the UE 115-a to send the delay status report 235 as part of padding (e.g., in portions of the PUSCH allocated for padding a PUSCH payload). In some examples, the network entity 105-a may configure the UE 115-a to send the delay status report 235 when a regular buffer status report is triggered.

[0094] In some cases, when there are available PUSCH resources, a delay status report 235 may be sent in the MAC-CE. The delay status report 235 may include Zm, the minimum remaining delay budget in buffered protocol data units in each logical channel configured with the delay status report. The PUSCH resources used to send the delay status report 235 may be a dynamic grant or a configured grant. In some cases, if no PUSCH resources are available to send the delay status report 235, the UE 115-a may trigger a scheduling request 240 to prompt the network to send a grant 245 for PUSCH to send the delay status report 235.

[0095] In some cases, the network entity 105-a may configure (e.g., in the second control information 230) a PUCCH resource for the UE 115-a to report an urgent delay status of a logical channel for which delay status reporting is enabled. PUCCH resources may be faster than PUSCH resources, but PUCCH resources may provide less information (e.g., a number of information bits) than PUSCH. Thus, PUCCH resources may be configured for more urgent delay status reporting (e.g., based on the priority level of the logical channel).

[0096] The network entity 105-a may configure which logical channels may use PUCCH resources to report the delay status report 235. For each logical channel configured to use PUCCH resources to report the delay status report 235, the network entity 105-a may configure (e.g., indicate in the second control information 230) a codepoint mapping for delay status reporting for the logical channel. For example, if the PUCCH resources used for delay status reporting support a 3-bit payload, the codepoint mapping may describe how possible values ​​of the remaining delay budget are mapped to values ​​in the PUCCH payload.

[0097] The network entity 105-a may configure which triggers are associated with PUCCH resources and which triggers are associated with PUSCH resources. For example, a logical channel m having the highest priority among all logical channels configured with a delay status report may be associated with sending a delay status report via a PUCCH resource. Once a delay status report 235 associated with a PUCCH resource is triggered, the delay status report 235 may be sent using the configured PUCCH resources. The network entity 105-a may indicate (e.g., in the first control information 225 or the second control information 230) the number of transmission instances for which a delay status report is to be sent via a PUCCH resource.

[0098] Figure 3An example of a process flow 300 for supporting delay status reporting for deadline-based scheduling in accordance with one or more aspects of the present disclosure is illustrated. The process flow 300 may include a UE 115-b, which may be an example of a UE 115 as described herein. The process flow 300 may include a network entity 105-b, which may be an example of a network entity 105 as described herein. In the following description of the process flow 300, operations between the network entity 105-b and the UE 115-b may be sent in an order different from the example order shown, or operations performed by the network entity 105-b and the UE 115-b may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 300, and other operations may be added to the process flow 300.

[0099] At 305, UE 115-b may receive first control information from network entity 105-b that identifies a packet delay budget for wireless communication over a logical channel. In some examples, the packet delay budget may be a packet delay budget for a QoS flow associated with the logical channel. In other examples, the packet delay budget may be a PDU aggregate delay budget for the QoS flow of the logical channel.

[0100] At 310 , the UE 115 - b may receive second control information from the network entity 105 - b that enables delay status reporting for PDUs associated with the logical channel based on a trigger.

[0101] At 315, UE 115-b may determine that a trigger is met.

[0102] At 320 , the UE 115 - b may send a delay status report indicating a remaining delay budget associated with the logical channel to the network entity 105 - b based on satisfying the trigger, wherein the remaining delay budget is a portion of a packet delay budget for the logical channel.

[0103] In some cases, UE 115-b may receive a remaining delay budget threshold for the logical channel along with the second control information, wherein the trigger is satisfied at 315 based on the remaining delay budget satisfying the remaining delay budget threshold. In some cases, the remaining delay budget indicated in the delay status report is a remaining delay budget of a MAC sub-PDU, an RLC sub-PDU, or a PDCP sub-PDU associated with the logical channel. In some cases, the remaining delay budget indicated in the delay status report may be a minimum remaining delay budget of a plurality of buffered PDUs in the logical channel, wherein the logical channel has the highest priority among the plurality of logical channels for which delay status reporting is enabled and which have non-empty buffers.

[0104] In some cases, UE 115-b may periodically send delay status reports, and the trigger is satisfied based on a periodicity parameter of the delay status report at 315. In some cases, the periodicity parameter may be indicated in the second control information received at 310.

[0105] In some cases, UE 115-b may send a delay status report in portions of the PUSCH allocated for filling a PUSCH payload.

[0106] In some cases, UE 115 - b may send a delay status report in conjunction with a buffer status report triggered for a logical channel, where the trigger is satisfied based on the buffer status report being triggered at 315 .

[0107] In some cases, UE 115-b may send a delay status report via available PUSCH resources in the MAC-CE.

[0108] In some cases, UE 115-b may receive an indication of a PUCCH resource for a delay status report for a logical channel. In some cases, UE 115-b may send a delay status report via a code point value included in the PUCCH resource, where the code point value indicates a remaining delay budget. In some cases, a trigger may be associated with sending a delay status report via the PUCCH resource. In some cases, UE 115-b may send a delay status report via the PUCCH resource over multiple transmission instances based on one of the first control information or the second control information.

[0109] Figure 4 A block diagram 400 of a device 405 supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is shown. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0110] The receiver 410 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to delay status reporting for deadline-based scheduling, data channels, information channels). The information may be communicated to other components of the device 405. The receiver 410 may utilize a single antenna or a collection of multiple antennas.

[0111] The transmitter 415 may provide means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information associated with various information channels (e.g., control channels related to delay status reporting for deadline-based scheduling, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 415 may be co-located with the receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0112] The communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of delay status reporting for deadline-based scheduling as described herein. For example, the communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0113] In some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0114] Additionally or alternatively, in some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0115] In some examples, communication manager 420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 410, transmitter 415, or both. For example, communication manager 420 may receive information from receiver 410, transmit information to transmitter 415, or be integrated in conjunction with receiver 410, transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.

[0116] According to examples as disclosed herein, the communication manager 420 may support wireless communications at a UE. For example, the communication manager 420 may be configured to or otherwise support a component for receiving a first control information identifying a packet delay budget for wireless communications over a logical channel. The communication manager 420 may be configured to or otherwise support a component for receiving a second control information that enables a delay status report for a PDU associated with the logical channel based on a trigger. The communication manager 420 may be configured to or otherwise support a component for sending a delay status report indicating a remaining delay budget associated with the logical channel based on satisfying a trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0117] By including or configuring a communications manager 420 according to examples as described herein, a device 405 (e.g., a processor controlling or otherwise coupled to a receiver 410, a transmitter 415, a communications manager 420, or a combination thereof) can support techniques for more efficiently utilizing communications resources by enabling delay status reporting.

[0118] Figure 5 A block diagram 500 of a device 505 supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the device 405 or UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0119] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to delay status reporting for deadline-based scheduling, data channels, information channels). The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0120] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels related to delay status reporting for deadline-based scheduling, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0121] Device 505 or its various components may be examples of components for performing various aspects of delay status reporting for deadline-based scheduling as described herein. For example, communication manager 520 may include packet delay budget configuration manager 525, delay status report configuration manager 530, delay status report manager 535, or any combination thereof. Communication manager 520 may be an example of various aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated with receiver 510, transmitter 515, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0122] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a UE. The packet delay budget configuration manager 525 may be configured to or otherwise support a component for receiving first control information identifying a packet delay budget for wireless communications over a logical channel. The delay status report configuration manager 530 may be configured to or otherwise support a component for receiving second control information that enables delay status reporting for a PDU associated with the logical channel based on a trigger. The delay status reporting manager 535 may be configured to or otherwise support a component for sending a delay status report indicating a remaining delay budget associated with the logical channel based on satisfying a trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0123] Figure 6A block diagram 600 of a communication manager 620 supporting delay status reporting for deadline-based scheduling is shown in accordance with one or more aspects of the present disclosure. The communication manager 620 may be an example of aspects of the communication manager 420, the communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of means for performing various aspects of delay status reporting for deadline-based scheduling as described herein. For example, the communication manager 620 may include a packet delay budget configuration manager 625, a delay status report configuration manager 630, a delay status report manager 635, a remaining delay budget threshold manager 640, a periodic delay status report manager 645, a PUSCH manager 650, a buffer status report manager 655, a PUCCH manager 660, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0124] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE. The packet delay budget configuration manager 625 may be configured to or otherwise support a component for receiving first control information that identifies a packet delay budget for wireless communications over a logical channel. The delay status report configuration manager 630 may be configured to or otherwise support a component for receiving second control information that enables delay status reporting for a PDU associated with the logical channel based on a trigger. The delay status reporting manager 635 may be configured to or otherwise support a component for sending a delay status report indicating a remaining delay budget associated with the logical channel based on satisfying a trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0125] In some examples, the remaining delay budget threshold manager 640 may be configured to or otherwise support means for receiving a remaining delay budget threshold for a logical channel along with the second control information, wherein the trigger is satisfied based on the remaining delay budget satisfying the remaining delay budget threshold.

[0126] In some examples, the remaining delay budget indicated in the delay status report is a remaining delay budget for a MAC sub-PDU, an RLC sub-PDU, or a PDCP sub-PDU associated with the logical channel.

[0127] In some examples, the remaining delay budget indicated in the delay status report is a minimum remaining delay budget for a set of multiple buffered protocol data units in the logical channel. In some examples, the logical channel has the highest priority among the set of multiple logical channels that have delay status reporting enabled and have non-empty buffers.

[0128] In some examples, to support sending delay status reports, periodic delay status reporting manager 645 may be configured or otherwise support means for periodically sending delay status reports, where a trigger is satisfied based on a periodicity parameter of the delay status report.

[0129] In some examples, to support sending delay status reports, PUSCH manager 650 may be configured or otherwise support means for sending delay status reports in portions of the PUSCH allocated for filling a PUSCH payload.

[0130] In some examples, to support sending a delay status report, the buffer status reporting manager 655 may be configured to or otherwise support components for sending a delay status report in conjunction with a buffer status report triggered for a logical channel, where the trigger is satisfied based on the buffer status report being triggered.

[0131] In some examples, to support sending a delay status report, PUSCH manager 650 may be configured or otherwise support means for sending a delay status report via available PUSCH resources in a MAC-CE.

[0132] In some examples, PUCCH manager 660 may be configured or otherwise support means for receiving an indication of PUCCH resources for delay status reporting for a logical channel.

[0133] In some examples, to support sending a delay status report, the PUCCH manager 660 may be configured or otherwise support means for sending a delay status report via a codepoint value included in a PUCCH resource, where the codepoint value indicates a remaining delay budget.

[0134] In some examples, the trigger is associated with sending a delay status report via a PUCCH resource.

[0135] In some examples, to support sending a delay status report, the PUCCH manager 660 may be configured or otherwise support means for sending a delay status report via PUCCH resources over multiple transmission instances based on one of the first control information or the second control information.

[0136] In some examples, the packet delay budget includes at least one of a packet delay budget for a QoS flow associated with the logical channel and a PDU aggregate delay budget for the QoS flow associated with the logical channel.

[0137] Figure 7A diagram of a system 700 including a device 705 supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is shown. The device 705 may be an example of a device 405, a device 505, or a UE 115 as described herein, or include components thereof. The device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, a memory 730, a code 735, and a processor 740. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., a bus 745).

[0138] I / O controller 710 can manage input signals and output signals of device 705. I / O controller 710 can also manage peripheral devices that are not integrated into device 705. In some cases, I / O controller 710 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 710 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 710 may be implemented as part of a processor, such as processor 740. In some cases, a user may interact with device 705 via I / O controller 710 or via hardware components controlled by I / O controller 710.

[0139] In some cases, the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bidirectionally via one or more antennas 725, wired or wireless links as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. The transceiver 715 or the transceiver 715 and one or more antennas 725 may be examples of transmitters 415, transmitters 515, receivers 410, receivers 510, or any combination thereof or components thereof as described herein.

[0140] The memory 730 may include random access memory (RAM) and read-only memory (ROM). The memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed by the processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 735 may not be directly executable by the processor 740, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 730 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0141] The processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a GPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting delay status reporting for deadline-based scheduling). For example, the device 705 or a component of the device 705 may include a processor 740 and a memory 730 coupled to or coupled to the processor 740, and the processor 740 and the memory 730 are configured to perform the various functions described herein.

[0142] According to examples as disclosed herein, the communication manager 720 may support wireless communication at a UE. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a first control information identifying a packet delay budget for wireless communication over a logical channel. The communication manager 720 may be configured to or otherwise support a component for receiving a second control information that enables a delay status report for a PDU associated with the logical channel based on a trigger. The communication manager 720 may be configured to or otherwise support a component for sending a delay status report indicating a remaining delay budget associated with the logical channel based on satisfying the trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0143] By including or configuring a communication manager 720 according to examples as described herein, the device 705 can support techniques for improved communication reliability, more efficient utilization of communication resources, improved coordination between devices, and improved utilization of processing power by enabling delay status reporting.

[0144] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 715, one or more antennas 725, or any combination thereof. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by the processor 740, the memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions executable by the processor 740 to cause the device 705 to perform various aspects of delay status reporting for deadline-based scheduling as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.

[0145] Figure 8 A flowchart illustrating a method 800 for supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is shown. The operations of the method 800 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 800 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0146] At 805, the method may include receiving first control information that identifies a packet delay budget for wireless communication over a logical channel. The operations of 805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 805 may be performed as described in reference to Figure 6 The described packet delay budget configuration manager 625 is performed.

[0147] At 810, the method may include receiving second control information that enables delay status reporting for a PDU associated with a logical channel based on a trigger. The operations of 810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 810 may be performed as described in reference to Figure 6 The described delay status reporting is configured to be performed by manager 630.

[0148] At 815, the method may include sending a delay status report indicating a remaining delay budget associated with the logical channel based at least in part on satisfying the trigger, wherein the remaining delay budget is a portion of a packet delay budget for the logical channel. The operations of 815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 815 may be performed as described in reference to Figure 6 The described delay status reporting manager 635 is executed.

[0149] Fig. 9 A flowchart illustrating a method 900 for supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is shown. The operations of the method 900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 900 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0150] At 905, the method may include receiving first control information that identifies a packet delay budget for wireless communication over a logical channel. The operations of 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed as described in reference to Figure 6 The described packet delay budget configuration manager 625 is performed.

[0151] At 910, the method may include receiving second control information that enables delay status reporting for a PDU associated with a logical channel based on a trigger. The operations of 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed as described in reference to Figure 6 The described delay status reporting is configured to be performed by manager 630.

[0152] At 915, the method may include receiving a remaining delay budget threshold for the logical channel along with the second control information. The operations of 915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 915 may be performed as described in reference to Figure 6 The described remaining delay budget threshold manager 640 is implemented.

[0153] At 920, the method may include sending a delay status report indicating a remaining delay budget associated with the logical channel based at least in part on satisfying a trigger, wherein the remaining delay budget is a portion of a packet delay budget for the logical channel, wherein the trigger is satisfied based at least in part on the remaining delay budget satisfying a remaining delay budget threshold. The operations of 920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 920 may be performed as described in reference to Figure 6 The described delay status reporting manager 635 is executed.

[0154] Fig.10 A flowchart illustrating a method 1000 for supporting delay status reporting for deadline-based scheduling according to one or more aspects of the present disclosure is shown. The operations of the method 1000 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1000 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0155] At 1005, the method may include receiving first control information that identifies a packet delay budget for wireless communication over a logical channel. The operations of 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed as described in reference to Figure 6 The described packet delay budget configuration manager 625 is performed.

[0156] At 1010, the method may include receiving second control information that enables delay status reporting for a PDU associated with a logical channel based on a trigger. The operations of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed as described in reference to Figure 6 The described delay status reporting is configured to be performed by manager 630.

[0157] At 1015, the method may include sending a delay status report indicating a remaining delay budget associated with the logical channel based at least in part on satisfying the trigger, wherein the remaining delay budget is a portion of a packet delay budget for the logical channel. The operations of 1015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed as described in reference to Figure 6 The described delay status reporting manager 635 is executed.

[0158] At 1020, the method may include periodically sending a delay status report, wherein the trigger is satisfied based at least in part on a periodicity parameter of the delay status report. The operations of 1020 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1020 may be performed as described in reference to Figure 6 The described periodic delay status reporting manager 645 is performed.

[0159] The following provides an overview of various aspects of the disclosure:

[0160] Aspect 1: A method for wireless communication at a UE, comprising: receiving first control information, the first control information identifying a packet delay budget for wireless communication via a logical channel; receiving second control information, the second control information enabling a delay status report for a PDU associated with the logical channel based on a trigger; and sending a delay status report indicating a remaining delay budget associated with the PDU associated with the logical channel based at least in part on satisfying the trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

[0161] Aspect 2: The method according to aspect 1 also includes: receiving a remaining delay budget threshold for the logical channel together with the second control information, wherein the trigger is satisfied at least in part based on the remaining delay budget satisfying the remaining delay budget threshold.

[0162] Aspect 3: A method according to aspect 2, wherein the remaining delay budget indicated in the delay status report is a remaining delay budget of a medium access control sub-PDU, a radio link control sub-PDU or a packet data convergence protocol sub-PDU associated with the logical channel.

[0163] Aspect 4: A method according to any one of Aspects 2 to 3, wherein the remaining delay budget indicated in the delay status report is the minimum remaining delay budget of multiple buffered PDUs in the logical channel, and the logical channel has the highest priority among multiple logical channels with delay status reporting enabled and having non-empty buffers.

[0164] Aspect 5: The method according to any one of Aspects 1 to 4, wherein sending the delay status report comprises: periodically sending the delay status report, wherein the trigger is satisfied based at least in part on a periodicity parameter of the delay status report.

[0165] Aspect 6: The method according to any one of aspects 1 to 5, wherein sending the delay status report comprises: sending the delay status report in each part of the PUSCH allocated for filling a PUSCH payload.

[0166] Aspect 7: A method according to any one of Aspects 1 to 6, wherein sending the delay status report comprises: sending the delay status report in conjunction with a buffer status report triggered for the logical channel, wherein the trigger is satisfied at least in part based on the buffer status report being triggered.

[0167] Aspect 8: The method according to any one of aspects 1 to 7, wherein sending the delay status report comprises: sending the delay status report via available PUSCH resources in MAC-CE.

[0168] Aspect 9: The method according to any one of aspects 1 to 8 further includes: receiving an indication of a PUCCH resource used for the delay status report for the logical channel.

[0169] Aspect 10: The method according to aspect 9, wherein sending the delay status report comprises: sending the delay status report via a code point value included in the PUCCH resource, wherein the code point value indicates the remaining delay budget.

[0170] Aspect 11: The method according to any one of aspects 9 to 10, wherein the trigger is associated with sending the delay status report via the PUCCH resource.

[0171] Aspect 12: A method according to any one of Aspects 9 to 11, wherein sending the delay status report comprises: sending the delay status report via the PUCCH resource at multiple transmission instances according to one of the first control information or the second control information.

[0172] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the packet delay budget comprises at least one of a packet delay budget for a QoS flow associated with the logical channel or a PDU set delay budget for a QoS flow associated with the logical channel.

[0173] Aspect 14: An apparatus for performing wireless communications at a UE, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions, the instructions being executable by the at least one processor to enable the UE to perform a method according to any one of Aspects 1 to 12.

[0174] Aspect 15: An apparatus for performing wireless communication at a UE, comprising: at least one component for performing the method according to any one of aspects 1 to 12.

[0175] Aspect 16: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by at least one processor to perform the method according to any one of aspects 1 to 12.

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

[0177] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDM, and other systems and radio technologies not explicitly mentioned herein, including future systems and radio technologies. Components within a wireless communication system may be coupled to each other (e.g., operatively coupled, communicatively coupled, functionally coupled, electronically coupled, and / or electrically coupled).

[0178] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

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

[0180] The functions described herein can be implemented in the form of hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether it is described in software, firmware, middleware, microcode, hardware description language, or other terms. When implemented in software executed by a processor, the function can be stored on a computer-readable medium as one or more instructions or codes, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software, firmware, hard wiring, or any combination thereof executed by a processor. The features of the implementation function can also be physically located at different locations, including being distributed so that the various parts of the function are implemented at different physical locations.

[0181] Computer-readable media include both non-transient computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another.Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer.As an example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase change memory, compact disk (CD) ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other non-transient medium that can be used to carry or store the desired program code components in the form of instructions or data structures and can be accessed by a general or special-purpose computer or a general or special-purpose processor.Moreover, any connection is appropriately referred to as computer-readable media.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable media. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0182] As used herein (including in the claims), "or" used in a listing of items (e.g., a listing of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive listing, so that, for example, a listing of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items can be adopted individually, or any combination of two or more of the listed items can be adopted. For example, if a composition is described as comprising components A, B, and / or C, the composition can comprise A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.

[0183] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as via searching in a table, database, or other data structure), ascertaining, and similar actions. Furthermore, "determining" may include receiving (such as receiving information or signaling, e.g., receiving information or signaling for determining, receiving information or signaling for identifying), accessing (such as accessing data in a memory or accessing information), etc. Furthermore, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0184] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: at least one processor; as well as a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to: receiving first control information identifying a packet delay budget for wireless communications over a logical channel; receiving second control information that enables delay status reporting for a protocol data unit associated with the logical channel based on a trigger; as well as A delay status report is sent based at least in part on satisfying the trigger, indicating a remaining delay budget associated with protocol data units associated with the logical channel, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

2. The apparatus of claim 1 , wherein the instructions are further executable by the at least one processor to cause the apparatus to: A remaining delay budget threshold for the logical channel is received along with the second control information, wherein the trigger is satisfied based at least in part on the remaining delay budget satisfying the remaining delay budget threshold.

3. The apparatus of claim 2, wherein the remaining delay budget indicated in the delay status report is a remaining delay budget of a medium access control sub-protocol data unit, a radio link control sub-protocol data unit, or a packet data convergence protocol sub-protocol data unit associated with the logical channel.

4. The device according to claim 2, wherein: The remaining delay budget indicated in the delay status report is a minimum remaining delay budget of a plurality of buffered protocol data units in the logical channel, and The logical channel has a highest priority among a plurality of logical channels that have delay status reporting enabled and have a non-empty buffer.

5. The apparatus of claim 1 , wherein the instructions for sending the delay status report are executable by the at least one processor to cause the apparatus to: The delay status report is periodically sent, wherein the trigger is satisfied based at least in part on a periodicity parameter of the delay status report.

6. The apparatus of claim 1 , wherein the instructions for sending the delay status report are executable by the at least one processor to cause the apparatus to: The delay status report is sent in portions of a physical uplink shared channel allocated for filling a physical uplink shared channel payload.

7. The apparatus of claim 1 , wherein the instructions for sending the delay status report are executable by the at least one processor to cause the apparatus to: The delay status report is sent in conjunction with a buffer status report triggered for the logical channel, wherein the trigger is satisfied based at least in part on the buffer status report being triggered.

8. The apparatus of claim 1, wherein the instructions for sending the delay status report are executable by the at least one processor to cause the apparatus to: The delay status report is sent via available physical uplink shared channel resources in a medium access control (MAC) control element.

9. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: An indication of a physical uplink control channel resource to be used for the delay status report for the logical channel is received.

10. The apparatus of claim 9, wherein the instructions for sending the delay status report are executable by the at least one processor to cause the apparatus to: The delay status report is sent via a codepoint value included in the physical uplink control channel resources, wherein the codepoint value is indicative of the remaining delay budget.

11. The apparatus of claim 9, wherein the trigger is associated with sending the delay status report via the physical uplink control channel resources.

12. The apparatus of claim 9, wherein the instructions for sending the delay status report are executable by the at least one processor to cause the apparatus to: The delay status report is transmitted via the physical uplink control channel resources at a plurality of transmission instances according to one of the first control information or the second control information.

13. The apparatus of claim 1, wherein the packet delay budget comprises at least one of a packet delay budget for a quality of service flow associated with the logical channel or a protocol data unit set delay budget for a quality of service flow associated with the logical channel.

14. A method for wireless communication at a user equipment (UE), comprising: receiving first control information identifying a packet delay budget for wireless communications over a logical channel; receiving second control information that enables delay status reporting for a protocol data unit associated with the logical channel based on a trigger; as well as A delay status report is sent based at least in part on satisfying the trigger, indicating a remaining delay budget associated with protocol data units associated with the logical channel, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

15. The method according to claim 14, further comprising: A remaining delay budget threshold for the logical channel is received along with the second control information, wherein the trigger is satisfied based at least in part on the remaining delay budget satisfying the remaining delay budget threshold.

16. The method of claim 15, wherein the remaining delay budget indicated in the delay status report is a remaining delay budget of a medium access control sub-protocol data unit, a radio link control sub-protocol data unit, or a packet data convergence protocol sub-protocol data unit associated with the logical channel.

17. The method of claim 15, wherein: The remaining delay budget indicated in the delay status report is a minimum remaining delay budget of a plurality of buffered protocol data units in the logical channel, and The logical channel has a highest priority among a plurality of logical channels that have delay status reporting enabled and have a non-empty buffer.

18. The method of claim 14, wherein sending the delay status report comprises: The delay status report is periodically sent, wherein the trigger is satisfied based at least in part on a periodicity parameter of the delay status report.

19. The method of claim 14, wherein sending the delay status report comprises: The delay status report is sent in portions of a physical uplink shared channel allocated for filling a physical uplink shared channel payload.

20. The method of claim 14, wherein sending the delay status report comprises: The delay status report is sent in conjunction with a buffer status report triggered for the logical channel, wherein the trigger is satisfied based at least in part on the buffer status report being triggered.

21. The method of claim 14, wherein sending the delay status report comprises: The delay status report is sent via available physical uplink shared channel resources in a medium access control (MAC) control element.

22. The method of claim 14, further comprising: An indication of a physical uplink control channel resource to be used for the delay status report for the logical channel is received.

23. The method of claim 22, wherein sending the delay status report comprises: The delay status report is sent via a codepoint value included in the physical uplink control channel resources, wherein the codepoint value is indicative of the remaining delay budget.

24. The method of claim 22, wherein the trigger is associated with sending the delay status report via the physical uplink control channel resources.

25. The method of claim 22, wherein sending the delay status report comprises: The delay status report is transmitted via the physical uplink control channel resources at a plurality of transmission instances according to one of the first control information or the second control information.

26. An apparatus for wireless communication at a user equipment (UE), comprising: means for receiving first control information identifying a packet delay budget for wireless communications over a logical channel; means for receiving second control information that enables delay status reporting for a protocol data unit associated with the logical channel based on a trigger; as well as Means for sending a delay status report indicating a remaining delay budget associated with protocol data units associated with the logical channel based at least in part on satisfying the trigger, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

27. The apparatus according to claim 26, further comprising: means for receiving, along with the second control information, a remaining delay budget threshold for the logical channel, wherein the trigger is satisfied based at least in part on the remaining delay budget satisfying the remaining delay budget threshold.

28. The apparatus of claim 27, wherein the remaining delay budget indicated in the delay status report is a remaining delay budget of a medium access control sub-protocol data unit, a radio link control sub-protocol data unit, or a packet data convergence protocol sub-protocol data unit associated with the logical channel.

29. The apparatus of claim 27, wherein: The remaining delay budget indicated in the delay status report is a minimum remaining delay budget of a plurality of buffered protocol data units in the logical channel, and The logical channel has a highest priority among a plurality of logical channels that have delay status reporting enabled and have a non-empty buffer.

30. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by at least one processor to: receiving first control information identifying a packet delay budget for wireless communications over a logical channel; receiving second control information that enables delay status reporting for a protocol data unit associated with the logical channel based on a trigger; and A delay status report is sent based at least in part on satisfying the trigger, indicating a remaining delay budget associated with protocol data units associated with the logical channel, wherein the remaining delay budget is a portion of the packet delay budget for the logical channel.

Images