Connected mode discontinuous reception settings for periodic traffic with jitter

Abstract

Methods, systems, and devices for wireless communication are described. A network entity may account for jitter in communication with a user equipment (UE) by adjusting connected mode discontinuous reception (CDRX) configuration parameters for the UE based on an estimated downlink traffic arrival time. For a downlink traffic burst, the network entity may estimate a traffic arrival offset based on determining traffic periodicity, an estimated time of arrival associated with one or more packets of the traffic burst, and at least one jitter parameter. The jitter parameter may represent the uncertainty of the time of arrival of the traffic burst. The network entity may select a CDRX offset value based on the estimated traffic arrival offset. For example, the network entity may send a message indicating the CDRX offset value as part of a CDRX configuration (e.g., to a UE, such as an augmented reality (XR) device).

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 942,990, filed by Hande et al. on September 12, 2022, entitled “CONNECTED MODEDISCONTINUOUS RECEPTION SETTINGS FOR PERIODIC TRAFFIC WITH JITTER,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications including a connected mode discontinuous reception (CDRX) arrangement for periodic traffic with jitter. Background Art

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

[0005] Some wireless communication systems may support extended reality (XR) applications, which may include virtual reality (VR), augmented reality (AR), mixed reality (MR), or a combination thereof. In addition, the XR system may implement a SplitXR system or may be an example of a SplitXR system, in which XR computing is split between an XR device and an XR server. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting connection mode discontinuous reception (CDRX) settings for periodic services with jitter. For example, the described technology allows a network entity to account for jitter by adjusting CDRX configuration parameters based on estimated service arrival times. The network entity may estimate a service arrival offset based on determining service periodicity, an estimated arrival time associated with one or more packets of a service burst, and at least one jitter parameter. The jitter parameter may represent uncertainty in the arrival time of the service burst. The network entity may select a CDRX offset value based on the estimated service arrival offset. For example, the network entity may send a message indicating a CDRX offset value as part of a CDRX configuration (e.g., to a user equipment (UE), such as an extended reality (XR) device).

[0007] The UE may operate in CDRX mode based on the CDRX offset value (e.g., and the CDRX configuration). In some examples, the network entity may dynamically update the CDRX offset value (e.g., based on an updated estimate of the traffic arrival offset) and may indicate the updated CDRX offset value to the UE. Additionally or alternatively, the UE may determine or otherwise calculate the CDRX offset value and may send a message indicating the CDRX offset value to the network entity. The network entity may select a CDRX offset value for the CDRX configuration based on an indication received from the UE.

[0008] A method for wireless communication at a network entity is described. The method may include: determining a traffic periodicity associated with one or more packets of a traffic burst based on a timing parameter associated with the one or more packets of the traffic burst; estimating a traffic arrival offset value based on the traffic periodicity, an estimated arrival time associated with the one or more packets of the traffic burst, and at least one jitter parameter; selecting a CDRX offset value based on the estimated traffic arrival offset value; and sending a message indicating the CDRX offset value to a UE for the UE to operate in a CDRX mode according to the CDRX offset value.

[0009] An apparatus for wireless communication at a network entity is described. The apparatus may include: at least one processor; and a memory, which is coupled to the processor (e.g., operatively, communicatively, functionally, electronically, or electrically). The memory may store instructions that are executable by the at least one processor to cause the network entity to: determine a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with the one or more packets of the service burst; estimate a service arrival offset value based on the service periodicity, an estimated arrival time associated with the one or more packets of the service burst, and at least one jitter parameter; select a connected mode discontinuous reception (CDRX) offset value based on the estimated service arrival offset value; and send a message indicating the CDRX offset value to a UE for the UE to operate in CDRX mode according to the CDRX offset value.

[0010] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with the one or more packets of the service burst; a component for estimating a service arrival offset value based on the service periodicity, an estimated arrival time associated with the one or more packets of the service burst, and at least one jitter parameter; a component for selecting a CDRX offset value based on the estimated service arrival offset value; and a component for sending a message indicating the CDRX offset value to a UE for the UE to operate in a CDRX mode according to the CDRX offset value.

[0011] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by at least one processor to perform the following operations: determine a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with the one or more packets of the service burst; estimate a service arrival offset value based on the service periodicity, an estimated arrival time associated with the one or more packets of the service burst, and at least one jitter parameter; select a CDRX offset value based on the estimated service arrival offset value; and send a message indicating the CDRX offset value to a UE for the UE to operate in a CDRX mode according to the CDRX offset value.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the estimated arrival time associated with the one or more packets of the service burst based on a service burst set, a service burst volume of the service burst set, a first arrival time for a first service burst in the service burst set, the service periodicity, or a combination thereof.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, estimating the service arrival offset value may include operations, features, components, or instructions for the following operations: estimating the service arrival offset value based on the earliest arrival time and the arrival time of the one or more packets of the service burst.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, estimating the service arrival offset value may include operations, features, components, or instructions for the following operations: estimating the service arrival offset value based on the earliest arrival time, the percentage value, and the arrival time of the one or more packets of the service burst.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the percentage value may be based on a quality of service of a communication link between the network entity and the UE, a packet delay budget, or a combination thereof.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, estimating the service arrival offset value may include operations, features, components, or instructions for estimating the service arrival offset value based on the at least one jitter parameter and a set of estimated arrival times for a set of service bursts that include the service burst.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least one jitter parameter includes a set of earliest arrival times associated with the set of traffic bursts.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least one jitter parameter includes a set of earliest arrival times associated with the set of traffic bursts, and a percentage value of a difference between the set of estimated arrival times and a set of nominal arrival times for the set of traffic bursts.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: updating an estimated traffic arrival offset value based on a second set of estimated arrival times for a second set of traffic bursts; and updating the CDRX offset value based on the estimated traffic arrival offset value.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending a second message indicating the updated CDRX offset value to the UE.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending the second message based on a difference between the CDRX offset value and the updated CDRX offset value satisfying a threshold.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second message includes a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), or a wake-up signal for the UE.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the CDRX offset value may include operations, features, components, or instructions for selecting the CDRX offset value to be equal to the estimated traffic arrival offset value plus a UE-specific offset.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UE-specific offset may be based on scheduling the traffic burst for the UE.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the CDRX value may include operations, features, components, or instructions for selecting the CDRX offset value to be equal to the estimated traffic arrival offset value.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: selecting a CDRX duty cycle periodicity equal to the determined traffic periodicity; and sending an indication of the CDRX duty cycle periodicity in the message.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the message indicating the CDRX offset value may include operations, features, components, or instructions for sending an indication of a CDRX parameter set for a CDRX configuration for the CDRX mode, the CDRX parameter set including the CDRX offset value.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timing parameter includes a rendered frames per second value or an average downlink traffic arrival time for two or more traffic bursts.

[0029] A method for wireless communication at a UE is described. The method may include: determining a traffic periodicity associated with one or more packets of a traffic burst based on a timing parameter associated with the one or more packets of the traffic burst; estimating a traffic arrival offset value based on the traffic periodicity, an estimated arrival time associated with the one or more packets of the traffic burst, and at least one jitter parameter; selecting a CDRX offset value based on the estimated traffic arrival offset value; and sending a message indicating the CDRX offset value to a network entity for the UE to operate in a CDRX mode according to the CDRX offset value.

[0030] An apparatus for wireless communication at a UE is described. The apparatus may include: at least one processor; and a memory, which is coupled to the processor (e.g., operatively, communicatively, functionally, electronically, or electrically). The memory may store instructions that can be executed by the at least one processor to cause the UE to: determine a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with the one or more packets of the service burst; estimate a service arrival offset value based on the service periodicity, an estimated arrival time associated with the one or more packets of the service burst, and at least one jitter parameter; select a CDRX offset value based on the estimated service arrival offset value; and send a message indicating the CDRX offset value to a network entity for the UE to operate in a CDRX mode according to the CDRX offset value.

[0031] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with the one or more packets of the service burst; a component for estimating a service arrival offset value based on the service periodicity, an estimated arrival time associated with the one or more packets of the service burst, and at least one jitter parameter; a component for selecting a CDRX offset value based on the estimated service arrival offset value; and a component for sending a message indicating the CDRX offset value to a network entity for the UE to operate in a CDRX mode according to the CDRX offset value.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to perform the following operations: determine a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with the one or more packets of the service burst; estimate a service arrival offset value based on the service periodicity, an estimated arrival time associated with the one or more packets of the service burst, and at least one jitter parameter; select a CDRX offset value based on the estimated service arrival offset value; and send a message indicating the CDRX offset value to a network entity for the UE to operate in a CDRX mode according to the CDRX offset value.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the estimated arrival time associated with the one or more packets of the service burst based on a service burst set, a service burst volume of the service burst set, a first arrival time for a first service burst in the service burst set, and the service periodicity.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the estimated arrival time, the estimated traffic arrival offset value, and the traffic periodicity may be associated with the one or more packets of the traffic burst arriving at a server.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, estimating the service arrival offset value may include operations, features, components, or instructions for the following operations: estimating the service arrival offset value based on the earliest arrival time and the arrival time of the one or more packets of the service burst.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, estimating the service arrival offset value may include operations, features, components, or instructions for the following operations: estimating the service arrival offset value based on the earliest arrival time, the percentage value, and the arrival time of the one or more packets of the service burst.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the percentage value may be based on a quality of service of a communication link between the network entity and the UE, a packet delay budget, or a combination thereof.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, estimating the service arrival offset value may include operations, features, components, or instructions for estimating the service arrival offset value based on the at least one jitter parameter and a set of estimated arrival times for a set of service bursts that include the service burst.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least one jitter parameter includes a set of earliest arrival times associated with the set of traffic bursts.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least one jitter parameter includes a set of earliest arrival times associated with the set of traffic bursts, and a percentage value of a difference between the set of estimated arrival times and a set of nominal arrival times for the set of traffic bursts.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: receiving a second message indicating an updated CDRX offset value; and operating in the CDRX mode according to the updated CDRX offset value.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second message includes an RRC message, a MAC-CE, or a wake-up signal for the UE.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the CDRX offset value may include operations, features, components, or instructions for selecting the CDRX offset value to be equal to the estimated traffic arrival offset value.

[0044] Some examples of methods, apparatuses, and non-transitory computer readable media described herein may further include operations, features, components, or instructions for operating in the CDRX mode according to a CDRX duty cycle periodicity that may be equal to the determined traffic periodicity.

[0045] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving an indication of a set of CDRX parameters for a CDRX configuration for the CDRX mode, the set of CDRX parameters including the CDRX offset value.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timing parameter includes a rendered frames per second value or an average downlink traffic arrival time for two or more traffic bursts. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 An example of a wireless communication system supporting a connected mode discontinuous reception (CDRX) setting for periodic traffic with jitter in accordance with one or more aspects of the present disclosure is illustrated.

[0048] Figure 2 An example of a wireless communication system supporting CDRX settings for periodic traffic with jitter in accordance with one or more aspects of the present disclosure is illustrated.

[0049] Figure 3 An example of a signaling diagram supporting CDRX settings for periodic traffic with jitter in accordance with one or more aspects of the present disclosure is illustrated.

[0050] Figure 4 An example of a process flow supporting CDRX setup for periodic traffic with jitter in accordance with one or more aspects of the present disclosure is illustrated.

[0051] Figure 5 and Figure 6 A block diagram of a device supporting CDRX settings for periodic traffic with jitter is shown in accordance with one or more aspects of the present disclosure.

[0052] Figure 7 A block diagram of a communications manager supporting CDRX settings for periodic traffic with jitter is shown in accordance with one or more aspects of the present disclosure.

[0053] Figure 8 A diagram of a system including a device supporting CDRX settings for periodic traffic with jitter is shown in accordance with one or more aspects of the present disclosure.

[0054] Fig. 9 and Fig.10 A block diagram of a device supporting CDRX settings for periodic traffic with jitter is shown in accordance with one or more aspects of the present disclosure.

[0055] Fig.11 A block diagram of a communications manager supporting CDRX settings for periodic traffic with jitter is shown in accordance with one or more aspects of the present disclosure.

[0056] Fig.12 A diagram of a system including a device supporting CDRX settings for periodic traffic with jitter is shown in accordance with one or more aspects of the present disclosure.

[0057] Figures 13 to 16A flow chart illustrating a method of supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0058] Extended reality (XR) data in a wireless communication system may include virtual reality (VR) data, augmented reality (AR) data, mixed reality (MR) data, and other types of data that may be associated with high reliability and low latency transmission. In some cases, a multimedia device (e.g., an XR device) that supports XR data may use a split implementation such as a SplitXR implementation. SplitXR may support the XR device by splitting related multimedia XR computations (such as rendered video frames) between the XR server and the XR device using computing resources on the XR server. In some examples, a network entity may relay XR data from the XR server to the XR device. For example, a network entity may send a SplitXR rendered video frame to a user equipment (UE) (e.g., an XR user, an XR device, or other device that supports XR communication) in a downlink transmission. In such examples, jitter may occur in the downlink transmission, for example, due to rendering time, encoding time, or real-time transport protocol (RTP) packetization time.

