DELAY STATUS REPORT

Description

1 / 55 DELAY STATUS REPORT TECHNICAL FIELD

[0001] This disclosure relates to wireless communications and, more specifically, to user equipment (UE), base station and methods for supporting delay status reporting (DSR). BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may also be known as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terminology. Each network communication device, such as a base station, may support wireless communications to one or multiple user communication devices, which may also be known as user equipment (UE) or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing wireless communication system features (e.g., timing features (e.g., symbols, slots, subframes, frames, or the like) or frequency features (e.g., subcarriers, carriers).In addition, the wireless communications system can support wireless communications in various radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies besides 5G (e.g., sixth generation (6G)).

[0003] A DSR reporting procedure can be used to provide the base station with the uplink data delay (UL) status. This delay status may include the remaining time (RT) of UL data, which is based on a value of its associated timer at the time of the first symbol of the physical uplink control channel (PUSCH) transmission in which the DSR is transmitted. The reporting procedure Petition 870250088790, dated 09 / 30 / 2025, page 10 / 85 2 / 55 DSR can also be used to provide the base station with the amount of UL data associated with the reported remaining time. The DSR report can improve UL scheduling. SUMMARY

[0004] This disclosure refers to the UE, the base station, and the methods that support the reporting of a DSR. With the UE, the base station, and the methods, during the calculation of the remaining time, the packets in a radio link control entity (RLC) are considered and a data volume of these packets is included in the DSR. Therefore, the data volume in the DSR is accurate.

[0005] Some UE implementations described in this document may include a processor and a processor-coupled transceiver, wherein the processor is configured to: receive, via the transceiver from a base station, at least one remaining time threshold to trigger the report of at least one DSR; trigger a report of at least one DSR based on at least one remaining time threshold;and transmit a first DSR between at least one DSR via the transceiver to the base station, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE Packet Data Convergence Protocol (PDCP) entity and a second data volume of a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets are less than or equal to at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.

[0006] In some implementations, the first set of packets comprises at least one of the following: PDCP service data units (SDUs) for which no PDCP protocol data unit (PDU) has been constructed, whose remaining time is less than or equal to a first remaining time limit between at least one remaining time limit, or PDCP PDUs that do not Petition 870250088790, dated 09 / 30 / 2025, p. 11 / 85 3 / 55 were submitted to lower layers of the PDCP entity, whose remaining time is less than or equal to the first remaining time threshold. The second set of packets comprises at least one of the following: RLC SDUs and RLC SDU segments that were not included in an RLC PDU, whose remaining time is less than or equal to the first remaining time threshold; RLC PDUs that are pending initial transmission, whose remaining time is less than or equal to the first remaining time threshold; or RLC PDUs that are pending retransmission, whose remaining time is less than or equal to the first remaining time threshold.

[0007] In some implementations, the processor is configured to trigger the first DSR report by: based on the determination that the remaining time of a third set of packets is less than or equal to at least a remaining time threshold, triggering the first DSR report, where the third set of packets comprises at least the first set of packets and the second set of packets.

[0008] In some implementations, the remaining time of the third set of packets is the shortest of the remaining times of the packets in the third set of packets.

[0009] In some implementations, the third set of packets comprises at least one of the following: PDCP SDUs for which no PDCP PDU has been constructed, PDCP PDUs that have not been submitted to lower layers of the PDCP entity, RLC SDUs and RLC SDU segments that have not been included in an RLC PDU, RLC PDUs that are pending initial transmission, or RLC PDUs that are pending retransmission.

[0010] In some implementations, the processor is configured to trigger the first DSR report from the PDCP entity. The processor is further configured to: provide the first data volume of the first packet set from the PDCP entity to a UE MAC entity; and provide the second data volume of the second packet set from the entity of Petition 870250088790, dated 09 / 30 / 2025, page 12 / 85 4 / 55 RLC for the MAC entity.

[0011] In some implementations, the processor is further configured to provide, from the PDCP entity to at least one of the RLC entities or the MAC entity, an indication that the first DSR report has been triggered.

[0012] In some implementations, the processor is further configured to: receive, via the transceiver from the base station, an indication that all protocol data units (PDUs) in a PDU set should be discarded if any of the PDUs are not successfully transmitted to the base station. The first sum comprises a data volume of all PDUs in the PDU set to be transmitted if the remaining time of any of the PDUs in the PDU set is less than or equal to at least one remaining time limit.

[0013] In some implementations, the at least one remaining time limit comprises at least one first remaining time limit and a second remaining time limit that is greater than the first remaining time limit. The processor is configured to trigger the first DSR report by one of the PDCP entity, the RLC entity, or a UE MAC entity.The processor is further configured to: provide the first data volume of the first packet set and a third data volume of a third packet set in the PDCP entity from the PDCP entity to the MAC entity, where the remaining time of the first packet set is less than or equal to the first remaining time limit, the remaining time of the third packet set is greater than the first remaining time limit and less than or equal to the second remaining time limit; and provide the second data volume of the second packet set and a fourth data volume of a fourth packet set in the RLC entity from the RLC entity to the MAC entity, where the remaining time of the second packet set is less than or equal to the first remaining time limit. Petition 870250088790, dated 09 / 30 / 2025, p. 13 / 85 5 / 55 The remaining time of the fourth set of packets is greater than the first remaining time limit and less than or equal to the second remaining time limit. The first DSR comprises the first sum of the first data volume and the second data volume, as well as a second sum of the third data volume and the fourth data volume.

[0014] In some implementations, the processor is configured to trigger the first DSR report by a UE MAC entity.

[0015] In some implementations, the processor is further configured to: receive, via the transceiver from the base station, an indication that all PDUs in a PDU set should be discarded if any of the PDUs are not successfully transmitted to the base station. The third packet set comprises a PDCP SDU that first arrives at the PDCP entity and has been successfully transmitted to the base station or has been submitted to a UE MAC entity, in which a PDU associated with the PDCP SDU is included in the PDU set if any of the PDUs in the PDU set belong to the first packet set or the second packet set.

[0016] In some implementations, the processor is configured to trigger the first DSR report by: based on the determination that the remaining time of the first packet set is less than or equal to the remaining time threshold, triggering the first DSR report by the PDCP entity; based on the determination that the remaining time of the second packet set is less than or equal to the remaining time threshold, triggering a second DSR report between at least one DSR by the RLC entity. The processor is further configured to: provide the first data volume of the first packet set from the PDCP entity to a UE MAC entity; and provide the second data volume of the second packet set from the RLC entity to the MAC entity. Petition 870250088790, dated 09 / 30 / 2025, page 14 / 85 6 / 55

[0017] In some implementations, the at least one remaining time limit comprises a first remaining time limit associated with a PDU Set Importance (PSI) value; and the processor is configured to trigger the first DSR report by: based on the determination that the remaining time of at least one set of PDUs with the PSI value is less than or equal to the first remaining time limit, triggering the first DSR report, where the at least one set of PDUs is comprised in the third set of packets.

[0018] In some implementations, the first sum comprises a volume of data from at least one set of PDUs with the PSI value.

[0019] In some implementations, the processor is further configured to determine the first sum of the first data volume and the second data volume when the first DSR report is triggered or at the time of transmission of the first DSR.

[0020] In some implementations, the processor is further configured to provide a request for the first volume of data from a UE MAC entity to the PDCP entity.

[0021] In some implementations, the processor is further configured to provide a request for the second data volume from a UE MAC entity to the RLC entity.

[0022] Some implementations of a base station described in this document may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: transmit, via the transceiver to a UE, at least one remaining time threshold to trigger the report of at least one DSR; and receive, via the transceiver from the UE, a first DSR among at least one DSR, wherein the first DSR comprises at least a first sum of a first volume of Petition 870250088790, dated 09 / 30 / 2025, page 15 / 85 7 / 55 data from a first set of packets in a UE PDCP entity and a second data volume from a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets is less than or equal to at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.

[0023] Some implementations of a method described in this document may include: receiving, in a UE from a base station, at least one remaining time threshold to trigger reporting of at least one DSR; triggering reporting of at least one DSR based on at least one remaining time threshold; and transmitting a first DSR between at least one DSR to the base station, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE PDCP entity and a second data volume of a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets are less than or equal to at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.

[0024] Some implementations of a method described in this document may include: transmitting, from a base station to a UE, at least one remaining time threshold for triggering a report of at least one DSR; and receiving, from the UE, a first DSR among at least one DSR, wherein the first DSR comprises at least a first sum of a first data volume from a first set of packets in a UE PDCP entity and a second data volume from a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets is less than or equal to one of at least one remaining time threshold, and the remaining time is associated with the discard timer of Petition 870250088790, dated 09 / 30 / 2025, p. 16 / 85 8 / 55 PDCP.

[0025] Some implementations of a processor described in this document may include at least one memory and a controller coupled to at least one memory and configured to make the controller: receive, from a base station, at least one remaining time threshold to trigger the report of at least one DSR; trigger a report of at least one DSR based on at least one remaining time threshold; and transmit a first DSR between at least one DSR to the base station, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE PDCP entity and a second data volume of a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets are less than or equal to one of at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.

[0026] It is important to emphasize that the summary section is not intended to identify key or essential features of the modalities of this disclosure, nor to be used to limit the scope of this disclosure. Other features of this disclosure will become easily understandable through the description below. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 illustrates an example of a wireless communications system that supports reporting of a DSR in accordance with aspects of this disclosure; Figure 2 illustrates a signaling diagram illustrating an example process that supports reporting of a DSR in accordance with aspects of this disclosure; Figure 3 illustrates an example process that supports reporting a DSR in accordance with aspects of this disclosure; Figure 4 illustrates a signaling diagram showing a Petition 870250088790, dated 09 / 30 / 2025, page 17 / 85 9 / 55 Example process supporting DSR reporting in accordance with aspects of this disclosure; Figure 5 illustrates an example process that supports reporting a DSR in accordance with aspects of this disclosure; Figure 6 illustrates a signaling diagram illustrating an example process that supports reporting of a DSR in accordance with aspects of this disclosure; Figure 7 illustrates an example process that supports reporting a DSR in accordance with aspects of this disclosure; Figure 8 illustrates a signaling diagram illustrating an example process that supports reporting of a DSR in accordance with aspects of this disclosure; Figure 9 illustrates a signaling diagram illustrating an example process that supports reporting of a DSR in accordance with aspects of this disclosure; Figure 10 illustrates an example of a device that supports reporting of a DSR and discarding based on a synchronization transmission set in accordance with some aspects of the present disclosure; Figure 11 illustrates an example of a processor that supports reporting a DSR discard based on a synchronization transmission set in accordance with aspects of this disclosure; and Figures 12 and 13 illustrate a flowchart of a method that supports reporting a DSR in accordance with aspects of this disclosure, respectively. DETAILED DESCRIPTION

[0028] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and assist those skilled in the art in understanding and implementing this disclosure, without suggesting any limitation as to its scope. The disclosure described in this Petition 870250088790, dated 09 / 30 / 2025, p. 18 / 85 10 / 55 document can be implemented in several ways beyond those described below.

[0029] In the description and claims that follow, unless otherwise defined, all technical and scientific terms used in this document have the same meaning commonly understood by a person with common knowledge in the field to which this disclosure pertains.

[0030] References in this disclosure to “a modality,” “an example modality,” “a modality,” “some modalities,” and the like indicate that the modality(ies) described may include a specific feature, structure, or characteristic, but it is not necessary that every modality includes the specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same modality(ies). Moreover, when a specific feature, structure, or characteristic is described in connection with a modality, it is understood that it is within the knowledge of a person skilled in the art to affect such feature, structure, or characteristic in connection with other modalities, whether explicitly described or not.

[0031] It should be understood that, although the terms “first” and “second” or similar terms may be used in this document to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element, and similarly, a second element may also be referred to as a first element, without departing from the scope of the modalities. As used in this document, the term “and / or” includes any and all combinations of one or more of the terms listed.

[0032] The terminology used in this document is intended only for the description of specific modalities and is not intended to limit Petition 870250088790, dated 09 / 30 / 2025, page 19 / 85 11 / 55 exemplary forms. As used in this document, the singular forms a, an and the should also include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the terms includes, comprising, has, having, includes and / or including, when used in this document, specify the presence of the resources, elements and / or components etc. declared, but do not preclude the presence or addition of one or more other resources, elements, components and / or combinations thereof.

[0033] As described above, the DSR reporting procedure is used to provide the base station with the UL data delay status. A separate MAC CE for DSR reporting can be defined. For example, DSR reporting cannot be coupled with buffer status reporting (BSR). Additionally, a UE can support threshold-based DSR reporting.

[0034] The existing PDCP discard mechanism causes a UE to calculate the remaining time and trigger the DSR erroneously for the reasons discussed below.

[0035] It is agreed that the UE calculates the remaining time based on the value of a PDCP discard timer and that the DSR report is triggered when the remaining delay of the UL data is less than or equal to a threshold configured by a base station. The threshold can be configured per logical channel group (LCG).

[0036] However, a PDCP entity in the UE does not interrupt the PDCP discard timer and discard a PDCP Service Data Unit (SDU), even if the PDCP SDU has been successfully transmitted to the base station. It is specified that when the discard timer expires for a PDCP SDU, or successful delivery of the PDCP SDU is confirmed by the PDCP status report, the transmitting PDCP entity must discard the PDCP SDU along with the corresponding PDCP Data PDU. If the corresponding PDCP Data PDU has already been transmitted, the PDCP SDU will be discarded. Petition 870250088790, dated 09 / 30 / 2025, p. 20 / 85 12 / 55 has been sent to lower layers, disposal will be indicated for lower layers.

[0037] According to the specification above, the UE only discards the PDCP SDU when the PDCP discard time expires and the successful delivery of a PDCP PDU is confirmed by the PDCP status report. The UE must not discard the PDCP SDU and interrupt the PDCP discard time even if the PDCP SDU has been successfully transmitted to the base station.

[0038] Because a PDCP SDU that has been successfully transmitted is not discarded and the corresponding PDCP discard timer is not stopped, the UE may calculate the remaining time and trigger the DSR erroneously.

[0039] Furthermore, it is necessary to resolve how to handle packets to be transmitted or retransmitted in a UE radio link control entity (RLC) for the calculation of remaining time and data volume reporting.

[0040] Currently, it is assumed that the remaining delay calculation and DSR triggering are performed in a UE PDCP entity. However, some packets may have been sent to the RLC entity and may be about to be transmitted or retransmitted in the RLC entity. The remaining time and the data volume corresponding to this data must also be considered in the DSR. Otherwise, the data volume in the DSR will not be accurate. Therefore, it is necessary to resolve how to handle packets to be transmitted or retransmitted in the RLC entity for the remaining time calculation and data volume reporting.

[0041] In view of the foregoing, this disclosure provides a solution that supports the reporting of a DSR. In this solution, an UE receives, from a base station, at least one remaining time limit to trigger the report of at least one DSR. The UE triggers the report of at least one DSR based on the at least one remaining time limit. In turn, the UE transmits Petition 870250088790, dated 09 / 30 / 2025, p. 21 / 85 13 / 55 a first DSR among at least one DSR for a base station. The first DSR comprises at least a first sum of a first data volume from a first set of packets in a UE PDCP entity and a second data volume from a second set of packets in a UE RLC entity. The remaining time of the first set of packets and the second set of packets is less than or equal to at least one remaining time threshold, and the remaining time is associated with a PDCP discard timer. With this solution, during the calculation of the remaining time, the packets in the RLC entity are considered and a data volume of these packets is included in the DSR. Therefore, the data volume in the DSR is accurate.

[0042] Aspects of the present disclosure are described in the context of a wireless communications system.

[0043] Figure 1 illustrates an example of a wireless communications system 100 that supports the reporting of a DSR in accordance with aspects of this disclosure. The wireless communications system 100 may include at least one of the following network entities 102 (also referred to as network equipment (NE)), one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE Enhanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network.In other implementations, the 100 wireless communications system may be a combination of a 4G network and a 5G network, or other suitable radio access technology, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20 standards. The 100 wireless communications system may support radio access technologies beyond 5G. Petition 870250088790, dated 09 / 30 / 2025, page 22 / 85 14 / 55 In addition, the 100 wireless communications system can support technologies such as time-division multiple access (TDMA), frequency-division multiple access (FDMA), or code-division multiple access (CDMA), etc.

[0044] Network entities 102 may be collectively referred to as network entities 102 or individually referred to as a network entity 102.

[0045] Network entities 102 may be dispersed over a geographical region to form the wireless communications system 100. One or more of the network entities 102 described in this document may be, include, or be referred to as a network node, a base station (BS), a network element, a radio access network (RAN) node, a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0046] A network entity 102 can provide a geographic coverage area 112 for which the network entity 102 can support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 can support wireless communication of service-related signals (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, a network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can be Petition 870250088790, dated 09 / 30 / 2025, page 23 / 85 15 / 55 overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described in this document may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0047] One or more UEs 104 may be dispersed across a geographic region of the wireless communications system 100. A UE 104 may include or be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

