Delayed status reporting for augmented reality (XR) wireless communications

Abstract

Methods and systems for transmitting a delay status report (DSR) between a user equipment (UE) device (105) and a network entity (112) to optimize resource allocation are disclosed herein. For example, a UE device receives a message from a network entity that configures one or more channels and a delay threshold associated with the one or more channels for the UE device. The UE device monitors first data arriving at an uplink buffer of one or more channels configured by the message. The UE device generates a DSR when the UE device determines that a delay of first data in an uplink buffer of the one or more channels has reached at least one of the delay thresholds. When a trigger condition associated with the DSR is satisfied, the UE device transmits the DSR to the network entity. The network entity may then reallocate resources to reduce data delay states in the UE device.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to and the benefit of U.S. Provisional Application No. 63 / 370,466, filed on August 4, 2022, entitled “DELAYSTATUS REPORT FOR EXTENDED REALITY (XR) WIRELESS COMMUNICATIONS,” under Article 8 of the Patent Cooperation Treaty (PCT), the entire contents of which are expressly incorporated herein by reference. Technical Field

[0002] The present disclosure relates generally to wireless communications and, more particularly, to systems and methods for reporting delay status. Background Art

[0003] The 3rd Generation Partnership Project (3GPP) is currently in the process of specifying updates to the radio interface known as 5G New Radio (5G NR) and the Next Generation Packet Core Network (NG-CN or NGC). The 5G NR architecture has three main parts: 5G Radio Access Network (5G-RAN), 5G Core Network (5GC), and User Equipment (UE). To facilitate the implementation of different data services and requirements, 3GPP 5G NR cellular networks support network slicing, which enables the reuse of virtualized and independent logical networks on the same physical network infrastructure.

[0004] Extended Reality (XR) includes various augmented reality, virtual reality, and mixed reality applications that leverage 5G NR network capabilities (e.g., ultra-low latency, high data transfer rates, etc.). Because XR anticipates low latency and high data rates, there is an opportunity to support more efficient resource allocation in 5G RAN. Summary of the invention

[0005] The present disclosure provides methods and techniques for generating and transmitting delay status reports between user equipment (UE) devices and network entities, such as to improve resource allocation. The disclosed technology can achieve communications that meet various requirements in extended reality (XR) applications. XR and cloud gaming (CG) can refer to various types of augmented, virtual, and hybrid environments in which users can use multiple devices to interface and interact with computer-generated environments in real time (or with minimal delay given hardware limitations). Therefore, if data transmission is delayed (for example, when insufficient resources are allocated in a particular input / output device), the user may perceive input and / or feedback delays.

[0006] XR communications require various capacity improvements over existing telecommunication capabilities. For example, XR services are characterized by stricter requirements for periodicity, multiple streams, synchronized streams, jitter avoidance, low latency, high reliability, etc. For the purpose of evaluating XR / CG applications, system capacity is defined as the maximum number of users per cell that meets a specific set of requirements. Although the specific set of requirements for XR / CG is still under discussion, they appear to cover a certain percentage (e.g., 90% or 95%) of UEs meeting a threshold packet delay budget (PDB) or a threshold packet error rate (PER).

[0007] Due to this approach to defining system capacity, the more a user's UE devices satisfy their XR service communication requirements, the higher the capacity of the serving cell. Because each UE may fall into different operating scenarios, the network entity may improve the network capacity of the network entity's calculation for XR applications by allocating resources to increase the number of users per cell that satisfy XR service communication requirements. Each user may have one or more UE devices. In an XR context, a user is satisfied when all UE devices involved in an XR application are satisfied—for example, if one of the multiple UE devices is out of sync or significantly delayed, the user is not satisfied even if the other UE devices are satisfied in terms of PDB or PER requirements. UE devices may provide individual and / or group identifiers (IDs) to signal that they belong to the same user or XR application session.

[0008] In New Radio (NR), buffer status reports can inform the network entity of the uplink buffer size level of the UE device. However, the network entity does not know when data arrives at the uplink buffer of the UE device. At best, the network can make some assumptions about the time when data arrives at the buffer based on the first-in-first-out (FIFO) and fluctuating buffer size level assumptions. Therefore, it is difficult for the network entity to optimize resource allocation to minimize the delay of pending uplink data stored in the buffer. The present disclosure solves these problems by configuring the UE device to generate and transmit delay status reports to the network entity, which can then support the network to allocate resources to maximize network capacity for XR and other applications.

[0009] According to various aspects of the present disclosure, for example, a UE device monitors data having a queuing delay greater than a delay threshold. The UE device dynamically or periodically transmits a delay status report to a network entity. The delay status report includes a volume of delayed data for a channel or channel group and a satisfaction level. For example, when the data stream of interest meets the corresponding packet error rate (PER) and packet delay budget (PDB) (or threshold) requirements, the UE device can be declared as a satisfied UE device. Based on the delay status report information, the network entity then determines a resource allocation update, if necessary, to improve network capabilities.

[0010] According to various aspects of the present disclosure, a UE device receives a message from a network entity that configures one or more channels and delay thresholds associated with the one or more channels for the UE device. The UE device monitors the first data arriving at the uplink buffer of the one or more channels configured by the message. When the UE device determines that the delay of the first data in the uplink buffer of the one or more channels has reached at least one of the delay thresholds, the UE device generates a delay status report (DSR). When a trigger condition associated with the DSR is met, the UE device can transmit the DSR to the network entity separately. Depending on the configuration specified in the configuration message, various trigger conditions may exist.

[0011] For example, one trigger condition may involve a first timer. When first data arrives at an uplink buffer of one or more channels, the UE device starts the first timer. When the first timer expires before the UE device has removed the first data from the buffer (e.g., in response to a completed or successful transmission of the first data), the trigger condition is met. In other words, the expiration of the first timer initiates both DSR generation and DSR transmission. In addition, the trigger condition may further accommodate one or more channels configured by the network entity to have a higher priority than other channels.

[0012] A trigger condition may involve receiving new data arriving at an uplink buffer of one or more channels. For example, a trigger condition associated with a DSR may include receiving new data when there is existing delayed data in the uplink buffer. In another example, a trigger condition may include receiving new data when delayed data in the uplink buffer (e.g., the sum of various data in the buffer) has exceeded a delay volume threshold. In yet another example, a trigger condition associated with a DSR may further include at least one of the following: the volume of the delayed portion of the first data exceeds a volume threshold defined in at least one of the delay thresholds; or the volume of the buffered first data exceeds a threshold criterion.

[0013] Another trigger condition may involve a second timer. For example, when transmitting a DSR to a network entity, the UE device may start a second timer. The UE device generates and transmits a second DSR when the second timer expires (e.g., the expiration of the second timer is a trigger condition for generating and transmitting the second DSR). The UE device may stop the second timer when (a) the UE device does not have delayed data in a memory buffer, (b) the volume of the delayed data has become less than a volume threshold defined in at least one of the delay thresholds, (c) the media access control (MAC) is reset, or (d) the UE device receives a request to stop the second timer from the network entity.

[0014] One trigger condition may involve a command from a network entity. For example, the UE device generates and transmits a DSR in response to receiving a command. The command may include one or more of the following: a media access control (MAC) control element (MAC CE); an identifier (ID) of a channel corresponding to the DSR; a delay timing threshold; or a delay volume threshold. In some cases, the first timer and the second timer are configured by a message that the network entity has sent to configure the UE device. As discussed further below, the network may implement other trigger conditions to improve wireless resource utilization based on the received DSR.

[0015] According to aspects of the present disclosure, the DSR may include useful information for a network entity to determine appropriate wireless resource allocation updates. For example, the DSR may include one or more identifiers (IDs) for one or more channels. The DSR may further include buffer size information for delay thresholds associated with one or more channels. The DSR may include a target level of resource allocation satisfaction for XR communications. The DSR may also include a maximum delay level allowable in the UE based on a memory buffer size, a delay time period for a layer, a delay volume for a layer, or a combination. Based on the DSR information, the network entity may reallocate wireless resources from one UE device to another UE device that experiences unsatisfied transmissions (e.g., delays exceeding a threshold). BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The described embodiments and advantages of the embodiments may be best understood by referring to the following description taken in conjunction with the accompanying drawings, which in no way limit any changes in form and detail that may be made to the described embodiments by one skilled in the art without departing from the spirit and scope of the described embodiments.

