Delay status reporting enhancement

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for a delay status reporting enhancement. A UE (102) receives (410), from a network entity (104), a configuration for a DSR of data in a logical channel buffer. The configuration indicates a first remaining time threshold for triggering the DSR. The UE (102) transmits (416), to the network entity (104), the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold. The DSR indicates the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel.

Description

DELAY STATUS REPORTING ENHANCEMENTCROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 586,867 filed on September 29, 2023 and U.S. Provisional Application Serial No. 63 / 609,564 filed on December 13, 2023, both entitled “Delay Status Reporting Enhancement”, and which are both expressly incorporated by reference herein in their entireties.TECHNICAL FIELD

[0002] The present disclosure relates generally to wireless communication, and more particularly, to delay status reporting of data in a logical channel buffer.BACKGROUND

[0003] The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR). An architecture for a 5G NR wireless communication system (5GS) includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), a 5G user equipment (UE), etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and / or increased capacity compared to prior generation cellular communication systems.

[0004] Wireless communication systems, in general, provide various telecommunication services (e g., telephony, video, data, messaging, etc.) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies. For example, the UE transmits, to a network entity, a delay status report (DSR) indicating delay information for data that is pending at the UE. There is an opportunity’ to define the DSR in a manner that balances a desire to provide UE pending data information in a timely manner with a desire for limited overhead signaling.BRIEF SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensiveoverview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] Extended reality (XR) data communicated between a user equipment (UE) and a network entity might experience jitter resulting from delay variations at a coderdecoder (codec) that encodes the XR data. Hence, the UE transmits, to the network entity, a delay status report (DSR) to indicate delay information per logical channel (LCH) or per logical channel group (LCG). In an example, the UE transmits the DSR to indicate delay information for a LCH transmit buffer that includes the XR data. In another example, the UE transmits the DSR to indicate delay information for an LCG. The DSR might also apply to reporting non-XR data. The DSR may further indicate a volume of data in the logical channel buffer along with a priority of the data. The network entity uses the information included in the DSR to perform “delay-aware” uplink scheduling of the data in the logical channel buffer (e.g., based on an urgency and / or priority of the data).

[0007] The UE calculates a remaining time until a packet data convergence protocol (PDCP) discard timer expires for a data unit in the logical channel transmit buffer. For example, the UE indicates, to the netw ork entity’ via the DSR, an expiration time (e.g., discard time) of the PDCP discard timer as the remaining delay time until discarding should occur for the data unit in the logical channel buffer. The DSR may indicate, to the network entity, the remaining delay time together with the volume information of the data in the logical channel buffer.

[0008] In some examples, the UE has data pending in multiple logical channel buffers at the same time, but the DSR is only configured to indicate the remaining delay time for one logical channel. Aspects of the present disclosure address the above-noted and other deficiencies by implementing a medium access control-control element (MAC-CE) for the DSR to indicate the remaining delay time and the data volume information for multiple logical channels. The DSR is triggered based on a threshold criterion (e.g., the remaining delay time) being fulfilled for at least one of the logical channels of a LCG.

[0009] According to some aspects, the UE receives from the network entity (and the network entity transmits to the UE) a configuration for a DSR to report about the data in the logical channel buffer. The configuration indicates a first remaining timethreshold for triggering the DSR. The UE transmits to the network entity (and the network entity receives from the UE) the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold. The DSR indicates the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 illustrates a diagram of a wireless communications system that includes a plurality of user equipments (UEs) and network entities in communication over one or more cells according to an embodiment.

[0011] FIG. 2 is a block diagram of an example protocol stack according to which the UE may communicate with network entities.

[0012] FIG. 3 is a diagram illustrating a timeline for a UE reporting delay status associated with protocol data unit (PDU) set discarding.

[0013] FIG. 4 illustrates a signaling diagram for indicating a delay status (DSR) for a plurality of logical channels.

[0014] FIG. 5 illustrates a diagram of data in transmit buffers of a plurality of logical channels included in a same logical channel group.

[0015] FIG. 6 illustrates a diagram of data in transmit buffers of a plurality of logical channels included in a different logical channel group.

[0016] FIG. 7 illustrates a table that indexes the remaining delay time against a first fraction of a time interval for a packet data convergence protocol (PDCP) discard timer.

[0017] FIG. 8 illustrates a table that indexes the remaining delay time against a second fraction of a time interval associated with the threshold for triggering the DSR report.

[0018] FIG. 9 illustrates a table that indexes the remaining delay time against a maximum time interval for the remaining delay time.

[0019] FIG. 10 is a flowchart of a method of wireless communication at a UE according to an embodiment.

[0020] FIG. 11 is a flowchart of a method of wireless communication at a network entity according to an embodiment.

[0021] FIG. 12 is a diagram illustrating a hardware implementation for an example UE apparatus according to some embodiments.

[0022] FIG. 13 is a diagram illustrating a hardware implementation for one or more example network entities according to some embodiments.DETAILED DESCRIPTION

[0023] FIG. 1 illustrates a diagram 100 of a wireless communications system associated with a plurality of cells 190. The wireless communications system includes user equipments (UEs) 102 and base stations / network entities 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, a CU 1 10 is implemented within a RAN node, and one or more DUs 108 may be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 may be implemented to communicate with one or more RUs 106. Any of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). The base station / network entity 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108), may be referred to as a transmission reception point (TRP).

[0024] Operations of the base station 104 and / or network designs may be based on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (IAB) network, an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN), which may also be referred to a cloud radio access network (C- RAN). Disaggregation may include distributing functionality across the two or more units at various physical locations, as well as distributing functionality' for at least one unit virtually, which can enable flexibility in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104d, 104e and / or the RUs 106a, 106b, 106c, 106d may communicate with the UEs 102a, 102b, 102c, 102d, and / or 102s via one or moreradio frequency (RF) access links based on a Uu interface. In examples, multiple RUs 106 and / or base stations 104 may simultaneously serve the UEs 102, such as by intracell and / or inter-cell access links between the UEs 102 and the RUs 106 / base stations 104.

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

[0026] The RUs 106 may be configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions, or lower layer PHY functionality, such as execution of fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RU 106 may be based on the functional split, such as a functional split of lower layers.

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

[0028] Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106, the DU 108, or the CU 110. The base stations 104 provide the UEs 102 with access to a core network 120. For example, the CU 110 of a base station 104 communicates directly with a core network 120 via a backhaul link 164 (e.g., based on a next generation (NG) interface). The base stations 104 may relay communications between the UEs 102 and the core network 120. The core network 120 may include an Access and Mobility Management Function (AMF) 121, a Session Management Function (SMF) 122, a User Plane Function (UPF) 123, a Unified Data Management (UDM) 124, a Gateway Mobile Location Center (GMLC) 125, and / or a Location Management Function (LMF) 126. The core network 120 may also include one or more location servers, which may include the GMLC 125 and the LMF 126, as well as other functional entities. For example, the one or more location servers include one or more location / positioning servers, which may include the GMLC 125 and the LMF 126 in addition to one or more of a position determination entity (PDE). a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like.

[0029] The AMF 121 is the control node that processes the signaling between the UEs 102 and the core network 120. The AMF 121 supports registration management, connection management, mobility management, and other functions. The SMF 122 supports session management and other functions. The UPF 123 supports packet routing, packet forwarding, and other functions. The UDM 124 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The GMLC 125 provides an interface for clients / applications (e.g.. emergency services) for accessing UE positioning information. The LMF 126 receives measurements and assistance information from the NG-RAN and the UEs 102 via the AMF 121 to compute the position of the UEs 102.

[0030] The base stations 104 may be associated with macrocells for higher-power cellular base stations and / or small cells for lower-power cellular base stations. For example, the cell 190e may correspond to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc.A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network.”

[0031] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as uplink (UL) transmissions, whereas transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104d of cell 190d to transmit a downlink / forward link communication to the UE 102d or receive an uplink / reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104d / RU 106d.

[0032] Communication links between the UEs 102 and the base stations 104 / RUs 106 may be based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be associated with one or more carriers. The UEs 102 and the base stations 104 / RUs 106 may utilize a spectrum bandwidth of Y MHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink carriers may be allocated in an asymmetric manner, with more or fewer carriers allocated to either the uplink or the downlink. A primary component carrier and one or more secondary component carriers may be included in the component carriers. The primary' component carrier may be associated with a primary cell (PCell) and a secondary' component carrier may be associated with a secondary' cell (SCell).