[0059] In some wireless communication systems, a UE (e.g., an XR device) may operate according to a connected mode discontinuous reception (CDRX) configuration, which may support reduced power consumption at the UE. The CDRX configuration may include a CDRX on-duration / off-duration cycle with a fixed periodicity that enables the UE to sleep (e.g., when there is no traffic between the UE and the network entity) and wake up during a periodic window (e.g., a wake-up window, a CDRX window) to receive traffic (e.g., downlink traffic) arriving from the network entity. The network entity may set parameters for the CDRX configuration of the UE. For example, the network entity may set the periodicity to match the traffic arrival pattern so that the traffic arrival falls within the wake-up window of the UE. However, in XR operations (e.g., SplitXR), due to jitter in the downlink transmission, the traffic may not arrive exactly according to the periodicity, and the UE may wake up too early or too late to receive the downlink transmission, which may increase latency and power consumption at the UE.

[0060] The techniques described herein are provided for estimating a CDRX offset for adjusting a wake-up window to reduce the impact of jitter on the UE, which can improve latency, power consumption, and the quality and reliability of SplitXR downlink transmissions. The UE may operate according to a CDRX configuration to receive periodic downlink traffic (e.g., XR data from an XR server). For example, the UE may receive downlink traffic according to a traffic periodicity equal to a frames per second (fps) value associated with the XR data. The network entity may configure the UE using the CDRX configuration, and may account for changes in traffic arrival times of periodic downlink traffic caused by jitter by calculating a traffic arrival offset value. Based on the traffic arrival offset value, the network entity may calculate a CDRX offset value, and may adjust the wake-up window of the CDRX configuration for the UE accordingly.

[0061] For example, the network entity may calculate the estimated arrival time as the difference between the actual arrival time of the packet at the UE and the nominal arrival time, wherein the nominal arrival time corresponds to the arrival time predicted by a periodic pattern (e.g., a periodic pattern without jitter). The network entity may calculate the CDRX offset value based on the minimum phase of the estimated arrival time, which may correspond to the earliest arrival time of the packet at the UE. Alternatively, the network entity may calculate the CDRX offset value based on a phase value (e.g., minimum phase) and a percentage of an estimated jitter value. Here, the estimated jitter value may correspond to the difference between the estimated arrival time and the nominal arrival time. In another example, the network entity may dynamically calculate and update the CDRX offset value over time. For example, the CDRX offset value may be calculated as a function of a set of estimated arrival times for a set of packets. The function may correspond to the minimum estimated arrival time in the set of estimated arrival times, or to the minimum estimated arrival time and a percentage value of the estimated jitter value associated with the set of estimated arrival times. In such an example, the network entity may update the CDRX offset value over time by recalculating the CXRX offset value using a different set of packets. The network entity may indicate the updated CDRX offset value to the UE.

[0062] In some cases, the calculation for determining the CDRX offset value may be performed by the network entity or the UE. For example, the UE may determine the CDRX offset value and may send an indication of the CDRX value to the network entity. The UE may request the network entity to utilize the indicated CDRX value in the CDRX configuration for the UE.

[0063] Aspects of the disclosure are first described in the context of a wireless communication system. Aspects of the disclosure are then discussed with reference to signaling diagrams and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to a connected mode discontinuous reception setup for periodic traffic with jitter.

[0064] Figure 1 An example of a wireless communication system 100 supporting a connected mode discontinuous reception setting for periodic traffic with jitter according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

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

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

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

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

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

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

[0076] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support a connected mode discontinuous reception setup for periodic traffic with jitter as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0110] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be based on IP. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection for a radio bearer supporting user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map transport channels to physical channels.

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

[0112] In some examples, the wireless communication system 100 may support XR devices. For example, the UE 115 may be an XR device, which may include a virtual reality (VR) device, an augmented reality device (AR), or a mixed reality (MR) device, wherein the MR device may include a combination of aspects of both VR devices and AR devices. In some cases, the XR device may be implemented using SplitXR. SplitXR may support XR devices (e.g., UE 115) by splitting multimedia XR computations between the XR server and the XR device using additional computing resources on an XR server (e.g., communicating with the network entity 105). XR transmission may have low latency and may include delay-sensitive processes at the UE 115 (e.g., to improve the quality of user experience). XR transmission may also include high data throughput (e.g., high data rate) that may consume a lot of power. For example, the network entity 105 may send large data packets, such as video frames, to the UE 115.

[0113] In addition, in some cases, the UE 115 may be configured with a DRX configuration, such as a CDRX configuration, in which the UE 115 transitions to a power-saving sleep state between active times when the UE 115 monitors communications from the network entity 105 (e.g., may monitor a physical downlink control channel (PDCCH) for one or more transmissions). The active time may be referred to as a CDRX window. Additionally or alternatively, the starting position (e.g., the start time) of the active time may be indicated by an offset value. The offset value may indicate a time slot or subframe at which the active time begins. The UE 115 may be configured with a CDRX duty cycle with a CDRX periodicity, such that the UE 115 wakes up during the CDRX window at intervals determined by the CDRX periodicity. In some examples, the active time may include an on-duration, may be extended by an inactivity timer, or both. In an XR system, the UE 115 (e.g., an XR device) may operate according to the CDRX configuration to receive XR services during the CDRX window, which may enable the UE 115 to save power and provide a reliable user experience.

[0114] XR services may include one or more data streams. For example, the network entity 105 may send two data streams. In some examples, each data stream may have a different configuration. For example, each data stream may have a different period and other variation characteristics, and may be independent of each other. In some cases, a first data stream may carry video data, and a second data stream may carry audio data. As another example, for XR video data, for an XR device, a first data stream may carry video data for the left eye (e.g., a first portion of the video data), and a second data stream may carry video data for the right eye (e.g., a second portion of the video data).

[0115] In some examples, XR communications may include one or more service bursts. For example, the network entity 105 may send one or more data packets in an XR service burst at the beginning of one or more CDRX cycles in a periodic transmission. In some examples, each XR service burst may include changes in the number and size of packets per burst. For example, an XR service burst at the beginning of a first CDRX cycle may have three data packets of a shorter length, while an XR service burst at the beginning of a second CDRX cycle after the first cycle may have two data packets of a longer length. In some cases, XR services may be sent according to non-integer or integer periods. For example, the network entity 105 may send XR data at 1 / 60 frames per second (fps), 16.67ms period, or at 1 / 120fps, 8.33ms period.

[0116] In some cases, XR communications may include a small packet delay budget (PDB). For example, if UE 115 loses data reception of one or more video frames after the amount of time defined by the PDB (e.g., due to processing delays, jitter, or speed mismatch), UE 115 may discard data for one or more video frames after the PDB. In some cases, network entity 105 may decide not to send data for one or more video frames after the time defined by the PDB. In some cases, violating the PDB may affect latency in communications, or may adversely affect the user experience due to the loss of one or more video frames.

[0117] In some examples, jitter may be introduced into XR communications, resulting in variations in the arrival time of XR traffic. For example, an XR traffic burst that is expected to arrive at the start of a CDRX cycle may arrive later (e.g., one or more ms after the start of the CDRX cycle). Additionally or alternatively, jitter may cause a burst of XR traffic to arrive before the start of a CDRX cycle or after the end of a CDRX cycle. In some examples, jitter may be caused by processing, interference, delays, and other factors at the network entity 105 or at the XR server. For example, some XR processing applications may depend on XR traffic to be rendered or sent, such as two-dimensional (2D) media content based on user input or user data. Therefore, such applications at the XR server (e.g., rendering, encoding, etc.) may take more time than expected, thereby delaying the sending of XR traffic bursts. Additionally or alternatively, a regular or periodic pattern of XR traffic may have a periodicity based on an associated fps to support a reliable user experience at UE 115, but the periodicity of the XR traffic may not be aligned with the periodicity of the CDRX cycle (e.g., CDRX duty cycle). This may result in a speed mismatch where the UE 115 and the XR traffic will be out of sync at one or more times.

[0118] In general, jitter may degrade performance at UE 115, especially when services (e.g., XR services) rely on accurate timing to obtain a reliable user experience. For example, when jitter causes XR services to arrive before or after the CDRX window, UE 115 may be in a sleep state and may fail to receive the XR services, which may increase latency. However, if UE 115 is configured to wake up more frequently (e.g., to ensure reception of XR services), UE 115 may consume a lot of power. According to the techniques described herein, UE 115 may be configured with an estimated CDRX offset value based on a service arrival time that takes into account jitter, so that UE 115 can receive services (e.g., XR services) with improved reliability and consistency while maintaining an appropriate level of power consumption. For example, a network entity 105 that configures UE 115 (e.g., using a CDRX configuration) can take into account changes in service arrival times caused by jitter by calculating a service arrival offset value, which can be based on an estimated service arrival time associated with one or more service bursts and one or more jitter parameters corresponding to one or more service bursts. Using the traffic arrival offset value, the network entity 105 may determine a CDRX offset value for the UE 115 that enables the UE 115 to reduce latency and power consumption.

[0119] In some cases, the calculations for determining the CDRX offset value may be performed by the network entity 105 or the UE 115. For example, the UE 115 may calculate the CDRX offset value and may send an indication of the CDRX value to the network entity 105. The UE 115 may request that the network entity 105 utilize the indicated CDRX value in the CDRX configuration for the UE 115.

[0120] Figure 2 An example of a wireless communication system 200 that supports CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100, or may be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115-a and a network entity 105-a (which may be examples of corresponding devices as described herein). Additionally, the wireless communication system 200 may include an XR server 210, which may include a core network 130 or a component of the core network 130 or may be an example of the core network 130 or a component of the core network 130, as described in reference Figure 1 UE 115 - a or network entity 105 - a may communicate with XR server 210 directly or indirectly.

[0121] exist Figure 2In an example of , UE 115-a may include an XR device or may be an example of an XR device and may communicate with an XR server 210 via network entity 105-a in SplitXR configuration 205. SplitXR configuration 205 may be implemented to reduce computational and processing costs for UE 115-a. In SplitXR configuration 205, XR server 210 may perform XR-related multimedia computations with UE 115-a, thereby reducing the computational load of UE 115-a. UE 115-a and XR server 210 may exchange XR-related information with the help of network entity 105-a to support XR applications at UE 115-a.

[0122] For example, the network entity 105-a and the XR server 210 may communicate via the communication link 207. Additionally, the network entity 105-a may communicate with the UE 115-a via one or more communication links 125 (e.g., a downlink communication link, an uplink communication link, etc.). The communication link 125-a may include one or more downlink channels (such as a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), etc.) or may be an example of one or more downlink channels. The communication link 125-b may include one or more uplink channels (such as a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), etc.) or may be an example of one or more uplink channels.

[0123] The wireless communication system 200 may support CDRX operations. For example, the UE 115-a may operate according to a CDRX configuration that enables the UE 115-a to sleep (e.g., when there is no traffic on the communication link 125-a) and wake up during a periodic window to receive traffic via the communication link 125-a. The network entity 105-a may set (e.g., select) CDRX parameters for the CDRX configuration at the UE 115-a, such as a CDRX cycle (e.g., duty cycle), an inactivity timer, an on-duration timer, and the like. For example, the network entity 105-a may set the periodicity of the CDRX configuration to match the periodicity of the traffic between the UE 115-a and the network entity 105-a, so that the periodic window of the CDRX configuration coincides with the arrival of periodic traffic at the UE 115-a. The network entity 105-a may indicate the CDRX configuration including the CDRX parameters to the UE 115-a, for example, via the communication link 125-a.

[0124] In some examples of the wireless communication system 200, the UE 115-a (e.g., an XR device) may include XR-related components, such as tracking and XR sensors for collecting tracking and sensor information 215 for XR-related multimedia operations. The tracking and sensor information 215 may be data such as user gestures and input data. The UE 115-a may send or otherwise report the tracking and sensor information 215 to the XR server 210 with the aid of the network entity 105-a. For example, the UE 115-a may send the tracking and sensor information 215 to the network entity 105-a via the communication link 125-a. The tracking and sensor information 215 (e.g., user gesture data) may be used by the XR server 210 to create a rendered video frame (e.g., a set of rendered frames 220) for the UE 115-a. In some examples, the tracking and sensor information 215 may be updated and reported over time, for example, based on the current user location. For example, UE 115 - a may send tracking and sensor information 215 with a periodicity equal to the video frame rate (eg, 90 Hz) at UE 115 - a .

