DELAY STATUS REPORTING

A user equipment (UE) may buffer data associated with a service. A delay status of the data may include an amount of time left before expiration of a timer (e.g., failure of a particular latency requirement) or an identification of data for which a timer has already expired (e.g., data for which the particular latency requirement has not been met). Some aspects described herein enable delay status reporting. For example, a UE may generate and transmit a delay status report identifying a delay status of data to a network node.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for delay status reporting.

BACKGROUND

SUMMARY

A user equipment (UE) may buffer data associated with a service. For example, the UE may have a buffer associated with data for an extended reality (XR) service being provided by the UE or by one or more XR devices in communication with the UE. The data may be associated with different entities, such as a data radio bearer, a logical channel, or a set of logical channels (e.g., a logical channel group). Some data may be associated with a timing criterion. For example, some data may have a latency requirement as part of a service being provided. In this case. XR service may be associated with a particular latency requirement and data associated with the XR service may be subject to the particular latency requirement. In some examples, a delay status of the data may include an amount of time left before expiration of a timer (e.g., failure of a particular latency requirement) or an identification of data for which a timer has already expired (e.g., data for which the particular latency requirement has not been met). A network node may schedule communication resources to ensure that data is not delayed. However, the network node may lack information regarding the data and/or a communication delay associated with the data.

Some aspects described herein enable delay status reporting. For example, a UE may receive information identifying a set of criteria for generating a delay status report and may, when the set of criteria is satisfied, generate and transmit the delay status report to a network node. In this case, the network node may use the delay status report to configure communications on a network, such as by scheduling resources, balancing loads, or changing quality of service parameters, among other examples. In this way, the UE and the network node can improve services being provided on the network, such as by scheduling additional resources to improve XR service latency when XR data is delayed.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving information identifying a set of criteria for delay status reporting. The method may include transmitting, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting information identifying a set of criteria for delay status reporting. The method may include receiving, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive information identifying a set of criteria for delay status reporting. The one or more processors may be configured to transmit, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit information identifying a set of criteria for delay status reporting. The one or more processors may be configured to receive, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive information identifying a set of criteria for delay status reporting. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit information identifying a set of criteria for delay status reporting. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving information identifying a set of criteria for delay status reporting. The apparatus may include means for transmitting, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting information identifying a set of criteria for delay status reporting. The apparatus may include means for receiving, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purposes of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

A user equipment (UE) may buffer data associated with a service. For example, the UE may have a buffer associated with data for an extended reality (XR) service being provided by the UE or by one or more XR devices in communication with the UE. A delay status of the data may include an amount of time left before expiration of a timer (e.g., failure of a particular latency requirement) or an identification of data for which a timer has already expired (e.g., data for which the particular latency requirement has not been met). A network node may schedule communication resources to ensure that data is not delayed. However, the network node may lack information regarding the data and/or a communication delay associated with the data.

Various aspects relate generally to delay status reporting. Some aspects more specifically relate to generation of a delay status report and transmission of a delay status report. In some aspects, a UE may receive information identifying a set of criteria for generating a delay status report. In some aspects, the UE may determine that the set of criteria is satisfied and generate a delay status report in connection with determining that the set of criteria is satisfied. In some aspects, the UE may transmit the delay status report to a network node. The network node may use the delay status report to configure communications on a network, such as by scheduling resources, balancing loads, or changing quality of service parameters, among other examples.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by the UE generating and transmitting a delay status report in connection with satisfaction of a set of configured criteria, the UE and the network node can improve services being provided on the network. For example, the described techniques can enable scheduling of additional resources to improve XR service latency when, for example, XR data is delayed.

In some examples, a network node110may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a network node110or a network node subsystem serving this coverage area, depending on the context in which the term is used. A network node110may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs120with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs120with service subscription. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs120having association with the femto cell (for example, UEs120in a closed subscriber group (CSG)). A network node110for a macro cell may be referred to as a macro network node. A network node110for a pico cell may be referred to as a pico network node. A network node110for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown inFIG.1, the network node110amay be a macro network node for a macro cell102a, the network node110bmay be a pico network node for a pico cell102b, and the network node110cmay be a femto network node for a femto cell102c. A network node may support one or multiple (for example, three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node110that is mobile (for example, a mobile network node).

The wireless network100may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (for example, a network node110or a UE120) and send a transmission of the data to a downstream node (for example, a UE120or a network node110). A relay station may be a UE120that can relay transmissions for other UEs120. In the example shown inFIG.1, the network node110d(for example, a relay network node) may communicate with the network node110a(for example, a macro network node) and the UE120din order to facilitate communication between the network node110aand the UE120d. A network node110that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, or a relay, among other examples.

The wireless network100may be a heterogeneous network that includes network nodes110of different types, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes110may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network100. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts).

The UEs120may be dispersed throughout the wireless network100, and each UE120may be stationary or mobile. A UE120may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. A UE120may be a cellular phone (for example, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (for example, a smart ring or a smart bracelet)), an entertainment device (for example, a music device, a video device, or a satellite radio), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device that is configured to communicate via a wireless or wired medium.