[0048] One or more UEs 104 can be devices of different forms or have different capabilities. Some examples of UEs 104 are illustrated in Figure 1. A UE 104 may be able to communicate with various types of devices, such as network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or other network equipment), as Petition 870250088790, dated 09 / 30 / 2025, page 24 / 85 16 / 55 shown in Figure 1. Additionally, or alternatively, a UE 104 can support communication with other network entities 102 or UEs 104, which can act as relays in the wireless communication system 100.

[0049] A UE 104 may also be able to support wireless communication directly with other UE 104s via a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or cellular-V2X deployments, the communication link 114 may be referred to as a side link. For example, a UE 104 may support wireless communication directly with another UE 104 via a PC5 interface.

[0050] A network entity 102 can support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 can interact with the core network 106 through one or more backhaul links 116 (for example, through an S1, N2, N2 interface or another network). Network entities 102 can communicate with each other through the backhaul links 116 (for example, through an X2, Xn interface or another network). In some implementations, network entities 102 can communicate with each other directly (for example, between network entities 102). In some other implementations, network entities 102 can communicate with each other indirectly (for example, through the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC).An ANC can communicate with one or more UEs 104 through one or more other access network transmission entities, which may be called radio heads. Petition 870250088790, dated 09 / 30 / 2025, page 25 / 85 17 / 55 smart or transmit-receive points (TRPs).