[0125] The XR server 210 may include components for executing an XR application related to rendering and encoding XR multimedia content. For example, the XR server 210 may generate 2D media content for the UE 115-a based on receiving the tracking and sensor information 215. The XR server 210 may render and encode the 2D media content. The XR server 210 may deliver the XR media content to the UE 115-a via a communication link such as the communication link 125-a (e.g., an LTE or 5G communication link). For example, the XR server 210 may generate a set of rendered frames 220, which may include a set of 2D video frames or may be an example of a set of 2D video frames. The set of rendered frames 220 may be encoded at the XR server 210 and sent to the UE 115-a. In some examples, the set of rendered frames 220 may be based on the tracking and sensor information 215 (e.g., user gestures and input data) sent from the UE 115-a (e.g., an XR device). For example, XR server 210 may utilize tracking and sensor information 215 to determine media content to display at UE 115 - a , and may render the media content including a set of rendered frames 220 (eg, as part of a rendering application).

[0126] UE 115-a may receive and process the set of rendered frames 220. For example, UE 115-a may include one or more components for receiving, decoding, and rendering XR media content (e.g., 2D media, such as the set of rendered frames 220). UE 115-a may decode the set of rendered frames 220, and in some examples, may perform additional rendering (e.g., XR viewpoint rendering) to deliver the 2D media to a display of UE 115-a. In some examples, the rate at which the XR server 210 sends the set of rendered frames 220 and the UE 115-a receives the set of rendered frames 220 may correspond to a video frame rate (e.g., 90 Hz) at UE 115-a (e.g., an XR device), for example, to enable UE 115-a to display the media without interruption.

[0127] The SplitXR configuration 205 may be associated with latency, for example, associated with the communication link 125, or may be attributable to an XR application executing at the UE 115-a or the XR server 210. In some examples, XR latency may be defined by the total motion to server rendering to device display (photons) (M2R2P) time. M2R2P may be defined as the sum of the total 5G round trip time (5G-RTT), the total UE 115-a (e.g., XR device) processing time, and the total XR server 210 processing time. The 5G-RTT may correspond to the total duration for a set of tracking and sensor information 215 to be sent via the communication link 125-b and the rendered frames 220 to be sent via the communication link 125-a, and therefore may include any latency associated with uplink and downlink transmissions in the wireless communication system 200. The user experience at the UE 115-a may be improved by reducing the M2R2P, which in turn may reduce the overall latency in the wireless communication system 200. However, the XR server 210, the UE 115-a, and the network entity 105-a may generate jitter, for example, due to rendering time, encoding time, RTP time, etc. In some cases, techniques for reducing M2R2P may also introduce jitter.

[0128] Jitter may introduce uncertainty in the arrival time of traffic, which may degrade performance at UE 115-a. For example, jitter may cause a misalignment between traffic arriving at UE 115-a and the periodic window of the CDRX configuration of UE 115-a, causing UE 115-a to fail to receive some or all of the XR traffic bursts. The techniques described herein support communication based on timing that takes into account jitter in the wireless communication system 200. For example, UE 115-a may operate according to a CDRX configuration that includes a CDRX offset value based on an estimated traffic arrival time, which may reduce latency and power consumption at UE 115-a.

[0129] For example, the network entity 105-a may determine the traffic arrival offset value by estimating the traffic arrival time of one or more traffic bursts (e.g., at the UE 115-a) and based on one or more jitter parameters. The one or more traffic bursts may include a set of rendered frames 220. The network entity 105-a may calculate or otherwise determine or select a CDRX offset value based on the traffic arrival offset value. For example, the network entity 105-a may set the CDRX offset value to be equal to the traffic offset value. The CDRX offset value may indicate the starting position (e.g., the starting subframe or time slot) of the periodic window (e.g., the active time) of the CDRX configuration. The CDRX offset may enable the UE 115-a to wake up to the on state at the correct time (e.g., at the starting position) to receive traffic data from the network entity 105-a.

[0130] As reference Figure 3 Further described, the network entity 105-a may select a CDRX offset value and may indicate the CDRX offset value to the UE 115-a. For example, the network entity 105-a may send a CDRX configuration message 235 indicating a CDRX configuration for the UE 115-a to the UE 115-a via the communication link 125-a. The CDRX configuration message 235 may include an indication of the CDRX offset value selected by the network entity 105-a and (in some cases) one or more other CDRX parameters for the CDRX configuration. The UE 115-a may operate in the CDRX mode according to the CDRX offset value.

[0131] Additionally or alternatively, the network entity 105-a may dynamically update the CDRX offset value. Here, the network entity 105-a may estimate the traffic arrival time of a set of traffic bursts (e.g., including the rendered frame set 220), and may recalculate the CDRX offset value by estimating the arrival time of different sets of traffic bursts over time. For example, the network entity 105-a may calculate a first CDRX offset value using a first set of traffic bursts arriving at the UE 115-a, and may indicate the first CDRX offset value to the UE 115-a (e.g., via the CDRX configuration message 235). The network entity 105-a may update the CDRX offset value by calculating a second CDRX offset value based on a second set of traffic bursts arriving at the UE 115-a and indicating the second CDRX offset value to the UE 115-a.

[0132] In some cases, UE 115-a may calculate or otherwise determine or select a CDRX offset value. UE 115-a may estimate the service arrival time of one or more service bursts (e.g., at XR server 210), and may determine one or more jitter parameters. UE 115-a may select a CDRX offset value based on a service arrival offset value associated with the estimated service arrival time and one or more jitter parameters. Here, the CDRX offset value determined by UE 115-a may be a CDRX offset value preferred by UE 115-a, for example, a CDRX offset value preferred by UE 115-a for use by network entity 105-a in CDRX configuration. UE 115-a may indicate (e.g., request) a CDRX offset value to network entity 105-a via a CDRX configuration request message 240. Network entity 105-a may select a CDRX offset value for use by UE 115-a based on receiving CDRX configuration request message 240.

[0133] Figure 3 An example of a signaling diagram 300 for supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is illustrated. The signaling diagram 300 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the signaling diagram 300 may be implemented by one or more wireless devices such as the network entity 105, the UE 115, or the XR server 210, which may be as described in reference to Figure 1 and Figure 2 Examples of corresponding devices described.

[0134] The signaling diagram 300 may be an example of a flow of traffic arrival times. For example, the signaling diagram 300 may include a downlink traffic burst 305 (e.g., downlink traffic burst 305-a, 305-b, or 305-c) including one or more packets received at a device (e.g., a UE, an XR device, etc.) at a corresponding traffic arrival time. Additionally, the signaling diagram 300 may include uplink traffic 310 sent by the device, e.g., to a network entity, an XR server, etc.

[0135] For example, as referenced Figure 2As described, signaling diagram 300 may illustrate XR services received at and sent by a UE, which may include an XR device or may be an example of an XR device. The UE may send uplink services 310 to a network entity or an XR server. The uplink services 310 may include tracking and sensor information, such as gesture input, controller data, or other types of XR-related multimedia information or data. In some cases, the uplink services may be one or more uplink service 310 signals (e.g., uplink services 310-a, 310-b, and 310-c) sent by the UE at different times. Additionally, the uplink services 310 may occur before or after the downlink service burst 305. The UE may receive a downlink service burst 305 from a network entity or an XR server. In some cases, the downlink service burst 305 may include a rendered frame set. In some examples, the downlink service burst 305 may be sent according to service periodicity (e.g., by a network entity, by an XR server). The traffic periodicity may correspond to the fps associated with the XR data at the UE (eg, rendering fps).For example, the periodicity may be equal to 1 / fps, such that one downlink traffic burst 305 is sent per period.

[0136] The UE may operate in CDRX mode according to the CDRX configuration. For example, the network entity may send a message indicating a CDRX parameter set for the CDRX configuration of the CDRX mode. The CDRX configuration may include one or more windows 315, and the CDRX parameter set may include a CDRX duty cycle periodicity associated with the one or more windows 315. Each window 315 may correspond to a duration during which the UE operates in an on state and can communicate with a network entity or an XR server or may be an example of the duration. For example, during window 315, the UE may wake up and monitor transmissions (e.g., downlink traffic bursts 305) from the network entity or XR server. Outside of window 315, the UE may operate in a sleep state and may suppress monitoring transmissions. The windows 315 (e.g., windows 315-a, windows 315-b, windows 315-c) may be configured according to periodicity so that the UE wakes up regularly during each window 315 to monitor transmissions. For example, window 315 may be configured with a periodicity equal to the service periodicity of the downlink traffic burst 305.

[0137] As shown, the time when the downlink traffic burst 305 arrives at the UE may be quasi-periodic. For example, the downlink traffic burst 305 may be configured to arrive at the UE according to a service arrival pattern with a periodicity of 1 / fps (e.g., service periodicity), but may be affected by jitter. Jitter may be caused by factors such as rendering time, encoder time, RTP packetization time, or a combination thereof, and may introduce randomness into the time when the downlink traffic burst 305 arrives at the UE. Therefore, the downlink traffic burst 305 arrival time may be irregular and may not exactly match the service arrival pattern, for example, may not arrive exactly according to the service periodicity.

[0138] For example, the UE may be configured with a CDRX configuration such that the window 315 occurs with a periodicity corresponding to the service periodicity of the downlink traffic burst 305, which may enable the UE to wake up to receive each downlink traffic burst 305. However, jitter may cause misalignment between the service periodicity and the periodicity of the window 315. For example, a downlink traffic burst 305-b may not arrive completely within the window 315-b. Because the UE may enter a sleep mode (e.g., and suppress monitoring from transmission) at the end of the window 315-b, the UE may fail to receive the portion of the downlink traffic burst 305-b that arrives after the end of the window 315-b. Therefore, the UE may not receive the entire downlink traffic burst 305-b, which may result in an increase in the total M2R2P time and latency associated with the downlink traffic burst 305.

[0139] Thus, the UE may be configured with a CDRX offset value for the CDRX offset 320. For example, the network entity may select a CDRX offset value for the CDRX offset 320, and may indicate the CDRX offset value to the UE, for example as part of a CDRX parameter set. As shown, the CDRX offset 320 may adjust the window 315 (e.g., window 315-c) to enable the UE to receive the entire downlink traffic burst 305-c. For example, the CDRX offset 320 may indicate a start time for the window 315-c based on an estimated arrival time of the downlink traffic burst 305-c. The CDRX offset value may correspond to an amount of a time slot, a subframe, or other unit in the time domain, such that the CDRX offset value indicates the CDRX offset 320. In some cases, the CDRX offset may be based on the actual arrival time of the downlink traffic burst 305-a, the downlink traffic burst 305-b, or a combination thereof. Additionally, the CDRX offset 320 may be based on one or more jitter parameters. One or more jitter parameters may represent an adjustment to the traffic arrival time caused by jitter.

[0140] The effect of jitter on the arrival time of traffic can be represented by a random factor r(n). That is, jitter may cause the arrival time of a given downlink traffic burst 305 to deviate from the expected arrival time (e.g., based on a completely periodic traffic arrival pattern), where the deviation from the expected arrival time can be represented by r(n). The random factor r(n) can be modeled as a range [r min ,r max ], where r is in ms. In some examples, the range can be defined as The distribution may have a standard deviation of 2 ms. The distribution of r(n) may represent the spread of traffic arrival times due to varying factors (e.g., rendering time, encoding time, or RTP packetization time). In some cases, it may be expected that the distribution of r(n) is not affected by the value of fps.

[0141] To select the CDRX offset value, the network entity may determine a traffic periodicity associated with at least one downlink traffic burst 305. The traffic periodicity may be based on a timing parameter. In some examples, the timing parameter may include a rendering fps. For example, if the rendering fps is known, the traffic periodicity p may be defined as Alternatively, if the network entity does not know the rendering fps, the network entity may estimate the traffic periodicity based on the average downlink traffic arrival time for two or more downlink traffic bursts 305 .

[0142] The downlink traffic arrival time for the downlink traffic burst 305 may be represented by the following equation 1. For the nth downlink traffic burst 305 including one or more packets, the arrival time of the downlink traffic may be calculated based on the traffic periodicity, the random factor (eg, jitter), and the initial time t5 0 To determine the arrival time of downlink traffic

[0143]

[0144] When the network entity is unaware of the rendering fps, the traffic periodicity may be calculated using the downlink traffic arrival times for two or more downlink traffic bursts 305, as shown in Equation 2 below.

[0145]