Some UEs120may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, or a location tag, that may communicate with a network node, another device (for example, a remote device), or some other entity. Some UEs120may be considered Internet-of-Things (IOT) devices, or may be implemented as NB-IOT (narrow band IoT) devices. Some UEs120may be considered a Customer Premises Equipment. A UE120may be included inside a housing that houses components of the UE120, such as processor components or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (for example, one or more processors) and the memory components (for example, a memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

In general, any number of wireless networks100may be deployed in a given geographic area. Each wireless network100may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology or an air interface. A frequency may be referred to as a carrier or a frequency channel. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases. NR or 5G RAT networks may be deployed.

In some examples, two or more UEs120(for example, shown as UE120aand UE120e) may communicate directly using one or more sidelink channels (for example, without using a network node110as an intermediary to communicate with one another). For example, the UEs120may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (for example, which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), or a mesh network. In such examples, a UE120may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by the network node110.

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may receive information identifying a set of criteria for delay status reporting: and transmit, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, the network node110may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit information identifying a set of criteria for delay status reporting: and receive, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

At the network node110, a transmit processor220may receive data from a data source212, intended for the UE120(or a set of UEs120). The transmit processor220may select one or more modulation and coding schemes (MCSs) for the UE120using one or more channel quality indicators (CQIs) received from that UE120. The network node110may process (for example, encode and modulate) the data for the UE120using the MCS(s) selected for the UE120and may provide data symbols for the UE120. The transmit processor220may process system information (for example, for semi-static resource partitioning information (SRPI)) and control information (for example, CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor220may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor230may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to a corresponding set of modems232(for example, T modems), shown as modems232athrough232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem232. Each modem232may use a respective modulator component to process a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem232may further use a respective modulator component to process (for example, convert to analog, amplify, filter, or upconvert) the output sample stream to obtain a downlink signal. The modems232athrough232tmay transmit a set of downlink signals (for example, T downlink signals) via a corresponding set of antennas234(for example, T antennas), shown as antennas234athrough234t.

At the UE120, a set of antennas252(shown as antennas252athrough252r) may receive the downlink signals from the network node110or other network nodes110and may provide a set of received signals (for example, R received signals) to a set of modems254(for example, R modems), shown as modems254athrough254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem254. Each modem254may use a respective demodulator component to condition (for example, filter, amplify, downconvert, or digitize) a received signal to obtain input samples. Each modem254may use a demodulator component to further process the input samples (for example, for OFDM) to obtain received symbols. A MIMO detector256may obtain received symbols from the modems254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor258may process (for example, demodulate and decode) the detected symbols, may provide decoded data for the UE120to a data sink260, and may provide decoded control information and system information to a controller/processor280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other examples. In some examples, one or more components of the UE120may be included in a housing284.

One or more antennas (for example, antennas234athrough234tor antennas252athrough252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmission or reception components, such as one or more components ofFIG.2.

On the uplink, at the UE120, a transmit processor264may receive and process data from a data source262and control information (for example, for reports that include RSRP, RSSI, RSRQ, or CQI) from the controller/processor280. The transmit processor264may generate reference symbols for one or more reference signals. The symbols from the transmit processor264may be precoded by a TX MIMO processor266if applicable, further processed by the modems254(for example, for DFT-s-OFDM or CP-OFDM), and transmitted to the network node110. In some examples, the modem254of the UE120may include a modulator and a demodulator. In some examples, the UE120includes a transceiver. The transceiver may include any combination of the antenna(s)252, the modem(s)254, the MIMO detector256, the receive processor258, the transmit processor264, or the TX MIMO processor266. The transceiver may be used by a processor (for example, the controller/processor280) and the memory282to perform aspects of any of the processes described herein.

In some aspects, the UE120includes means for receiving information identifying a set of criteria for delay status reporting: and/or means for transmitting, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume. The means for the UE120to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254. MIMO detector256, receive processor258, transmit processor264. TX MIMO processor266, controller/processor280, or memory282.

In some aspects, the network node110includes means for transmitting information identifying a set of criteria for delay status reporting: and/or means for receiving, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume. The means for the network node110to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220. TX MIMO processor230, modem232, antenna234. MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

FIG.4is a diagram illustrating an example400of a timing for delay status reporting, in accordance with the present disclosure.

As shown inFIG.4, a reporting entity may be configurable with a timeline for delay status reporting (DSR), which may also be referred to as “delay information reporting (DIR)”. The reporting entity may be an entity for which a UE120reports delay information in a DSR message. For example, the reporting entity may be a data radio bearer (DRB), a logical channel (LCH), or a set of logical channels (e.g., a logical channel group (LCG)). In some examples, a DRB may include a plurality of LCHs corresponding to a plurality of protocol data unit (PDU) sets, each including one or more PDUs with a common parameter (e.g., an importance level parameter). A UE120may be configured with a plurality of reporting entities, in some examples.

As further shown inFIG.4, the timeline for delay status reporting may be based at least in part on an arrival time410. The arrival time410may include a time at which a first PDU of a PDU set is received by the UE120. In some examples, the first received PDU may be different than a first indexed PDU (e.g., as a result of out of order delivery of PDUs). An amount of remaining time for a PDU may be associated with a PDU set delay budget (PSDB) or a packet delay budget (PDB). For example, the UE120(or the reporting entity thereof) may be configured with a PSDB timer, which represents an amount of time after the arrival time410during which a PDU set can be delivered from the UE120to a destination device (e.g., a network node (not shown)). Similarly, the UE120may be configured with a PDB timer, which represents an amount of time after the arrival time410during which a PDU (e.g., which is not associated with a PDU set) can be delivered from the UE120to a destination device (e.g., before a failure occurs).

The UE120may be configured with a time threshold420(TDIR,m) for a reporting entity m. The time threshold420may be configured as an absolute time or a percentage of time between the arrival time410and an end of the PSDB or PDB. However, a network node110and UE120may lack signaling for exchanging or synchronizing a configuration relating to a reporting timeline of a reporting entity. For example, the UE120may not be configured with information indicating a triggering threshold from which the UE120can determine whether the triggering threshold is satisfied at the time threshold420. Accordingly, the UE120and network node110may not be synchronized at a current time430and evaluate whether a deadline440has occurred.

Some aspects described herein enable delay status reporting. For example, a UE may receive information identifying a set of criteria for generating a delay status report and may, when the set of criteria is satisfied, generate and transmit the delay status report to a network node. In this case, the network node may use the delay status report to configure communications on a network, such as by scheduling resources, balancing loads, or changing quality of service parameters, among other examples. In this way, the UE and the network node can improve services being provided on the network, such as by scheduling additional resources to improve XR service latency when XR data is delayed. In some aspects, by enabling configuration of a reporting entity (e.g., a UE120), a network node and a UE may maintain synchronization, thereby enabling efficient allocation of resources for transmitting data associated with one or more services.

FIGS.5A and5Bare diagrams illustrating an example500associated with delay status reporting, in accordance with the present disclosure. As shown inFIGS.5A and5B, example500includes communication between a network node110and a UE120.

As further shown inFIG.5A, and by reference number510, the UE120may receive information identifying a delay status reporting configuration. For example, the UE120may receive, from the network node110, information identifying a set of criteria for delay status reporting. The set of criteria for delay status reporting may include one or more parameter values, such as one or more values for a delay deadline, a data volume threshold, an amount of time for a prohibit timer, a reporting threshold, or another configurable parameter, as described herein. In some aspects, the UE120may receive information identifying a parameter for determine whether a delay deadline is satisfied. For example, the UE120may receive information identifying a PSDB. In this case, the UE120may determine an amount of time remaining to transmit a delay status report based at least in part on a delay deadline (e.g., which is a function of the PSDB) and a current time (e.g., at which the UE120is evaluating whether to transmit the delay status report). Additionally, or alternatively, the UE120may receive information identifying a PDB for determining the delay deadline for PDUs not included in a PDU set. In some aspects, the PDB may be configured based on a quality of service (QOS) flow specific basis. For example, the UE120may receive information indicating a PDB for a particular QoS flow (and PDUs thereof). A QoS flow may refer to one or more data packets associated with a specific PDU and/or data radio bearer (DRB) and associated with one or more QoS parameters, such as a level of priority, a data rate, or a latency, among other examples. Accordingly, the UE120may have a plurality of QoS flows for receiving traffic from a network (e.g., the network node110) and may have a PDB for each QoS flow (e.g., a different PDB or the same PDB). The PDB may be a QoS characteristic that specifies an upper bound for an amount of time that a packet may be delayed between a network source, associated with the network node110, and the UE120. For example, a particular QOS flow may be configured with a 2 millisecond (ms) PDB, which indicates that packets can be delayed up to 2 ms when being conveyed from, for example, a user plane function (UPF) (e.g., via the network node110) to a UE120

In some aspects, the UE120may receive information identifying a time threshold. For example, the UE120may receive information indicating the time threshold TDIR,massociated with a reporting entity m of the UE120. In this case, the UE120may evaluate whether the time threshold is satisfied to determine whether to generate and transmit a delay status report for the reporting entity m, as described herein. Additionally, or alternatively, the UE120may receive information identifying a data volume threshold. Vprohibit, which represents a data volume to accumulate in a buffer before a delay status report is triggered. In this case, the value of Vprohibitis configurable to control often the UE120triggers delay status reports (e.g., a higher value of Vprohibitreduces a frequency of delay status reports, thereby reducing a utilization of network resources, a lower value of Vprohibitincreases a frequency of delay status reports, thereby reducing delay). A data volume may include an amount of data (e.g., a quantity of packets, a quantity of bits, or another data metric) that, for example, is accumulated in a buffer.

Additionally, or alternatively, the UE120may receive information identifying a time threshold. Tprohibit, Which represents a time period in which the UE120does not trigger delay status reports. In this case, the value of Tprohibitis configurable to control often the UE120triggers delay status reports (e.g., a higher value of Tprohibitreduces a frequency of delay status reports, thereby reducing a utilization of network resources, a lower value of Tprohibitincreases a frequency of delay status reports, thereby reducing delay).

As further shown inFIG.5A, and by reference numbers520and530, the UE120may evaluate whether to transmit a delay status report and may generate the delay status report. For example, the UE120may determine whether the set of criteria for delay status reporting is satisfied and may, when the set of criteria is satisfied, generate a delay status report identifying a status of a buffer.

In some aspects, the UE120may determine whether a delay deadline is satisfied. For example, the UE120may determine whether the delay deadline is satisfied for one or more PDUs. In some aspects, a PDU may be included in a PDU set. When a PDU is included in a PDU set, the UE120may determine the delay deadline based at least in part on a time at which a first PDU of the PDU set is received by the UE. For example, the UE120may receive a first PDU of a PDU set (e.g., which may or may not be a first index PDU of the PDU set) at a time T1and may determine the delay deadline Tdeadline=T1+T2, where T2represents a PSDB of a QoS flow that includes the received first PDU. Accordingly, the UE120may determine whether a remaining time to transmit a delay status report as Tremaining=Tdeadline−Tcurrent. Where Tcurrentrepresents a time at which the UE120is evaluating whether to transmit a delay status report. Alternatively, when a received PDU is not included in a PDU set, the UE120may determine the delay deadline based at least in part on a PDB. For example, the UE120may receive a PDU and determine Tdeadline=T1+T2, where T1represents a time at which the PDU is received and T2represents the PDB for a QOS flow that includes the PDU.

In some aspects, the UE120may determine whether a time threshold for reporting a delay status is satisfied. For example, a reporting entity m of the UE120(e.g., the UE120may include a plurality of reporting entities corresponding to a plurality of applications or QoS flows) may be configured with a time threshold TDIR,mthat, when satisfied, may trigger the UE120to transmit a delay status report.

In some aspects, the UE120may determine whether a data volume threshold is satisfied to determine whether to generate and transmit a delay status report. For example, the UE120determine whether a data volume in a buffer associated with a reporting entity satisfies a threshold Vprohibit. In some aspects, the UE120may determine whether a delay status report is to be triggered for a slot. For example, the UE120may determine Surgent, Which represents a data volume with a remaining time less than TDIR(if TDIRis configured as an absolute time). Additionally, or alternatively, the UE120may determine Surgentas a data volume with a remaining time below TDIR×PSDB or TDIR×PDB (if TDIRis configured as a percentage). Additionally, or alternatively, the UE120may determine a data volume. Srefreported in a previously triggered delay status report (e.g., if a previous delay status report has occurred, otherwise Srefmay be set to a default value, such as 0). In this case, when the UE120evaluates Surgent−Sref>Vprohibit, the UE120may trigger a delay status report. In other words, the UE120determines whether difference between a current data volume, with a remaining time less than a time threshold, and a previously reported data volume, with a remaining time less than the time threshold, is greater than a threshold amount.

Similarly, the UE120may determine whether to generate and transmit a delay status report based at least in part on whether a prohibit timer Tprohibitis active. For example, when the prohibit timer is not active (e.g., the UE120is not prohibited from triggering a delay status report), the UE120can trigger a delay status report. In this case, the UE120may start the prohibit timer when a delay status report is triggered and may forgo triggering further delay status reports until after the prohibit timer has elapsed or after a delay status report MAC control element (CE) (MAC CE) is transmitted via a physical uplink shared channel (PUSCH).

In some aspects, the UE120may determine whether to generate and transmit a delay status report based at least in part on a configured periodicity. For example, the network node110may configure periodic reporting of a delay status of the UE120. In this case, the network node110may configure delay status reporting to occur in each time period t, which may be a configurable parameter (e.g., configured via network node110radio resource control (RRC) signaling, such as a configuration information element (IE)) or a static parameter (e.g., that is in a specification, such as specifying a periodicity of delay status reporting occurring (or potentially occurring) in each slot). In some aspects, the network node110may enable or disable periodic reporting on, for example, a per reporting entity basis. For example, the network node110may configure, using static signaling, periodic delay status reporting and may select, by transmitting a MAC CE, one or more reporting entities of a UE120for which the UE120is to perform the periodic delay status reporting. In some aspects, the UE120may determine whether to generate and transmit a delay status report based at least in part on an occurrence of a mobility event. For example, the mobility event may occur when the UE120changes a primary cell (PCell) (e.g., as a result of a handover) or a primary secondary cell (PSCell) (e.g., as a result of a secondary cell group (SCG) change). Based on these events, the UE120may trigger a delay status report to indicate to a new cell (e.g., the network node110) a delay status of one or more reporting entities of the UE120.

In some aspects, the UE120may evaluate one or more reporting thresholds for one or more reporting entities, m, when generating a delay status report. For example, the UE120may evaluate a reporting threshold Vm,1, . . . , Vm,m, where n represents a quantity of intervals for reporting. In other words, the UE120may determine to report buffered data with a remaining time between Vm,iand Vm,i+1for i=1 . . . . n. For example, the UE120may generate a MAC CE, as shown inFIG.5B, conveying information associated with a set of reporting thresholds. In this case, a set of reporting entities and a set of values that the UE120reports in the MAC CE may be based at least in part on, for example, the configuration information.

As further shown inFIG.5B, the MAC CE may include a bitmap Lmthat indicates whether a reporting entity m is being reported in the MAC CE. In this case, the bitmap Lmhas a size of 2×B (e.g., if the reporting entity of the UE120is a DRB or LCH) or 1×B, where B represents a quantity of reporting entities m. The MAC CE may further include a parameter Bm, which indicates which buffer status report table, of a set of possible buffer status report tables, is being used for reporting a data volume. In this case, the UE120may include the parameter Bm, when the UE120is configured with a plurality of classes of BSR tables, such as enhanced 3GPP Release 18 specified BSR tables and pre-Release 18 BSR tables. The UE120may include, for each reporting entity being reported, a parameter Sm,i, which represents a data volume buffered for reporting entity m with a remaining time between Vm,iand Vm,j+1(e.g., for j=1, . . . , n). In some aspects, the UE120may encode the parameter Sm,jusing a specified BSR table, as described above and, for example, indicated with Bm.

In some aspects, the UE120may include a parameter Tmindicating a duration between a sampling instance (e.g., when the UE120determines a delay status) and a transmission time of a PUSCH that includes the delay status report. For example, the UE120may indicate a quantity of slots indicating a time duration between an identification of the delay status and reporting of the delay status. In some aspects, the sampling instance may represent a slot in which a delay status report is triggered. In some aspects, the sampling instance may represent a slot in which a MAC PDU including the delay status report is generated. In this case, the UE120may select reporting entities and/or reported values for the reporting entities based at least in part on which sampling instance is used.

As further shown inFIG.5A, and by reference number540, the UE120may transmit delay status reporting. For example, the UE120may transmit a delay status report to the network node110. In this case, the UE120may transmit a MAC CE, as described herein, using a PUSCH resource for transmitting the MAC CE. In some aspects, the UE120may transmit the delay status reporting with a particular priority. For example, a delay status report MAC CE may be associated with a higher logical channel prioritization (LCP) priority value than is assigned to a buffer status report. In other words, the delay status report MAC CE may have a first priority that is higher than a second priority of a buffer status report message, which may result in the delay status report MAC CE being prioritized for receiving uplink resources for transmission.

In some aspects, when there is a PUSCH resource available and the UE120has a pending delay status report for transmission, the UE120may multiplex the delay status report onto the PUSCH for transmission. For example, the UE120may piggyback the delay status report with one or more other communications that are to be conveyed via the PUSCH resource. Additionally, or alternatively, to convey the delay status report in the PUSCH resource, the UE120may puncture the PUSCH resource and overwrite one or more other communications that are to be conveyed via the PUSCH resource. Alternatively, the UE120may request PUSCH resources from the network node110via a scheduling request (SR). In this case, the network node110may configure dedicated physical uplink control channel (PUCCH) resources for transmitting SRs to request resources for, for example, transmission of delay status reports.

In some aspects, the UE120may start or stop a prohibit timer in connection with transmitting the MAC CE. For example, the UE120may stop a running prohibit timer Tprohibitwhen transmitting the MAC CE to enable generation of a new, updated a delay status report. Additionally, or alternatively, the UE120may cancel one or more other pending delay status reports. In some aspects, the UE120may receive an allocation of resources. For example, based at least in part on transmitting the delay status report, the UE120may receive, from the network node110, information identifying an allocation of resources for transmitting data reported in the delay status report.

As indicated above.FIGS.5A and5Bis provided as an example. Other examples may differ from what is described with respect toFIGS.5A and5B.

FIG.6is a flowchart of an example method600of wireless communication. The method600may be performed by, for example, a UE (e.g., UE120).

At610, the UE may receive information identifying a set of criteria for delay status reporting. For example, the UE (e.g., using communication manager140and/or reception component802, depicted inFIG.8) may receive information identifying a set of criteria for delay status reporting, as described above. In some aspects, the UE is configured to receive signaling associated with configuring one or more parameters of the delay status report. In some aspects, the one or more parameters include at least one of a data volume threshold parameter, a timer parameter, or one or more reporting thresholds.

At620, in some aspects, the UE may determine that the set of criteria for delay status reporting is satisfied. For example, the UE (e.g., using communication manager140and/or determination component808, depicted inFIG.8) may determine that the set of criteria for delay status reporting is satisfied, as described above. In some aspects, the UE may determine that the set of criteria for delay status reporting is satisfied based at least in part on determining that a timer has expired or that a data volume in a buffer satisfies a threshold.

At630, in some aspects, the UE may generate the delay status report. For example, the UE (e.g., using communication manager140and/or report generation component810, depicted inFIG.8) may generate, based at least in part on determining that the set of criteria for delay status reporting is satisfied, the delay status report, as described above. In some aspects, the delay status report is associated with a first priority that is higher than a second priority of a buffer status report. In some aspects, the delay status report is multiplexed onto a physical uplink shared channel resource. In some aspects, the delay status report is included in a physical uplink shared channel resource requested via a scheduling request.

At640, the UE may transmit, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume. For example, the UE (e.g., using communication manager140and/or transmission component804, depicted inFIG.8) may transmit, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume, as described above.

In some aspects, the delay status reporting is associated with at least one of a data radio bearer, a logical channel, or a logical channel group. In some aspects, the delay status is based at least in part on a delay deadline for a protocol data unit associated with the data volume or on a packet delay budget associated with a quality of service flow, the quality of service flow including the protocol data unit. In some aspects, the delay status is based at least in part on a time threshold for triggering generation of the delay status report or for reporting the delay status report. In some aspects, the delay status report is based at least in part on whether a threshold data volume is associated with a remaining time, wherein the remaining time is less than a time threshold.

In some aspects, the delay status report is based at least in part on a data volume reported in a previous delay status report. In some aspects, the delay status report is based at least in part on a status of a timer. In some aspects, alone or in combination with one or more of the first through ninth aspects, the timer is stopped based at least in part on transmission of the delay status report.

In some aspects, the delay status report is based at least in part on a configured periodicity. In some aspects, the configured periodicity is associated with a reporting entity. In some aspects, the delay status report is based at least in part on an occurrence of a mobility event. In some aspects, the delay status report is included in a MAC CE. In some aspects, the MAC CE includes at least one of a delay status report reporting entity bitmap, a buffer status report table bitmap, an indicator of data with a remaining time within a configured range, an indicator of data with a remaining time less than a threshold, an indicator that the MAC CE is for a reporting entity, an indicator of a buffer status report table, a sampling instance duration indicator, or a transmission time indicator.

AlthoughFIG.6shows example blocks of method600, in some aspects, method600may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.6. Additionally, or alternatively, two or more of the blocks of method600may be performed in parallel.

FIG.7is a flowchart of an example method700of wireless communication. The method700may be performed by, for example, a network node (e.g., network node110).

At710, the network node may transmit information identifying a set of criteria for delay status reporting. For example, the network node (e.g., using communication manager150and/or transmission component1004, depicted inFIG.10) may transmit information identifying a set of criteria for delay status reporting, as described above. In some aspects, the delay status reporting is associated with at least one of a data radio bearer, a logical channel, or a logical channel group. In some aspects, the network node may transmit signaling associated with configuring one or more parameters of the delay status report. In some aspects, the one or more parameters include at least one of a data volume threshold parameter, a timer parameter, or one or more reporting thresholds.

At720, the network node may receive a delay status report. For example, the network node (e.g., using communication manager150and/or reception component1002, depicted inFIG.10) may receive, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume, as described above. In some aspects, the delay status is based at least in part on a delay deadline for a protocol data unit associated with the data volume or on a packet delay budget associated with a quality of service flow, the quality of service flow including the protocol data unit. In some aspects, the delay status is based at least in part on a time threshold for triggering generation of the delay status report or for reporting the delay status report. In some aspects, the delay status report is based at least in part on whether a threshold data volume is associated with a remaining time, wherein the remaining time is less than a time threshold.

In some aspects, the delay status report is based at least in part on a data volume reported in a previous delay status report. In some aspects, the delay status report is based at least in part on a status of a timer. In some aspects, the timer is stopped based at least in part on transmission of the delay status report. In some aspects, the delay status report is based at least in part on a configured periodicity.

In some aspects, the configured periodicity is associated with a reporting entity. In some aspects, the delay status report is based at least in part on an occurrence of a mobility event. In some aspects, the delay status report is included in a MAC CE. In some aspects, the MAC CE includes at least one of a delay status report reporting entity bitmap, a buffer status report table bitmap, an indicator of data with a remaining time within a configured range, an indicator of data with a remaining time less than a threshold, an indicator that the MAC CE is for a reporting entity, an indicator of a buffer status report table, a sampling instance duration indicator, or a transmission time indicator. In some aspects, the delay status report is associated with a first priority that is higher than a second priority of a buffer status report. In some aspects, the delay status report is multiplexed onto a physical uplink shared channel resource. In some aspects, the delay status report is included in a physical uplink shared channel resource requested via a scheduling request.

At730, in some aspects, the network node may communicate with the UE in accordance with a content of the delay status reporting. For example, the network node (e.g., using communication manager150, reception component1002, and/or transmission component1004, depicted inFIG.10) may communicate with the UE in accordance with a content of the delay status reporting. In some aspects, the network node may schedule resources for the UE and/or an XR device associated therewith based at least in part on the content of the delay status reporting.

AlthoughFIG.7shows example blocks of method700, in some aspects, method700may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.7. Additionally, or alternatively, two or more of the blocks of method700may be performed in parallel.

The reception component802may receive information identifying a set of criteria for delay status reporting. The transmission component804may transmit, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

The determination component808may determine that the set of criteria for delay status reporting is satisfied. The report generation component810may generate the delay status report based at least in part on determining that the set of criteria for delay status reporting is satisfied. The reception component802may receive signaling associated with configuring one or more parameters of the delay status report.

FIG.9is a diagram illustrating an example900of a hardware implementation for an apparatus905employing a processing system910, in accordance with the present disclosure. The apparatus905may be a UE.

The processing system910may be implemented with a bus architecture, represented generally by the bus915. The bus915may include any number of interconnecting buses and bridges depending on the specific application of the processing system910and the overall design constraints. The bus915links together various circuits including one or more processors and/or hardware components, represented by the processor920, the illustrated components, and the computer-readable medium/memory925. The bus915may also link various other circuits, such as timing sources, peripherals, voltage regulators, and/or power management circuits.

The processing system910may be coupled to a transceiver930. The transceiver930is coupled to one or more antennas935. The transceiver930provides a means for communicating with various other apparatuses over a transmission medium. The transceiver930receives a signal from the one or more antennas935, extracts information from the received signal, and provides the extracted information to the processing system910, specifically the reception component802. In addition, the transceiver930receives information from the processing system910, specifically the transmission component804, and generates a signal to be applied to the one or more antennas935based at least in part on the received information.

The processing system910includes a processor920coupled to a computer-readable medium/memory925. The processor920is responsible for general processing, including the execution of software stored on the computer-readable medium/memory925. The software, when executed by the processor920, causes the processing system910to perform the various functions described herein for any particular apparatus. The computer-readable medium/memory925may also be used for storing data that is manipulated by the processor920when executing software. The processing system further includes at least one of the illustrated components. The components may be software modules running in the processor920, resident/stored in the computer readable medium/memory925, one or more hardware modules coupled to the processor920, or some combination thereof.

In some aspects, the processing system910may be a component of the UE120and may include the memory282and/or at least one of the TX MIMO processor266, the receive (RX) processor258, and/or the controller/processor280. In some aspects, the apparatus905for wireless communication includes means for receiving information identifying a set of criteria for delay status reporting: and/or means for transmitting, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume. The aforementioned means may be one or more of the aforementioned components of the apparatus800and/or the processing system910of the apparatus905configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system910may include the TX MIMO processor266, the RX processor258, and/or the controller/processor280. In one configuration, the aforementioned means may be the TX MIMO processor266, the RX processor258, and/or the controller/processor280configured to perform the functions and/or operations recited herein.

FIG.9is provided as an example. Other examples may differ from what is described in connection withFIG.9.

The transmission component1004may transmit information identifying a set of criteria for delay status reporting. The reception component1002may receive, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume. The transmission component1004may transmit signaling associated with configuring one or more parameters of the delay status report. The determination component1008may determine the set of criteria for delay status reporting.

FIG.11is a diagram illustrating an example1100of a hardware implementation for an apparatus1105employing a processing system1110, in accordance with the present disclosure. The apparatus1105may be a network node.

The processing system1110may be implemented with a bus architecture, represented generally by the bus1115. The bus1115may include any number of interconnecting buses and bridges depending on the specific application of the processing system1110and the overall design constraints. The bus1115links together various circuits including one or more processors and/or hardware components, represented by the processor1120, the illustrated components, and the computer-readable medium/memory1125. The bus1115may also link various other circuits, such as timing sources, peripherals, voltage regulators, and/or power management circuits.

The processing system1110may be coupled to a transceiver1130. The transceiver1130is coupled to one or more antennas1135. The transceiver1130provides a means for communicating with various other apparatuses over a transmission medium. The transceiver1130receives a signal from the one or more antennas1135, extracts information from the received signal, and provides the extracted information to the processing system1110, specifically the reception component1002. In addition, the transceiver1130receives information from the processing system1110, specifically the transmission component1004, and generates a signal to be applied to the one or more antennas1135based at least in part on the received information.

The processing system1110includes a processor1120coupled to a computer-readable medium/memory1125. The processor1120is responsible for general processing, including the execution of software stored on the computer-readable medium/memory1125. The software, when executed by the processor1120, causes the processing system1110to perform the various functions described herein for any particular apparatus. The computer-readable medium/memory1125may also be used for storing data that is manipulated by the processor1120when executing software. The processing system further includes at least one of the illustrated components. The components may be software modules running in the processor1120, resident/stored in the computer readable medium/memory1125, one or more hardware modules coupled to the processor1120, or some combination thereof.

In some aspects, the processing system1110may be a component of the network node110and may include the memory242and/or at least one of the TX MIMO processor230, the RX processor238, and/or the controller/processor240. In some aspects, the apparatus1105for wireless communication includes means for transmitting information identifying a set of criteria for delay status reporting: and/or means for receiving, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume. The aforementioned means may be one or more of the aforementioned components of the apparatus1000and/or the processing system1110of the apparatus1105configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system1110may include the TX MIMO processor230, the receive processor238, and/or the controller/processor240. In one configuration, the aforementioned means may be the TX MIMO processor230, the receive processor238, and/or the controller/processor240configured to perform the functions and/or operations recited herein.

FIG.11is provided as an example. Other examples may differ from what is described in connection withFIG.11.

Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving information identifying a set of criteria for delay status reporting: and transmitting, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Aspect 2: The method of Aspect 1, further comprising: determining that the set of criteria for delay status reporting is satisfied: and generating the delay status report based at least in part on determining that the set of criteria for delay status reporting is satisfied.

Aspect 3: The method of any of Aspects 1-2, wherein the delay status reporting is associated with at least one of: a data radio bearer, a logical channel, or a logical channel group.

Aspect 4: The method of any of Aspects 1-3, wherein the delay status is based at least in part on a delay deadline for a protocol data unit associated with the data volume or on a packet delay budget associated with a quality of service flow, the quality of service flow including the protocol data unit.

Aspect 5: The method of any of Aspects 1-4, wherein the delay status is based at least in part on a time threshold for triggering generation of the delay status report or for reporting the delay status report.

Aspect 6: The method of any of Aspects 1-5, further comprising: receiving signaling associated with configuring one or more parameters of the delay status report.

Aspect 7: The method of Aspect 6, wherein the one or more parameters include at least one of: a data volume threshold parameter, a timer parameter, or one or more reporting thresholds.

Aspect 8: The method of any of Aspects 1-7, wherein the delay status report is based at least in part on whether a threshold data volume is associated with a remaining time, wherein the remaining time is less than a time threshold.

Aspect 9: The method of any of Aspects 1-8, wherein the delay status report is based at least in part on a data volume reported in a previous delay status report.

Aspect 10: The method of any of Aspects 1-9, wherein the delay status report is based at least in part on a status of a timer.

Aspect 11: The method of Aspect 10, wherein the timer is stopped based at least in part on transmission of the delay status report.

Aspect 12: The method of any of Aspects 1-11, wherein the delay status report is based at least in part on a configured periodicity.

Aspect 13: The method of Aspect 12, wherein the configured periodicity is associated with a reporting entity.

Aspect 14: The method of any of Aspects 1-13, wherein the delay status report is based at least in part on an occurrence of a mobility event.

Aspect 15: The method of any of Aspects 1-14, wherein the delay status report is included in a medium access control (MAC) control element (CE).

Aspect 16: The method of Aspect 15, wherein the MAC CE includes at least one of: a delay status report reporting entity bitmap, a buffer status report table bitmap, an indicator of data with a remaining time within a configured range, an indicator of data with a remaining time less than a threshold, an indicator that the MAC CE is for a reporting entity, an indicator of a buffer status report table, a sampling instance duration indicator, or a transmission time indicator.

Aspect 17: The method of any of Aspects 1-16, wherein the delay status report is associated with a first priority that is higher than a second priority of a buffer status report.

Aspect 18: The method of any of Aspects 1-17, wherein the delay status report is multiplexed onto a physical uplink shared channel resource.

Aspect 19: The method of any of Aspects 1-18, wherein the delay status report is included in a physical uplink shared channel resource requested via a scheduling request.

Aspect 20: A method of wireless communication performed by a network node, comprising: transmitting information identifying a set of criteria for delay status reporting: and receiving, based at least in part on the set of criteria being satisfied, a delay status report including an indicator of a data volume and a delay status associated with the data volume.

Aspect 21: The method of Aspect 20, wherein the delay status reporting is associated with at least one of: a data radio bearer, a logical channel, or a logical channel group.

Aspect 22: The method of any of Aspects 20-21, wherein the delay status is based at least in part on a delay deadline for a protocol data unit associated with the data volume or on a packet delay budget associated with a quality of service flow, the quality of service flow including the protocol data unit.

Aspect 23: The method of any of Aspects 20-22, wherein the delay status is based at least in part on a time threshold for triggering generation of the delay status report or for reporting the delay status report.

Aspect 24: The method of any of Aspects 20-23, further comprising: transmitting signaling associated with configuring one or more parameters of the delay status report.

Aspect 25: The method of Aspect 24, wherein the one or more parameters include at least one of: a data volume threshold parameter, a timer parameter, or one or more reporting thresholds.

Aspect 26: The method of any of Aspects 20-25, wherein the delay status report is based at least in part on whether a threshold data volume is associated with a remaining time, wherein the remaining time is less than a time threshold.

Aspect 27: The method of any of Aspects 20-26, wherein the delay status report is based at least in part on a data volume reported in a previous delay status report.

Aspect 28: The method of any of Aspects 20-27, wherein the delay status report is based at least in part on a status of a timer.

Aspect 29: The method of Aspect 28, wherein the timer is stopped based at least in part on transmission of the delay status report.

Aspect 30: The method of any of Aspects 20-29, wherein the delay status report is based at least in part on a configured periodicity.

Aspect 31: The method of Aspect 30, wherein the configured periodicity is associated with a reporting entity.

Aspect 32: The method of any of Aspects 20-31, wherein the delay status report is based at least in part on an occurrence of a mobility event.

Aspect 33: The method of any of Aspects 20-32, wherein the delay status report is included in a medium access control (MAC) control element (CE).

Aspect 34: The method of Aspect 33, wherein the MAC CE includes at least one of: a delay status report reporting entity bitmap, a buffer status report table bitmap, an indicator of data with a remaining time within a configured range, an indicator of data with a remaining time less than a threshold, an indicator that the MAC CE is for a reporting entity, an indicator of a buffer status report table, a sampling instance duration indicator, or a transmission time indicator.

Aspect 35: The method of any of Aspects 20-34, wherein the delay status report is associated with a first priority that is higher than a second priority of a buffer status report.

Aspect 36: The method of any of Aspects 20-35, wherein the delay status report is multiplexed onto a physical uplink shared channel resource.

Aspect 37: The method of any of Aspects 20-36, wherein the delay status report is included in a physical uplink shared channel resource requested via a scheduling request.