[0051] In some implementations, a 102 network entity can be configured in a disaggregated architecture, which can be configured to utilize a protocol stack distributed physically or logically between two or more 102 network entities, such as an Integrated Access Backhaul Network (IAB), an Open Radio Access Network (O-RAN) (e.g., an O-RAN Alliance-sponsored network configuration), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a 102 network entity might include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), an Intelligent RAN Controller (RIC) (e.g., a Near RT(RT) RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0052] A RU may also be called a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of the 102 network entities in a disaggregated RAN architecture may be colocated, or one or more components of the 102 network entities may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more 102 network entities of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0053] The division of functionality between a CU, a DU, and a RU can be flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed in a CU, a DU, or an RU. For example, a Petition 870250088790, dated 09 / 30 / 2025, p. 26 / 85 18 / 55 A functional split of a protocol stack can be employed between a CU and a DU so that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU may host higher protocol layer functionality and signaling (e.g., a layer 3 (L3), a layer 2 (L2)) (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). A CU can be connected to one or more DUs or RUs, and the one or more DUs or RUs can host lower protocol layers, such as a layer 1 (L1) (e.g., physical layer (PHY)) or an L2 (e.g., radio link control layer (RLC), medium access control layer (MAC)) functionality and signaling, and each can be at least partially controlled by the CU 160.

[0054] Additionally, or alternatively, a functional split of the protocol stack can be employed between a DU and a RU so that the DU can support one or more layers of the protocol stack and the RU can support one or more different layers of the protocol stack. The DU can support one or multiple different cells (e.g., through one or more RUs). In some implementations, a functional split between a CU and a DU, or between a DU and an RU, can be within a protocol layer (e.g., some functions for a protocol layer can be performed by a CU, a DU, or an RU, while other protocol layer functions are performed by a different CU, DU, or RU).

[0055] A CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU can be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1u), and a DU can be connected to one or more RUs via a Petition 870250088790, dated 09 / 30 / 2025, p. 27 / 85 19 / 55 fronthaul communication link (e.g., open fronthaul (FH) interface). In some implementations, a midhaul communication link or a fronthaul communication link may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

[0056] The 106 core network can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The 106 core network can be an evolved packet core (EPC) or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), mobility and access management functions (AMF)) and a user plane entity that routes packets or interconnects external networks (e.g., a service gateway (S-GW), a packet data network gateway (PDN) (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.).) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0057] The core network 106 can communicate with the packet data network 108 through one or more backhaul links 116 (for example, through an S1, N2, N2 interface or other network). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (for example, a Protocol Data Unit (PDU) session or similar) with the core network 106 through a network entity 102. The network Petition 870250088790, dated 09 / 30 / 2025, page 28 / 85 Core 106 20 / 55 can route traffic (e.g., control information, data, and the like) between UE 104 and application server 118 using the established session (e.g., the established PDU session). The PDU session can be an example of a logical connection between UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0058] In the wireless communications system 100, network entities 102 and UEs 104 can use resources of the wireless communications system 100 (e.g., timing resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, network entities 102 and UEs 104 can support different resource structures. For example, network entities 102 and UEs 104 can support different frame structures. In some implementations, such as in 4G, network entities 102 and UEs 104 can support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, network entities 102 and UEs 104 can support multiple frame structures (e.g., multiple frame structures).Network entities 102 and UEs 104 can support various frame structures based on one or more numerologies.

[0059] One or more numerologies may be supported in the 100 wireless communications system, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may use one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., Petition 870250088790, dated 09 / 30 / 2025, p. 29 / 85 21 / 55 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) can be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0060] A time interval of a resource (for example, a communication resource) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include several subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0061] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on one or more numerologies supported in the 100 wireless communication system. For example, the first, second, third, fourth, and fifth numerologies (i.e., μ = 0, μ = 1, μ = 2, μ = 3, μ = 4) associated with the respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may use a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot can include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some Petition 870250088790, dated 09 / 30 / 2025, p. 30 / 85 In 22 / 55 implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that the reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0062] In the 100 wireless communications system, an electromagnetic (EM) spectrum can be divided, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the 100 wireless communications system can support one or multiple operating frequency bands, such as frequency band designations FR1 (510 MHz - 7.125 GHz), FR2 (24.25 GHz — 52.6 GHz), FR3 (7.125 GHz — 24.25 GHz), FR4 (52.6 GHz — 114.25 GHz), FR4a or FR4-1 (52.6 GHz — 71 GHz) and FR5 (114.25 GHz — 300 GHz). In some implementations, network entities 102 and UEs 104 can perform wireless communications in one or more of the operating frequency bands. In some implementations, FR1 can be used by network entities 102 and UEs 104, among other equipment or devices, for cellular communications traffic (e.g., control information, data).In some implementations, FR2 can be used by network entities 102 and UEs 104, among other equipment or devices for short-range, high-data-rate capabilities.

[0063] FR1 can be associated with one or multiple numerologies (for example, at least three numerologies). For example, FR1 can be associated with a first numerology (for example, μ=0), Petition 870250088790, dated 09 / 30 / 2025, p. 31 / 85 23 / 55 which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2), which includes 60 kHz subcarrier spacing. FR2 can be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 can be associated with a third numerology (e.g., μ=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3), which includes 120 kHz subcarrier spacing.

[0064] Figure 2 illustrates a signaling diagram illustrating an example process 200 that supports reporting of a DSR in accordance with aspects of this disclosure. Process 200 may involve UE 104 and base station 102 in Figure 1. For the purposes of discussion, process 200 will be described with reference to Figure 1.

[0065] As shown in Figure 2, UE 104 receives 210, from base station 102, at least one remaining time threshold to trigger a report of at least one DSR.

[0066] In some implementations, at least one remaining time threshold can be configured to trigger reporting of at least one DSR to a data radio carrier (DRB) or to an LCG.

[0067] In some implementations, at least one remaining time threshold can be set by a radio resource control (RRC) message.

[0068] In turn, the UE 104 triggers 220 reports of at least one DSR based on at least one remaining time threshold.

[0069] Next, UE 104 transmits 230 a first DSR between at least one DSR to base station 102. The first DSR comprises at least a first sum of a first data volume from a first set of packets in a PDCP entity of UE 104 and a second data volume from a second set of packets in an RLC entity of UE 104. The remaining time of Petition 870250088790, dated 09 / 30 / 2025, page 32 / 85 24 / 55 The first set of packets and the second set of packets is less than or equal to at least one remaining time threshold, and the remaining time is associated with a PDCP discard timer.

[0070] With process 200, during the calculation of the remaining time, the packets to be transmitted or retransmitted in the RLC entity are considered and a data volume of these packets is included in the DSR. Therefore, the data volume in the DSR is accurate.

[0071] Next, some implementations of process 200 will be described with reference to Figures 3 to 13.

[0072] Figure 3 illustrates an example of process 300 that supports reporting of a DSR in accordance with aspects of this disclosure. Process 300 can be considered as an example of the implementation of process 200. Process 300 may involve UE 104 and base station 102 in Figure 1. For the purposes of discussion, process 300 will be described with reference to Figure 1.

[0073] In process 300, the UE 104 PDCP entity triggers a DSR report if the remaining time of a third packet set is less than or equal to a remaining time threshold. The third packet set comprises at least the first packet set and the second packet set. The PDCP entity provides the first data volume of the first packet set in the PDCP entity to the MAC entity. In addition, the PDCP entity may provide an indication to at least one of the RLC entities or the MAC entity. The indication indicates that the DSR report has been triggered. Hereafter, the indication will also be referred to as the DSR-triggered indication for brevity.

[0074] The RLC entity provides the second data volume of the second set of packets in the RLC entity to the MAC entity.

[0075] The MAC entity transmits a MAC control element (CE) to a DSR for base station 102. From here on, Petition 870250088790, dated 09 / 30 / 2025, page 33 / 85 25 / 55 A MAC CE for a DSR will also be referred to as DSR MAC CE, for simplicity. The DSR MAC CE may comprise a first sum of the first data volume and the second data volume. For example, the DSR MAC CE may comprise a buffer size field that comprises the first sum of the first data volume and the second data volume. The DSR MAC CE may also comprise remaining time information associated with the first sum.

[0076] Figure 4 illustrates a signaling diagram illustrating an example process 400 that supports reporting of a DSR in accordance with aspects of this disclosure. Process 400 can be considered as an example implementation of process 200 or 300. Process 400 may involve UE 104 and base station 102 in Figure 1. For discussion purposes, process 400 will be described with reference to Figure 1.

[0077] As shown in Figure 4, UE 104 receives 410 from base station 102, a remaining time limit for triggering a DSR report.

[0078] In some implementations, the remaining time limit can be configured to trigger the DSR report to a DRB or to an LCG.

[0079] In some implementations, the remaining time limit can be set by an RRC message.

[0080] If the remaining time of a third set of packets is less than or equal to the remaining time limit, the PDCP entity triggers a DSR 420 report.

[0081] In some implementations, the remaining time of the third set of packets is the smallest or shortest of the remaining times of the packets in the third set.