[0146] For example, the network entity may use downlink traffic burst 305-a (eg, ) and downlink traffic burst 305-b (e.g., ) is used to calculate the traffic periodicity for signaling diagram 300. The traffic periodicity may be equal to the average traffic arrival time of downlink traffic burst 305-a and downlink traffic burst 305-b. In some examples, the network entity may set the CDRX duty cycle periodicity for window 315 equal to the traffic periodicity calculated by equation 2.

[0147] Based on the traffic periodicity, the network entity may determine (eg, calculate) an estimated arrival time r associated with the downlink traffic burst 305 (eg, one or more packets of the downlink traffic burst 305). est (n). For example, for the nth downlink traffic burst 305, the estimated arrival time may be equal to the difference between the actual arrival time and the expected arrival time of the downlink traffic burst 305. The expected arrival time may correspond to the arrival time of the downlink traffic burst 305 without jitter, for example, if the downlink traffic burst 305 arrives exactly according to the traffic periodicity. The estimated arrival time may be represented by Equation 3 below.

[0148]

[0149] In some examples, the network entity may calculate an estimated arrival time for multiple downlink traffic bursts 305. For example, the network entity may calculate an estimated arrival time for each of the downlink traffic bursts 305-a, 305-b, and 305-c. est Additionally or alternatively, the network entity may calculate r for a set of n downlink traffic bursts 305. est (n). In either case, the network entity may determine the downlink traffic burst 305 based on the r est For example, the first jitter parameter may correspond to the minimum phase of the estimated arrival time. Here, for one or more values ​​of n, the network entity may determine r est The minimum phase may indicate the earliest arrival time for the downlink traffic burst 305.

[0150] For example, the network entity may calculate Equation 3 for downlink traffic burst 305-a to determine r est (1). The network entity may calculate Equation 3 for the downlink traffic burst 305-b to determine r est (2) r est (1) and r est The minimum value of (2) may correspond to the minimum phase. Based on the minimum phase, the network entity may estimate (eg, predict) an earliest arrival time (eg, earliest possible arrival time) for the downlink traffic burst 305-c.

[0151] The second jitter parameter may correspond to a percentage value of the estimated arrival time associated with one or more downlink traffic bursts 305. est The x percentile value of (n) may represent a traffic arrival time corresponding to x percent of the traffic (eg, x percent of the traffic arrives at the traffic arrival time).

[0152] In some cases, the second jitter parameter may be understood as a percentage value of the jitter (e.g., the jitter value). Here, the second jitter parameter may be equal to the percentage value of the difference between the nominal arrival time of the downlink traffic burst 305 (e.g., the arrival time predicted by the periodic pattern with the calculated periodicity p and no jitter) and the estimated arrival time of the downlink traffic burst 305.

[0153] The network entity may determine (e.g., calculate) a traffic arrival offset value based on traffic periodicity, estimated arrival times of one or more downlink traffic bursts 305, and at least one jitter parameter. For example, for downlink traffic bursts 305, at least one jitter parameter may be a minimum phase, so that the network entity may estimate the traffic arrival offset based on the earliest arrival time and the actual arrival time of the downlink traffic bursts 305. The traffic arrival offset may be represented by Equation 4 shown below, where is the first arrival time for a service burst, and Min phase equal to min(r est (n)). In some examples, the first arrival time for the traffic burst may correspond to a nominal arrival time of the traffic burst.

[0154]

[0155] The network entity may select the CDRX offset value based on the traffic arrival offset value. When the traffic arrival offset value is given by Equation 4 (e.g., when the jitter parameter corresponds to the minimum phase), the CDRX offset value may enable the UE to receive the earliest arriving downlink traffic burst 305. That is, based on min(r est The CDRX offset value of (n)) may enable the UE to receive a downlink traffic burst 305 that would otherwise arrive before the window 315. For example, the CDRX offset value may indicate the starting position of the window 315 that occurs before the downlink traffic burst 305 arrives.

[0156] Alternatively, the network entity may select a time based on the earliest arrival time (eg, min(r est(n))) and the percentage value DPx to calculate (e.g., determine or estimate) the traffic arrival offset value, as shown in the following equation 5. For example, the traffic arrival offset value may correspond to the sum of the nominal arrival time of the downlink traffic burst 305, the minimum phase of the downlink traffic burst 305, and the percentage value of the jitter.

[0157]

[0158] In Equation 5, DPx represents (r est (n)), for example, the percentage of traffic arriving at a given arrival time. The network entity may select a CDRX offset value based on Equation 5 to enable the UE to receive approximately x percent of traffic. For example, if x=50, the CDRX offset value may enable the UE to receive approximately 50% of the traffic. In other words, the CDRX offset value may adjust the starting position of window 315 so that window 315 is positioned to receive 50% of downlink traffic bursts 305. In some cases, the network entity may select a value of x based on a tradeoff between latency and power. For example, a relatively low value of x may be associated with relatively low latency but higher power consumption, while a relatively high value of x may correspond to relatively high latency and reduced power consumption. In some examples, the network entity may select a value of x based on the quality of service of the communication link between the network entity 105 and the UE 115, a packet delay budget, or a combination thereof.

[0159] In some cases, the network entity may statically determine the CDRX offset value. Here, the network entity may determine the CDRX offset value based on a traffic arrival offset value calculated for, for example, a single downlink traffic burst 305. For example, during establishment of a CDRX configuration for the UE, the network entity may determine the CDRX offset value based on the downlink traffic burst 305-a. The network entity may configure the UE with the CDRX offset value, and the UE may operate in CDRX mode according to the CDRX offset value until otherwise indicated (e.g., until otherwise instructed, or until the UE is reconfigured with a new CDRX offset value or CDRX configuration).

[0160] Alternatively, the network entity may dynamically estimate the traffic arrival offset over time, and may update the CDRX offset value based on the dynamic estimate of the traffic arrival offset. For example, the network entity may determine the CDRX offset value based on the traffic arrival offset value corresponding to the set of downlink traffic bursts 305. The set of downlink traffic bursts 305 may correspond to the m most recently received downlink traffic bursts 305, so that the network entity continuously recalculates and updates the CDRX offset value when a new downlink traffic burst 305 is received. The network entity may indicate the updated CDRX offset value to the UE. Updating the CDRX offset value in this manner may enable the UE to dynamically adjust the CDRX offset 320 to ensure reception of the downlink traffic burst 305.

[0161] For example, the network entity may estimate the traffic arrival offset value based on at least one jitter parameter and a set of estimated arrival times for a set of downlink traffic bursts 305, as shown in Equation 6 below. The traffic arrival offset value may be a function of the set of estimated arrival times, wherein the set of downlink traffic bursts 305 includes a set of m most recently received downlink traffic bursts 305. The network entity may select the CDRX offset value based on Equation 6. For example, the network entity may select the CDRX offset value to be equal to the traffic arrival offset value given by Equation 6.

[0162]

[0163] In some cases, the service arrival offset value may be a function of at least one jitter parameter. For example, the function f may correspond to Min as expressed in Equation 7 below: phase .

[0164] Min phase =min(r est (n),r est (n-1),...,r est (nm)) (7)

[0165] In this example, for the nth downlink traffic burst 305, the network entity may calculate Equation 7 to determine the minimum phase corresponding to the last (e.g., most recent) m estimated arrival times (e.g., of the last m downlink traffic bursts 305). As in Equation 4, the network entity may calculate the traffic arrival offset value (and the CDRX offset value) based on the minimum phase to set the CDRX offset 320 so that the UE can receive the earliest arriving downlink traffic burst 305.

[0166] As another example, the traffic arrival offset value may be a function of the minimum phase and a percentage value of jitter associated with a set of estimated arrival times for a set of downlink traffic bursts 305, where the percentage value is denoted by DP. For example, function f may be represented by equation 8 as shown below.

[0167] DPx=x%*r est (r est (n),r est (n-1),...,r est (nm)) (8)

[0168] Here, the percentage value may be equal to the difference between each estimated arrival time associated with a corresponding downlink traffic burst 305 of the set of downlink traffic bursts 305 and each nominal arrival time associated with a corresponding downlink traffic burst 305 of the set of downlink traffic bursts 305. In some examples, the network entity may select the value of x or the function f based on a tradeoff between latency and power consumption. In such examples, dynamically adjusting the CDRX offset may be applicable to situations where the jitter (e.g., r(n)) has time correlation. For example, the rendering time, encoder time, and RTP packetization time may correspond to time-based jitter caused by time-dependent content being rendered and encoded.

[0169] In some cases, when a change in the arrival time (e.g., the estimated arrival time) causes a relatively large change in the CDRX offset value, the network entity may dynamically update the CDRX offset value. For example, the network entity may calculate a first CDRX offset value based on a first set of downlink traffic bursts 305. The network entity may set the CDRX offset value for the UE to be equal to the first CDRX offset value. The UE may receive a second set of downlink traffic bursts 305 over time. The network entity may calculate a second CDRX offset value based on the second set of downlink traffic bursts 305. However, if the second CDRX offset value does not change relative to the first CDRX offset value, the network entity may refrain from updating the CDRX offset value for the UE, for example to avoid an increase in signaling overhead. Alternatively, if the second CDRX offset value is significantly different from the first CDRX offset value, the network entity may update the CDRX offset value for the UE by indicating the second CDRX offset value to the UE.

[0170] For example, if the difference (eg, the absolute value of the difference) between the first CDRX offset value and the second CDRX offset value satisfies (eg, is greater than) a first threshold, the network entity may semi-statically update the CDRX offset value, as shown in Equation 9.

[0171] |CDRX_offset 1 -CDRX_offset2 |>Threshold 1 (9)

[0172] If Equation 9 satisfies the first threshold, the network entity may select a second CDRX offset value for CDRX offset 320. In this example, the network entity may send an RRC message including an indication of the second CDRX offset value to the UE. The UE may operate in CDRX mode according to the second CDRX offset value based on receiving the RRC message.

[0173] In another example, the network entity may use MAC-CE and a second threshold to more dynamically update the CDRX offset value (e.g., at an increased frequency compared to the RRC message), wherein the second threshold may be less than the first threshold. If Equation 9 satisfies the second threshold, the network entity may select a second CDRX offset value and may indicate the second CDRX offset value to the UE in the MAC-CE. Additionally or alternatively, the network entity may update the CDRX offset value based on a third threshold, wherein the third threshold may be less than the second threshold. Here, if Equation 9 satisfies the third threshold, the network entity may indicate the second CDRX offset value to the UE as part of the wake-up signal. In some examples, the network entity may update the CDRX offset value based on a combination of the first threshold, the second threshold, and the third threshold. For example, the network entity may use corresponding signaling (e.g., RRC signaling, MAC-CE, wake-up signal) to dynamically select and update the CDRX offset value at a frequency determined by the first threshold, the second threshold, and the third threshold.

[0174] In some examples, the UE may calculate and select a CDRX offset value for CDRX offset 320 as described herein. For example, the UE may determine the CDRX offset value based on equations 1 to 8. The UE may indicate the CDRX offset value to the network entity, for example as part of a CDRX configuration request message (e.g., uplink traffic 310). The UE may send a CDRX configuration request message to indicate a request for the network entity to use the indicated CDRX offset value. For example, the network entity may set the CDRX offset value for CDRX offset 320 to be equal to the CDRX offset value indicated by the UE.

[0175] Figure 4An example of a process flow 400 for supporting CDRX settings for periodic services with jitter according to one or more aspects of the present disclosure is illustrated. The process flow 400 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the process flow 400 may illustrate operations between a UE 115-b and a network entity 105-b (which may be examples of corresponding devices described herein). In the following description of the process flow 400, operations between the UE 115-b and the network entity 105-b may be sent in an order different from the example order shown, or operations performed by the UE 115-b and the network entity 105-b may be performed in a different order or at different times. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400.

[0176] At 405, UE 115-b may determine a traffic periodicity associated with one or more packets of the traffic burst based on a timing parameter associated with the one or more packets of the traffic burst. For example, the timing parameter may include a rendered fps value or an average downlink traffic arrival time for two or more traffic bursts. For example, UE 115-b may determine the traffic periodicity according to Equation 2.

[0177] At 410, UE 115-b may estimate a traffic arrival offset value based on the traffic periodicity determined at 405, an estimated arrival time associated with one or more packets of the traffic burst, and at least one jitter parameter. For example, UE 115-b may determine an estimated arrival time associated with one or more packets of the traffic burst using Equation 3 based on a traffic burst set, a traffic burst amount of the traffic burst set, a first arrival time for a first traffic burst in the traffic burst set, traffic periodicity, or a combination thereof. At least one jitter parameter may include a minimum phase corresponding to the earliest arrival time associated with one or more packets of the traffic burst, a percentage value (e.g., a percentage value of jitter) of the difference between the estimated arrival time associated with one or more packets of the traffic burst and the nominal arrival time associated with one or more packets of the traffic burst, or a combination thereof. For example, at least one jitter parameter may correspond to a minimum phase, and UE 115-b may calculate a traffic arrival offset value according to Equation 4. In another example, at least one jitter parameter may correspond to a minimum phase and a percentage value, and UE 115-b may calculate a traffic arrival offset value according to Equation 5.