[0033] Some UEs 102, such as the UEs 102a and 102s, may perform device-to-device (D2D) communications over sidelink. For example, a sidelink communication / D2D link utilizes a spectrum for a wireless wide area network (WWAN) associated with uplink and downlink communications. Such sidelink / D2D communication may be performed through various wireless communications systems, such as wireless fidelity (Wi-Fi) systems. Bluetooth systems, Long Term Evolution (LTE) systems. New Radio (NR) systems, etc.

[0034] The UEs 102 and the base stations 104 / RUs 106 may each include a plurality of antennas. The plurality of antennas may correspond to antenna elements, antennapanels, and / or antenna arrays that may facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of communication beams 132 to the UE 102b in one or more transmit directions of the RU 106b. The UE 102b may receive the downlink beamformed signal based on a second set of communication beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b may also transmit an uplink beamformed signal (e.g., sounding reference signal (SRS)) to the RU 106b based on the second set of communication beams 134b in one or more transmit directions of the UE 102b. The RU 106b may receive the uplink beamformed signal from the UE 102b in one or more receive directions of the RU 106b. The UE 102b may perform beam training to determine the best receive and transmit directions for the beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104 / RUs 106 may or may not be the same.

[0035] In further examples, beamformed signals may be communicated between a first base station / RU 106a and a second base station 104e. For instance, the base station 104e of the cell 190e may transmit a beamformed signal to the RU 106a based on the communication beams 138 in one or more transmit directions of the base station 104e. The RU 106a may receive the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the downlink beamformed signal from the base station 104e based on UE communication beams 130 in one or more receive directions of the UE 102e. The UE 102e may also transmit an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e may receive the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.

[0036] The base station 104 may include and / or be referred to as a network entity. That is, “network entity'’ may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108. and / or the CU 110. The base station 104 may also include and / or be referred to as a next generation evolved Node B (ng- eNB), a next generation NB (gNB), an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, abasic service set (BSS). an extended service set (ESS), a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station, or a disaggregated base station including one or more RUs 106. DUs 108, and / or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN). In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station / RU 106a. In such cases, the base station 104e can be a master node and the base station / RU 106a can be a secondary node.

[0037] Still referring to FIG. 1 , in certain aspects, any of the UEs 102 may include a delay status report (DSR) component 140 configured to: receive, from a network entity7, a configuration for a DSR of data in a logical channel buffer, the configuration indicating a first remaining time threshold for triggering the DSR; and transmit, to the network entity, the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold, the DSR indicating the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel.

[0038] In certain aspects, any of the base stations 104 or a network entity of the base stations 104 may include an uplink scheduling component 150 configured to: transmit, to a UE, a configuration for a DSR of data in a logical channel buffer, the configuration indicating a first remaining time threshold for triggering the DSR; and receive, from the UE, the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold, the DSR indicating the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel.

[0039] Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. Further, although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G- Advanced and future versions. LTE, LTE-advanced (LTE-A), and other wireless technologies, such as 6G.

[0040] FIG. 2 illustrates an example protocol stack 200 according to which the UE 102 may communicate with an eNB / ng-eNB or a gNB (e.g., one or more of the basestations / network entities 104, 106). In the example stack 200. a physical (PHY) layer 202A of an evolved-universal mobile telecommunications system (UMTS) terrestrial radio access (EUTRA) provides transport channels to the EUTRA medium access control (MAC) sublayer 204A, which in turn provides logical channels to the EUTRA radio link control (RLC) sublayer 206A. The EUTRA RLC sublayer 206A in turn provides REC channels to a EUTRA packet data convergence protocol (PDCP) sublayer 208 and, in some cases, to an NR PDCP sublayer 210.

[0041] Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 in turn may provide data transfer services to the service data adaptation protocol (SDAP) sublayer 212 or a radio resource control (RRC) sublayer (not shown in FIG. 2). The UE 102, in some implementations, supports both the EUTRA and the NR stack as shown in FIG. 2, to support handover between EUTRA and NR base stations and / or to support dual connectivity (DC) over EUTRA and NR interfaces. Further, as illustrated in FIG. 2, the UE 102 may support layering of NR PDCP 210 over EUTRA RLC 206 A, and SDAP sublayer 212 over the NR PDCP sublayer 210.

[0042] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets (e.g., from an internet protocol (IP) layer, layered directly or indirectly over the PDCP layer 208 or 210) that may be referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206A or 206B) that may be referred to as PDUs. On a control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide signaling radio bearers (SRBs) to the RRC sublayer (not shown in FIG. 2) to exchange RRC messages or non-access stratum (NAS) messages, for example. On a user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide data radio bearers (DRBs) to support data exchange. Data exchanged on the NR PDCP sublayer 210 may be SDAP PDUs, IP packets, or Ethernet packets.

[0043] FIG. 3 is a diagram 300 illustrating a timeline for a UE reporting delay status associated with protocol data unit (PDU) set discarding. The UE transmits a DSR to a network entity indicating delay information for a logical channel buffer (e.g., a packet data convergence protocol (PDCP) transmit buffer) that includes PDU sets (e.g., a group of PDUs including extended reality (XR) data such as video frames or video slices) queued for transmission to the network entity. The UE transmits, to thenetwork entity, the DSR via a medium access control-control element (MAC-CE). uplink control information (UCI), etc. The techniques associated with the diagram 300 may be implemented for any of the SDAP layer, the PDCP layer, the RLC layer, or the MAC layer.

[0044] The network entity determines when a network congestion level is nearing or exceeds a threshold. In order to alleviate the network congestion, the network entity configures the UE to discard PDU sets when the network entity detects that the network congestion is nearing or exceeds the threshold. At time tl (also labeled t = 0), the UE receives a first PDU set (e.g., PDU set 1) 314a in a transmit buffer from an application or an upper layer (e.g., as part of an encoder-decoder (codec)) and sets a first discard time interval Tl 334a using a discard timer. A length of the discard time interval Tl 334 may be configured by the network entity7based on a delay budget associated with the PDU set 314. If the first discard timer tracking the time interval Tl 334a expires before the UE transmits the first PDU set 314a, the UE discards the remaining PDUs in the first PDU set 314a at time t2 (e g., the end of the discard time interval Tl 334a). In this FIG. 3 example, the first PDU set 314a is fully transmitted at time instance t=3 and thus the UE does not discard any portion of the first PDU set 314a. If, however, a portion 315a of the first PDU set remained in the buffer at time instance t2 (also labeled instance t=6), the UE would discard that portion 315a after time instance t2.

[0045] At time t3 (also labeled t=2), the UE receives a second PDU set (e.g., PDU set 2) 314b in the buffer from the application or an upper layer and starts another instance of the discard time interval Tl 334b. The UE may have multiple overlapping discard time intervals Tl 334 running simultaneously, where each discard time interval 334 starts when a subsequent PDU set 314 arrives in the buffer. If the discard time interval Tl 334b expires before the UE transmits the second PDU set 314b, the UE discards the second PDU set 314b at time t4. In this FIG. 3 example, the second PDU set 314b is fully transmitted at time instance t=6 and thus the UE does not discard any portion of the second PDU set 314b. Similar to the first PDU set 314a, if a portion 315b of the second PDU set remained in the buffer at time instance t4, the UE would discard that portion 315b after time instance t4.

[0046] The UE may transmit PDUs of the PDU set 314 over multiple physical uplink shared channel (PUSCH) occasions (e.g., multiple slots). As shown in the shaded regions of FIG. 3, the amount of data remaining in the transmit buffer tends to, butdoesn’t have to, decrease with each PUSCH occasion. For example, at t=0. the UE has not transmitted any PDUs of PDU set 1 314a. At t=l, the UE has transmitted a portion of the PDUs of PDU set 1 314a. At t=2, the UE has transmitted an additional portion of the PDUs of PDU set 1 314a with the remaining PDUs indicated by reference numeral 315a, at which time the remaining time T2 336a of the discard time interval T1 334a is below athreshold 356a for triggering the DSR to indicate the delay information for the remainder of the first PDU set 315a. In contrast, to the data in the transmit buffer for PDU set 1 314a, which tends to decrease with each PUSCH occasion, the amount of data in the transmit buffer for PDU set 2 314b does not decrease at every PUSCH occasion. For example, the amount of data in the transmit buffer for PDU set 2 314b remains the same between time instance t=2 and time instance t=3, and then subsequently tends to decrease after time instance t=3.