[0017] Figure 1 is a block diagram depicting an example environment for a user equipment (UE) device 105 to report delay status to a radio access network (RAN) 112 according to some embodiments;

[0018] Figure 2is a signaling diagram illustrating an example method of reporting delay status from the UE device 105 to the network entity 112 according to some embodiments.

[0019] Figure 3 is a signaling diagram depicting an example method of reporting delay status from a UE device 105 to a RAN 112 according to some embodiments;

[0020] Figure 4 shows example timers associated with reporting of delay status by a UE according to some embodiments;

[0021] Figure 5 Example events associated with delayed data for reporting delayed status are shown in accordance with some embodiments.

[0022] Figure 6 is a flow chart depicting a method for reporting delay status by a UE device according to some embodiments;

[0023] Figure 7 is a flow chart depicting a method for resource allocation by a network entity according to some embodiments; and

[0024] Figure 8 is a block diagram depicting an example device diagram of a UE device or communication device according to some embodiments.

[0025] FIG. 9 illustrates various examples of trigger conditions according to some embodiments. DETAILED DESCRIPTION

[0026] For ease of illustration, the following techniques are described in an example context in which one or more UE devices and a RAN implement one or more radio access technologies (RATs), including at least a fifth generation (5G) new radio (NR) standard (e.g., third generation partnership project (3GPP) release 15, 3GPP release 16, etc.) (hereinafter referred to as "5G NR" or "5G NR standard"). However, the present disclosure is not limited to networks configured with 5G NR RATs, but rather the techniques described herein may be applied to any combination of different RATs employed at UE devices and RANs. Furthermore, the present disclosure is not limited to the examples and contexts described herein, but rather the techniques described herein may be applied to any network environment.

[0027] Figure 11 is a block diagram of an example environment 100 for a user equipment (UE) device 105 to report a delay status to a radio access network (RAN) 112 according to some embodiments. The example environment 100 shows an example system architecture of a 5G system capable of delivering data for an extended reality (XR) application. As shown, relevant functions of the 5G system are shown, including a UE device 105, a RAN 112, and a core network (CN) 150. The CN 150 includes a user plane function (UPF) 155, a trusted data network (DN) 160, a policy control function (PCF) 162, and a network exposure function (NEF) 164. XR-specific functions or components may include a 5G-XR client 106 of the UE device 105, an application function (AF) 163 and an application server (AS) 166 in the trusted DN 160, and an AF 173 and an AS 176 in an external DN 170 that provides various XR applications. The external DN 170 may be a 5G-XR application provider that utilizes 5G system functions (e.g., coupled with the NEF 164 and UPF 155 of the 5G system). The UE device 105 including the 5G-XR aware application 107 may utilize the 5G-XR client 106 and the network function 150 using the network interface and API.

[0028] XR may refer to a human-computer interaction experience that is enhanced or replaced with visual, audio, and / or tactile computer-generated objects. For example, XR may be one or more of augmented reality (AR), mixed reality (MR), virtual reality (VR), and interpolations among these XR variants. AR refers to providing users with additional information or artificially generated items or content overlaid on the real surrounding environment. VR refers to a rendered version (e.g., generated by a computer) of a visual / audio scene. MR refers to an advanced form of AR in which some virtual elements are inserted into a physical scene with the intent to provide the illusion that the elements are part of the real scene. In some cases, AR, MR, and VR may be generally referred to as immersion, which typically requires measuring the user's movements (e.g., six degrees of freedom) and providing near-instantaneous feedback to the user (e.g., via visual, audio, and tactile components).

[0029] Computer technologies (e.g., 3D graphics and measurement) and wearable technologies (e.g., motion sensors, visual and audio feedback, etc.) are enablers of XR. For example, human-machine communication and human-human communication utilize handheld and wearable end-user devices (e.g., UE devices). These technologies typically capture, generate, process, and communicate with large amounts of data in real time (or with strict low latency requirements). Figure 1 As shown, the 5G-XR application and 5G-XR client of the UE device 105 can capture user data and communicate it to the RAN 112.

[0030] Cloud gaming (CG) is an example use case of XR, as CG can utilize AR, MR, or VR. CG applications typically offload a large amount of computation from various UE devices (e.g., VR headsets, cameras, motion sensors, smart phones, etc.) to edge servers or remote servers. CG and other XR use cases are typically characterized by quasi-periodic traffic (with possible jitter) and high downlink (DL) data rates (e.g., video streaming) combined with frequent uplink (UL) signaling (e.g., gesture / control updates and / or UL video streaming). In order to achieve cognitive presence and perceived presence, both DL and UL traffic can be characterized by relatively strict packet delay budgets (PDBs) or threshold criteria. However, current discontinuous reception (DRX) configurations are not well suited for (i) non-integer XR traffic periodicity, (ii) variable XR data rates, and / or (iii) quasi-periodic XR periodicity. The present disclosure provides methods and techniques for meeting these XR-driven requirements.

[0031] The set of expected XR and CG services presents a specific set of categories and characteristics of data streams (e.g., video), and they can change "on the fly" or dynamically. Additional information about running services from higher layers, such as QoS flow association, frame level QoS, ADU-based QoS, XR-specific QoS, etc., can be beneficial in facilitating informed selection of radio parameters by the RAN 112. XR application awareness by UE devices and network entities can improve user experience, improve NR system capacity to support XR services, and reduce UE power consumption (e.g., efficient radio parameters increase energy efficiency and can improve battery life in many small UE devices).

[0032] When evaluating XR capacity, a UE device 105 can be considered a satisfied UE if the XR data stream meets the corresponding packet error rate (PER) and PDB requirements, such as successfully transmitting more than a certain percentage of packets within a given air interface PDB. For example, in a DL-only evaluation, only DL streams are considered when identifying UE satisfaction. In an UL-only evaluation, only UL streams are considered when identifying UE satisfaction. Evaluating XR capacity at the system level involves calculating the maximum number of UE devices per cell (or user when the user has multiple UE devices) using at least the percentage of satisfied UEs among the connected UEs. For example, the percentage can be 90% or 95%.

[0033] The PDB can be used to specify or model the latency requirements of XR services in the RAN (e.g., air interface). For example, the PDB is a finite time threshold for a packet to be transmitted from the RAN 112 to the UE device 105 over the air. For a given packet, the downlink delay caused in the air interface can be measured from the time the packet arrives at the RAN 112 to the time the packet is successfully transmitted to the UE device 105. When the delay is greater than a given PDB for a packet, the packet is considered to have a violated PDB. The value of the PDB may vary for different applications and service types. XR services may try their best to meet the packet delivery success rate. For example, when the packet delivery delay exceeds a given PDB, the system assessment may consider the packet delivery to have failed. For example, for a DL stream, the expected packet delivery success rate may be 99% (PER less than 1%).

[0034] like Figure 1 As shown in the environment 100 of , the communication between the UE device 105 and the RAN 112 of various aspects of the present disclosure seeks to improve XR traffic flows to provide efficient resource allocation and scheduling for XR service characteristics (periodicity, multiple flows, jitter, latency, reliability, etc.). As previously mentioned, the XR capacity can be characterized in terms of the maximum number of users per cell using a target percentage of satisfied UE devices, and the RAN 112 can determine the conditions of unsatisfied UE devices to improve resource allocation efficiency. The present disclosure provides techniques for the RAN 112 to configure the UE device 105 to generate and transmit a delay status report to the RAN 112 when certain conditions (e.g., conditions that prevent inefficient resource consumption) are met.

[0035] In current practice in 5G NR, the RAN 112 may be aware of the buffer size level of the UE device 105 via buffer status reports. The RAN 112 may not know when data arrives at the UE's buffer and / or which UE device (among multiple UE devices including the UE device 105) may have more buffered data waiting in the buffer for an extended period of time. As a result, the RAN 112 may not be able to efficiently allocate resources (e.g., bandwidth, channel priority, etc.) to maximize network capacity for XR applications.

[0036] The present disclosure provides methods and techniques for overcoming such shortcomings by transmitting delay status reports from the UE device 105 to the RAN 112 (e.g., periodically, when a predefined triggering criterion is reached, or when required by the network). For example, the delay status report includes information about the volume of data on the delay of one or more channels and the satisfaction level. The RAN 112 can then adjust or update resource allocation based on the delay status reports (e.g., from multiple UE devices) to maximize the XR capacity of the environment 100. Figures 2 to 5Detailed examples are discussed further.