[0178] In some examples, the estimated traffic arrival offset value and the traffic periodicity may be associated with the arrival of one or more packets of a traffic burst at the server.

[0179] In some examples, UE 115-b may determine the estimated service arrival offset value based on at least one jitter parameter and a set of estimated arrival times for a set of service bursts including the service burst. In such examples, at least one jitter parameter may include a set of earliest arrival times associated with the set of service bursts and may correspond to Equation 7. Alternatively, at least one jitter parameter may include a set of earliest arrival times associated with the set of service bursts, and a percentage value of the difference between a corresponding estimated arrival time associated with each service burst and a corresponding nominal arrival time associated with each service burst for the set of service bursts, and may correspond to Equation 8.

[0180] In some cases, the percentage value may be based on a quality of service of a communication link between the UE 115 - b and the network entity 105 - b , a packet delay budget associated with the UE 115 - b , or a combination thereof.

[0181] At 415, the UE 115-b may select a CDRX offset value based on the estimated traffic arrival offset value estimated at 410. In some implementations, the UE 115-b may select the CDRX offset value to be equal to the estimated traffic arrival offset.

[0182] At 420, the UE 115-b may send a message indicating the CDRX offset value (e.g., selected at 415) for the UE 115-b to operate in the CDRX mode according to the CDRX offset value (e.g., selected at 415), and the network entity 105-b may receive the message. For example, the UE 115-b may send the message to request the network entity 105-b to use the indicated CDRX offset value for the CDRX configuration for the UE 115-b. The CDRX offset value indicated in the message at 420 may be an example of a preferred CDRX offset value (e.g., preferred by the UE 115-b for operating in the CDRX mode).

[0183] At 425, the network entity 105-b may determine a traffic periodicity associated with one or more packets of the traffic burst based on a timing parameter associated with the one or more packets of the traffic burst. For example, the timing parameter may include a rendered fps value (e.g., associated with the UE 115-b) or an average downlink traffic arrival time for two or more traffic bursts arriving at the UE 115-b. For example, the network entity 105-b may determine the traffic periodicity according to Equation 2.

[0184] In some examples, network entity 105 - b may select the CDRX duty cycle periodicity for UE 115 - b to be equal to the traffic periodicity.

[0185] At 430, the network entity 105-b may estimate a traffic arrival offset value based on the traffic periodicity determined at 425, the estimated arrival time associated with one or more packets of the traffic burst, and at least one jitter parameter. For example, the network entity 105-b may determine the estimated arrival time associated with one or more packets of the traffic burst using Equation 3 based on a traffic burst set, a traffic burst volume of the traffic burst set, a first arrival time for a first traffic burst in the traffic burst set, the traffic periodicity, or a combination thereof. The at least one jitter parameter may include a minimum phase corresponding to the earliest arrival time associated with one or more packets of the traffic burst, a percentage value of a difference between an estimated arrival time associated with one or more packets of the traffic burst and a nominal arrival time associated with one or more packets of the traffic burst, or a combination thereof. For example, the at least one jitter parameter may correspond to the minimum phase, and the network entity 105-b may calculate the traffic arrival offset value according to Equation 4. In another example, the at least one jitter parameter may correspond to the minimum phase and a percentage value, and the network entity 105-b may calculate the traffic arrival offset value according to Equation 5.

[0186] In some examples, the estimated traffic arrival offset value and traffic periodicity may be associated with the arrival of one or more packets of a traffic burst at UE 115-b.

[0187] In some examples, the network entity 105-b may determine the estimated service arrival offset value based on at least one jitter parameter and a set of estimated arrival times for a set of service bursts including the service burst. In such examples, the at least one jitter parameter may include a set of earliest arrival times associated with the set of service bursts and may correspond to Equation 7. Alternatively, the at least one jitter parameter may include a set of earliest arrival times associated with the set of service bursts, and a percentage value of the difference between a corresponding estimated arrival time associated with each service burst and a corresponding nominal arrival time associated with each service burst for the set of service bursts, and may correspond to Equation 8.

[0188] In some cases, the percentage value may be based on a quality of service of a communication link between the UE 115 - b and the network entity 105 - b , a packet delay budget associated with the UE 115 - b , or a combination thereof.

[0189] At 435, the network entity 105-b may select a CDRX offset value based on the estimated traffic arrival offset determined at 430. In some examples, the network entity 105-b may select the CDRX offset value to be equal to the estimated traffic arrival offset value determined at 430 plus a UE 115-b specific offset. For example, the network entity 105-b may select or otherwise determine the UE 115-b specific offset based on scheduling a traffic burst for the UE 115-b. The UE 115-b specific offset may be based on a scheduling delay associated with the UE 115-b, a packet delay budget for the UE 115-b, a quality of service of a communication link between the UE 115-b and the network entity 105-b, or a combination thereof.

[0190] At 440, the network entity 105-b may send a message indicating a CDRX offset value for the UE 115-b to operate in the CDRX mode according to the CDRX offset value, and the UE 115-b may receive the message. In some examples, the message indicating the CDRX offset value may include an indication of a set of CDRX parameters for a CDRX configuration for the CDRX mode. For example, the network entity 105-b may send a message indicating a set of CDRX parameters including a CDRX offset value, a CDRX duty cycle periodicity, or both at 440. The CDRX configuration may be for the UE 115-b to operate in the CDRX mode according to the set of CDRX parameters.

[0191] In some examples, the CDRX offset value indicated in the message sent by the network entity 105-b at 440 may be the same as the preferred CDRX offset value indicated in the message sent by the UE 115-b at 420. For example, the network entity 105-b may select the preferred CDRX offset value indicated in the message at 420 at 435. At 440, the network entity 105-b may send a message to the UE 115-b indicating the preferred CDRX offset value.

[0192] At 445, in some examples, the network entity 105-b may update the CDRX offset value. The network entity 105-b may, for example, update the estimated traffic arrival offset from 430 based on a second set of estimated arrival times for a second set of traffic bursts. For example, the network entity 105-b may calculate a second traffic arrival offset value based on the second set of estimated arrival times and at least one jitter parameter. The network entity 105-b may select a second CDRX offset value based on the second traffic arrival offset value. For example, the network entity 105-b may select the second CDRX offset value to be equal to the second traffic arrival offset value, or to be equal to the second traffic arrival offset value plus a UE-specific offset (e.g., specific to UE 115-b). The network entity 105-b may update the CDRX offset value to be equal to the second CDRX offset value.

[0193] In some examples, the network entity 105-b may update (or refrain from updating) the CDRX offset value based on one or more thresholds. For example, the network entity 105-b may determine the absolute value of the difference between the CDRX offset value and the second CDRX offset value. The network entity 105-b may compare the absolute value with at least one of the first threshold, the second threshold, and the third threshold (e.g., according to Equation 9). The first threshold may be greater than the second threshold, and the second threshold may be greater than the third threshold. As an example, the network entity 105-b may compare the absolute value with the third threshold. If the absolute value satisfies (e.g., is greater than) the third threshold, the network entity 105-b may update the CDRX value to be equal to the second CDRX offset value. However, if the absolute value fails to meet the third threshold, the network entity 105-b may compare the absolute value with the second threshold. If the absolute value meets (e.g., is greater than) the second threshold, the network entity 105-b may update the CDRX offset value to be equal to the second CDRX offset value. Alternatively, if the absolute value fails to meet the second threshold, the network entity 105-b may compare the absolute value with the first threshold. If the absolute value satisfies (eg, is greater than) the first threshold, the network entity 105-b may update the CDRX offset value to be equal to the second CDRX offset value. If the absolute value fails to satisfy the first threshold, the network entity 105-b may refrain from updating the CDRX offset value.

[0194] At 450, in some examples, the network entity 105-b may send a second message indicating the updated CDRX offset value to the UE 115-b. In some examples, the second message may be based on one or more thresholds. For example, if the absolute value satisfies a third threshold, the network entity 105-b may send an indication of the updated CDRX offset value as part of a wake-up signal (e.g., the second message may be a wake-up signal). If the absolute value satisfies the second threshold, the network entity 105-b may send an indication of the updated CDRX offset value as part of a MAC-CE (e.g., the second message may be a MAC-CE). If the absolute value satisfies the third threshold, the network entity 105-b may send an indication of the updated CDRX offset value as part of an RRC message (e.g., the second message may be an RRC message).

[0195] The UE 115-b may operate in the CDRX mode according to the CDRX offset value indicated by the network entity 105-b. For example, the UE 115-b may operate in the CDRX mode according to the CDRX offset value indicated at 440 or the updated CDRX offset value indicated at 450. Additionally, the UE 115-b may operate in the CDRX mode according to a set of CDRX parameters indicated by the network entity 105-b. For example, the UE 115-b may operate according to a CDRX duty cycle periodicity indicated by the network entity 105-b.

[0196] Figure 5 A block diagram 500 of a device 505 supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the network entity 105 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0197] Receiver 510 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 505. In some examples, receiver 510 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0198] The transmitter 515 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 505. For example, the transmitter 515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 515 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 515 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 515 and the receiver 510 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0199] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of CDRX setup for periodic traffic with jitter as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0201] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, a graphics processing unit (GPU), an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

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

[0203] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a network entity. For example, the communication manager 520 may be configured to or otherwise support a component for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with one or more packets of the service burst. The communication manager 520 may be configured to or otherwise support a component for estimating a service arrival offset value based on service periodicity, an estimated arrival time associated with one or more packets of the service burst, and at least one jitter parameter. The communication manager 520 may be configured to or otherwise support a component for selecting a CDRX (CDRX) offset value based on the estimated service arrival offset value. The communication manager 520 may be configured to or otherwise support a component for sending a message indicating a CDRX offset value to a UE for the UE to operate in a CDRX mode according to the CDRX offset value.

[0204] By including or configuring the communication manager 520 according to the examples described herein, the device 505 (e.g., a processor that controls or otherwise couples with the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof) can support techniques for adaptively setting CDRX configuration parameters based on traffic patterns. For example, setting CDRX offset values ​​based on estimated traffic arrival times can improve the efficiency of scheduling and utilizing communication resources, reduce latency, and reduce processing at the device 505.

[0205] Figure 6 A block diagram 600 of a device 605 supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or the network entity 105 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0206] Receiver 610 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 605. In some examples, receiver 610 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 610 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0207] The transmitter 615 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 605. For example, the transmitter 615 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 615 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 615 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 615 and the receiver 610 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0208] Device 605 or its various components may be examples of components for performing various aspects of CDRX settings for periodic services with jitter as described herein. For example, communication manager 620 may include periodic component 625, service arrival offset value component 630, CDRX offset value component 635, CDRX configuration component 640, or any combination thereof. Communication manager 620 may be an example of various aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0209] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a network entity. The periodicity component 625 may be configured to or otherwise support components for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with one or more packets of the service burst. The service arrival offset value component 630 may be configured to or otherwise support components for estimating a service arrival offset value based on service periodicity, an estimated arrival time associated with one or more packets of the service burst, and at least one jitter parameter. The CDRX offset value component 635 may be configured to or otherwise support components for selecting a CDRX offset value based on an estimated service arrival offset value. The CDRX configuration component 640 may be configured to or otherwise support components for sending a message indicating a CDRX offset value to a UE for the UE to operate in a CDRX mode according to the CDRX offset value.

[0210] Figure 7 A block diagram 700 of a communication manager 720 supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of CDRX settings for periodic traffic with jitter as described herein. For example, the communication manager 720 may include a periodicity component 725, a traffic arrival offset value component 730, a CDRX offset value component 735, a CDRX configuration component 740, an arrival time component 745, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0211] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a network entity. The periodicity component 725 may be configured to or otherwise support components for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with one or more packets of the service burst. The service arrival offset value component 730 may be configured to or otherwise support components for estimating a service arrival offset value based on service periodicity, an estimated arrival time associated with one or more packets of the service burst, and at least one jitter parameter. The CDRX offset value component 735 may be configured to or otherwise support components for selecting a CDRX offset value based on an estimated service arrival offset value. The CDRX configuration component 740 may be configured to or otherwise support components for sending a message indicating a CDRX offset value to a UE for the UE to operate in a CDRX mode according to the CDRX offset value.