[0047] FIG. 3 shows the first PDU set 314a and the second PDU set 314b placed into different buffers. In other situations, a single buffer receives multiple PDU Sets at staggered time intervals, and thus not only could the amount of data in a transmit buffer decrease (e.g., PDU Set 1) or stay the same (e.g., PDU Set 2 between t=2 and t=3), but it could also increase. Additionally, although FIG. 3 presumes independent buffers, the same concept applies to buffers that are part of a PDCP entity, part of a LCH, or part of a LCG.

[0048] In order to assist the network entity in scheduling PDU sets from multiple UEs, the UE transmits, to the network entity (e.g., via PUSCH), the DSR indicating the remaining time T2 336a within the discard time interval T1 334a and the amount of PDUs 315a remaining in the transmit buffer. The UE may report the DSR to the network entity periodically or when the remaining time T2 336a fulfills a threshold criterion (e.g., less than or equal to a delay threshold 356a). The network entity configures the UE with a delay threshold value. In some examples, the network entity configures multiple threshold values for a logical channel group.

[0049] The DSR indicates the remaining time T2 336a within the discard time interval T1 334a and the amount of PDUs 315a remaining in the transmit buffer related to the first PDU set 314a. When the remaining time T2336b within the discard time interval T1 334b is below a threshold 356b, the DSR may indicate the amount of PDUs 315b remaining in the transmit buffer related to the second PDU set 314b. The UE transmits the DSR in a first MAC-CE and / or a buffer status report (BSR) in a second MAC-CE, where the second MAC-CE is different from the first MAC-CE. FIG. 4shows a signaling diagram for a UE providing a DSR; and FIG. 5 describes delay status reporting for one logical channel / logical channel group, whereas FIG. 6 describes delay status reporting for multiple logical channels / logical channel groups.

[0050] FIG. 4 illustrates a signaling diagram 400 for indicating a DSR for a plurality of logical channels based on whether a logical channel buffer fulfills a threshold criterion. The signaling diagram 400 includes communication(s) 402 between a UE 102, a network entity 104, and / or a core network 120. For example, the UE 102 performs an initial access procedure, such as a random access channel (RACH) procedure, to synchronize with the network and obtain an identifier (ID) for radio access communications with the network (e.g., radio access communications with the network entity 104 and / or the core network 120).

[0051] The core netw ork 120 (e.g., including an AMF) may transmit 404, to the netw ork entity 104, a core netw ork-to-netw ork entity message. The message may be a next generation application protocol (NGAP) message, such as an initial context setup message, and may indicate UE capabilities, such as whether the UE 102 supports a DSR for multiple logical channels. In other implementations, the netw ork entity 104 receives the UE capability information from another network entity / base station (not shown in FIG. 4), such as a gNB or an eNB. In still further implementations, the network entity 104 receives the UE capability information from the UE 102. For example, the network entity 104 transmits 406 a UE capability enquiry message to the UE 102 and receives 408, in response to the UE capability7enquiry message, the UE capability information indicating the UE capabilities.

[0052] The network entity 104 transmits 410 an RRC configuration message to the UE 102. The RRC configuration message may be based on the UE capability information received 404, 408 from the core netw ork 120, the UE 102, and / or the second netw ork entity / second base station (not shown in FIG. 4). The RRC configuration message indicates logical channel configuration(s), a DSR configuration, etc. For example, the RRC configuration message indicates a threshold criterion for triggering the DSR. The RRC configuration message may indicate per logical channel (LCH) parameters or per logical channel group (LCG) parameters. Thus, the threshold criterion for triggering the DSR may correspond to a remaining delay time for data in the transmit buffer of a LCH or a LCG being less than or equal to a threshold time until the UE 102 would discard the data unit(s) in the transmit buffer. Even though the remaining delay time is less than the threshold, it is still possible that the UE 102 transmits thedata in the transmit buffer before an expiration of the discard timer. However, fulfillment of the threshold criterion for at least one logical channel still triggers the DSR being sent to the network entity 104. The UE 102 transmits 412 an RRC configuration complete message to the network entity 104 in response to being configured based on the RRC configuration message.

[0053] The UE 102 communicates 414, between the UE 102 and the network entity 104 / core network 120, uplink data of the logical channel(s). Based on the RRC configuration, the UE 102 determines 415 whether the threshold criterion is fulfilled. That is, the UE 102 determines 415 whether the logical channel buffer for at least one logical channel includes data with a remaining delay time that fulfills the threshold criterion (e.g., a delay time that is less than or equal to the threshold amount of remaining time until the UE 102 would discard the data). If the threshold criterion is fulfilled, the UE 102 transmits 416. to the network entity 104, the DSR indicating delay information for a plurality of logical channels. The DSR may also indicate a volume of data in the logical channel buffer and / or a priority of the data. If the threshold criterion is not fulfilled, the UE 102 awaits an uplink scheduling grant from the network entity 104, which may be based on a DSR that indicates delay information for only one logical channel.

[0054] The network entity 104 determines 418, based on the DSR, the uplink scheduling for the data in the logical channel buffer. For example, the network entity 104 schedules urgent data and / or high priority data on an uplink transmission that is earlier in time than an uplink transmission for non-urgent data and / or low priority data. The network entity 104 transmits 420, to the UE 102. downlink control information (DCI) to schedule the uplink transmission(s). Based on the uplink scheduling, the UE 102 transmits 422, to the network entity 104, one or more uplink MAC PDUs including the uplink data from the logical channel buffer and indicating the corresponding logical channel IDs. While FIG. 4 shows the DSR signaling between the UE 102 and the network, FIGs. 5-6 illustrate example DSR reports for data pending in the logical channel buffer of various logical channels and / or logical channel groups.

[0055] FIG. 5 illustrates a diagram 500 of data pending in the transmit buffers of a plurality of logical channels 552a-552c included in a same logical channel group 554 and example DSR reports 540a-540c for the data. That is, the diagram 500 illustrates a per LCH configuration for delay status reporting. Each PDCP entity and associated logical channel corresponds to a respective logical channel buffer. That is, PDCPentity 1 550a and LCH 1 552a correspond to a first logical channel buffer with remaining delay time Tl, PDCP entity 2 550b and LCH 2 552b correspond to a second logical channel buffer with remaining delay time T2, and PDCP entity 3 550c and LCH 3 552c correspond to a third logical channel buffer with remaining delay time T3.

[0056] The logical channel buffers of the plurality of logical channels 552a-552c are each associated with a threshold 556a-556c. The thresholds 556a-556c may correspond to a common threshold for LCG 1 554 or multiple thresholds for LCG 1 554 including a first threshold (e.g., threshold 1) 556a for LCH 1 552a, a second threshold 556b (e.g., threshold 2) for LCH 2 552b, and a third threshold 556c (e.g., threshold 3) for LCH 3. In some examples, a subset of the multiple thresholds includes a same threshold (e.g., threshold 1 and threshold 2 are the same value while threshold 3 is different). In other examples, all of the multiple thresholds are different thresholds. Regardless of whether the thresholds 556a-556c are a common threshold for LCG 1 554 or include different thresholds for LCG 1 554, a DSR 540a-540c is triggered for the network entity when the remaining delay time Tl, T2, T3 for at least one of the logical channels 552a-552c is less than or equal to the respective corresponding threshold 556a-556c for the at least one logical channel 556a-556c.

[0057] In a first implementation of the per LCH configuration, the logical channel group includes separate thresholds 556a-556c for the logical channels of the logical channel group (i.e., multiple thresholds per LCG including one / separate threshold per LCH of the LCG). When the remaining delay time Tl, T2, T3 for at least one of the logical channels 552a-552c falls below its respective threshold 556a-556c, the UE may report delay information in the DSR for some or all of the logical channels 552a-552c in LCG 1 554 including the at least one logical channel that fulfills the threshold criterion (e.g., the logical channel with the remaining delay time that falls below the respective threshold). For example, a first DSR 540a indicates delay information for all of the logical channels 552a-552c in LCG 1 554 including even the second logical channel 552b whose remaining delay time does not fulfill the threshold criterion of the second threshold 556b. In another example, a second DSR 540b indicates delay information for a first logical channel 552a that fulfills a first threshold criterion and a second logical channel 552b that does not fulfill a second threshold criterion, but excludes from the second DSR 540b, delay information for another logical channel (e.g., LCH 556c) that fulfills a third threshold criterion. This might be expected when the secondlogical channel 552b has high priority information while the third logical channel 552c has low priority information or recently reported its delay information. In yet another example, a third DSR 540c only reports delay information for logical channels (e.g., LCH 1 552a and LCH 3 552c) that fulfill their respective threshold criterion. While the third DSR 540c illustrates delay information being reported for all of the logical channels that fulfill their respective threshold criterion, the third DSR 540c may alternatively report delay information for a subset (i.e., not all) of the logical channels that fulfill their respective threshold criterion.