[0037] UE device 105 may report the delay status to one or more entities in the network. For example, Figure 2 1 shows a signaling diagram for UE device 105 to report delay status to network entity 112, and Figure 3 A method of reporting delay status within the UE device 105 to the RAN 112 is presented.

[0038] Figure 2 is a signaling diagram 200 depicting an example method of reporting delay status from a UE device 105 to a network entity 112 according to some embodiments. The UE device 105 may communicate with Figure 1 105. Likewise, the network entity 112 may correspond to the RAN 112. The signaling diagram 200 is not limited to a single instance of the UE device 105 or the network entity 112. In some cases, multiple UE devices may signal with the network entity 112, and the UE device 105 may signal with multiple network entities to report delay status of different radio bearers or logical channels.

[0039] although Figure 2 Example operations between the UE device 105 and the RAN 112 are shown, but in other implementations, different entities may perform similar or identical operations. For example, in some embodiments, instead of or in place of the RAN 112, another UE device may perform similar operations via a sidelink connection with the UE device 105 (e.g., via PC5 instead of Uu). That is, other UE devices may configure the UE device 105 to transmit a DSR via a sidelink for updating sidelink resource allocations. In some embodiments, instead of or in place of the UE device 105, another network entity (e.g., a base station, such as a 4G LTE base station, etc.) may monitor the XR traffic in its buffer (downlink, uplink, or both) and transmit the DSR when one or more trigger conditions are met. For example, a child base station may provide a delayed status report to a parent base station in an integrated access and backhaul (IAB) configuration. Other variants are possible without limitation to the examples of the UE device 105 and RAN 112 discussed below.

[0040] like Figure 2As shown, the network entity 112 transmits 210 a message to configure the UE device 105 regarding the delay status reporting process. For example, the network entity 112 transmits a first message to configure a first channel for the UE. The first channel may be a radio bearer or a logical channel. The first message may include a first delay time threshold, a first delay volume threshold, or both associated with the first channel. The first channel may refer to a channel set or a channel group. For example, the network transmits a first message to configure a channel set or a channel group for the UE device 105. There may be a time delay threshold or a volume threshold associated with the channel group. The channels in the group may apply the same time delay threshold. The volume threshold may be applied at the channel group level (and to each individual channel, if so configured). When applied at the channel group level, the volume threshold may be applied to the amount of data from the channel group.

[0041] The first message from the network entity 112 to the UE device 105 may be implemented in various forms. In an example, the first message may be a radio resource control (RRC) reconfiguration message. In another example, the first message may be an RRC setup message. In yet another example, the first message may be an RRC reconstruction message or an RRC recovery message. In some examples, the first message may be a system information message.