[0212] In some examples, the arrival time component 745 may be configured as or otherwise support components for determining an estimated arrival time associated with one or more packets of a traffic burst based on a traffic burst set, a traffic burst volume of a traffic burst set, a first arrival time for a first traffic burst in a traffic burst set, traffic periodicity, or a combination thereof.

[0213] In some examples, to support estimating a traffic arrival offset value, traffic arrival offset value component 730 may be configured or otherwise support means for estimating a traffic arrival offset value based on an earliest arrival time and an arrival time of one or more packets of a traffic burst.

[0214] In some examples, to support estimating a traffic arrival offset value, the traffic arrival offset value component 730 may be configured as or otherwise support components for estimating a traffic arrival offset value based on an earliest arrival time, a percentage value, and an arrival time of one or more packets of a traffic burst.

[0215] In some examples, the percentage value of the estimated arrival time is based on a quality of service of a communication link between the network entity and the UE, a packet delay budget, or a combination thereof.

[0216] In some examples, to support estimating a traffic arrival offset value, the traffic arrival offset value component 730 may be configured as or otherwise support a component for estimating a traffic arrival offset value based on at least one jitter parameter and a set of estimated arrival times for a set of traffic bursts comprising a traffic burst.

[0217] In some examples, at least one jitter parameter includes a set of earliest arrival times associated with a set of traffic bursts. In some examples, at least one jitter parameter includes a set of earliest arrival times associated with a set of traffic bursts, and a percentage value of a difference between a respective estimated arrival time associated with each traffic burst and a respective nominal arrival time associated with each traffic burst for the set of traffic bursts.

[0218] In some examples, the traffic arrival offset value component 730 may be configured to or otherwise support means for updating the estimated traffic arrival offset value based on a second set of estimated arrival times for a second traffic of the burst set. In some examples, the CDRX offset value component 735 may be configured to or otherwise support means for updating the CDRX offset value based on the estimated traffic arrival offset value.

[0219] In some examples, CDRX configuration component 740 may be configured to or otherwise support means for sending a second message indicating the updated CDRX offset value to the UE. In some examples, CDRX configuration component 740 may be configured to or otherwise support means for sending the second message based on the difference between the CDRX offset value and the updated CDRX offset value satisfying a threshold. In some examples, the second message includes an RRC message, a MAC-CE, or a wake-up signal for the UE.

[0220] In some examples, to support selecting a CDRX offset value, CDRX offset value component 735 may be configured or otherwise support means for selecting a CDRX offset value equal to the estimated traffic arrival offset value plus a UE-specific offset. In some examples, the UE-specific offset is based on scheduling traffic bursts for the UE.

[0221] In some examples, to support selecting a CDRX value, CDRX offset value component 735 can be configured or otherwise support means for selecting a CDRX offset value equal to an estimated traffic arrival offset value.

[0222] In some examples, CDRX configuration component 740 can be configured or otherwise support means for selecting a CDRX duty cycle periodicity equal to the determined traffic periodicity. In some examples, CDRX configuration component 740 can be configured or otherwise support means for sending an indication of the CDRX duty cycle periodicity in a message.

[0223] In some examples, to support sending a message indicating a CDRX offset value, CDRX configuration component 740 may be configured or otherwise support means for sending an indication of a set of CDRX parameters for a CDRX configuration for a CDRX mode, the set of CDRX parameters including the CDRX offset value.

[0224] In some examples, the timing parameters include a rendered fps value or an average downlink traffic arrival time for two or more traffic bursts.

[0225] Figure 8 A diagram of a system 800 including a device 805 supporting CDRX settings for periodic services with jitter according to one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a network entity 105 as described herein, or include components thereof. The device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 805 may include components that support output and acquisition of communications, such as a communication manager 820, a transceiver 810, an antenna 815, a memory 825, a code 830, and a processor 835. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 840).

[0226] As described herein, the transceiver 810 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 810 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 810 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 805 may include one or more antennas 815, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 810 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 815, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 815, from a wired receiver), and for demodulating a signal. In some implementations, the transceiver 810 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 815 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 815 configured to support various sending operations or output operations, or a combination thereof. In some implementations, the transceiver 810 may include or be configured to be coupled to one or more processors or memory components, which are operable to: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 810 or the transceiver 810 and one or more antennas 815 or the transceiver 810 and one or more antennas 815 and one or more processors or memory components (e.g., processor 835 or memory 825 or both) may be included in a chip or chip assembly installed in the device 805. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0228] The processor 835 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, a GPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 835 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 835. The processor 835 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 825) to enable the device 805 to perform various functions (e.g., various functions or tasks that support CDRX settings for periodic services with jitter). For example, the device 805 or a component of the device 805 may include a processor 835 and a memory 825 coupled to the processor 835, and the processor 835 and the memory 825 are configured to perform various functions described herein. The processor 835 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, a virtual machine, or a container instance)), which may host functions for performing the functions of the device 805 (e.g., by executing code 830). The processor 835 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 805 (such as in the memory 825). In some specific implementations, the processor 835 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (the output set may be passed to, for example, other systems or components of the device 805). For example, the processing system of the device 805 may refer to a system including various other components or subcomponents of the device 805 (such as the processor 835 or the transceiver 810 or the communication manager 820 or other components or combinations of components of the device 805). The processing system of the device 805 may be docked with other components of the device 805, and may process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of the device 805 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 805 can send information output from the chip or modem. Additionally or alternatively, in some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 805 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0229] In some examples, bus 840 may support communications of protocol layers (e.g., within protocol layers) of a protocol stack. In some examples, bus 840 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 805, or communications performed between different components of device 805 that may be co-located or may be located in different locations (e.g., where device 805 may refer to a system in which one or more of communication manager 820, transceiver 810, memory 825, code 830, and processor 835 may be located in one of the different components or divided between the different components).

[0230] In some examples, the communication manager 820 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 820 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 820 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UEs 115 in coordination with the other network entities 105. In some examples, the communication manager 820 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0231] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a network entity. For example, the communication manager 820 may be configured to or otherwise support a component for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with one or more packets of the service burst. The communication manager 820 may be configured to or otherwise support a component for estimating a service arrival offset value based on service periodicity, an estimated arrival time associated with one or more packets of the service burst, and at least one jitter parameter. The communication manager 820 may be configured to or otherwise support a component for selecting a CDRX (CDRX) offset value based on the estimated service arrival offset value. The communication manager 820 may be configured to or otherwise support a component for sending a message indicating a CDRX offset value to a UE for the UE to operate in a CDRX mode according to the CDRX offset value.

[0232] By including or configuring a communication manager 820 according to examples as described herein, the device 805 can support techniques for adaptively setting CDRX configuration parameters based on traffic patterns. For example, setting a CDRX offset value based on estimated traffic arrival times can improve the efficiency of scheduling and utilizing communication resources, reduce latency, and reduce processing at the device 805. In addition, the CDRX offset value can enable improved coordination between the device 805 and other devices (such as XR devices), which can improve the user experience.

[0233] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 810, one or more antennas 815 (e.g., where applicable), or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the transceiver 810, the processor 835, the memory 825, the code 830, or any combination thereof. For example, the code 830 may include instructions that are executable by the processor 835 to cause the device 805 to perform various aspects of CDRX settings for periodic traffic with jitter as described herein, or the processor 835 and the memory 825 may be otherwise configured to perform or support such operations.

[0234] Fig. 9 A block diagram 900 of a device 905 supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of a UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0235] The receiver 910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to CDRX settings for periodic traffic with jitter). The information may be passed to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0236] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to CDRX settings for periodic traffic with jitter), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0237] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of CDRX setup for periodic traffic with jitter as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0238] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a DSP, a CPU, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0239] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

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

[0241] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support a component for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with one or more packets of the service burst. The communication manager 920 may be configured to or otherwise support a component for estimating a service arrival offset value based on service periodicity, an estimated arrival time associated with one or more packets of the service burst, and at least one jitter parameter. The communication manager 920 may be configured to or otherwise support a component for selecting a CDRX (CDRX) offset value based on the estimated service arrival offset value. The communication manager 920 may be configured to or otherwise support a component for sending a message indicating a CDRX offset value to a network entity for the UE to operate in CDRX mode according to the CDRX offset value.

[0242] By including or configuring the communication manager 920 according to the examples described herein, the device 905 (e.g., a processor that controls or otherwise couples with the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) can support techniques for operating according to CDRX configuration parameters based on traffic patterns. For example, the device 905 can utilize CDRX offset values ​​based on estimated traffic arrival times that take jitter into account, which can improve the efficiency of scheduling and utilizing communication resources, reduce latency, and reduce processing at the device 905.

[0243] Fig.10 A block diagram 1000 of a device 1005 supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0244] The receiver 1010 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to CDRX settings for periodic traffic with jitter). The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0245] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to CDRX settings for periodic traffic with jitter), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0246] Device 1005 or its various components may be examples of components for performing various aspects of CDRX settings for periodic services with jitter as described herein. For example, communication manager 1020 may include periodic component 1025, service arrival offset value component 1030, CDRX offset value component 1035, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0247] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE. The periodicity component 1025 may be configured to or otherwise support components for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with one or more packets of the service burst. The service arrival offset value component 1030 may be configured to or otherwise support components for estimating a service arrival offset value based on service periodicity, an estimated arrival time associated with one or more packets of the service burst, and at least one jitter parameter. The CDRX offset value component 1035 may be configured to or otherwise support components for selecting a CDRX offset value based on the estimated service arrival offset value. The CDRX offset value component 1035 may be configured to or otherwise support components for sending a message indicating a CDRX offset value to a network entity for the UE to operate in a CDRX mode according to the CDRX offset value.

[0248] Fig.11 A block diagram 1100 of a communication manager 1120 supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of CDRX settings for periodic traffic with jitter as described herein. For example, the communication manager 1120 may include a periodicity component 1125, a traffic arrival offset value component 1130, a CDRX offset value component 1135, an arrival time component 1140, a CDRX mode component 1145, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0249] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at the UE. The periodicity component 1125 may be configured to or otherwise support components for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with one or more packets of the service burst. The service arrival offset value component 1130 may be configured to or otherwise support components for estimating a service arrival offset value based on service periodicity, an estimated arrival time associated with one or more packets of the service burst, and at least one jitter parameter. The CDRX offset value component 1135 may be configured to or otherwise support components for selecting a CDRX offset value based on the estimated service arrival offset value. In some examples, the CDRX offset value component 1135 may be configured to or otherwise support components for sending a message indicating a CDRX offset value to a network entity for the UE to operate in CDRX mode according to the CDRX offset value.

[0250] In some examples, the arrival time component 1140 may be configured as or otherwise support components for determining an estimated arrival time associated with one or more packets of a traffic burst based on a traffic burst set, a traffic burst volume of the traffic burst set, a first arrival time for a first traffic burst in the traffic burst set, and a traffic periodicity.

[0251] In some examples, the estimated arrival time, the estimated traffic arrival offset value, and the traffic periodicity are associated with the arrival of one or more packets of the traffic burst at the server.

[0252] In some examples, to support estimating a traffic arrival offset value, traffic arrival offset value component 1130 may be configured as or otherwise support means for estimating a traffic arrival offset value based on an earliest arrival time and an arrival time of one or more packets of a traffic burst.

[0253] In some examples, to support estimating a traffic arrival offset value, the traffic arrival offset value component 1130 may be configured to or otherwise support a component for estimating a traffic arrival offset value based on an earliest arrival time, a percentage value, and an arrival time of one or more packets of a traffic burst. In some examples, the percentage value is based on a quality of service, a packet delay budget, or a combination thereof, of a communication link between a network entity and a UE.

[0254] In some examples, to support estimating a service arrival offset value, the service arrival offset value component 1130 may be configured to or otherwise support a component for estimating a service arrival offset value based on at least one jitter parameter and a set of estimated arrival times for a service burst set including a service burst. In some examples, at least one jitter parameter includes a set of earliest arrival times associated with a service burst set. In some examples, at least one jitter parameter includes a set of earliest arrival times associated with a service burst set, and a percentage value of the difference between a corresponding estimated arrival time associated with each service burst and a corresponding nominal arrival time associated with each service burst for the service burst set.

[0255] In some examples, CDRX offset value component 1135 may be configured or otherwise support means for receiving a second message indicating an updated CDRX offset value. In some examples, CDRX mode component 1145 may be configured or otherwise support means for operating in CDRX mode according to the updated CDRX offset value. In some examples, the second message includes an RRC message, a MAC-CE, or a wake-up signal for the UE.

[0256] In some examples, to support selecting a CDRX offset value, CDRX offset value component 1135 may be configured or otherwise support means for selecting a CDRX offset value equal to an estimated traffic arrival offset value.