[0058] In a second implementation of the per LCH configuration, the logical channel group includes a common threshold 556a-556c for the logical channels of the logical channel group. When the remaining delay time Tl, T2, T3 for at least one of the logical channels 552a-552c falls below the common threshold 556a-556c, the UE may report delay information in the DSR for some or all of the logical channels 552a-552c in LCG 1 554 including the at least one logical channel that fulfills the threshold criterion of the common threshold (e.g., the logical channel with the remaining delay time that falls below the common threshold). The UE reports, in a DSR 540a-540c, the delay information associated with the common threshold using similar DSR configurations (e.g., DSR 504a-540c) as described above in association with the separate / multiple thresholds for different logical channels.

[0059] The DSRs 540a-540c may indicate a LCG ID, a LCH ID, and / or a remaining delay time TN for each logical channel reported in the DSR 540a-540c. The LCH ID may be a legacy LCH ID or an extended logical channel identifier (eLCID). The UE reports the remaining delay time Tl, T2, T3 per LCH. Along with the remaining delay time, the DSR might include an indication of the volume of data associated with each reported delay. The UE may also indicate a priority of the data in the logical channel buffers. The UE may have a maximum number of LCHs that the UE can (or is permitted to) report. The maximum number of LCHs reported via one DSR report 540a-540c may be predefined or explicitly signaled by the network entity (e.g., via RRC configuration). The maximum number of reported LCHs may be configured per LCG. The network entity indicates, to the UE, the LCHs to be reported per LCG (e.g., via the RRC configuration). For example, the network entity selects the LCHs associated with XR traffic.

[0060] The UE may prioritize the reporting of delay information for LCHs of high priority. For example, the network entity configures a PDU set importance (PSI)threshold to indicate a level of data importance for including, in the DSR report 540a- 540c, the delay information of which the importance of the associated data fulfills the PSI threshold. The network entity may enable / disable the PSI threshold to adjust (e.g., reduce) an amount of information reported in the DSR report 540a-540c when the remaining delay time associated with the information is close to an expiration time of the discard timer. A bitmap in the MAC-CE may indicate which LCHs are being reported by the UE. FIG. 5 illustrates a per LCH configuration for delay status reporting, whereas FIG. 6 illustrates a per LCG configuration for delay status reporting.

[0061] FIG. 6 illustrates a diagram 600 of data pending in the transmit buffers of a plurality of logical channels 652, 662 included in different logical channel groups 654, 664 and a corresponding DSR report 640 for the data. For per LCG reporting in the diagram 600, each PDCP entity and associated logical channel corresponds to a respective logical channel buffer. That is, PDCP entity 1 650 and LCH 1 652 correspond to a first logical channel buffer with remaining delay time Tl in LCG 1 654 and PDCP entity' 2 660 and LCH 2 662 correspond to a second logical channel buffer with remaining delay time T2 in LCG 2 664.

[0062] The logical channel buffers of the plurality of logical channels 652-662 are each associated with a threshold 656-666. The threshold 656-666 may correspond to a common threshold across the LCGs 654-664 or different thresholds across the LCGs 654-664 including a first threshold (e.g., threshold 1) 656 associated with LCG 1 654 and a second threshold 666 (e.g., threshold 2) associated with LCG 2 664. Regardless of whether the thresholds 656-666 are a common threshold or separate thresholds across the LCGs 654-664, the DSR 640 is triggered for the network entity when the remaining delay time Tl, T2 associated with at least one of the LCGs 654-664 is less than or equal to the respective threshold 656-666.

[0063] The DSR 640 indicates delay information for a plurality of LCGs. In the diagram 600, the DSR 640 indicates delay information for a first LCG (e.g., LCG 1) 654 associated with a first remaining delay time Tl that fulfills a first threshold criterion and a second LCG (e.g., LCG 2) 664 associated with a second remaining delay time T2 that does not fulfill a second threshold criterion. The DSR 640 may further include or exclude other LCGs (not shown) that fulfill a corresponding threshold criterion. In some examples, the DSR 640 only reports delay information for LCGs (e.g., LCG 1 654) that include a logical channel that fulfills a threshold criterion and does not reportdelay information for other LCGs (e.g., LCG 2 664) that do not include a logical channel that fulfills a threshold criterion. The DSR 640 may report the delay information for all of the LCGs that include a logical channel that fulfills the threshold criterion or a subset of the LCGs that include a logical channel that fulfills the threshold criterion. The DSR 640 may include similar information as described above with respect to the DSRs 540a-540c, such as an LCG ID, an LCH ID, and / or a remaining delay time TN associated with each LCG reported in the DSR 640. As mentioned previously with respect to FIG. 5, the DSR might also include an indication of the volume of data and / or the priority of the data associated with each reported delay. FIGs. 5-6 described threshold(s) for triggering a DSR. FIGs. 7-9 describe various options of how the UE reports remaining delay time.

[0064] FIG. 7 illustrates a table 700 that indexes the remaining delay time against a first fraction of a time interval for a PDCP discard timer. FIG. 8 illustrates a table 800 that indexes the remaining delay time against a second fraction of a time interval associated with the threshold for triggering the DSR report. FIG. 9 illustrates a table 900 that indexes the remaining delay time against a maximum time interval for the remaining delay time.

[0065] The UE may determine the remaining delay per PDU set. In some examples, the remaining delay is based on using a time of arrival, in the buffer, of a first PDU of a PDU Set. In other examples, the remaining delay time is equal to a shortest remaining delay of a PDU that is not yet transmitted from the PDU set. If multiple PDU Sets arrive in the buffer at approximately the same time, the UE may report a single remaining delay for the group of multiple PDU sets along with a total volume of data in buffers for the group of PDU sets.

[0066] If the length of a bit-field in a DSR MAC-CE indicating the remaining time 336 is predefined or configured to the UE 102 as n bits, then a step size of the indicated remaining delay corresponds to Td / 2n. where Td is equal to the PDCPdiscardT imer or the remainingTimeThreshold. Td / 2nmay be rounded up or dow n to the nearest integer, e.g., in unit of milliseconds, slots, OFDM symbols, etc. In another example, where the step size for reporting 416 the remaining delay is predefined, selected, or configured, the number of bits for the reporting 416 is based on the step size. For example, the number of bits in the report corresponds to ceil(log2(Td / step_size)) , where the ceil() function rounds up the output to the nearest integer (e g., in unit of milliseconds, slots, OFDM symbols, etc.) and log2() is a binarylogarithmic function / logarithm of base 2. In an example, if the PDCPdiscardTimer or the remainingTimeThreshold is configured to 10 ms and the step size = 0.5ms, then ceil(log2(10 / 0.5)) =5 bits. That is, the UE 102 uses 5 bits to report 416 the remaining delay in the DSR per LCG.

[0067] In another example, the UE 102 uses a fixed number of bits to report 416 the remaining delay, where the fix number of bits is equal to or less than a predefined number of bits and remaining / unused bits are all set to 0 or all set to 1. For example, if the UE 102 uses 5 bits to report 416 the remaining delay, but the bit-field has 7 bits, the remaining 2 bits are each set to 0 or each set to 1.

[0068] In another example, a logarithmic mapping provides increased granularity for shorter remaining delays that require increased accuracy. For example, to generate k steps that are logarithmically distributed, a parameter scale might be defined as scale = Td / log (1+ k) and step next = step _previous + log (2 + l) *scale, where i is an integer indicating a step index, and where 0 < i < k+1. A plurality of mapping techniques may be predefined or configured to the UE 102, such that the UE 102 may select a mapping with a smallest residual error. The UE 102 may indicate 416 the selected mapping for calculation of the remaining delay in the DSR report. The network entity 104 may configure 410 the UE 102 to report 416 the residual error of the remaining delay mapping and / or statistics about the residual error of the remaining delay mapping. The UE 102 may report residual error information dynamically (e.g., via MAC-CE or DCI) or semi-statically (via RRC). The network entity7104 use the information to adj ust the mapping and improve the accuracy of the reporting. In some examples, the UE 102 indicates 408. to the network entity 104, a capability of the UE 102 for reporting the residual error information.