[0082] In some implementations, the remaining time of a packet in the third set is associated with its associated PDCP discard timer. For example, the remaining time is the value of a PDCP discard timer (configured by Petition 870250088790, dated 09 / 30 / 2025, page 34 / 85 26 / 55 (RRC) minus the PDCP discard timer execution time. The PDCP discard timer is initiated upon receiving a PDCP SDU associated with the packet from the UE 104 upper layer. Typically, the PDCP discard timer value is set according to the packet delay budget (PDB) or the PDU set delay budget (PSDB). When the PDCP discard timer expires, the UE 104 must discard the PDCP SDU.

[0083] In some implementations, the third set of packets does not comprise any PDCP SDU that has been successfully transmitted to base station 102. In such implementations, the third set of packets may comprise at least one of the following: PDCP SDUs for which no PDCP PDU has been built, PDCP PDUs that have not been submitted to the lower layers of the PDCP entity, or RLC SDUs or PDUs can be considered as RLC data volume, where RLC data volume can be a quantity of data available for transmission on the RLC entity.

[0084] Since the third set of packets does not comprise any PDCP SDU that was successfully transmitted to base station 102, UE 104 does not erroneously trigger the DSR.

[0085] In some implementations, RLC SDUs or PDUs that can be considered as RLC data volume may comprise at least one of the following: RLC SDUs and RLC SDU segments that were not included in an RLC PDU, where an RLC SDU segment may be a segment of an RLC SDU, RLC PDUs that are pending initial transmission, or RLC PDUs pending retransmission (RLC Acknowledged Mode (AM)).

[0086] In these implementations, during the time calculation Petition 870250088790, dated 09 / 30 / 2025, page 35 / 85 27 / 55 remaining, the packets to be transmitted or retransmitted in the RLC entity are considered and a data volume of these packets is included in the DSR. Therefore, the data volume in the DSR is accurate.

[0087] In some implementations, UE 104 may receive, from base station 102, an indication that all PDUs in a PDU set should be discarded if any of the PDUs are not successfully transmitted to the base station. The indication is also called a pdu-SetDiscard indication. The pduSetDiscard indication can be configured when PDU set integration is required, i.e., all PDUs in the PDU set are required for the application layer on the receiver side to use the PDU set.In such implementations, the third packet set may comprise a PDCP SDU from the PDU set that arrives first at the PDCP entity and has been successfully transmitted to base station 102 or has been sent to the MAC entity, meaning that the remaining time of the first PDU from the PDU set is considered to trigger the DSR reporting procedure if there are any PDUs from the PDU set pending transmission or retransmission at the PDCP entity or the RLC entity. A PDU from the PDU set associated with the PDCP SDU is included in the first packet set if any of the PDUs in the PDU set belong to the first or second packet set.

[0088] The PDCP entity provides 430 the first data volume of the first set of packets in the PDCP entity to the MAC entity.

[0089] In some implementations, the PDCP entity may provide the first data volume of the first set of packets in the PDCP entity to the MAC entity when the DSR report is triggered or at the time of DSR transmission. For example, the PDCP entity may provide the first data volume in a subframe or slot in which the DSR is transmitted. Petition 870250088790, dated 09 / 30 / 2025, p. 36 / 85 28 / 55 for base station 102.

[0090] In some implementations, the PDCP entity may receive a request for the first data volume from the MAC entity. Upon receiving the request, the PDCP entity may provide the first data volume to the MAC entity.

[0091] In some implementations, the PDCP entity may also provide the DSR-triggered indication to at least one of the RLC entities or the MAC entity.

[0092] In some implementations, the first set of packages may comprise at least one of the following: PDCP SDUs for which PDCP PDUs have not been built, whose remaining time is less than or equal to a first remaining time limit between at least one remaining time limit, or PDCP PDUs that have not been submitted to the lower layers of the PDCP entity, whose remaining time is less than or equal to the first remaining time limit.

[0093] In some implementations, if UE 104 receives the pdu-SetDiscard indication from base station 102, the first packet set may comprise the remaining PDUs from the PDU set if the remaining time of any of the PDUs in the PDU set is less than or equal to the remaining time limit.

[0094] In some implementations, the PDCP entity may provide the remaining time of the third packet set to the MAC entity.

[0095] The RLC entity provides 440 the second data volume of the second packet set in the RLC entity to the MAC entity.

[0096] In some implementations, the RLC entity may provide the second data volume from the second set of packets in the RLC entity to the MAC entity when the DSR report is triggered or at the time of DSR transmission. For example, the RLC entity may provide the second data volume in a Petition 870250088790, dated 09 / 30 / 2025, p. 37 / 85 29 / 55 subframe or slot in which the DSR is transmitted to base station 102.

[0097] In some implementations, the RLC entity may receive the DSR-triggered indication from the PDCP entity. Upon receiving the DSR-triggered indication, the RLC entity may provide the second data volume of the second packet set in the RLC entity to the MAC entity.

[0098] In some implementations, the RLC entity may receive a request for the second data volume from the MAC entity. Upon receiving the request, the RLC entity may provide the second data volume to the MAC entity.

[0099] In some implementations, the second set of packages may comprise at least one of the following: RLC SDUs and RLC SDU segments that were not included in an RLC PDU, whose remaining time is less than or equal to the first remaining time threshold, RLC PDUs that are pending initial transmission, whose remaining time is less than or equal to the first remaining time limit, or RLC PDUs that are pending retransmission, whose remaining time is less than or equal to the first remaining time limit.

[00100] Consider an example of the first set of packets, the second set of packets, and the third set of packets. In this example, the PDCP discard timer value is equal to 50 ms. The remaining time limit is equal to 15 ms.

[00101] PDCP SDUs for which no PDCP PDU has been built and PDCP PDUs that have not been sent to lower layers may comprise packet #1 (RT=10 ms) and packet #2 (RT=20 ms).

[00102] RLC SDUs and RLC SDU segments that have not yet been included in an RLC PDU, RLC PDUs that are pending initial transmission, and RLC data PDUs that are pending retransmission may comprise packet #3 (RT=12ms) and the Petition 870250088790, dated 09 / 30 / 2025, p. 38 / 85 30 / 55 packet #4 (RT=40ms).

[00103] In this example, the third set of packets may include packet #1 (RT=10 ms), packet #2 (RT=20 ms), packet #3 (RT=12 ms), and packet #4 (RT=40 ms). The first set of packets may include packet #1 (RT=10 ms), and the second set may include packet #3 (RT=12 ms).

[00104] With continuous reference to Figure 4, the MAC entity transmits a DSR MAC CE to base station 102. The DSR MAC CE may comprise the first sum of the first data volume and the second data volume. For example, the DSR MAC CE may comprise a buffer size field that comprises the first sum of the first data volume and the second data volume.

[00105] In some implementations, the first sum of the first data volume and the second data volume may be a total value of the first data volume and the second data volume when the DSR is triggered.

[00106] Alternatively, in some implementations, the first sum of the first data volume and the second data volume may be a total amount of the first data volume and the second data volume at the time the DSR is transmitted to base station 102. For example, the first sum of the first data volume and the second data volume may be a total amount of the first data volume and the second data volume in a subframe or slot in which the DSR is transmitted to base station 102.

[00107] In some implementations, if UE 104 receives the pdu-SetDiscard indication from base station 102, the first sum may comprise a data volume of all PDUs in the set of PDUs to be transmitted if the remaining time of any of the PDUs in the set of PDUs is less than or equal to the remaining time limit.

[00108] In some implementations, the DSR MAC CE can also Petition 870250088790, dated 09 / 30 / 2025, p. 39 / 85 31 / 55 understand the remaining time of the third set of packets, and the remaining time is associated with the first sum of the first data volume and the second data volume. The remaining time of the third set of packets is the smallest or shortest of the remaining times of the packets in the third set.

[00109] In some implementations, the remaining time can be calculated when the DSR is triggered. In this case, the remaining time is indicated by the PDCP entity.

[00110] Alternatively, in some implementations, the remaining time may be calculated at the time of DSR transmission. For example, the remaining time may be calculated in a subframe or slot in which the DSR is transmitted to base station 102. In such implementations, the MAC entity may need to recalculate the remaining time. For example, the reported remaining time is the remaining time indicated by the PDCP entity minus the buffered time of the remaining time indicated by the MAC entity.

[00111] In some implementations, UE 104 may report DSR using the gradual method. In these implementations, DSR may encompass data volumes for different remaining time thresholds. This will be described with reference to Figures 5 and 6.

[00112] Figure 5 illustrates an example of process 500 that supports reporting of a DSR in accordance with aspects of this disclosure. Process 500 can be considered as an example of the implementation of process 200. Process 500 may involve UE 104 and base station 102 in Figure 1. For the purposes of discussion, process 500 will be described with reference to Figure 1.

[00113] In process 500, at least one remaining time threshold can comprise at least one first remaining time threshold (represented by a remaining time threshold #1) and a second remaining time threshold (represented by a remaining time threshold #2). The remaining time threshold #2 is greater than the remaining time threshold #1. Petition 870250088790, dated 09 / 30 / 2025, page 40 / 85 32 / 55

[00114] The UE 104 PDCP entity triggers a DSR report if the remaining time of the third packet set is less than or equal to one of the remaining time limits #1 and #2. The third packet set comprises at least the first packet set and the second packet set.

[00115] The PDCP entity provides the gradual data volumes in the PDCP entity to the MAC entity.

[00116] The RLC entity provides the gradual data volumes in the RLC entity to the MAC entity.

[00117] The MAC entity transmits the DSR MAC CE to base station 102. The DSR MAC CE comprises at least the total amount of data volumes in the PDCP entity and the data volumes in the RLC entity by the graded method.

[00118] Figure 6 illustrates a signaling diagram illustrating an example process 600 that supports reporting of a DSR in accordance with aspects of this disclosure. Process 600 can be considered as an example implementation of process 200 or 500. Process 600 may involve UE 104 and base station 102 in Figure 1. For discussion purposes, process 600 will be described with reference to Figure 1.

[00119] As shown in Figure 6, UE 106 receives 610 from base station 102, the remaining time limit #1 and the remaining time limit #2 to trigger a DSR report. For example, the remaining time limit #1 can be equal to 5 ms and the remaining time limit #2 can be equal to 10 ms. The remaining time limit #1 and the remaining time limit #2 can be set to the same as the single remaining time limit in processes 300 and 400.

[00120] In some implementations, remaining time limit #1 and remaining time limit #2 can be configured to trigger DSR reporting to a DRB or LCG.

[00121] In some implementations, remaining time limit #1 and remaining time limit #2 can be set by Petition 870250088790, dated 09 / 30 / 2025, p. 41 / 85 33 / 55 a message from RRC.

[00122] If the remaining time of the third packet set is less than or equal to one of the remaining time limits #1 and #2, the PDCP entity triggers a 620 DSR report. The third packet set can be defined as the same as processes 300 and 400.

[00123] In some implementations, the PDCP entity may provide a DSR-triggered indication with a corresponding remaining time limit to the MAC entity.

[00124] For example, if the remaining time of the third packet set is less than or equal to remaining time limit #2, but greater than remaining time limit #1, the PDCP entity provides the MAC entity with an indication that the DSR was triggered by remaining time limit #2. If the remaining time is less than or equal to remaining time limit #1, the PDCP entity provides the MAC entity with an indication that the DSR was triggered by remaining time limit #1 or triggered by both remaining time limit #1 and remaining time limit #2. Hereafter, the indication will also be referred to as the DSR-triggered indication, for the sake of brevity.

[00125] The PDCP entity provides 630 gradual data volumes in the PDCP entity for the MAC entity.

[00126] In some implementations, the PDCP entity may provide the gradual data volumes in the PDCP entity to the MAC entity when the DSR report is triggered or at the time of DSR transmission. For example, the PDCP entity may provide the gradual data volumes in the PDCP entity in a subframe or slot in which the DSR is transmitted to base station 102.

[00127] In some implementations, the PDCP entity may receive a request for gradual data volumes in the PDCP entity from the MAC entity. Upon receiving the request, the PDCP entity may provide the gradual data volumes in Petition 870250088790, dated 09 / 30 / 2025, p. 42 / 85 34 / 55 PDCP entity for MAC entity.

[00128] In some implementations, the gradual data volumes in the PDCP entity may comprise a first data volume (represented by data volume #1) of a first set of packets and a third data volume (represented by data volume #3) of a third set of packets in the PDCP entity. The remaining time of the first set of packets is less than or equal to the remaining time limit #1, and the remaining time of the third set of packets is greater than the remaining time limit #1 and less than or equal to the remaining time limit #2. For example, the remaining time of the first set of packets is less than or equal to 5 ms, and the remaining time of the third set of packets may be between 5 ms and 10 ms.

[00129] In some implementations, the first set of packages may comprise at least one of the following: PDCP SDUs for which PDCP PDUs have not been built, whose remaining time is less than or equal to the remaining time limit #1, or PDCP PDUs that have not been submitted to the lower layers of the PDCP entity, whose remaining time is less than or equal to the remaining time limit #1.

[00130] In some implementations, the third set of packages may comprise at least one of the following: PDCP SDUs for which PDCP PDUs have not been built, whose remaining time is greater than remaining time limit #1 and less than or equal to remaining time limit #2, or PDCP PDUs that have not been submitted to the lower layers of the PDCP entity, whose remaining time is greater than the remaining time limit #1 and less than or equal to the remaining time limit #2.

[00131] In some implementations, if UE 104 receives the pdu-SetDiscard indication from base station 102, the first set of packets may comprise the remaining PDUs of Petition 870250088790, dated 09 / 30 / 2025, p. 43 / 85 35 / 55 set of PDUs if the remaining time of any of the PDUs in the set of PDUs is less than or equal to the remaining time limit #1.

[00132] In some implementations, the PDCP entity may provide the remaining time of the third packet set to the MAC entity.

[00133] The RLC entity provides 640 gradual data volumes in the RLC entity for the MAC entity.

[00134] In some implementations, the RLC entity may provide the gradual data volumes in the RLC entity to the MAC entity when the DSR report is triggered or at the time of DSR transmission. For example, the RLC entity may provide the gradual data volumes in the RLC entity in a subframe or slot in which the DSR is transmitted to base station 102.

[00135] In some implementations, the RLC entity may receive the DSR-triggered indication from the PDCP entity. Upon receiving the DSR-triggered indication, the RLC entity may provide the gradual data volumes in the RLC entity to the MAC entity.

[00136] In some implementations, the RLC entity may receive a request for the gradual data volumes in the RLC entity from the MAC entity. Upon receiving the request, the RLC entity may provide the gradual data volumes in the RLC entity to the MAC entity.

[00137] In some implementations, the gradual data volumes in the RLC entity may comprise a second data volume (represented by data volume #2) from a second set of packets and a fourth data volume (represented by data volume #4) from a fourth set of packets in the RLC entity. The remaining time of the second set of packets is less than or equal to the remaining time limit #1, and the remaining time of the fourth set of packets is greater than the limit of Petition 870250088790, dated 09 / 30 / 2025, p. 44 / 85 36 / 55 remaining time #1 is less than or equal to the remaining time limit #2. For example, the remaining time of the second set of packets is less than or equal to 5 ms, and the remaining time of the fourth set of packets could be between 5 ms and 10 ms.

[00138] In some implementations, the second set of packages may comprise at least one of the following: RLC SDUs and RLC SDU segments that were not included in an RLC PDU, whose remaining time is less than or equal to the remaining time threshold #1, RLC PDUs that are pending initial transmission, whose remaining time is less than or equal to the remaining time limit #1, or RLC PDUs that are pending retransmission, whose remaining time is less than or equal to the remaining time limit #1.

[00139] In some implementations, the fourth set of packages may comprise at least one of the following: RLC SDUs and RLC SDU segments that were not included in an RLC PDU, whose remaining time is greater than remaining time threshold #1 and less than or equal to remaining time threshold #2, RLC PDUs pending initial transmission, whose remaining time is greater than remaining time limit #1 and less than or equal to remaining time limit #2, or RLC PDUs pending retransmission, whose remaining time is greater than remaining time limit #1 and less than or equal to remaining time limit #2.

[00140] The MAC entity transmits a DSR MAC CE to base station 102. The DSR MAC CE may comprise the first sum of the first data volume and the second data volume, as well as a second sum of the third data volume and the fourth data volume. For example, the DSR MAC CE may comprise a buffer size field comprising the first sum and the second sum.

[00141] In some implementations, the first sum may be Petition 870250088790, dated 09 / 30 / 2025, p. 45 / 85 37 / 55 is the total data volume #1 in the PDCP entity and data volume #3 in the RLC entity when the DSR is triggered. The second sum could be the total data volume #2 in the PDCP entity and data volume #4 in the RLC entity when the DSR is triggered.

[00142] Alternatively, in some implementations, the first sum may be a total amount of data volume #1 in the PDCP entity and data volume #3 in the PDCP entity at the time the DSR is transmitted to base station 102. For example, the first sum may be a total amount of data volume #1 in the PDCP entity and data volume #3 in the RLC entity in a subframe or slot in which the DSR is transmitted to base station 102. The second sum may be a total amount of data volume #2 in the PDCP entity and data volume #4 in the RLC entity at the time the DSR is transmitted to base station 102. For example, the second sum may be a total amount of data volume #2 in the PDCP entity and data volume #4 in the RLC entity in a subframe or slot in which the DSR is transmitted to base station 102.

[00143] In some implementations, the DSR MAC CE may also include the gradual remaining time of the third packet set.

[00144] In some implementations, the gradual remaining time of the third set of packets is the smallest or shortest of the remaining times of the packets in the third set.

[00145] Alternatively, in some implementations, the gradual remaining time of the third set of packets may be the smallest of the remaining times of the packets in the third set for each remaining time threshold. For example, the gradual remaining time may comprise the smallest remaining time that is less than or equal to remaining time threshold #1 and the smallest remaining time that is between remaining time threshold #1 and remaining time threshold #2.

[00146] In some implementations, the remaining time is gradual Petition 870250088790, dated 09 / 30 / 2025, page 46 / 85 38 / 55 can be calculated when the DSR is triggered. In this case, the gradual remaining time is indicated by the PDCP entity.

[00147] Alternatively, in some implementations, the gradual remaining time may be calculated at the time of DSR transmission. For example, the gradual remaining time may be calculated in a subframe or slot in which the DSR is transmitted to base station 102. In such implementations, the MAC entity may need to recalculate the gradual remaining time. For example, the reported gradual remaining time is the gradual remaining time indicated by the PDCP entity minus the buffered time of the gradual remaining time indicated in the MAC entity.

[00148] In some implementations, each PDCP entity and RLC entity can trigger a DSR independently. This will be described with reference to Figures 7 and 8.

[00149] Figure 7 illustrates an example of process 700 that supports reporting of a DSR in accordance with aspects of this disclosure. Process 700 can be considered an example of the implementation of process 200. Process 700 may involve UE 104 and base station 102 in Figure 1. For the purposes of discussion, process 700 will be described with reference to Figure 1.

[00150] In process 700, each of the PDCP entity and the RLC entity can trigger a DSR independently.

[00151] Specifically, the PDCP entity triggers a DSR if the remaining time of the first set of packets is less than or equal to a remaining time limit.

[00152] The RLC entity triggers a second DSR if the remaining time of the second packet set is less than or equal to the remaining time limit.

[00153] The PDCP entity provides the first volume of data from the first set of packets to the MAC entity.

[00154] The RLC entity provides the second data volume of the second packet set to the MAC entity.

[00155] The MAC entity transmits the DSR MAC CE to the Petition 870250088790, dated 09 / 30 / 2025, page 47 / 85 39 / 55 base station 102. The DSR MAC CE comprises at least the first sum of the first data volume and the second data volume.

[00156] Figure 8 illustrates a signaling diagram illustrating an example process 800 that supports reporting of a DSR in accordance with aspects of this disclosure. Process 800 can be considered as an example implementation of process 200 or 700. Process 800 may involve UE 104 and base station 102 in Figure 1. For discussion purposes, process 800 will be described with reference to Figure 1.

[00157] Actions 810, 830, and 840 in case 800 are similar to actions 410, 430, and 440 in case 400. Details of these actions are omitted for brevity.

[00158] Process 800 differs from process 400 in actions 820, 825, and 850.

[00159] Specifically, if the remaining time of the first packet set is less than or equal to the remaining time threshold, the PDCP entity triggers 820 to report a first DSR. The first packet set is defined as the same as action 430 in process 400.

[00160] If the remaining time of the second packet set is less than or equal to the remaining time threshold, the RLC entity triggers a second DSR report. The second packet set is defined as the same as action 440 in process 400.

[00161] The MAC entity transmits 850 the first DSR or the second DSR to base station 102. Each of the DSRs and the second DSR comprises a DSR MAC CE. The DSR MAC CE may comprise the first sum of the first data volume and the second data volume. Details of the DSR MAC CE may be the same as described in relation to action 450 in process 400.

[00162] In some implementations, the MAC entity may trigger a DSR. This will be described with reference to Figure 9.

[00163] Figure 9 illustrates a signaling diagram illustrating an example 900 process that supports reporting. Petition 870250088790, dated 09 / 30 / 2025, page 48 / 85 40 / 55 a DSR in accordance with aspects of this disclosure. Process 900 can be considered an example of the implementation of process 200. Process 900 may involve UE 104 and base station 102 in Figure 1. For the purposes of discussion, process 900 will be described with reference to Figure 1.

[00164] Actions 910, 930, 940, and 950 in case 900 are similar to actions 410, 430, 440, and 450 in case 400. Details of these actions are omitted for brevity.

[00165] Process 900 is different from process 400 in a 920 action.

[00166] Specifically, if the remaining time of the third packet set is less than or equal to the remaining time threshold, the MAC entity triggers DSR report 920. The third packet set is defined as the same as in any of the processes 300 to 800.

[00167] In some implementations, sets of PDUs with different PSI values ​​can be configured with different PDCP discard timers. PDU Set Importance (PSI) can be used to identify the relative importance of a set of PDUs compared to other sets of PDUs within a Quality of Service (QoS) flow. In these implementations, a PSI-based DSR can be applied.

[00168] In such implementations, UE 104 receives at least one remaining time limit from base station 102. The at least one remaining time limit may comprise a first remaining time limit associated with a PSI value. In other words, base station 102 may set the remaining time limit by PSI.

[00169] In some implementations, the first remaining time limit associated with the PSI value can be configured to trigger a DSR report for data with a PSI value of a DRB or for an LCG.

[00170] In some implementations, the first time limit Petition 870250088790, dated 09 / 30 / 2025, p. 49 / 85 The remaining 41 / 55 associated with the PSI value can be configured via an RRC message.

[00171] In such implementations, if the remaining time of at least one set of PDUs with the PSI value is less than or equal to the first remaining time threshold, UE 104 triggers the DSR report. The at least one set of PDUs is included in the third set of packages. The third set of packages can be defined as the same as those in process 400. In other words, in the third set of packages, there may be different subsets of packages with different PSI values. During the calculation of the remaining time, UE 104 can only consider packages with the PSI value associated with the first remaining time threshold.

[00172] In turn, UE 104 transmits the DSR to base station 102. The DSR comprises the first sum of the first data volume of the first packet set with the PSI value and the second data volume of the second packet set with the PSI value. For example, the DSR comprises the first sum of the first data volume of the first packet set with the PSI value and the second data volume of the second packet set with the PSI value at the time the DSR is transmitted.

[00173] In some implementations, the DSR may also include a PSI or bitmap indication to show whether the DSR includes the volume of data and / or time remaining for a given PSI value.

[00174] Figure 10 illustrates an example of a 1000 device that supports delay reporting and discarding based on a synchronization transmission set, according to aspects of this disclosure. The 1000 device may be an example of a 102 base station or a 104 UE, as described in this document. The 1000 device may support wireless communication with one or more 102 network entities, 104 UEs, or any combination thereof. The 1000 device may include components Petition 870250088790, dated 09 / 30 / 2025, page 50 / 85 42 / 55 for bidirectional communications, including components for transmitting and receiving communications, such as a processor 1002, a memory 1004, a transceiver 1006 and, optionally, an I / O controller 1008. These components may be in electronic communication or coupled in another way (e.g., operatively, communicatively, functionally, electronically, electrically) by means of one or more interfaces (e.g., buses).

[00175] Processor 1002, memory 1004, transceiver 1006, or various combinations thereof or various components thereof may be examples of means for carrying out various aspects of the present disclosure, as described in this document. For example, processor 1002, memory 1004, transceiver 1006, or various combinations or components thereof may support a method for carrying out one or more of the operations described in this document.

[00176] In some implementations, the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may be implemented in hardware (for example, in communications management circuits). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means to perform the functions described in this disclosure. In some implementations, the processor 1002 and the memory 1004 coupled to the processor 1002 may be configured to perform one or more of the functions described in this document (for example, executing, by the processor 1002, instructions stored in memory 1004).

[00177] For example, the 1002 processor can support Petition 870250088790, dated 09 / 30 / 2025, page 51 / 85 43 / 55 wireless communication on device 1000, according to the examples disclosed in this document. Processor 1002 can be configured to support a means to perform the following: receive, in a UE from a base station, at least one remaining time threshold to trigger the report of at least one DSR; trigger the report of at least one DSR based on the at least one remaining time threshold; and transmit a first DSR between the at least one DSR to the base station, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE PDCP entity and a second data volume of a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets is less than or equal to one of at least one remaining time threshold, and the remaining time associated with the PDCP discard timer.

[00178] Alternatively, in some implementations, the 1002 processor can be configured to be operable to support a means of accomplishing the following: transmitting, from a base station to a UE, at least one remaining time threshold for triggering a report of at least one DSR; and receiving, from the UE, a first DSR among at least one DSR, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE PDCP entity and a second data volume of a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets is less than or equal to one of at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.

[00179] The 1002 processor may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a Petition 870250088790, dated 09 / 30 / 2025, page 52 / 85 44 / 55 programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the 1002 processor may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the 1002 processor. The 1002 processor may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1004) to enable the 1000 device to perform various functions of the present disclosure.

[00180] Memory 1004 may include random access memory (RAM) and read-only memory (ROM). Memory 1004 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1002, cause device 1000 to perform various functions described in this document. The code may be stored in a non-transient, computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executable by processor 1002, but may cause a computer (e.g., when compiled and executed) to perform the functions described in this document. In some implementations, memory 1004 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operation, such as interaction with peripheral components or devices.

[00181] The I / O controller 1008 can manage input and output signals for device 1000. The I / O controller 1008 can also manage peripherals not integrated into device M02. In some implementations, the I / O controller 1008 may represent a physical connection or port for an external peripheral. In some implementations, the I / O controller 1008 may utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another operating system. Petition 870250088790, dated 09 / 30 / 2025, page 53 / 85 45 / 55 known. In some implementations, the 1008 I / O controller may be implemented as part of a processor, such as the 1006 processor. In some implementations, a user may interact with the 1000 device via the 1008 I / O controller or via hardware components controlled by the 1008 I / O controller.

[00182] In some implementations, the 1000 device may include a single 1010 antenna. However, in other implementations, the 1000 device may have more than one 1010 antenna (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The 1006 transceiver may communicate bidirectionally, via one or more 1010 antennas, wired or wireless links, as described in this document. For example, the 1006 transceiver may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The 1006 transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more 1010 antennas for transmission, and to demodulate packets received from one or more 1010 antennas.The 1006 transceiver may include one or more transmit chains, one or more receive chains, or a combination thereof.

[00183] A transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator to modulate data into a carrier signal, preparing the signal for wireless transmission. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain also Petition 870250088790, dated 09 / 30 / 2025, page 54 / 85 46 / 55 may include at least one power amplifier configured to amplify the modulated signal to a power level appropriate for wireless transmission. The transmission chain may also include one or more 1010 antennas to transmit the amplified signal into the air or wirelessly.

[00184] A receiving chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiving chain might include one or more 1010 antennas to receive the signal via aerial or wireless transmission. The receiving chain might include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiving chain might include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during signal transmission. The receiving chain might include at least one decoder to decode and process the demodulated signal to receive the transmitted data.

[00185] Figure 11 illustrates an example of a processor 1100 that supports delay reporting and discarding based on a synchronization transmission set in accordance with aspects of this disclosure. The processor 1100 may be an example of a processor configured to perform various operations according to the examples described in this document. The processor 1100 may include a controller 1102 configured to perform various operations according to the examples described in this document. The processor 1100 may optionally include at least one memory 1104, such as L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1100 may optionally include one or more arithmetic logic units (ALUs) 1106. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, Petition 870250088790, dated 09 / 30 / 2025, page 55 / 85 47 / 55 communicatively, functionally, electronically, electrically) through one or more interfaces (e.g., buses).

[00186] The 1100 processor may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, get, retrieve, transmit, send, forward, store, determine, identify, access, write, read) as described in this document. The processor chipset may include one or more cores, one or more caches (e.g., local memory or memory included in the processor chipset (e.g., the 1100 processor) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), and others).

[00187] The 1102 controller can be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the 1100 processor to enable the 1100 processor to support various operations, as described in the examples in this document. For example, the 1102 controller can operate as a control unit for the 1100 processor, generating control signals that manage the operation of various components of the 1100 processor. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[00188] Controller 1102 can be configured to fetch (e.g., get, retrieve, receive) instructions from memory 1104 and determine the subsequent instruction(s) to be executed. Petition 870250088790, dated 09 / 30 / 2025, p. 56 / 85 48 / 55 executed to enable the 1100 processor to support various operations as described in this document. The 1102 controller can be configured to track the memory address of instructions associated with memory 1104. The 1102 controller can be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the 1102 controller can be configured to interpret the instruction and determine the control signals to be sent to other components of the 1100 processor to enable the 1100 processor to support various operations as described in this document. Additionally, or alternatively, the 1102 controller can be configured to manage the data flow within the 1100 processor. The 1102 controller can be configured to control the data transfer between registers, arithmetic logic units (ALUs), and other functional units of the 1100 processor.

[00189] 1104 memory may include one or more caches (e.g., local memory or memory included in the 1100 processor or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, 1104 memory may reside within or on a processor chipset (e.g., local to the 1100 processor). In some other implementations, 1104 memory may reside externally to the processor chipset (e.g., remote to the 1100 processor).

[00190] Memory 1104 can store computer-readable, computer-executable code, including instructions that, when executed by processor 1100, cause processor 1100 to perform various functions described in this document. The code can be stored in a non-transient computer-readable medium, such as system memory or another type of memory. Controller 1102 and / or processor 1100 can be configured to execute computer-readable instructions stored in Petition 870250088790, dated 09 / 30 / 2025, page 57 / 85 49 / 55 memory 1104 to enable processor 1100 to perform various functions. For example, processor 1100 and / or controller 1102 can be coupled to memory 1104; processor 1100, controller 1102, and memory 1104 can be configured to perform various functions described in this document. In some examples, processor 1100 may include multiple processors, and memory 1104 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described in this document.

[00191] One or more 1106 ALUs can be configured to support various operations as described in this document. In some implementations, one or more 1106 ALUs may reside within or on a processor chipset (e.g., the 1100 processor). In some other implementations, one or more 1106 ALUs may reside externally to the processor chipset (e.g., the 1100 processor). One or more 1106 ALUs can perform one or more calculations, such as addition, subtraction, multiplication, and division, on data. For example, one or more 1106 ALUs may receive input operands and an operation code, which determines an operation to be performed. One or more 1106 ALUs can be configured with a variety of logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation.Additionally, or alternatively, one or more 1106 ALUs can support logical operations such as AND, OR, XOR, NOR, and NAND, allowing one or more 1106 ALUs to handle conditional operations, comparisons, and bitwise operations.

[00192] The 1100 processor can support wireless communication according to the examples disclosed in this document. The 1100 processor can be configured to support a means for Petition 870250088790, dated 09 / 30 / 2025, page 58 / 85 50 / 55 perform the following: receive, in a UE from a base station, at least one remaining time threshold to trigger the report of at least one DSR; trigger the report of at least one DSR based on the at least one remaining time threshold; and transmit a first DSR between the at least one DSR to the base station, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE PDCP entity and a second data volume of a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets is less than or equal to one of at least one remaining time threshold, and the remaining time associated with the PDCP discard timer.

[00193] Alternatively, in some implementations, the 1100 processor can be configured to be operable to support a means of accomplishing the following: transmitting, from a base station to a UE, at least one remaining time threshold to trigger the reporting of at least one DSR; and receiving, from the UE, a first DSR among at least one DSR, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE PDCP entity and a second data volume of a second set of packets in a UE RLC entity, the remaining time of the first set of packets and the second set of packets is less than or equal to one of at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.

[00194] Figure 12 illustrates a flowchart of a 1200 method that supports reporting of a DSR in accordance with aspects of this disclosure. The operations of the 1200 method can be implemented by a device or its components, as described in this document. For example, the operations of the 1200 method can be performed by a UE 104, as described in this Petition 870250088790, dated 09 / 30 / 2025, page 59 / 85 51 / 55 document. In some implementations, the device may execute a set of instructions to control the device's function elements to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[00195] In 1210, the method may include receiving, in an UE from a base station, at least one remaining time threshold to trigger a report from at least one DSR. 1210 operations may be performed according to the examples described in this document. In some implementations, aspects of 1210 operations may be performed by a device as described with reference to Figure 1.

[00196] In 1220, the method may include triggering the reporting of at least one DSR based on at least one remaining time limit. 1220 operations may be performed according to the examples described in this document. In some implementations, aspects of 1220 operations may be performed by a device as described with reference to Figure 1.

[00197] In 1230, the method may include transmitting a first DSR between at least one DSR to the base station. The first DSR comprises at least a first sum of a first data volume from a first set of packets in a UE PDCP entity and a second data volume from a second set of packets in a UE RLC entity, the remaining time of the first and second sets of packets being less than or equal to one of at least one remaining time threshold, and the remaining time associated with the PDCP discard timer. 1220 operations may be performed according to the examples described in this document. In some implementations, aspects of 1220 operations may be performed by a device as described with reference to Figure 1.

[00198] Figure 13 illustrates a flowchart of a 1300 method. Petition 870250088790, dated 09 / 30 / 2025, pp. 60 / 85 52 / 55 which supports reporting of a DSR in accordance with aspects of this disclosure. The operations of method 1300 may be implemented by a device or its components, as described in this document. For example, the operations of method 13 may be performed by a base station 102, as described in this document. In some implementations, the device may execute a set of instructions to control the device's function elements to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[00199] In 1310, the method may include transmitting, from a base station to a UE, at least one remaining time limit to trigger a report of at least one DSR. 1310 operations may be performed according to the examples described in this document. In some implementations, aspects of 1310 operations may be performed by a device as described with reference to Figure 1.

[00200] In 1320, the method may include receiving, from the UE, a first DSR among at least one DSR. The first DSR comprises at least a first sum of a first data volume from a first set of packets in a UE PDCP entity and a second data volume from a second set of packets in a UE RLC entity, the remaining time of the first and second sets of packets being less than or equal to one of at least one remaining time threshold, and the remaining time associated with the PDCP discard timer. 1320 operations may be performed according to the examples described in this document. In some implementations, aspects of 1320 operations may be performed by a device as described with reference to Figure 1.

[00201] It should be noted that the implementations of this disclosure described with reference to Figures 2 to 9 are also applicable to device 1000 and processor 1100. Petition 870250088790, dated 09 / 30 / 2025, pp. 61 / 85 53 / 55 and to methods 1200 and 1300.

[00202] It should be noted that the methods described in this document describe possible implementations, and that operations and steps may be rearranged or modified in other ways, and that other implementations are possible. Furthermore, aspects of two or more methods may be combined.

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

[00204] The functions described in this document may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored or transmitted as one or more instructions or code in a computer-readable medium. Other examples and implementations are within the scope of the disclosure and the appended claims. For example, due to the nature of software, the functions described in this document may be implemented using software executed by a processor, hardware, firmware, cabling, or combinations thereof. Features that implement functions may also be Petition 870250088790, dated 09 / 30 / 2025, page 62 / 85 54 / 55 physically located in various positions, including being distributed in such a way that parts of the functions are implemented in different physical locations.

[00205] Computer-readable media include non-transient storage media and communication media, including any means that facilitate the transfer of a computer program from one place to another. A non-transient storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disc storage or other magnetic storage devices, or any other non-transient medium that can be used to carry or store desired program code media in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[00206] As used in this document, including in the claims, the article "a" before an element is unrestricted and understood as referring to at least one of those elements or to one or more of those elements. The terms "a," "at least one," "one or more," and "at least one of one or more" may be interchangeable. As used in this document, including in the claims, or as used in a list of items (for example, a list of items preceded by a phrase such as "at least one of" or "one or more of" or "one or both of") indicates an inclusive list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used in this document, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, Petition 870250088790, dated 09 / 30 / 2025, pp. 63 / 85 55 / 55 An example step described as being based on condition A may be based on either condition A or condition B, without departing from the scope of this disclosure. In other words, as used in this document, the expression “based on” should be interpreted in the same way as the expression “based at least in part on”. Furthermore, as used in this document, including in the claims, a “set” may include one or more elements.

[00207] The description in this document is provided to enable a person of ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person of ordinary skill in the art, and the generic principles set forth in this document may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described in this document, but should be given the broader scope consistent with the principles and new features disclosed in this document. Petition 870250088790, dated 09 / 30 / 2025, pp. 64 / 85

Claims

1 / 8 CLAIMS 1. User equipment (UE), characterized in that it comprises: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver from a base station, at least one remaining time threshold to trigger the reporting of at least one Delay Status Report (DSR); trigger the reporting of at least one DSR based on the at least one remaining time threshold; and transmit a first DSR between the at least one DSR via the transceiver to the base station, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE Packet Data Convergence Protocol (PDCP) entity and a second data volume of a second set of packets in a UE Radio Link Control (RLC) entity,The remaining time of the first set of packets and the second set of packets is less than or equal to at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.

2. A UE, according to claim 1, characterized in that: the first set of packets comprises at least one of the following: PDCP service data units (SDUs) for which no PDCP protocol data unit (PDU) has been constructed, whose remaining time is less than or equal to a first remaining time threshold among at least one remaining time threshold, or PDCP PDUs that have not been submitted to the lower layers. Petition 870250088790, dated 09 / 30 / 2025, pp. 65 / 85. 2 / 8 of the PDCP entity, whose remaining time is less than or equal to the first remaining time threshold; and the second set of packets comprises at least one of the following: RLC SDUs and RLC SDU segments that were not included in an RLC PDU, whose remaining time is less than or equal to the first remaining time threshold, RLC PDUs that are pending initial transmission, whose remaining time is less than or equal to the first remaining time threshold, or RLC PDUs that are pending retransmission, whose remaining time is less than or equal to the first remaining time threshold.

3. A device according to claim 1, characterized in that the processor is configured to trigger the first DSR report by: based on the determination that the remaining time of a third set of packets is less than or equal to at least a remaining time threshold, triggering the first DSR report, wherein the third set of packets comprises at least the first set of packets and the second set of packets.

4. EU, according to claim 3, characterized by the fact that the remaining time of the third set of packets is the shortest among the remaining times of the packets in the third set of packets.

5. EU, according to claim 3, characterized in that the third set of packets comprises at least one of the following: PDCP service data units (SDUs) for which no PDCP protocol data units (PDUs) have been constructed, PDCP PDUs that have not been submitted to the lower layers of the PDCP entity, Petition 870250088790, dated 09 / 30 / 2025, page 66 / 85 3 / 8 RLC SDUs and RLC SDU segments that have not been included in an RLC PDU, RLC PDUs that are pending initial transmission, or RLC PDUs that are pending retransmission.

6. UE, according to claim 3, characterized in that: the processor is configured to trigger the first DSR report by the PDCP entity; and the processor is further configured to: provide the first data volume of the first packet set from the PDCP entity to a Medium Access Control (MAC) entity of the UE; and provide the second data volume of the second packet set from the RLC entity to the MAC entity.

7. UE, according to claim 6, characterized in that the processor is further configured to: provide, from the PDCP entity to at least one of the RLC entities or the MAC entity, an indication that the first DSR report has been triggered.

8. A UE, according to claim 6, characterized in that: the processor is further configured to: receive, via the transceiver from the base station, an indication indicating that all protocol data units (PDUs) in a PDU set should be discarded if any of the PDUs is not successfully transmitted to the base station; and the first sum comprises a data volume of all PDUs in the PDU set to be transmitted if the remaining time of any of the PDUs in the PDU set is less than or equal to the remaining time limit of at least one.

9. UE, according to claim 3, characterized by Petition 870250088790, dated 09 / 30 / 2025, p. 67 / 85 4 / 8, in that: the at least one remaining time limit comprises at least a first remaining time limit and a second remaining time limit that is greater than the first remaining time limit; the processor is configured to trigger a report of the first DSR by one of the PDCP entities, the RLC entity, or a Medium Access Control (MAC) entity of the UE; and the processor is further configured to: provide the first data volume of the first packet set and a third data volume of a third packet set in the PDCP entity from the PDCP entity to the MAC entity, where the remaining time of the first packet set is less than or equal to the first remaining time limit, the remaining time of the third packet set is greater than the first remaining time limit and less than or equal to the second remaining time limit;and provide the second data volume of the second packet set and a fourth data volume of a fourth packet set in the RLC entity from the RLC entity to the MAC entity, wherein the remaining time of the second packet set is less than or equal to the first remaining time threshold, the remaining time of the fourth packet set is greater than the first remaining time threshold and less than or equal to the second remaining time threshold; and the first DSR comprises the first sum of the first data volume and the second data volume, as well as a second sum of the third data volume and the fourth data volume.

10. UE, according to claim 3, characterized in that the processor is configured to trigger the first DSR report by a UE medium access control (MAC) entity.

11. UE, according to claim 3, characterized by Petition 870250088790, dated 09 / 30 / 2025, p. 68 / 85 5 / 8, in that: the processor is further configured to: receive, via the transceiver from the base station, an indication indicating that all protocol data units (PDUs) in a PDU set should be discarded if any of the PDUs are not successfully transmitted to the base station; and the third packet set comprises a PDCP service data unit (SDU) that first arrives at the PDCP entity and has been successfully transmitted to the base station or has been sent to a UE medium access control (MAC) entity, wherein a PDU associated with the PDCP SDU is included in the PDU set if any of the PDUs in the PDU set belong to the first packet set or the second packet set.

12. UE, according to claim 1, characterized in that: the processor is configured to trigger the first DSR report by: based on the determination that the remaining time of the first packet set is less than or equal to at least one remaining time threshold, triggering the first DSR report by the PDCP entity; based on the determination that the remaining time of the second packet set is less than or equal to at least one remaining time threshold, triggering a second DSR report by the RLC entity; and the processor is further configured to: provide the first data volume of the first packet set from the PDCP entity to a UE medium access control (MAC) entity; and provide the second data volume of the second packet set from the RLC entity to the MAC entity. Petition 870250088790, dated 09 / 30 / 2025, p. 69 / 85 6 / 8 13. UE, according to claim 3, characterized in that: at least one remaining time threshold comprises a first remaining time threshold associated with a PDU set importance value (PSI); and the processor is configured to trigger the first DSR report by: based on the determination that the remaining time of at least one set of PDUs with the PSI value is less than or equal to the first remaining time threshold, triggering the first DSR report, wherein the at least one set of PDUs is comprised in the third set of packets.

14. EU, according to claim 13, characterized in that the first sum comprises a data volume of at least one set of PDUs with the PSI value.

15. UE, according to claim 1, characterized in that the processor is further configured to: determine the first sum of the first data volume and the second data volume when the first DSR report is triggered or at the time of transmission of the first DSR.

16. UE, according to claim 1, characterized in that the processor is further configured to: provide a request for the first data volume from a UE medium access control (MAC) entity to the PDCP entity.

17. UE, according to claim 1, characterized in that the processor is further configured to: provide a request for the second data volume from a UE medium access control (MAC) entity to the RLC entity.

18. Base station, characterized by the fact that it comprises: a processor; and a transceiver coupled to the processor, Petition 870250088790, dated 09 / 30 / 2025, p.70 / 85 7 / 8 wherein the processor is configured to: transmit, via the transceiver to a user equipment (UE), at least one remaining time threshold to trigger the reporting of at least one Delay Status Report (DSR); and receive, via the transceiver from the UE, a first DSR among at least one DSR, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE Packet Data Convergence Protocol (PDCP) entity and a second data volume of a second set of packets in a UE Radio Link Control (RLC) entity, the remaining time of the first set of packets and the second set of packets is less than or equal to one of at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.

19. Processor for wireless communication, characterized in that it comprises: at least one memory; and a controller coupled to at least one memory and configured to make the controller: receive, from a base station, at least one remaining time threshold to trigger a report of at least one Delay Status Report (DSR); trigger the report of at least one DSR based on the at least one remaining time threshold; and transmit a first DSR between the at least one DSR to the base station, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a UE Data Packet Convergence Protocol (PDCP) entity and a second data volume of a second set of packets in a UE Radio Link Control (RLC) entity, the time Petition 870250088790, dated 09 / 30 / 2025, p.71 / 85 8 / 8 remaining from the first set of packets and the second set of packets is less than or equal to at least one remaining time limit, and the remaining time is associated with the PDCP discard timer.

20. A method for wireless communication, characterized in that it comprises: receiving, in a user equipment (UE) from a base station, at least one remaining time threshold to trigger a report of at least one Delay Status Report (DSR); triggering the report of at least one DSR based on the at least one remaining time threshold; and transmitting a first DSR between the at least one DSR to the base station, wherein the first DSR comprises at least a first sum of a first data volume of a first set of packets in a Packet Data Convergence Protocol (PDCP) entity of the UE and a second data volume of a second set of packets in a Radio Link Control (RLC) entity of the UE, the remaining time of the first set of packets and the second set of packets is less than or equal to one of at least one remaining time threshold, and the remaining time is associated with the PDCP discard timer.Petition 870250088790, dated 09 / 30 / 2025, pp. 72-85.

Images