[0257] In some examples, CDRX mode component 1145 may be configured or otherwise support components for operating in CDRX mode according to a CDRX duty cycle periodicity equal to the determined traffic periodicity.

[0258] In some examples, CDRX mode component 1145 may be configured or otherwise support means for receiving an indication of a set of CDRX parameters for a CDRX configuration for a CDRX mode, the set of CDRX parameters including a CDRX offset value.

[0259] In some examples, the timing parameters include a rendered fps value or an average downlink traffic arrival time for two or more traffic bursts.

[0260] Fig.12A diagram of a system 1200 including a device 1205 supporting CDRX settings for periodic traffic with jitter according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a UE 115 as described herein, or include components thereof. The device 1205 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1205 may include components for two-way voice and data communications, including components for sending communications and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245).

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

[0262] In some cases, the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1215 may communicate bidirectionally via one or more antennas 1225, a wired or wireless link, as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1215 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1225 for transmission, and for demodulating packets received from one or more antennas 1225. The transceiver 1215 or the transceiver 1215 and one or more antennas 1225 may be examples of transmitters 915, transmitters 1015, receivers 910, receivers 1010, or any combination thereof or components thereof as described herein.

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

[0264] The processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a GPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1240. The processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to enable the device 1205 to perform various functions (e.g., various functions or tasks supporting CDRX settings for periodic services with jitter). For example, the device 1205 or a component of the device 1205 may include a processor 1240 and a memory 1230 coupled to or coupled to the processor 1240, and the processor 1240 and the memory 1230 are configured to perform the various functions described herein.

[0265] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at the UE. For example, the communication manager 1220 may be configured to or otherwise support a component for determining a service periodicity associated with one or more packets of a service burst based on a timing parameter associated with one or more packets of the service burst. The communication manager 1220 may be configured to or otherwise support a component for estimating a service arrival offset value based on service periodicity, an estimated arrival time associated with one or more packets of the service burst, and at least one jitter parameter. The communication manager 1220 may be configured to or otherwise support a component for selecting a CDRX offset value based on the estimated service arrival offset value. The communication manager 1220 may be configured to or otherwise support a component for sending a message indicating a CDRX offset value to a network entity for the UE to operate in CDRX mode according to the CDRX offset value.

[0266] By including or configuring the communication manager 1220 according to examples as described herein, the device 1205 can support techniques for operating according to CDRX configuration parameters based on traffic patterns. For example, the device 1205 can utilize CDRX offset values ​​based on estimated traffic arrival times that account for jitter, which can improve the efficiency of scheduling and utilizing communication resources, reduce latency, and reduce power consumption at the device 1205. In addition, the CDRX offset values ​​can enable improved coordination between the device 1205 and the XR server, which can improve the user experience at the device 1205.

[0267] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions that are executable by the processor 1240 to cause the device 1205 to perform various aspects of CDRX settings for periodic traffic with jitter as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.

[0268] Fig.13 A flow chart illustrating a method 1300 for supporting CDRX settings for periodic services with jitter according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 8 The described network entity performs. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0269] At 1305, the method may include determining a traffic periodicity associated with one or more packets of the traffic burst based at least in part on a timing parameter associated with one or more packets of the traffic burst. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described periodic component 725 executes.

[0270] At 1310, the method may include estimating a traffic arrival offset value based at least in part on traffic periodicity, estimated arrival times associated with one or more packets of a traffic burst, and at least one jitter parameter. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The described traffic arrival offset value component 730 performs.

[0271] At 1315, the method may include selecting a CDRX offset value based at least in part on the estimated traffic arrival offset value. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference Figure 7 The CDRX offset value component 735 is described as performing.

[0272] At 1320, the method may include sending a message indicating a CDRX offset value to the UE for the UE to operate in a CDRX mode according to the CDRX offset value. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference Figure 7 The CDRX configuration component 740 is described as performing.

[0273] Fig.14 A flow chart illustrating a method 1400 for supporting CDRX settings for periodic services with jitter according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 8 The described network entity performs. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0274] At 1405, the method may include determining a traffic periodicity associated with one or more packets of the traffic burst based at least in part on a timing parameter associated with one or more packets of the traffic burst. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The described periodic component 725 executes.

[0275] At 1410, the method may include estimating a traffic arrival offset value based at least in part on traffic periodicity, estimated arrival times associated with one or more packets of a traffic burst, at least one jitter parameter, and a set of estimated arrival times for a set of traffic bursts including the traffic burst. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 7 The described traffic arrival offset value component 730 performs.

[0276] At 1415, the method may include selecting a CDRX offset value based at least in part on the estimated traffic arrival offset value. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference Figure 7 The CDRX offset value component 735 is described as performing.

[0277] At 1420, the method may include sending a message indicating a CDRX offset value to the UE for the UE to operate in a CDRX mode according to the CDRX offset value. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference Figure 7 The CDRX configuration component 740 is described as performing.

[0278] At 1425, the method may include updating the estimated traffic arrival offset value based at least in part on a second set of estimated arrival times for a second set of traffic bursts. The operations of 1425 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1425 may be performed as described in reference to Figure 7 The described traffic arrival offset value component 730 performs.

[0279] At 1430, the method may include updating the CDRX offset value based at least in part on the estimated traffic arrival offset value. The operations of 1430 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1430 may be performed as described in reference to Figure 7 The CDRX offset value component 735 is described as performing.

[0280] At 1435, the method may include sending a second message to the UE indicating the updated CDRX offset value. The operations of 1435 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1435 may be performed as described in reference to Figure 7 The CDRX configuration component 740 is described as performing.

[0281] Fig.15 A flow chart illustrating a method 1500 for supporting CDRX settings for periodic services with jitter according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or components thereof as described herein. Figures 1 to 4 and Figures 9 to 12 The described UE 115 performs. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0282] At 1505, the method may include determining a traffic periodicity associated with one or more packets of the traffic burst based at least in part on a timing parameter associated with one or more packets of the traffic burst. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.11 The described periodic component 1125 executes.

[0283] At 1510, the method may include estimating a traffic arrival offset value based at least in part on traffic periodicity, estimated arrival times associated with one or more packets of a traffic burst, and at least one jitter parameter. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.11 The described service arrival offset value component 1130 performs.

[0284] At 1515, the method may include selecting a CDRX offset value based at least in part on the estimated traffic arrival offset value. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference Fig.11 The CDRX offset value component 1135 is described to perform.

[0285] At 1520, the method may include sending a message indicating a CDRX offset value to a network entity for the UE to operate in CDRX mode according to the CDRX offset value. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference Fig.11The CDRX offset value component 1135 is described to perform.

[0286] Fig.16 A flow chart illustrating a method 1600 for supporting CDRX settings for periodic services with jitter according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or components thereof as described herein. Figures 1 to 4 and Figures 9 to 12 The described UE 115 performs. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0287] At 1605, the method may include determining a traffic periodicity associated with one or more packets of the traffic burst based at least in part on a timing parameter associated with one or more packets of the traffic burst. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The described periodic component 1125 executes.

[0288] At 1610, the method may include estimating a traffic arrival offset value based at least in part on traffic periodicity, an estimated arrival time associated with one or more packets of a traffic burst, and at least one jitter parameter, wherein the at least one jitter parameter includes an earliest arrival time associated with one or more packets of the traffic burst, and a percentage value of a difference between the estimated arrival time and a nominal arrival time associated with the one or more packets of the traffic burst. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.11 The described service arrival offset value component 1130 performs.

[0289] At 1615, the method may include selecting a CDRX offset value based at least in part on the estimated traffic arrival offset value. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference Fig.11 The CDRX offset value component 1135 is described to perform.

[0290] At 1620, the method may include sending a message indicating a CDRX offset value to a network entity for the UE to operate in CDRX mode according to the CDRX offset value. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference Fig.11 The CDRX offset value component 1135 is described to perform.

[0291] At 1625, the method may include receiving an indication of a CDRX parameter set for a CDRX configuration of a CDRX mode, the CDRX parameter set including a CDRX offset value. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference Fig.11 The CDRX mode component 1145 is described to perform.

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

[0293] Aspect 1: A method for wireless communication at a network entity, comprising: determining a service periodicity associated with one or more packets of a service burst based at least in part on timing parameters associated with the one or more packets of the service burst; estimating a service arrival offset value based at least in part on the service periodicity, an estimated arrival time associated with the one or more packets of the service burst, and at least one jitter parameter; selecting a CDRX offset value based at least in part on the estimated service arrival offset value; and sending a message indicating the CDRX offset value to a UE so that the UE operates in a CDRX mode according to the CDRX offset value.

[0294] Aspect 2: The method according to Aspect 1 also includes: determining the estimated arrival time associated with the one or more groups of the service burst based at least in part on a service burst set, the service burst volume of the service burst set, the first arrival time for the first service burst in the service burst set, the service periodicity, or a combination thereof.

[0295] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the at least one jitter parameter includes an earliest arrival time associated with the one or more packets of the service burst, and wherein estimating the service arrival offset value includes: estimating the service arrival offset value based at least in part on the earliest arrival time and the arrival time of the one or more packets of the service burst.

[0296] Aspect 4: A method according to any one of Aspects 1 to 2, wherein the at least one jitter parameter includes an earliest arrival time associated with the one or more packets of the service burst, and a percentage value of the difference between the estimated arrival time associated with the one or more packets of the service burst and a nominal arrival time associated with the one or more packets of the service burst, and wherein estimating the service arrival offset value includes: estimating the service arrival offset value based at least in part on the earliest arrival time, the percentage value, and the arrival time of the one or more packets of the service burst.

[0297] Aspect 5: The method according to aspect 4, wherein the percentage value is based at least in part on a quality of service of a communication link between the network entity and the UE, a packet delay budget, or a combination thereof.

[0298] Aspect 6: A method according to any one of Aspects 1 to 2, wherein estimating the service arrival offset value comprises: estimating the service arrival offset value based at least in part on the at least one jitter parameter and a set of estimated arrival times for a set of service bursts including the service burst.

[0299] Aspect 7: The method according to aspect 6, wherein the at least one jitter parameter comprises a set of earliest arrival times associated with the set of traffic bursts.

[0300] Aspect 8: A method according to Aspect 6, wherein the at least one jitter parameter comprises a set of earliest arrival times associated with the set of service bursts, and a percentage value of the difference between the set of estimated arrival times and a set of nominal arrival times for the set of service bursts.

[0301] Aspect 9: The method according to any one of Aspects 6 to 8 further includes: updating the estimated service arrival offset value based at least in part on a second set of estimated arrival times for a second set of service bursts; and updating the CDRX offset value based at least in part on the estimated service arrival offset value.

[0302] Aspect 10: The method according to Aspect 9 further includes: sending a second message indicating the updated CDRX offset value to the UE.

[0303] Aspect 11: The method according to aspect 10 further includes: sending the second message based at least in part on the difference between the CDRX offset value and the updated CDRX offset value satisfying a threshold.

[0304] Aspect 12: The method according to any one of aspects 10 to 11, wherein the second message includes an RRC message, a MAC-CE, or a wake-up signal for the UE.

[0305] Aspect 13: The method according to any one of aspects 1 to 12, wherein selecting the CDRX offset value comprises: selecting the CDRX offset value to be equal to the estimated traffic arrival offset value plus a UE-specific offset.

[0306] Aspect 14: The method according to aspect 13, wherein the UE-specific offset is based at least in part on scheduling the traffic burst for the UE.

[0307] Aspect 15: The method according to any one of aspects 1 to 14, wherein selecting the CDRX value comprises: selecting the CDRX offset value to be equal to the estimated traffic arrival offset value.

[0308] Aspect 16: The method according to any one of Aspects 1 to 15 further includes: selecting a CDRX duty cycle periodicity to be equal to the determined traffic periodicity; and sending an indication of the CDRX duty cycle periodicity in the message.

[0309] Aspect 17: A method according to any one of Aspects 1 to 16, wherein sending the message indicating the CDRX offset value further comprises: sending an indication of a CDRX parameter set for a CDRX configuration for the CDRX mode, the CDRX parameter set including the CDRX offset value.

[0310] Aspect 18: The method according to any one of aspects 1 to 17, wherein the timing parameter comprises a rendering frames per second value or an average downlink traffic arrival time for two or more traffic bursts.

[0311] Aspect 19: A method for performing wireless communications at a UE, comprising: determining a service periodicity associated with one or more packets of a service burst based at least in part on timing parameters associated with the one or more packets of the service burst; estimating a service arrival offset value based at least in part on the service periodicity, an estimated arrival time associated with the one or more packets of the service burst, and at least one jitter parameter; selecting a CDRX offset value based at least in part on the estimated service arrival offset value; and sending a message indicating the CDRX offset value to a network entity so that the UE operates in CDRX mode based on the CDRX offset value.