[0069] The UE 102 may report 416 a buffer size in the DSR report, such as when the UE 102 is configured for PDU Set-based discard and discards an entire PDU set upon expiration of a discard timer for a PDU of the PDU set. PDU Set-based discard techniques are based on reporting the amount of data associated with the remaining delay, which further indicates a total size of all PDUs in a same PDU set as the PDU that triggered the DSR. Configuring or enabling the DSR reporting may be based on the PDU Set-based discard being configured or enabled. In another implementation, the DSR reporting is configured or enabled independently from, or in an absence of, configuration of the PDU Set-based discard to facilitate network scheduling. In another implementation, if PDU Set-based discard is not configured or enabled, theDSR reporting may be based on individual PDU granularity, rather than a granularity of the PDU Set, thereby resulting in the size of the PDU being reported 416 in the buffer size field of the DSR report. In another implementation, if PDU Set-based discard is not configured or enabled, the DSR reporting is based on a granularity of an entire LCG, rather than a PDU Set granularity, thereby resulting in the buffer size field of DSR report indicating the amount of data in buffer for the associated LCG. In another implementation, if PDU-Set based discard is not configured or enabled, the UE 102 disables the DSR reporting or switches to another DSR reporting technique (e.g., a pre-defined or configured DSR reporting technique). In another implementation, the UE 102 supports DSR reporting based on both PDU Set-based reporting and PDU-based reporting. The UE 102 may implement PDU Set-based DSR reporting by default. However, if PDU Set-based discard is not configured or enabled, the UE 102 may implement the PDU-based DSR reporting.

[0070] Each DSR report may be associated with a single BSR table. A single bit in the DSR report indicates which BSR table has been selected by the UE 102 for the buffer size report (e.g., an enhanced BSR table, a legacy BSR table, etc.). In another implementation, the UE 102 uses the enhanced BSR table if the size of the data reported in the buffer size of the DSR report is within a range of the enhanced BSR table. Otherwise, the UE 102 may use a legacy BSR table and may refrain from indicating the BSR table in the DSR report. In another implementation, the network entity 104 configures a BSR table per LCG (e.g., viaRRC) to be used for a buffer size calculation field and / or a buffer size field in the DSR report associated with the reported remaining delay. In another implementation, the enhanced BSR table is predefined and used for the buffer size field in the DSR report to indicate the amount of data associated with each remaining delay.

[0071] The UE 102 may indicate, to the network entity 104, feedback regarding a preferred BSR table to be used per LCG in the DSR report for indicating the buffer status for the amount of data associated with the reported remaining delay. The UE 102 may indicate, to the network entity 104, feedback information in UE Assistance information (UAI) or via RRC.

[0072] In an example, if the DSR is triggered by the remaining delay of a PDU of a PDU Set (e.g., the threshold criterion for the remaining delay is fulfilled 415) and the DSR has not yet been transmitted 416 to the network entity, but a subset PDUs or the PDU Set associated with the DSR has been transmitted prior to the transmission 416 of theDSR. the DSR transmission 416 is updated by the UE 102 with an updated amount of data associated with the remaining delay.

[0073] In an example, if the UE 102 transmits 416, to the network entity 104, the DSR and the network entity 104 decodes the DSR, identifies the remaining delay, and determines from the reported remaining delay that the PDCP discard timer has already expired, the network entity 104 determines that the UE 102 has discarded the data (e.g., PDU or PDU Set) reported 416 in the DSR.

[0074] The UE 102 may cancel transmission 416 of the DSR if the UE 102 receives, from the network entity 104, an RRC re-configuration and deactivates the DSR reporting. Cancellation of the DSR transmission may occur after the UE 102 sends an 'RRC connection reconfiguration complete’ message to the network entity 104. A timeout mechanism for the DSR MAC-CE may be pre-defined or configured. For example, a timer is triggered when the remaining delay fulfills 415 the threshold criterion. If the DSR MAC-CE is not yet transmitted before the timer expires, the UE 102 cancels the transmission. In another example, the UE 102 implements an updated delay threshold and cancels the DSR MAC-CE if the remaining delay fulfils an updated threshold criterion.

[0075] The UE 102 may cancel the DSR when the UL grant(s) are able to accommodate the data to be signaled / indicated by the DSR but not otherwise sufficient to additionally accommodate a MAC-CE for the DSR plus a sub-header of the DSR. The UE may cancel the BSR and the DSR when the UL grant(s) are able to accommodate the data to be signaled / indicated by the DSR but not otherwise sufficient to additionally accommodate a MAC-CE for DSR plus a sub-header of the DSR and a MAC-CE for the BSR plus a sub-header of the BSR.

[0076] If a padding BSR and a DSR are to be transmitted based on the same UL grant and if the padding bits are not sufficient in number to accommodate both the padding BSR and DSR. the UE 102 cancels, drops, or delays the padding BSR and the DSR based on a priority of the padding BSR and the DSR. The remaining delay in the DSR may be reported in unit of milliseconds, slots, OFDM symbols, or a fraction of Td (e.g., 1 / 2, 1 / 3, 1 / 4, etc.), where Td is equal to the PDCPdiscardTimer or the remammgTime Threshold.

[0077] In a first example where the remaining delay is explicitly signaled, the remaining delay is indexed, as illustrated via the rows of table 700, against a fraction of the time interval used for the PDCP discard timer. The remaining delay is rounded-down to anearest indexed level in the DSR table 700 or rounded-down to a smallest time unit (e.g., 5.3 milliseconds is rounded-down to 5 milliseconds). The fraction of the PDCP discard timer is based on a maximum PDCPdiscardTimer value for the remaining delay, where Pl, . . . , P(N-1) are between 0 and 1. The UE selects and reports the time index associated with the interval that corresponds to the remaining delay.

[0078] For example, assume FIG. 3 shows the first PDU of the first PDU set 314a arriving at time instance t=0 and the first PDU of the second PDU set 314b arriving at time instance t=2. Thus, at t=3, the remaining delay for the first PDU set is 5 / 7 of the discard time interval T1 334 and the remaining delay for the second PDU set is 7 / 7 of the discard time interval T1 334. The fractions of this example are provided simply for ease of illustration. Applying these fractions to the table of FIG. 7, N = 7 and thus the indices transmitted for the two discard time intervals would be 2 and 6. Alternatively, N could be normalized to 100 (i.e., 100%) and the indices transmitted could be 42 and 99.

[0079] In a second example where the remaining delay is explicitly signaled, the remaining delay is indexed, as illustrated via the rows of table 800, against a fraction of the time interval used as the threshold amount of time for triggering the DSR. The fraction of the time interval used for the threshold is based on a maximum remaining delay time qual to the threshold time, where Pl P(N-l) are between 0 and 1. The UE similarly selects and reports the time index associated with the interval that corresponds to the remaining delay.

[0080] Continuing the previous example based on FIG. 3, assume the threshold amount of time for triggering the DSR is 5 time units. Thus, at t=3, the remaining delay for the first PDU set is 5 / 5 of the threshold amount of time and the remaining delay for the second PDU set is 7 / 5 of the threshold amount of time. Applying these fractions to the table of FIG. 7, N = 5 and thus the indices transmitted for the two discard time intervals would be 4 and 4 (as the maximum value). Alternatively, N could be normalized to 100 (i.e., 100%) and the indices transmitted could be 99 and 99.

[0081] In a third example where the remaining delay is explicitly signaled, the remaining delay is indexed, as illustrated via the rows of table 900, against a time interval for the remaining delay time. That is. a maximum time interval for the remaining delay time is segmented into smaller intervals, where Tl. . . . , TN are predefined, configured by the network entity (e.g., via RRC configuration), or determined by the UE (e.g.,based on execution of a formula). The UE likewise selects and reports the time index associated with the interval that corresponds to the remaining delay.

[0082] Instead of using index values to indicate the time intervals, the first column of tables 700-900 may include a sequence of bits that maps to the time intervals. The UE reports the sequence of bits to indicate that the remaining delay for the corresponding time interval. The number of bits and / or the number of time intervals may be predefined or configured by the network entity (e.g., via RRC configuration). The DSR tables may be configured similar to a BSR table, where the UE selects the time index associated with the remaining delay. The DSR table includes a first column for DSindex and a second column for DSvalus. The UE maps the remaining delay to a DSvalue and reports the associated DSindex. In some examples, a time step Ts, such as milliseconds, is predefined or configured by the network entity (e.g., via RRC configuration). The UE determines the time index Ti to report to the network entity using the formula Ti = floor (RemainingDelay / Ts) . A value of the remaining delay reported in the DSR may be rounded-down or rounded-up to a closest integer of the utilized time unit (e.g., milliseconds, orthogonal frequency division multiplexing (OFDM) symbols, slots, etc ). Alternatively, each increment could be differently sized (e.g., TI = 10 ms. T2 = 25 ms, T3 = 50 ms, etc).