[0042] After receiving the delay status report configuration, the UE device 105 determines 220 to generate a delay status report by monitoring the delay status of the buffered data. For example, when the first data of the first channel arrives ( Figure 8 After the first data is transmitted to the uplink buffer (shown in FIG. 1 ), the UE device 105 monitors whether the queuing delay of the first data is longer than the first time delay threshold. The UE device 105 implements the monitoring by starting a first timer and associating the first timer with the first data. For example, when the first timer expires and the UE device 105 has not yet transmitted the first data from the buffer, the UE device 105 may consider the first data to be delayed. In other words, the recorded state of the first data may be indicated as delayed in the UE device 105. Over time, when the first data is transmitted (which may include receiving a positive confirmation from the first data receiver), the UE device 105 may clear the first data from the uplink buffer and remove the delayed state of the first data.

[0043] In some cases, due to data segmentation, only a portion of the data may have completed transmission. In this case, the UE device 105 may not consider the segmented first data to be delayed (and the delay status may be considered segment by segment). For example, under the Packet Data Convergence Protocol (PDCP), the UE device 105 may associate and start a timer for each arriving PDCP service data unit (SDU). If the timer expires and the PDCP SDU has not been transmitted to the network entity 112, the UE device 105 considers the PDCP SDU to be delayed. When the data is delayed, the UE device 105 may report the size of the delayed data (or the sum of all delayed data) to the network entity 112 in a Delay Status Report (DSR) (and mark the delayed data). After the UE device 105 has transmitted the first data, the UE device 105 may stop the first timer.

[0044] When triggered, the UE device 105 generates a delay status report 105 and transmits 230 the DSR to the network entity 112. The trigger depends on various conditions that can be configured by the network entity 112. In some cases, the trigger condition avoids wasting uplink resources when the DSR, although generated, may not be sufficient to notify the network entity 112 to update resource allocation. For example, the DSR may be generated due to time delays or excessive volume in a channel buffer of the UE device 105, but the corresponding channel may not have a sufficient priority level (as configured) for the DSR transmission. Figures 3 to 5 Various trigger conditions are further discussed and illustrated in FIG. 9 .

[0045] The DSR includes information from various aspects. For example, the DSR includes an identifier (ID) of an associated channel or channel set or channel group. A bitmap can be used to associate each bit in the bitmap with a channel or channel group. In this example, if a bit is set, it means that the delay status information of the corresponding delayed data is included in the DSR. 105 The DSR can provide corresponding buffer size information for the delayed data. In some cases, the buffer size information can indicate the actual buffer size or one or more buffer size ranges.

[0046] In some embodiments, the DSR may indicate a satisfaction level of the UE device 105. For example, the UE device 105 may calculate the percentage of data that is delayed and include the satisfaction level of the channel in the DSR. In some embodiments, the DSR may indicate a maximum delay duration of delayed data in an uplink buffer of the UE device 105. The maximum delay duration may include an indicator of an actual delayed period or a range covering the actual delayed period (e.g., the range may correspond to an urgency level).

[0047] The UE device 105 may transmit 230 the DSR in various forms. For example, the UE device 105 may transmit the DSR in a media access control element (MAC CE), for example, as a DSR MAC CE. The DSR MAC CE may be associated with a unique ID (e.g., a logical channel ID) to distinguish itself from other MAC CEs in a MAC protocol data unit (PDU). The UE device 105 may include other buffer-related status reports (e.g., as defined in the 5G NR standard) in the DSR MAC CE. For example, for each channel, the UE device 105 may include first buffer size information to indicate the buffer size of both delayed data and non-delayed data. The UE device 105 may also include second buffer size information to indicate the buffer size of delayed data. In some embodiments, the DSR MAC CE has a higher priority than data from other logical channels. For example, when assembling a MAC PDU, the UE device 105 may first include the DSR MAC CE in the MAC PDU. In some cases, the DSR MAC CE may include delay information (eg, remaining time) associated with data volume information (eg, volume of data to be transmitted).

[0048] In some embodiments, the DSR MAC CE may have different formats. For example, the DSR MAC CE may have a short format of 5 or / to 8 bits in length. The DSR MAC CE may have a long format of 16 or / to 32 bytes in length. Each format is identified by a unique ID such as a different logical channel identifier. Depending on the available space in the MAC PDU, the UE device 105 may select one of the different formats and include the DSR in the MAC PDU. The UE device 105 may report the DSR of each channel (e.g., in multiple channels or channel sets or channel groups). In one example, if the DSR MAC CE is not long enough to accommodate all DSRs, the UE device 105 first includes the DSR of the high priority channel / set / group (e.g., and does not transmit the low priority DSR due to the length limitation). However, in another example, the UE device 105 first includes the DSR of the channel with the largest amount of delayed data (and satisfies both the delay timing threshold and the delay volume threshold).

[0049] In some cases, when a DSR transmission is triggered at the UE device 105, there may not be available uplink radio resources for the UE device 105 to transmit the DSR. In this case, the UE device 105 may send a scheduling request to the network entity 112. In an example, the network entity 112 may allocate dedicated physical uplink control channel (PUCCH) resources for the UE device 105 to transmit such a scheduling request. The PUCCH resource allocation may be configured at 210 by a message transmitted from the network entity 112 to the UE device 105.

[0050] In some cases, instead of (or in lieu of) a scheduling request (e.g., when there is no PUCCH resource allocation), the UE device 105 initiates a random access procedure. For example, the network entity 112 may allocate a preamble or a physical random access channel (PRACH) opportunity for the UE device 105 to perform a random access procedure for DSR transmission. The PRACH opportunity includes time-frequency resources for the UE device to transmit the preamble. In some cases, the preamble or PRACH opportunity may be included in a message transmitted 210 from the network entity 112 to the UE device 105.

[0051] As shown, the network entity 112 then transmits 240 a resource allocation to the UE device 105 in response to the DSR. For example, after receiving the DSR from the UE device 105 (and other UE devices), the network entity 112 may allocate resources to the UE (and other UEs) using a channel or channel set / channel group with a higher priority because the DSR is triggered when delayed data in the UE device 105 negatively affects the XR capacity assessment. When there are multiple UE devices with a common priority level, the network entity 112 may allocate resources to the UE device with the largest volume of delayed data. The resource allocation update may allow the UE device 105 to increase the transmission bandwidth to shorten the time delay, reduce the volume of delayed data in the buffer, or both, thereby resulting in a positive satisfaction level for the UE device 105.

[0052] Figure 3 3 is a signaling diagram 300 depicting an example method of reporting delay status from the UE device 105 to the RAN 112 according to some embodiments. The signaling diagram 300 shares some common features with the signaling diagram 200 while including detailed features regarding various conditions for initiating DSR generation and / or triggering DSR transmission. Figure 2 As mentioned, different entities may replace the UE 105 or the RAN 112. As shown, the UE device 105 receives 310 a message from the RAN 112 that configures the UE device 105 with one or more channels and delay thresholds associated with the one or more channels for delay status reporting. See also Figure 2210 of FIG. 9 . When the triggering condition is met, the UE device 105 determines 320 to transmit the DSR. Various triggering conditions (eg, 322-328 and 910-950 of FIG. 9 ) are discussed below.

[0053] Based on the received configuration for delay status reporting, the UE device 105 monitors 322 first data arriving at least one uplink buffer of one or more channels. The one or more channels may include two or more channels that share a common set of associated delay thresholds. In some cases, the status of the first data in the uplink buffer may be separate from other triggering conditions that may cause the generation and transmission of a DSR (e.g., monitoring 322 may be an optional embodiment using dashed lines).

[0054] The UE device 105 determines 324 whether the delay of the first data in the buffer of the corresponding channel has reached the delay threshold received 310 earlier in the message. The delay threshold may include a delay timing threshold, a delay volume threshold, or both. The delay timing threshold may include corresponding timing thresholds of various timers. The delay volume threshold may include a configured volume limit configured for the uplink buffer to trigger DSR transmission (e.g., at 328 and with respect to Figures 4 to 5 When the delay of the first data has not reached 324 (no branch) the delay threshold, the operation of the UE device 105 returns to the UE device monitoring 322 for subsequent data arrival.

[0055] On the other hand, when the delay has reached 324 (yes branch) the delay threshold, the operation of the UE device 105 proceeds to 326a-b and 328. As shown, depending on the implementation, generating the DSR at 326a or 326b may occur before or after determining 328 the satisfaction of the trigger condition. Examples of various non-exhaustive trigger conditions 910-950 are shown in FIG. 9 and are described below in conjunction with Figure 4 and Figure 5 After the DSR is generated 326 and the triggering conditions are met 328, the UE device 105 transmits 330 the DSR to the RAN 112.

[0056] exist Figure 4 4 , graph 400 illustrates example delayed data volumes in an uplink buffer of UE device 105 (eg, y-axis) along a timeline (eg, x-axis). Figure 4Three example timing periods T1, T2, and T3 corresponding to three timer durations are shown. The three example timing periods correspond to: (1) a duration T1 measured by a first timer, in which specific data is already present in the uplink buffer; (2) a duration T2 measured by a second timer, which specifies periodic transmission or retransmission of a subsequent DSR after an initial DSR; and (3) a duration T3 measured by a third timer, which prohibits the UE device 105 from transmitting a DSR. The delayed timing threshold indicated by the message transmitted 310 from the RAN 112 may indicate the duration of at least one of the example timing periods T1, T2, and T3 (e.g., the message need not indicate all three timer durations, and all three timer durations may be specified in other ways based on other parameters, calculations, or protocols).

[0057] For example, the delay timing threshold may indicate a value of at least T1. Figure 4 As shown, when receiving the first data in at least one uplink buffer at t0, the UE device 105 starts a first timer. The first timer tracks at least a first duration layer (T1). When the UE device 105 has not yet transmitted the first data, the UE device 105 generates (e.g., at) the first timer when the first timer reaches the duration threshold T1. Figure 3 In other words, when the first timer expires at T1 and when the first data in the uplink buffer of the corresponding channel has a queuing delay greater than the delay timing threshold, the UE device 105 generates a DSR. See element 920 of FIG. 9. Figure 5 Discuss the different T1 layers.

[0058] In some cases, the configuration message defines or indicates a trigger condition based on both a volume threshold and a delay duration threshold. For example, the trigger condition may be satisfied when the volume of data in at least one uplink buffer is greater than a volume threshold defined relative to at least one of the delay duration thresholds. Figure 4 As shown, the first data stays in the uplink buffer for a period of time exceeding the delay time threshold T1, and the first data also exceeds the delay volume threshold V1 (e.g., the lower indicator on the y-axis in the graph 400). Therefore, the trigger condition is met, and the UE device 105 transmits at t1 at the end of the duration T1 (e.g., at Figure 3 330) DSR.

[0059] In some cases, the delay volume threshold may include multiple layers. In a different scenario, for example, if the delay volume threshold of the first data is configured as V2 greater than the threshold volume V1 (e.g., the upper indicator on the y-axis in the graph 400), the trigger condition is not satisfied when the timer T1 expires, and the UE device 105 does not transmit the DSR at t1. For example, if Figure 3 As shown, when the UE device 105 determines that the trigger condition has not been met 328 (no branch), the operation returns to the UE device monitoring 322 for the arrival of subsequent data. D When the uplink buffer is cleared at t2 thereafter, the UE device 105 may cancel or clear the DSR associated with the first data.

[0060] The UE device 105 may retransmit the DSR or periodically transmit another DSR based on monitoring the second timer of periodicity T2. Figure 4 As shown, when both the second timer (tracking an integer cycle of T2) and the first timer (e.g., T1 of the delayed data in the uplink buffer) expire, the UE device 105 can retransmit the DSR at t4. See element 910 of Figure 9. The UE device 105 can stop the second timer in various situations. For example, after the UE device 105 has no delayed data in the uplink buffer, the UE device 105 stops the second timer. In some embodiments, the UE device 105 stops the second timer when the amount of delayed data has become less than the delay volume threshold. In some embodiments, the UE device 105 stops the second timer when the MAC entity is reset. In some embodiments, when the UE device 105 receives a command from the RAN 112 requesting the UE to stop the second timer (not shown), the UE device 105 stops the second timer. For example, the command can be a MAC CE with a unique logical channel to distinguish itself from other MAC CEs. In some cases, the UE device 105 can start or restart the second timer after transmitting the current or most recently generated DSR. The first message includes a periodicity for setting the time length of the second timer.

[0061] If (pre-existing or new) delayed data continues to experience a delay in excess of T1 in the uplink buffer, and the third timer does not prohibit retransmission, retransmission of the DSR may occur periodically within each complete cycle of T2. The third timer measures the duration for which the UE device 105 should not retransmit a subsequent DSR, even if the trigger condition is satisfied after the previous DSR has been transmitted. For example, after the UE device 105 transmits the DSR at t1, the UE device 105 starts the third timer and may not transmit another DSR until after t2. The third timer prevents frequent transmission of DSRs that may overburden communication overhead. In some embodiments, a message transmitted 310 from the RAN 112 to the UE device 105 configures the duration T3 of the third timer. In some embodiments, regardless of the configuration of the third timer, when the UE device receives a new uplink grant from the RAN 112, the UE device 105 may not transmit another DSR (or DSRs) immediately after the most recent DSR transmission.

[0062] Another example of a trigger condition includes: when there is delayed data in the uplink buffer, the UE device 105 monitors the arrival of new data in one or more configured channels. For example, when new data arrives in the uplink buffer and the UE device 105 has delayed data in the uplink buffer, the transmission of the DSR can be triggered. In some embodiments, the trigger condition includes: when the amount of delayed data in the uplink buffer is greater than the delay volume threshold, the new data arrival is detected.

[0063] In some cases, as shown in Figure 9 at element 930, the trigger condition is determined by the amount of delayed data. For example, when the total amount of delayed data in the UE device 105 is greater than a threshold, the UE device 105 transmits the DSR. The total amount of delayed data can be considered for all channels as a whole, rather than for individual channels / sets / groups.

[0064] In some cases, as shown in FIG9 at element 940, the triggering condition is in response to signaling from the RAN 112. For example, the UE device 105 may transmit the DSR when the UE device 105 receives a command from the RAN 112 requesting the DSR. If the UE device 105 has not yet generated the DSR, the UE device 105 may transmit a notification to the RAN 112 announcing the DSR and / or transmit a subsequent DSR to be generated when the delay threshold is met.

[0065] In some embodiments, the command is communicated in a MAC CE. In some embodiments, the command includes an ID of a channel / set / group so that the UE device reports a delay status for a specific channel / set / group. In some embodiments, the command includes a delay threshold. The delay threshold may supplement, update, or replace the delay threshold configured by the message at 310. The commanded delay threshold may indicate a delay time threshold and / or a delay volume threshold. When the delayed data exceeds a threshold specified in the uplink buffer, the UE device 105 may generate a DSR accordingly.

[0066] In some embodiments, as shown in FIG. 9 at element 950, the trigger condition is associated with other uplink transmissions such as a buffer status report. For example, when the UE device 105 triggers a buffer status report, the buffer status report trigger automatically triggers a DSR transmission, and the UE device 105 generates a DSR transmission accordingly. On the other hand, the UE device 105 can be configured to associate a buffer status report with a DSR. For example, if the UE device 105 triggers a DSR, the UE device 105 also generates a buffer status report. Both DSR and buffer status reports can facilitate the RAN 112 to monitor the uplink buffer status of multiple UE devices in order to schedule radio resources to improve wireless capacity, which can greatly benefit XR applications.

[0067] As discussed above, several factors may affect the triggering conditions: (1) how long the data has been delayed (as measured by the first timer); (2) the timing of the reporting behavior to ensure timely reporting and prevent unnecessary reporting (e.g., the second timer and the third timer); (3) how much data has been delayed in the uplink buffer (as measured in terms of volume); and (4) the priority of the channel in the uplink buffer (e.g., not all UE devices or channels are treated equally). Figure 5 Duration layers and channel priorities are discussed further.

[0068] Figure 5An example event 500 for reporting a delay status associated with delayed data is shown. The layers of the first timer may include a series of segment durations. As shown, on the top row, four example duration layers of T1 are provided. The four example layers of T1 include: (1) within 20ms; (2) between 21 and 40ms; (3) between 41 and 80ms; and (4) 81ms or more. In some cases, layer information may be provided in the DSR so that the RAN 112 can determine resource allocation and / or channel prioritization. In some embodiments, the series of segment durations includes incremental length increases, such as 0-10ms, 11-30ms, 31-60ms, and above 61ms. Note that although this example uses ms duration units, alternative measurement units may be used.

[0069] Figure 5 FIG. 1 shows two priority levels of uplink buffers corresponding to two channels. As shown, priority levels are provided for buffer 1 of channel 1 and buffer 2 of channel 2. Priority 1 of channel 1 is higher than priority 2 of channel 2. Three examples (A, B, and C) of delayed data are shown. The delayed data has different delay properties in terms of delay duration and channel priority level.

[0070] In some embodiments, the triggering condition associated with DSR specifies that the channel configured by RAN 112 for DSR has a higher priority than other channels. Figure 5 As shown, when both delayed data B and C are in layer 2, because delayed data C has a higher priority than delayed data B, UE device 105 transmits a DSR associated with delayed data C, but does not transmit a DSR associated with delayed data B. Similarly, when the first timer expires and the first channel has the highest priority among channels having data or delayed data in the uplink buffer, the trigger condition is met.

[0071] In some embodiments, the trigger condition includes advancing the layer duration of the first timer. For example, the delayed data A may not have reached the delay volume threshold and does not meet the trigger condition for DSR transmission. Therefore, when the delayed data A is in layer 1 (e.g., within 20ms), the UE device 105 does not transmit the DSR (even if the first timer has expired at the first layer). When the time delay of the delayed data extends to the next layer or another specified layer (e.g., the third layer or the fourth layer), the UE device 105 can transmit the DSR.

[0072] For low priority channels, the trigger conditions may include exceeding the delay volume threshold and the highest layer of the first timer (e.g., Figure 5For example, upon reaching layer 4, the UE device 105 may transmit only the DSR corresponding to the delayed data B.

[0073] In some embodiments, the UE combines delayed data within the layer to meet the volume threshold of the delay for triggering DSR transmission. For example, assuming that each of the delayed data A and the delayed data C has an amount lower than the delay volume threshold for the channel in the uplink buffer, the UE device 105 may not trigger the corresponding DSR. When the delayed data A stays in the uplink buffer for a duration extending into layer 2 (and the delayed data C stays in layer 2), the size of the combination of delayed data A and C is greater than the delay volume threshold. Therefore, when the delayed data A arrives at layer 2, the UE device 105 transmits the DSR generated relative to the delayed data A when in layer 1 (and may or may not include information about the delayed data C in layer 2). In this way, the variables of delay layer, delay volume, and channel priority can all interact. Using these parameters, the network 112 can request DSR at a frequency that helps improve system capacity while limiting the overhead used to transmit the DSR.

[0074] Figure 6 6 is a flow chart depicting a method 600 for reporting a delay status by a UE device according to some embodiments. The method 600 is performed by processing logic including hardware (e.g., circuitry, dedicated logic, programmable logic, processor, processing device, central processing unit (CPU), system on chip (SoC), etc.), software (e.g., instructions and / or applications running / executing on a processing device), firmware (e.g., microcode), or a combination thereof. The method 600 is performed by a processor such as Figure 1 , Figure 2 or Figure 3 The UE device 105 is executed by the UE device.

[0075] refer to Figure 6 and Figure 7 , methods 600, 700 illustrate example functionality used by various embodiments. Although specific functional blocks ("blocks") are disclosed in methods 600, 700, such blocks are examples. That is, embodiments are well suited to performing various other blocks or variations of the blocks listed in methods 600, 700. The blocks in methods 600, 700 may be performed in an order different from the order presented, and not all blocks in methods 600, 700 must be performed.

[0076] like Figure 6 As shown, method 600 includes block 610: receiving a message (eg, Figure 2The method 600 includes a block 620 of generating a delay status report (DSR) (e.g., Figure 2 The delay of the first data includes a length of time during which the first data has been held in at least one uplink buffer. The method 600 includes a block 630 of transmitting a DSR to a network entity when a trigger condition associated with the DSR is met (e.g., Figure 2 Operation 230).

[0077] In aspects, the one or more channels may include two or more channels that share a common set of associated delay thresholds.The delay threshold may include at least one of a delay timing threshold or a delay volume threshold.

[0078] In various aspects, the message to configure the UE device may include at least one of: a radio resource control (RRC) reconfiguration message; an RRC setup message; an RRC reestablishment message; an RRC resume message; or a system information message.

[0079] In various aspects, generating the DSR is based on a first timer. Upon receiving first data in at least one uplink buffer of one or more channels, the UE device may start the first timer T1. Figure 4 The first timer may track at least a first duration layer. When the first timer reaches the first duration layer and when the UE device has not yet transmitted the first data, the UE device may generate a DSR. In some cases, the first duration layer is one of a plurality of duration layers. Figure 5 The plurality of duration layers may include a series of segment durations, which may include incremental length increases. In various aspects, when the UE device has completed transmitting the first data, the UE device may stop the first timer.

[0080] The triggering condition associated with the DSR may include: the first timer T1 expires before the UE device has completed transmitting the first data. In some cases, the triggering condition associated with the DSR may further include: one or more channels configured by the network entity have a higher priority than other channels. Figure 5 In some cases, the trigger condition associated with the DSR may further include: a volume of the first data in the at least one uplink buffer is greater than a volume threshold V1 defined in at least one of the delay thresholds.

[0081] In various aspects, when transmitting the DSR to the network entity, the UE device may start a second timer T2. When the second timer expires, the UE device may generate and transmit a second DSR. In some embodiments, the UE device stops the second timer when the UE device has cleared data exceeding at least one of the delay thresholds in at least one uplink buffer. In some embodiments, the UE device stops the second timer when the volume of data exceeding at least one of the delay thresholds in at least one uplink buffer has become less than a volume threshold V1 defined in at least one of the delay thresholds. In some embodiments, the UE device stops the second timer when the MAC entity is reset. In some embodiments, the UE device stops the second timer when the UE device receives a request to stop the second timer from the network entity. The second timer may be stopped by a request from Figure 2 or Figure 3 The network entity 112 receives the messages 210 and 310 to configure the first timer and the second timer.

[0082] In various aspects, the UE device may start a third timer T3 when transmitting a DSR and refrain from transmitting the next DSR until the third timer has expired (see Figure 4 ), wherein the third timer and the first timer are configured by a message configuring the UE device. In some cases, the trigger condition associated with the next DSR may include the expiration of the third timer.

[0083] In various aspects, a trigger condition associated with a DSR may include receiving new data arriving at at least one uplink buffer of one or more channels. The delay of the first data may further include an amount of delayed data greater than a delay volume threshold. The trigger condition associated with the DSR may include receiving a command from a network entity and generating and transmitting the DSR in response to receiving the command. The command may include one or more of the following: a MAC CE, an ID of a channel for which the DSR is to be generated, a delay timing threshold, or a delay volume threshold.

[0084] In various aspects, the triggering condition associated with the DSR may be incorporated into generating a buffer status report.Transmitting the DSR to the network entity may include transmitting both the buffer status report and the DSR to the network entity.

[0085] In various aspects, the DSR may include at least one of: one or more identifiers (IDs) of one or more channels; buffer size information of first data in at least one uplink buffer; a target level of resource allocation satisfaction for extended reality (XR) communication; or a maximum delay level allowable in the UE based on a memory buffer size or a delay threshold. The delay threshold may include at least one of: a delay time of a layer or a delay volume of a layer.

[0086] In various aspects, transmitting a DSR to a network entity may include: transmitting a MAC CE or physical layer signaling of transmitting the DSR. The MAC CE may include an ID associated with the DSR. The MAC CE may further include a buffer status indicating a corresponding amount of both delayed data and non-delayed data. The MAC CE may include multiple DSRs corresponding to multiple channels in one or more channels. The MAC CE may prioritize multiple DSRs based on priority sorting of multiple channels. In some embodiments, the priority sorting includes two or more sorting layers. The two or more sorting layers may include at least: a first sorting layer based on a priority category and a second sorting layer based on a corresponding volume of delayed data.

[0087] In various aspects, the UE device may receive a new uplink grant from the network entity and cancel the subsequent DSR when the DSR has been previously transmitted to the network entity. In various aspects, when the UE device has completed transmitting the first data at t2, the UE device may clear the first data in the at least one uplink buffer. C D . See Figure 4 .

[0088] The UE device may receive an allocation of additional resources, an indication to adjust transmission priority, or both from a network entity in response to receiving the DSR. The allocation of additional resources may reduce a data delay state of the UE device.

[0089] Figure 7 is a flow chart depicting a method for resource allocation by a network entity according to some embodiments. The method 700 is performed by processing logic including hardware (e.g., circuitry, dedicated logic, programmable logic, processor, processing device, central processing unit (CPU), system on chip (SoC), etc.), software (e.g., instructions and / or applications running / executing on a processing device), firmware (e.g., microcode), or a combination thereof. The method 700 is performed by a processor such as Figure 1 , Figure 2 or Figure 3 The network entity 112 is executed by the network entity.

[0090] like Figure 7As shown, method 700 includes block 710: transmitting a message from a network entity to a user equipment (UE) device to configure a delay threshold associated with a wireless communication channel for the UE device. See also 210, 310, 610. Method 700 includes block 730: receiving a DSR from the UE device. The DSR indicates that a delay of first data in at least one uplink buffer of the wireless communication channel has reached a delay threshold. The delay includes a length of time during which the first data has been retained in the at least one uplink buffer. Method 700 includes block 740: in response to the DSR, transmitting an allocation of wireless resources in the UE device to address the delay reported in the DSR. See also Figure 2 of 240.

[0091] In various aspects, a network entity may receive multiple DSRs from multiple UE devices. The network entity may allocate radio resources to corresponding UE devices based on corresponding priorities, delays, or both. In some embodiments, the network entity transmits a message configuring the UE device by transmitting a MAC CE indicating a service priority (e.g., a priority of one or more channels). The network entity may allocate additional radio resources in the UE device based on the service priority. In some embodiments, the network entity transmits to the UE device (1) an allocation of additional resources, (2) an indication for adjusting transmission priority, or (3) both. In some embodiments, the message configuring the UE device includes at least one of the following: an RRC reconfiguration message; an RRC setup message; an RRC reconstruction message; an RRC recovery message; or a system information message.

[0092] Figure 8 800 is a block diagram illustrating an example device diagram 800 of a UE device 805 (e.g., UE device 105) according to some embodiments. Device diagram 800 describes a UE device that can implement various aspects of reporting delay status (e.g., in an XR application). UE device 805 may include Figure 8 The UE device 805 includes an antenna 801, a radio frequency (RF) front end 804, and one or more RF transceivers 806 (e.g., a 3GPP fourth generation (4G) long term evolution (LTE) transceiver 806-1 and a 5G NR transceiver 806-2) for communicating with the UE. Figure 1802.15.4, ZigBee, Thread, etc.) to communicate with other UE devices (not shown) such as those UE devices in a wireless tethered configuration with the UE device 805. The RF front end 804 couples or connects the LTE transceiver 806-1, the 5G NR transceiver 806-2, and the local wireless network transceiver 806-3 to the antenna 801 to facilitate various types of wireless communications.

[0093] The antenna 801 of the UE device 805 includes an array of multiple antennas configured to be similar or different from each other. The antenna 801 and the RF front end 804 are tuned to and / or can be tuned to one or more frequency bands, such as those defined by 3GPP LTE, 3GPP 5GNR, IEEE WMAN or other communication standards. The antenna 801, the RF front end 804, the LTE transceiver 806-1, the 5GNR transceiver 806-2 and / or the local wireless network transceiver 806-3 are configured to support beamforming (e.g., analog, digital or hybrid), or in-phase and orthogonal (I / Q) operation (e.g., I / Q modulation or demodulation operation) for transmission and reception of communication with the base station 112. By way of example, the antenna 801 and the RF front end 804 operate in sub-gigahertz bands, sub-6 GHz bands and / or above 6 GHz bands defined by 3GPP LTE, 3GPP 5G NR or other communication standards.

[0094] Using at least a portion of antenna 801, UE device 805 can form a beam that is steered or unsteered, wide or narrow, or shaped (e.g., shaped into a hemisphere, cube, fan, cone, or cylinder). One or more transmit antennas can produce an unsteered omnidirectional radiation pattern or a steerable beam.

[0095] The UE device 805 includes one or more sensors 808 implemented to detect various attributes such as temperature, supplied power, power usage, battery status, etc. The sensors 808 may include any one or a combination of temperature sensors, thermistors, battery sensors, and power usage sensors. The UE device 805 uses the various attributes to determine whether the UE device 805 is capable of connecting to the cellular network 112 over its air interface, or whether the UE device 805 simply has sufficient resources (e.g., battery power, etc.) to connect to the cellular network 112 using a sidelink connection to another UE device.

[0096] The UE device 805 also includes at least one processor 810 and a non-transitory computer-readable storage medium 812 (CRM812). The computer-readable storage medium described herein does not include propagation signals. The CRM 812 includes any suitable memory or storage device that can be used to store device data 814 of the UE device 805, such as a random access memory (RAM), a static RAM (SRAM), a dynamic RAM (DRAM), a non-volatile RAM (NVRAM), a read-only memory (ROM), or a flash memory. The device data 814 includes, for example, user data, multimedia data, beamforming codebooks, applications, and / or an operating system of the UE device 805, which can be executed by the processor 810 to implement user plane communications, control plane signaling, and user interaction with the UE device 805.

[0097] The CRM 812 includes a communication manager 816. Alternatively or additionally, the communication manager 816 is implemented in whole or in part as hardware logic or circuitry that is integrated or separate from other components of the UE device 805. The communication manager 816 configures the RF front end 804, the LTE transceiver 806-1, the 5G NR transceiver 806-2, and / or the local wireless network transceiver 806-3 to perform one or more wireless communication operations.

[0098] The CRM 812 further includes a DSR manager 818, a DSR configuration client 820, and one or more uplink buffers 822. The DSR manager 818 and the DSR configuration client 820 allow the UE device 805 to be configured by a network entity to generate and transmit DSRs regarding delayed data in the one or more uplink buffers 822. In some embodiments, one or more of these components are implemented in whole or in part as hardware logic or circuitry that is integrated or separate from other components of the UE device 805.

[0099] Unless specifically noted otherwise, terms such as "establishing", "receiving", "transmitting", etc. refer to actions and processes performed or implemented by a computing device that manipulate data represented as physical (electronic) quantities within registers and memories of the computing device into other data similarly represented as physical quantities within the computing device memory or registers or other such information storage, transmission or display devices. In addition, the terms "first", "second", "third", "fourth", etc. as used herein are intended as labels to distinguish different elements and may not necessarily have ordinal meanings according to their numerical designations.

[0100] The examples described herein also relate to an apparatus for performing the operations described herein. This apparatus may be specially constructed for the desired purpose, or the apparatus may include a general-purpose computing device selectively programmed by a computer program stored in the computing device. Such a computer program may be stored in a computer-readable non-transitory storage medium.

[0101] The methods and illustrative examples described herein are not inherently related to any particular computer or other device. Various general purpose systems may be used according to the teachings described herein, or more specialized devices may be conveniently constructed to perform the required method steps. The required structures of a variety of these systems will be presented as described above.

[0102] The above description is intended to be illustrative rather than restrictive. Although the present disclosure has been described with reference to specific illustrative examples, it will be appreciated that the present disclosure is not limited to the described examples. The scope of the present disclosure should be determined with reference to the following claims and the full scope of equivalents to which the claims are authorized.

[0103] As used herein, the singular forms "a", "an", "said", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should be further understood that the terms "comprises", "comprising", "includes", and / or "including" when used herein specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. Therefore, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting.

[0104] It should also be noted that in some alternative implementations, the functions / actions noted may not occur in the order noted in the figures. For example, two figures shown in succession may actually be performed substantially simultaneously or may sometimes be performed in reverse order, depending on the functionality / actions involved.

[0105] Although the method operations are described in a particular order, it should be understood that other operations may be performed between the described operations, that the described operations may be adjusted so that they occur at slightly different times, or that the described operations may be distributed in a system that allows the processing operations to occur at various intervals associated with the process.

[0106] Various units, circuits, or other components may be described or claimed as being "configured to" or "configurable to" perform one or more tasks. In such contexts, the phrases "configured to" or "configurable to" are used to represent a structure by indicating that a unit / circuit / component includes a structure (e.g., a circuit system) that performs one or more tasks during operation. Thus, even if a specified unit / circuit / component is not currently operating (e.g., not turned on), it can be said that the unit / circuit / component is configured to perform a task, or is configurable to perform a task. Units / circuits / components used with the "configured to" or "configurable to" language include hardware - e.g., circuits, memory storing program instructions executable to implement operations, etc. The recitation that a unit / circuit / component is "configured to" perform one or more tasks, or "configurable to" perform one or more tasks is expressly intended not to invoke the sixth paragraph of 35 USC §112 with respect to that unit / circuit / component. Additionally, "configured to" or "configurable to" may include general structures (e.g., general circuitry) manipulated by software and / or firmware (e.g., an FPGA or a general purpose processor executing software) to operate in a manner capable of performing the tasks in question. "Configured to" may also include adjusting a manufacturing process (e.g., a semiconductor manufacturing facility) to manufacture a device (e.g., an integrated circuit) suitable for implementing or performing one or more tasks. "Configurable to" is expressly intended not to apply to blank media, an unprogrammed processor or an unprogrammed general purpose computer, or an unprogrammed programmable logic device, programmable gate array, or other unprogrammed device, unless accompanied by a programming medium that imparts the unprogrammed device with the ability to be configured to perform the disclosed functions.

[0107] For the purpose of explanation, the above description has been described with reference to specific embodiments. However, the above illustrative discussion is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments are selected and described in order to best explain the principles of the embodiments and their practical application, so that those skilled in the art can best utilize the embodiments and various modifications that may be suitable for the intended specific use. Therefore, the embodiments of the present invention are considered to be illustrative and not restrictive, and the disclosure is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims. Example aspects

[0108] Example 1 is a method of wireless communication by a user equipment (UE) device, the method comprising: receiving a message from a network entity to configure a delay threshold associated with a wireless communication channel for the UE device; upon determining that a delay of first data arriving at at least one uplink buffer of the wireless communication channel has reached the delay threshold, generating a delay status report (DSR); and When a trigger condition associated with the DSR is met, the DSR is transmitted to the network entity.

[0109] Example 2 is a method according to Example 1, wherein the wireless communication channel includes two or more channels that share a common set of associated delay thresholds, and wherein the delay threshold includes at least one of a delay timing threshold or a delay volume threshold.

[0110] Example 3 is a method according to any of Examples 1 or 2, wherein the message to configure the UE device includes at least one of: Radio Resource Control (RRC) reconfiguration message; RRC setup message; RRC re-establishment message; RRC recovery message; or System information message.

[0111] Example 4 is a method according to any one of Examples 1 to 3, wherein generating the DSR comprises: starting a first timer upon receiving the first data in the at least one uplink buffer of the wireless communication channel, wherein the first timer tracks at least a first duration layer; and The DSR is generated when the first timer reaches the first duration layer and when the UE device has not completed transmitting the first data.

[0112] Example 5 is a method according to example 4, wherein the first duration layer is one duration layer of a plurality of duration layers.

[0113] Example 6 is a method according to example 5, wherein the plurality of duration layers comprises a series of segmented durations having incremental increases in length.

[0114] Example 7 is the method according to Example 4, further comprising: When the UE device removes the first data from the at least one uplink buffer, the first timer is stopped.

[0115] Example 8 is a method according to Example 4, wherein the trigger condition associated with the DSR comprises: The first timer expires before the UE device has completed transmitting the first data.

[0116] Example 9 is the method of Example 8, wherein the trigger condition associated with the DSR further comprises at least one of: The wireless communication channel configured by the network entity has a higher priority than other channels; or A volume of the first data in the at least one uplink buffer is greater than a volume threshold defined in the delay threshold.

[0117] Example 10 is the method according to Example 4, further comprising: When transmitting the DSR to the network entity, starting a second timer; When the second timer expires, generating and transmitting a second DSR; and The second timer is stopped when: The UE device has cleared data exceeding the delay threshold in the at least one uplink buffer; the volume of data in the at least one uplink buffer has become smaller than a volume threshold defined in the delay threshold; Reset the Media Access Control (MAC); or A request to stop the second timer is received from the network entity.

[0118] Example 11 is the method of Example 10, wherein the first timer and the second timer are configured by the message received from the network entity.

[0119] Example 12 is the method according to Example 4, further comprising: When transmitting the DSR, starting a third timer; and Refraining from transmitting a next DSR until the third timer has expired, wherein the third timer and the first timer are configured by the message configuring the UE device.

[0120] Example 13 is the method of Example 12, wherein the trigger condition associated with the next DSR comprises expiration of the third timer.

[0121] Example 14 is a method according to Example 1, wherein the trigger condition associated with the DSR comprises: New data arriving at the at least one uplink buffer of the wireless communication channel is received, wherein the delay of the first data further includes an amount of delayed data greater than a delay volume threshold.

[0122] Example 15 is a method according to Example 1, wherein the trigger condition associated with the DSR comprises: receiving a command from the network entity; and generating and transmitting the DSR in response to receiving the command, wherein the command includes at least one of: Medium Access Control (MAC) Control Element (MAC CE); an identifier (ID) of the channel for which the DSR is generated; Delay timing threshold; or Delay volume threshold.

[0123] Example 16 is a method according to Example 1, wherein the triggering condition associated with the DSR includes: generating a buffer status report.

[0124] Example 17 is the method of Example 16, wherein transmitting the DSR to the network entity comprises: Both the buffer status report and the DSR are transmitted to the network entity.

[0125] Example 18 is a method according to any one of Examples 1 to 13, wherein the DSR includes at least one of: one or more identifiers (IDs) of one or more channels; buffer size information of the first data in the at least one uplink buffer; The target level of satisfaction of resource allocation for extended reality (XR) communications; or A maximum delay level allowable in the UE based on a memory buffer size or at least one of: The delay time of one layer, or The delayed volume of the first floor.

[0126] Example 19 is the method of any one of Examples 1 to 18, wherein transmitting the DSR to the network entity comprises: transmitting a medium access control element (MAC CE), wherein the MAC CE includes an identifier (ID) associated with the DSR; or The physical layer signaling of the DSR is transmitted.

[0127] Example 20 is the method of Example 19, wherein the MAC CE further includes a buffer status indicating respective amounts of both delayed data and non-delayed data.

[0128] Example 21 is a method according to Example 19, wherein the MAC CE includes a plurality of DSRs corresponding to a plurality of wireless communication channels, and wherein the MAC CE prioritizes the plurality of DSRs based on a priority ranking of the plurality of wireless communication channels.

[0129] Example 22 is a method according to Example 21, wherein the priority sorting includes two or more sorting layers, and the two or more sorting layers include at least: A first ranking layer based on priority categories; and A second sorting layer based on the corresponding volume of delayed data.

[0130] Example 23 is a method according to any one of Examples 1 to 22, further comprising: receiving a new uplink grant from the network entity; and When the DSR has been previously transmitted to the network entity, a subsequent DSR is cancelled.

[0131] Example 24 is a method according to any one of Examples 1 to 23, further comprising: An allocation of additional resources, an indication to adjust transmission priority, or both are received from the network entity.

[0132] Example 25 is a method according to any one of Examples 1 to 24, further comprising: clearing the first data in the at least one uplink buffer when the UE device has completed transmitting the first data.

[0133] Example 26 is a method of wireless communication by a network entity, the method comprising: transmitting to a user equipment (UE) device a message configuring a delay threshold associated with a wireless communication channel for the UE device; receiving a delay status report (DSR) from the UE device, the DSR indicating that a delay of first data of at least one uplink buffer of the wireless communication channel has reached the delay threshold, the delay comprising a length of time during which the first data has been retained in the at least one uplink buffer; and In response to the DSR, an allocation of radio resources in the UE device is transmitted to account for the delay reported in the DSR.

[0134] Example 27 is the method according to Example 26, further comprising: receiving a plurality of DSRs from a plurality of UE devices; and Radio resources are allocated to corresponding UE devices based on corresponding priorities, delays, or both.

[0135] Example 28 is a method according to Example 26, wherein transmitting the message to configure the UE device comprises: transmitting a media access control element (MAC CE) indicating a traffic priority; and The allocation of radio resources in the UE device is based on the service priority.

[0136] Example 29 is the method of Example 28, wherein transmitting the allocation of radio resources to the UE comprises: (1) allocation of additional resources, (2) indication for adjusting transmission priority, or (3) both.

[0137] Example 30 is the method of Example 26, wherein the message to configure the UE device includes at least one of: Radio Resource Control (RRC) reconfiguration message; RRC setup message; RRC re-establishment message; RRC recovery message; or System information message.

[0138] Example 31 is the method of Example 26, wherein the DSR for includes at least one of: an identifier (ID) of the wireless communication channel; buffer size information of the first data in the at least one uplink buffer; The target level of satisfaction of resource allocation for extended reality (XR) communications; or A maximum delay level allowable in the UE based on a memory buffer size or at least one of: The range of delay times, or The extent of the delayed volume.

[0139] Example 32 is a user equipment (UE), comprising: one or more radio frequency (RF) modems; a processor coupled to the one or more RF modems; and At least one memory storing executable instructions for manipulating the processor or at least one of the one or more RF modems to perform a method according to any one of Examples 1 to 25.

[0140] Example 33 is a network entity comprising: one or more radio frequency (RF) modems; a processor coupled to the one or more RF modems; and At least one memory storing executable instructions for manipulating the processor or at least one of the one or more RF modems to perform a method according to any one of Examples 26 to 31.

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: receiving a message from a network entity configuring a delay threshold associated with a wireless communication channel for the UE device; upon determining that a delay of first data arriving at at least one uplink buffer of the wireless communication channel has reached the delay threshold, generating a delay status report DSR, the delay of the first data comprising a length of time during which the first data has been maintained in the at least one uplink buffer; and When a trigger condition associated with the DSR is met, the DSR is transmitted to the network entity.

2. The method of claim 1 , wherein the wireless communication channels comprise two or more channels that share a common set of associated delay thresholds, and wherein the delay thresholds comprise at least one of a delay timing threshold or a delay volume threshold.

3. The method according to any one of claims 1 or 2, wherein the message for configuring the UE device comprises at least one of the following: Radio Resource Control RRC reconfiguration message; RRC setup message; RRC re-establishment message; RRC recovery message; or System information message.

4. The method according to any one of claims 1 to 3, wherein generating the DSR comprises: starting a first timer upon receiving the first data in the at least one uplink buffer of the wireless communication channel, wherein the first timer tracks at least a first duration layer; as well as The DSR is generated when the first timer reaches the first duration layer and when the UE device has not completed transmitting the first data. 5 . The method of claim 4 , wherein the first duration layer is one of a plurality of duration layers comprising a series of segmented durations having incremental increases in length.

6. The method according to claim 4, further comprising: When the UE device removes the first data from the at least one uplink buffer, the first timer is stopped.

7. The method of claim 4, wherein the trigger condition associated with the DSR comprises at least one of: The first timer expires before the UE device has completed transmitting the first data; The wireless communication channel configured by the network entity has a higher priority than other channels; or A volume of the first data in the at least one uplink buffer is greater than a volume threshold defined in the delay threshold.

8. The method of claim 4, further comprising at least one of the following: When transmitting the DSR to the network entity, starting a second timer; When the second timer expires, generating and transmitting a second DSR; and The second timer is stopped when: The UE device has cleared data exceeding the delay threshold in the at least one uplink buffer; the volume of data in the at least one uplink buffer has become smaller than a volume threshold defined in the delay threshold; Reset the Media Access Control MAC; or A request to stop the second timer is received from the network entity.

9. The method according to claim 4, further comprising: When transmitting the DSR, starting a third timer; as well as Refraining from transmitting a next DSR until the third timer has expired, wherein the third timer and the first timer are configured by the message configuring the UE device.

10. The method of claim 1, wherein the triggering condition associated with the DSR comprises: New data arriving in the at least one uplink buffer of the wireless communication channel is received, wherein the delay of the first data further includes an amount of delayed data greater than a delay volume threshold.

11. The method of claim 1 , wherein the triggering condition associated with the DSR comprises: receiving a command from the network entity; and generating and transmitting the DSR in response to receiving the command, wherein the command includes at least one of: Media Access Control MAC Control Element MAC CE; The identifier ID of the channel for which the DSR is generated; Delay timing threshold; or Delay volume threshold.

12. The method of claim 1, wherein the triggering condition associated with the DSR comprises generating a buffer status report, and wherein transmitting the DSR to the network entity comprises transmitting both the buffer status report and the DSR to the network entity.

13. The method according to any one of claims 1 to 12, wherein the DSR comprises at least one of: One or more identifiers ID of the one or more channels; buffer size information of the first data in the at least one uplink buffer; The target level of satisfaction of resource allocation for extended reality (XR) communications; or A maximum delay level allowable in the UE based on a memory buffer size or at least one of: The delay time of one layer, or The delayed volume of the first floor.

14. The method according to any one of claims 1 to 13, wherein transmitting the DSR to the network entity comprises: transmitting a media access control element MAC CE, wherein the MAC CE comprises an identifier ID associated with the DSR; or The physical layer signaling of the DSR is transmitted.

15. The method according to any one of claims 1 to 14, further comprising: receiving a new uplink grant from the network entity; cancelling a subsequent DSR when the DSR has previously been transmitted to the network entity; receiving from the network entity an allocation of additional resources, an indication to adjust transmission priority, or both; as well as When the UE device has completed transmitting the first data, clearing the first data in the at least one uplink buffer.

16. A method for wireless communication by a network entity, the method comprising: transmitting a message to a user equipment (UE) device for configuring a delay threshold associated with a wireless communication channel for the UE device; receiving a delay status report DSR from the UE device, the DSR indicating that a delay of first data in at least one uplink buffer of the wireless communication channel has reached the delay threshold, the delay comprising a length of time during which the first data has been held in the at least one uplink buffer; as well as In response to the DSR, an allocation of radio resources in the UE device is transmitted to account for the delay reported in the DSR.

17. A device comprising: one or more radio frequency (RF) modems; a processor coupled to the one or more RF modems; as well as At least one memory storing executable instructions for manipulating at least one of the processor or the one or more RF modems to perform the method according to any one of claims 1 to 16.

Images