[0312] Aspect 20: The method according to Aspect 19 also includes: determining the estimated arrival time associated with the one or more packets of the service burst based at least in part on a service burst set, a service burst volume of the service burst set, a first arrival time for a first service burst in the service burst set, and the service periodicity.

[0313] Aspect 21: The method according to any one of aspects 19 to 20, wherein the estimated arrival time, the estimated traffic arrival offset value and the traffic periodicity are associated with the one or more packets of the traffic burst arriving at a server.

[0314] Aspect 22: A method according to any one of Aspects 19 to 21, wherein the at least one jitter parameter includes an earliest arrival time associated with the one or more packets of the service burst, and wherein estimating the service arrival offset value includes: estimating the service arrival offset value based at least in part on the earliest arrival time and the arrival time of the one or more packets of the service burst.

[0315] Aspect 23: A method according to any one of Aspects 19 to 21, wherein the at least one jitter parameter includes an earliest arrival time associated with the one or more packets of the service burst, and a percentage value of the difference between the estimated arrival time associated with the one or more packets of the service burst and a nominal arrival time associated with the one or more packets of the service burst, and wherein estimating the service arrival offset value includes: estimating the service arrival offset value based at least in part on the earliest arrival time, the percentage value, and the arrival time of the one or more packets of the service burst.

[0316] Aspect 24: The method according to aspect 23, wherein the percentage value is based at least in part on a quality of service of a communication link between the network entity and the UE, a packet delay budget, or a combination thereof.

[0317] Aspect 25: A method according to any one of Aspects 19 to 21, wherein estimating the service arrival offset value comprises: estimating the service arrival offset value based at least in part on the at least one jitter parameter and a set of estimated arrival times for a set of service bursts including the service burst.

[0318] Aspect 26: The method according to Aspect 25, wherein the at least one jitter parameter comprises a set of earliest arrival times associated with the set of traffic bursts.

[0319] Aspect 27: A method according to Aspect 25, wherein the at least one jitter parameter includes a set of earliest arrival times associated with the set of service bursts, and a percentage value of the difference between the set of estimated arrival times and a set of nominal arrival times for the set of service bursts.

[0320] Aspect 28: The method according to any one of aspects 25 to 27 further includes: receiving a second message indicating an updated CDRX offset value; and operating in the CDRX mode according to the updated CDRX offset value.

[0321] Aspect 29: The method according to Aspect 28, wherein the second message includes an RRC message, a MAC-CE, or a wake-up signal for the UE.

[0322] Aspect 30: The method according to any one of aspects 19 to 29, wherein selecting the CDRX offset value comprises: selecting the CDRX offset value to be equal to the estimated traffic arrival offset value.

[0323] Aspect 31: The method according to any one of aspects 19 to 30, further comprising: operating in the CDRX mode according to a CDRX duty cycle periodicity equal to the determined traffic periodicity.

[0324] Aspect 32: The method according to any one of aspects 19 to 31, further comprising: receiving an indication of a CDRX parameter set for a CDRX configuration for the CDRX mode, the CDRX parameter set comprising the CDRX offset value.

[0325] Aspect 33: A method according to any one of aspects 19 to 32, wherein the timing parameter comprises a rendered frames per second value or an average downlink traffic arrival time for two or more traffic bursts.

[0326] Aspect 34: An apparatus for wireless communication at a network entity, comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 1 to 18.

[0327] Aspect 35: An apparatus for wireless communication at a network entity, comprising at least one component for performing a method according to any one of aspects 1 to 18.

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

[0329] Aspect 37: An apparatus for performing wireless communications at a UE, comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 19 to 33.

[0330] Aspect 38: An apparatus for wireless communication at a UE, comprising at least one component for performing a method according to any one of aspects 19 to 33.

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

[0332] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and other implementations are possible. In addition, aspects of two or more of these methods may be combined.

[0333] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDM, including future systems and radio technologies, and other systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

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

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

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

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

Claims

1. An apparatus for wireless communication at a network entity, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to: determining a traffic periodicity associated with one or more packets of a traffic burst based at least in part on a timing parameter associated with the one or more packets of the traffic burst; estimating a traffic arrival offset value based at least in part on the traffic periodicity, an estimated arrival time associated with the one or more packets of the traffic burst, and at least one jitter parameter; selecting a connected mode discontinuous reception (CDRX) offset value based at least in part on the estimated traffic arrival offset value; as well as A message indicating the CDRX offset value is sent to a user equipment (UE) for the UE to operate in a CDRX mode according to the CDRX offset value.

2. The apparatus of claim 1 , wherein the instructions are further executable by the at least one processor to cause the network entity to: The estimated arrival time associated with the one or more packets of the traffic bursts is determined at least in part based on a traffic burst set, a traffic burst volume of the traffic burst set, a first arrival time for a first traffic burst in the traffic burst set, the traffic periodicity, or a combination thereof.

3. The apparatus of claim 1 , wherein the at least one jitter parameter comprises an earliest arrival time associated with the one or more packets of the traffic burst, and wherein the instructions for estimating the traffic arrival offset value are executable by the at least one processor to cause the network entity to: The traffic arrival offset value is estimated based at least in part on the earliest arrival time and an arrival time of the one or more packets of the traffic burst.

4. The apparatus of claim 1 , wherein the at least one jitter parameter comprises an earliest arrival time associated with the one or more packets of the traffic burst, and a percentage value of a difference between the estimated arrival time associated with the one or more packets of the traffic burst and a nominal arrival time associated with the one or more packets of the traffic burst, and wherein the instructions for estimating the traffic arrival offset value are executable by the at least one processor to cause the network entity to: The traffic arrival offset value is estimated based at least in part on the earliest arrival time, the percentage value, and arrival times of the one or more packets of the traffic burst.

5. The apparatus of claim 4, wherein the percentage value is based at least in part on a quality of service of a communication link between the network entity and the UE, a packet delay budget, or a combination thereof.

6. The apparatus of claim 1, wherein the instructions for estimating the traffic arrival offset value are executable by the at least one processor to cause the network entity to: The traffic arrival offset value is estimated based at least in part on the at least one jitter parameter and a set of estimated arrival times for a set of traffic bursts including the traffic burst.

7. The apparatus of claim 6, wherein the at least one jitter parameter comprises a set of earliest arrival times associated with the set of traffic bursts.

8. The apparatus of claim 6, wherein the at least one jitter parameter comprises a set of earliest arrival times associated with the set of traffic bursts, and a percentage value of a difference between the set of estimated arrival times and a set of nominal arrival times for the set of traffic bursts.

9. The apparatus of claim 6, wherein the instructions are further executable by the at least one processor to cause the network entity to: updating the estimated traffic arrival offset value based at least in part on a second set of estimated arrival times for a second set of traffic bursts; and The CDRX offset value is updated based at least in part on the estimated traffic arrival offset value.

10. The apparatus of claim 9, wherein the instructions are further executable by the at least one processor to cause the network entity to: A second message indicating the updated CDRX offset value is sent to the UE.

11. The apparatus of claim 10, wherein the instructions are further executable by the at least one processor to cause the network entity to: The second message is sent based at least in part on a difference between the CDRX offset value and the updated CDRX offset value satisfying a threshold.

12. The apparatus of claim 10, wherein the second message comprises a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), or a wake-up signal for the UE.

13. The apparatus of claim 1 , wherein the instructions for selecting the CDRX offset value are executable by the at least one processor to cause the network entity to: The CDRX offset value is selected to be equal to the estimated traffic arrival offset value plus a UE-specific offset.

14. The apparatus of claim 1, wherein the instructions for selecting the CDRX value are executable by the at least one processor to cause the network entity to: The CDRX offset value is selected to be equal to the estimated traffic arrival offset value.

15. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the network entity to: selecting a CDRX duty cycle periodicity equal to the determined traffic periodicity; and An indication of the CDRX duty cycle periodicity is sent in the message.

16. The apparatus of claim 1, wherein the instructions for sending the message indicating the CDRX offset value are further executable by the at least one processor to cause the network entity to: An indication of a set of CDRX parameters for a CDRX configuration for the CDRX mode is sent, the set of CDRX parameters including the CDRX offset value.

17. The apparatus of claim 1, wherein the timing parameter comprises a rendered frames per second value or an average downlink traffic arrival time for two or more traffic bursts.

18. An apparatus for wireless communication at a user equipment (UE), comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to: determining a traffic periodicity associated with one or more packets of a traffic burst based at least in part on a timing parameter associated with the one or more packets of the traffic burst; estimating a traffic arrival offset value based at least in part on the traffic periodicity, an estimated arrival time associated with the one or more packets of the traffic burst, and at least one jitter parameter; selecting a connected mode discontinuous reception (CDRX) offset value based at least in part on the estimated traffic arrival offset value; as well as A message indicating the CDRX offset value is sent to a network entity for the UE to operate in CDRX mode according to the CDRX offset value.

19. The apparatus of claim 18, wherein the instructions are further executable by the at least one processor to cause the UE to: The estimated arrival time associated with the one or more packets of the traffic burst is determined based at least in part on a set of traffic bursts, a traffic burst volume of the set of traffic bursts, a first arrival time for a first traffic burst in the set of traffic bursts, and the traffic periodicity.

20. The apparatus of claim 18, wherein the estimated arrival time, the estimated traffic arrival offset value, and the traffic periodicity are associated with the one or more packets of the traffic burst arriving at a server.

21. The apparatus of claim 18, wherein the at least one jitter parameter comprises an earliest arrival time associated with the one or more packets of the traffic burst, and wherein the instructions for estimating the traffic arrival offset value are executable by the at least one processor to cause the UE to: The traffic arrival offset value is estimated based at least in part on the earliest arrival time and an arrival time of the one or more packets of the traffic burst.

22. The apparatus of claim 18, wherein the at least one jitter parameter comprises an earliest arrival time associated with the one or more packets of the traffic burst, and a percentage value of a difference between the estimated arrival time associated with the one or more packets of the traffic burst and a nominal arrival time associated with the one or more packets of the traffic burst, and wherein the instructions for estimating the traffic arrival offset value are executable by the at least one processor to cause the UE to: The traffic arrival offset value is estimated based at least in part on the earliest arrival time, the percentage value, and arrival times of the one or more packets of the traffic burst.

23. The apparatus of claim 18, wherein the instructions for estimating the traffic arrival offset value are executable by the at least one processor to cause the UE to: The traffic arrival offset value is estimated based at least in part on the at least one jitter parameter and a set of estimated arrival times for a set of traffic bursts including the traffic burst.

24. The apparatus of claim 23, wherein the instructions are further executable by the at least one processor to cause the UE to: receiving a second message indicating an updated CDRX offset value; and Operating in the CDRX mode according to the updated CDRX offset value.

25. The apparatus of claim 24, wherein the second message comprises a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), or a wake-up signal for the UE.

26. The apparatus of claim 18, wherein the instructions for selecting the CDRX offset value are executable by the at least one processor to cause the UE to: The CDRX offset value is selected to be equal to the estimated traffic arrival offset value.

27. The apparatus of claim 18, wherein the instructions are further executable by the at least one processor to cause the UE to: Operating in the CDRX mode according to a CDRX duty cycle periodicity equal to the determined traffic periodicity.

28. The apparatus of claim 18, wherein the instructions are further executable by the at least one processor to cause the UE to: An indication of a set of CDRX parameters for a CDRX configuration for the CDRX mode is received, the set of CDRX parameters including the CDRX offset value.

29. A method for wireless communication at a network entity, comprising: determining a traffic periodicity associated with one or more packets of a traffic burst based at least in part on a timing parameter associated with the one or more packets of the traffic burst; estimating a traffic arrival offset value based at least in part on the traffic periodicity, an estimated arrival time associated with the one or more packets of the traffic burst, and at least one jitter parameter; selecting a connected mode discontinuous reception (CDRX) offset value based at least in part on the estimated traffic arrival offset value; as well as A message indicating the CDRX offset value is sent to a user equipment (UE) for the UE to operate in a CDRX mode according to the CDRX offset value.

30. A method for wireless communication at a user equipment (UE), comprising: determining a traffic periodicity associated with one or more packets of a traffic burst based at least in part on a timing parameter associated with the one or more packets of the traffic burst; estimating a traffic arrival offset value based at least in part on the traffic periodicity, an estimated arrival time associated with the one or more packets of the traffic burst, and at least one jitter parameter; selecting a connected mode discontinuous reception (CDRX) offset value based at least in part on the estimated traffic arrival offset value; as well as A message indicating the CDRX offset value is sent to a network entity for the UE to operate in CDRX mode according to the CDRX offset value.

Images