[0083] Similar to BSR techniques, multiple DSR tables may be predefined or configured for the UE. The UE indicates, to the network entity, a DSR table of the multiple DSR tables via MAC-CE together with an indication of a remaining delay, data volume, and / or data priority. Time thresholds (e.g.. per LCG or per LCH) are dynamically adjusted by the network entity (e.g.. via MAC-CE). Dynamic adjustment of the time threshold provides flexibility for the network entity to adapt to different levels of congestion and netw ork conditions, such as a changing channel quality7. If the UE is to report, to the network entity, both a BSR and a DSR on a same PUSCH, the UE may prioritize either the BSR or the DSR by postponing or dropping one of the BSR or the DSR. In other examples, the UE multiplexes the BSR and the DSR on the same PUSCH.

[0084] The UE may use, for the DSR, one of the BSR tables used for BSR reporting to report the volume of data associated to the remaining delay. The UE reports, in the DSR, an indication of the BSR table used for the reporting of the volume of data. A MAC-CE sub-field in the MAC-CE header of the DSR is dedicated to indicating which BSR table the UE is using for reporting the volume of data in the DSR. Inother examples, the BSR table is predefined or configured (e.g.. via RRC configuration) for the DSR for reporting the volume of data associated with the remaining delays. DSR applies rules as the BSR to select the BSR table for reporting the volume of data associated with the remaining delay (e.g., a threshold on the volume of data to select the BSR table). A threshold for the data volume associated with the delay allows the UE to report the DSR when the remaining delay is below a delay threshold and when the volume of data is above the data volume threshold (i. e. , to avoid reporting for very small amounts of data).

[0085] In some implementations, the UE does not report a DSR for data when a prior DSR for the same data has already been reported. The UE reports the DSR for the highest priority data having the shortest remaining delay. The DSR indicates the data priority together with the remaining delay and the volume of associated data, where the data priority is based on the PSI. The network entity configures the UE to report the DSR on LCG(s) and / or LCH(s) via RRC configuration. The DSR includes an indication of which LCGs / LCHs are included in the report (e.g., the LCGs / LCHs are indicated by bitmap).

[0086] If the network entity does not receive a PUSCH carrying the DSR, the network entity schedules a retransmission of the PUSCH. The UE may perform an updated calculation of the content included in the DSR. In other examples, the UE retransmits the same DSR to allow the network entity to perform soft combining of the initial transmission and the retransmission. Data associated with an expired discard timer is included in the DSR for when a value of the discard timer is less than a threshold, such as when the data includes a high prionty (e.g.. a PSI above a PSI threshold). Scheduling the expired data may avoid error propagation. The network entity may configure two thresholds per LCG / LCH / PDCP entity'. A first threshold of the two thresholds is an upper Threshold T1 and second threshold of the two thresholds is a lower threshold T2. If the remaining delay is below T1 and above T2, the UE reports the DSR. Otherwise, the UE does not report the DSR. If the remaining delay is below T2, the network entity no longer has enough time to decode the DSR and schedule the data before the expiration of the discard timer. FIGs. 4-9 illustrate delay status reporting enhancements. FIGs. 10-11 show methods for implementing one or more aspects of FIGs. 4-9. In particular, FIG. 10 shows an implementation by the UE 102 of the one or more aspects of FIGs. 4-9. FIG. 11 shows an implementation by the network entity' 104 of the one or more aspects of FIGs. 4-9.

[0087] FIG. 10 illustrates a flowchart 1000 of a method of wireless communication at a UE. With reference to FIGs. 1-9, the method may be performed by the UE 102. In embodiments, the UE 102 transmits 1008, to a network entity, UE capability information indicating a capability of the UE for indicating, in a DSR, a first remaining delay time for a first logical channel that fulfills a first threshold criterion and a second remaining delay time for a second logical channel. For example, referring to FIG. 4, the UE 102 transmits 408, to the network entity 104, UE capability information indication the UE capabilities.

[0088] The UE receives 1010. from the network entity, a configuration for the DSR of data in a logical channel buffer — the configuration indicates a first threshold criterion for triggering the DSR. For example, referring to FIG. 4, the UE 102 receives 410, from the network entity 104, an RRC configuration, which may indicate LCH configuration(s), a DSR configuration, etc., including a threshold criterion for triggering the DSR.

[0089] The UE determines 1015 whether the threshold criterion is fulfilled. If the threshold criterion is not fulfilled, the UE awaits reception 1020 of a scheduling DCI from the network entity. If the threshold criterion is fulfilled, the UE transmits 1016, to the network entity, the DSR when the first remaining delay time to a discard of the data in the logical channel buffer of the first logical channel fulfills the first threshold criterion — the DSR indicates the first remaining delay time for the first logical channel that fulfills the first threshold criterion and the second remaining delay time for the second logical channel. For example, referring to FIG. 4, the UE 102 transmits 416, to the network entity 104, the DSR when the UE 102 determines 415 that the threshold criterion is fulfilled.

[0090] The UE receives 1020, from the network entity, DCI scheduling an uplink transmission of the data in the logical channel buffer for the first logical channel within the first remaining delay time and the second logical channel within the second remaining delay time. For example, referring to FIG. 4, the UE 102 receives 420, from the network entity 104, DCI(s) scheduling an uplink transmission based on the DSR. FIG. 10 describes a method from a UE-side of a wireless communication link, whereas FIG. 11 describes a method from a network-side of the wireless communication link.

[0091] FIG. 11 is a flowchart 1100 of a method of wireless communication at a network entity. With reference to FIGs. 1-9, the method may be performed by one or morenetwork entities 104, which may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, and / or the CU 110. In embodiments, the network entity 104 receives 1108, from a UE, UE capability information indicating a capability of the UE for indicating, in a DSR, a first remaining delay time for a first logical channel that fulfills a first threshold criterion and a second remaining delay time for a second logical channel. For example, referring to FIG. 4, the network entity 104 receives 408, from the UE 102, UE capability information indication the UE capabilities.

[0092] The network entity transmits 1110. to the UE, a configuration for the DSR of data in a logical channel buffer — the configuration indicates a first threshold criterion for triggering the DSR. For example, referring to FIG. 4, the network entity 104 transmits 410, to the UE 102, an RRC configuration, which may indicate LCH configuration(s), a DSR configuration, etc., including a threshold criterion for triggering the DSR.

[0093] The network entity receives 1116, from the UE, the DSR when the first remaining delay time to a discard of the data in the logical channel buffer of the first logical channel fulfills the first threshold criterion — the DSR indicates the first remaining delay time for the first logical channel that fulfills the first threshold criterion and the second remaining delay time for the second logical channel. For example, referring to FIG. 4, the network entity 104 receives 416, from the UE 102, the DSR when the UE based on the threshold criterion being fulfilled.

[0094] The network entity 104 determines 1118 uplink scheduling based on the DSR. For example, referring to FIG. 4, the network entity 104 determines 418 the uplink scheduling based on the DSR received 416 from the UE 102.

[0095] The network entity transmits 1120, to the UE, DCI scheduling an uplink transmission of the data in the logical channel buffer for the first logical channel within the first remaining delay time and the second logical channel within the second remaining delay time. For example, referring to FIG. 4. the network entity 104 transmits 420, to the UE 102, DCI(s) scheduling an uplink transmission based on the DSR. A UE apparatus 1202, as described in FIG. 12, may perform the method of flowchart 1000. The one or more network entities 104, as described in FIG. 13, may perform the method of flowchart 1100.

[0096] FIG. 12 is a diagram 1200 illustrating an example of a hardware implementation for a UE apparatus 1202. The UE apparatus 1202 may be the UE 102, a component of the UE 102, or may implement UE functionality. The UE apparatus 1202 mayinclude an application processor 1206, which may have on-chip memory 1206’. In examples, the application processor 1206 may be coupled to a secure digital (SD) card 1208 and / or a display 1210. The application processor 1206 may also be coupled to a sensor(s) module 1212, a power supply 1214, an additional module of memory 1216, a camera 1218. and / or other related components.

[0097] The UE apparatus 1202 may further include a wireless baseband processor 1226, which may be referred to as a modem. The wireless baseband processor 1226 may have on-chip memory 1226'. Along with, and similar to, the application processor 1206. the wireless baseband processor 1226 may also be coupled to the sensor(s) module 1212, the power supply 1214, the additional module of memory 1216, the camera 1218, and / or other related components. The wireless baseband processor 1226 may be additionally coupled to one or more subscriber identity module (SIM) card(s) 1220 and / or one or more transceivers 1230 (e.g.. wireless RF transceivers).

[0098] Within the one or more transceivers 1230. the UE apparatus 1202 may include a Bluetooth module 1232, a WLAN module 1234, an SPS module 1236 (e.g., GNSS module), and / or a cellular module 1238. The Bluetooth module 1232, the WLAN module 1234, the SPS module 1236. and the cellular module 1238 may each include an on-chip transceiver (TRX), or in some cases, just a transmitter (TX) or just a receiver (RX). The Bluetooth module 1232, the WLAN module 1234, the SPS module 1236, and the cellular module 1238 may each include dedicated antennas and / or utilize antennas 1240 for communication with one or more other nodes. For example, the UE apparatus 1202 can communicate through the transceiver(s) 1230 via the antennas 1240 with another UE (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlmk communication), where the network entity 104 may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, or the CU 110.

[0099] The wireless baseband processor 1226 and the application processor 1206 may each include a computer-readable medium / memory 1226', 1206', respectively. The additional module of memory 1216 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1226', 1206', 1216 may be non-transitory. The wireless baseband processor 1226 and the application processor 1206 may each be responsible for general processing, including execution of software stored on the computer-readable medium / memory 1226', 1206', 1216. The software, when executed by the wireless baseband processor 1226 / applicationprocessor 1206, causes the wireless baseband processor 1226 / application processor 1206 to perform the various functions described herein. The computer-readable medium / memon may also be used for storing data that is manipulated by the wireless baseband processor 1226 / application processor 1206 when executing the software. The wireless baseband processor 1226 / application processor 1206 may be a component of the UE 102. The UE apparatus 1202 may be a processor chip (e.g., modem and / or application) and include just the wireless baseband processor 1226 and / or the application processor 1206. In other examples, the UE apparatus 1202 may be the entire UE 102 and include the additional modules of the apparatus 1202.

[0100] As discussed in FIG. 1 and implemented with respect to FIG. 10, the DSR component 140 is configured to: receive, from a network entity, a configuration for a DSR of data in a logical channel buffer, the configuration indicating a first remaining time threshold for triggering the DSR; and transmit, to the network entity, the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold, the DSR indicating the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel. The DSR component 140 may be within the application processor 1206 (e.g., at 140a), the wireless baseband processor 1226 (e.g., at 140b), or both the application processor 1206 and the wireless baseband processor 1226. The DSR component 140a-140b may be one or more hardware components specifically configured to cany' out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm. stored within a computer-readable medium for implementation by the one or more processors, or a combination thereof.

[0101] FIG. 13 is a diagram 1300 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include, or may correspond to, at least one of the RU 106, the DU, 108, or the CU 110. The CU 110 may include a CU processor 1346, which may have on-chip memory 1346'. In some aspects, the CU 110 may further include an additional module of memory’ 1356 and / or a communications interface 1348, both of which may be coupled to the CU processor 1346. The CU 110 can communicate with the DU 108 through a midhaul link 162,such as an Fl interface between the communications interface 1348 of the CU 110 and a communications interface 1328 of the DU 108.

[0102] The DU 108 may include a DU processor 1326, which may have on-chip memory' 1326'. In some aspects, the DU 108 may further include an additional module of memory 1336 and / or the communications interface 1328, both of which may be coupled to the DU processor 1326. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1328 of the DU 108 and a communications interface 1308 of the RU 106.

[0103] The RU 106 may include an RU processor 1306, which may have on-chip memory 1306'. In some aspects, the RU 106 may further include an additional module of memory 1316, the communications interface 1308, and one or more transceivers 1330, all of which may be coupled to the RU processor 1306. The RU 106 may further include antennas 1340. which may be coupled to the one or more transceivers 1330, such that the RU 106 can communicate through the one or more transceivers 1330 via the antennas 1340 with the UE 102.

[0104] The on-chip memory71306', 1326', 1346' and the additional modules of memory71316, 1336, 1356 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1306, 1326, 1346 is responsible for general processing, including execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor(s) 1306, 1326, 1346 causes the processor(s) 1306, 1326, 1346 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) 1306, 1326, 1346 when executing the software. In examples, the uplink scheduling component 150 may sit at any of the one or more network entities 104, such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110. the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106.

[0105] As discussed in FIG. 1 and implemented with respect to FIG. 11, the uplink scheduling component 150 is configured to; transmit, to a UE, a configuration for a DSR of data in a logical channel buffer, the configuration indicating a first remaining time threshold for triggering the DSR; and receive, from the UE, the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold, the DSR indicating thefirst remaining delay time for the first logical channel and a second remaining delay time for a second logical channel. The uplink scheduling component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 1306 (e.g.. at 150a), the DU processor 1326 (e.g., at 150b), and / or the CU processor 1346 (e.g.. at 150c). The uplink scheduling component 150a-150c may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1306, 1326, 1346 configured to perform the stated processes / algorithm, stored within a computer- readable medium for implementation by the one or more processors 1306, 1326, 1346. or a combination thereof.

[0106] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flow charts.

[0107] The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0108] Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0109] An element, or any portion of an element, or any combination of elements may be implemented as a ‘'processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems-on-chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0110] If the functionality described herein is implemented in software, the functions may be stored on, or encoded as, one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer- readable media includes computer storage media and can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer.

[0111] Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, machine learning (ML)-enabled devices, etc. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further toaggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein.

[0112] Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders / summers, etc. Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of varying configurations.

[0113] The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims.

[0114] Reference to an element in the singular does not mean "one and only one" unless specifically stated, but rather '‘one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may”, “might”, and “can”, as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of). The phrase “For example” often carries a similar connotation to “may” and, therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases.

[0115] Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C” or “one or more of A, B, or C” include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiples of A, multiples of B, and / or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set ofelements where the elements number one or more. Terms or articles such as “a”. “an”, and / or “the” may refer to one of an item, feature, element, etc., that the term or article precedes, or may refer to more than one of said item, feature, element, etc. that the term or article precedes. For example, the recitation “a widget” does not preclude reference to multiples of said widget, as “multiple widgets” necessarily includes “a widget”. Hence, the recitation “a widget” may be interpreted as “at least one widget” or, similarly, interpreted as “one or more widgets”.

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

[0117] Reference numbers, as used in the specification and figures, are sometimes cross- referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbers that have different leading numbers but have one or more of the same trailing numbers (e.g., 206, 306, 406, etc., may refer to similar features in the drawings). Hence, like numbers may refer to like actions.

[0118] Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module.” “mechanism.” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A”, where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently.

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

[0120] Example 1 is a method of wireless communication at a UE including: receiving, from a netw ork entity', a configuration for a DSR of data in a logical channel buffer,the configuration indicating a first remaining time threshold for triggering the DSR; and transmitting, to the network entity, the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold, the DSR indicating the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel.

[0121] Example 2 may be combined with Example 1 and includes that the first logical channel is included in a first LCG and the second logical channel is included in a second LCG.

[0122] Example 3 may be combined with Example 2 and includes that the configuration indicates, for the first LCG, the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, the first remaining time threshold being different from the second remaining time threshold, and includes that the second remaining delay time for the second logical channel is less than the second remaining time threshold.

[0123] Example 4 may be combined with Example 2 and includes that the configuration indicates, for the first LCG, the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, the first remaining time threshold being different from the second remaining time threshold, and includes that the second remaining delay time for the second logical channel is not less than the second remaining time threshold.

[0124] Example 5 may be combined with Example 2 and includes that the configuration indicates, for the first LCG. the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, and includes that the first remaining time threshold and the second remaining time threshold are the same, and includes that the second remaining delay time for the second logical channel is less than the second remaining time threshold.

[0125] Example 6 may be combined with Example 2 and includes that the configuration indicates, for the first LCG, the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, and includes that the first remaining time threshold and the second remaining time threshold are the same, and includes that the second remainingdelay time for the second logical channel is not less than the second remaining time threshold.

[0126] Example 7 may be combined with any of Examples 1-6 and further includes receiving the data in the logical channel buffer as a PDU set including a PDU with a shortest remaining delay time in the PDU set, the first remaining delay time indicated in the DSR being equal to the shortest remaining delay time of the PDU in the PDU set.

[0127] Example 8 may be combined with any of Examples 1-7 and includes that the DSR indicates the first remaining delay time using an index for at least one of: a first fraction of time of a PDCP discard timer, a second fraction of time of the first remaining time threshold for triggering the DSR, or a time interval of a maximum for the first remaining delay time.

[0128] Example 9 may be combined with any of Examples 2-8 and includes that the DSR indicates: the first remaining delay time for the first logical channel of the first LCG and the second remaining delay time for the second logical channel of the second LCG based on anumber of bits in a bit field, a buffer size corresponding to an amount of data associated with each of the first remaining delay time and the second remaining delay time based on a volume of the data in the logical channel buffer for the first logical channel and the second logical channel, and LCG IDs of the first LCG and the second LCG.

[0129] Example 10 may be combined with any of Examples 1-9 and further includes receiving, from the network entity, DCI scheduling an uplink transmission of the data in the logical channel buffer for the first logical channel within the first remaining delay time and the second logical channel within the second remaining delay time.

[0130] Example 11 may be combined with Example 10 and further includes cancelling the DSR when the scheduled uplink transmission includes all of the data in the logical channel buffer associated with the DSR.

[0131] Example 12 may be combined with any of Examples 1-11 and further includes receiving, from the netw ork entity, an RRC reconfiguration message, the DSR being cancelled based on the receiving the RRC reconfiguration message.

[0132] Example 13 is a method of wireless communication at a network entity, including: transmitting, to a UE, a configuration for a DSR of data in a logical channel buffer, the configuration indicating a first remaining time threshold for triggering the DSR; and receiving, from the UE, the DSR when a first remaining delay time to a discardof the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold, the DSR indicating the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel.

[0133] Example 14 may be combined with Example 13 and includes that the first logical channel is included in a first LCG and the second logical channel is included in a second LCG.

[0134] Example 15 may be combined with Example 14 and includes that the configuration indicates, for the first LCG, the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, the first remaining time threshold being different from the second remaining time threshold.

[0135] Example 16 may be combined with Example 14 and includes that the configuration indicates, for the first LCG. the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, and includes that the first remaining time threshold and the second remaining time threshold are the same.

[0136] Example 17 may be combined with any of Examples 14-16 and includes that the DSR indicates: the first remaining delay time for the first logical channel of the first LCG and the second remaining delay time for the second logical channel of the second LCG based on anumber of bits in a bit field, a buffer size corresponding to an amount of data associated with each of the first remaining delay time and the second remaining delay time based on a volume of the data in the logical channel buffer for the first logical channel and the second logical channel, and LCG IDs of the first LCG and the second LCG.

[0137] Example 18 may be combined with any of Examples 13-17 and includes that the DSR indicates the first remaining delay time using an index for at least one of: a first fraction of time of a PDCP discard timer, a second fraction of time of the first remaining time threshold for triggering the DSR, or a time interval of a maximum for the first remaining delay time.

[0138] Example 19 may be combined with any of Examples 13-18 and further includes transmitting, to the UE, DCI scheduling an uplink transmission of the data in the logical channel buffer for the first logical channel within the first remaining delay time and the second logical channel within the second remaining delay time.

[0139] Example 20 may be combined with any of Examples 13-19 and further includes transmitting, to the UE, an RRC reconfiguration message, the DSR being cancelled based on the RRC reconfiguration message.

[0140] Example 21 is an apparatus for wireless communication for implementing a method as in any of Examples 1-20.

[0141] Example 22 is an apparatus for wireless communication including means for implementing a method as in any of Examples 1-20.

[0142] Example 23 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of Examples 1-20.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. A method of wireless communication at a user equipment, UE, (102), comprising: receiving (410), from a network entity (104), a configuration for a delay status report, DSR. of data in a logical channel buffer, the configuration indicating a first remaining time threshold for triggering the DSR; and transmitting (416), to the network entity (104), the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold, the DSR indicating the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel.

2. The method of claim 1, wherein the first logical channel is included in a first logical channel group, LCG. and the second logical channel is included in a second LCG.

3. The method of claim 2, wherein the configuration indicates, for the first LCG, the first remaining time threshold for the first logical channel and indicates, for the second LCG. a second remaining time threshold for the second logical channel, the first remaining time threshold being different from the second remaining time threshold, wherein the second remaining delay time for the second logical channel is less than the second remaining time threshold.

4. The method of claim 2. wherein the configuration indicates, for the first LCG. the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, the first remaining time threshold being different from the second remaining time threshold, wherein the second remaining delay time for the second logical channel is not less than the second remaining time threshold.

5. The method of claim 2, wherein the configuration indicates, for the first LCG, the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, wherein the first remaining time threshold and the second remaining time threshold are the same, whereinthe second remaining delay time for the second logical channel is less than the second remaining time threshold.

6. The method of claim 2, wherein the configuration indicates, for the first LCG. the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, wherein the first remaining time threshold and the second remaining time threshold are the same, wherein the second remaining delay time for the second logical channel is not less than the second remaining time threshold.

7. The method of any of claims 1-6, further comprising: receiving the data in the logical channel buffer as a protocol data unit, PDU, set including a PDU with a shortest remaining delay time in the PDU set. the first remaining delay time indicated in the DSR being equal to the shortest remaining delay time of the PDU in the PDU set.

8. The method of any of claims 1-7, wherein the DSR indicates the first remaining delay time using an index for at least one of: a first fraction of time of a packet data convergence protocol, PDCP, discard timer, a second fraction of time of the first remaining time threshold for triggering the DSR, or a time interval of a maximum for the first remaining delay time.

9. The method of any of claims 2-8, wherein the DSR indicates: the first remaining delay time for the first logical channel of the first LCG and the second remaining delay time for the second logical channel of the second LCG based on a number of bits in a bit field, a buffer size corresponding to an amount of data associated with each of the first remaining delay time and the second remaining delay time based on a volume of the data in the logical channel buffer for the first logical channel and the second logical channel, andLCG identifiers, IDs, of the first LCG and the second LCG.

10. The method of any of claims 1-9, further comprising:receiving (420), from the network entity (104), downlink control information. DCI, scheduling an uplink transmission of the data in the logical channel buffer for the first logical channel within the first remaining delay time and the second logical channel within the second remaining delay time.

11. The method of claim 10, further comprising: cancelling the DSR when the scheduled uplink transmission includes all of the data in the logical channel buffer associated with the DSR.

12. The method of any of claims 1-1 1, further comprising: receiving, from the network entity, a radio resource control, RRC, reconfiguration message, the DSR being cancelled based on the receiving the RRC reconfiguration message.

13. A method of wireless communication at a network entity (104), comprising: transmitting (410), to a user equipment, UE, (102), a configuration for a delay status report, DSR, of data in a logical channel buffer, the configuration indicating a first remaining time threshold for triggering the DSR; and receiving (416), from the UE (102), the DSR when a first remaining delay time to a discard of the data in the logical channel buffer of a first logical channel is less than the first remaining time threshold, the DSR indicating the first remaining delay time for the first logical channel and a second remaining delay time for a second logical channel.

14. The method of claim 13, wherein the first logical channel is included in a first logical channel group, LCG, and the second logical channel is included in a second LCG.

15. The method of claim 14. wherein the configuration indicates, for the first LCG. the first remaining time threshold for the first logical channel and indicates, for the second LCG, a second remaining time threshold for the second logical channel, the first remaining time threshold being different from the second remaining time threshold.

16. The method of claim 14, wherein the configuration indicates, for the first LCG, the first remaining time threshold for the first logical channel and indicates, for the secondLCG. a second remaining time threshold for the second logical channel, wherein the first remaining time threshold and the second remaining time threshold are the same.

17. The method of any of claims 14-16, wherein the DSR indicates: the first remaining delay time for the first logical channel of the first LCG and the second remaining delay time for the second logical channel of the second LCG based on a number of bits in a bit field, a buffer size corresponding to an amount of data associated with each of the first remaining delay time and the second remaining delay time based on a volume of the data in the logical channel buffer for the first logical channel and the second logical channel, andLCG identifiers, IDs, of the first LCG and the second LCG.

18. An apparatus for wireless communication comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of claims 1-17.

Images