Resource cycle method

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may wake up at the start in a subframe based at least in part on a subframe index of a resource cycle and a system frame number (SFN) wrap-around offset considering a cumulative length of a hyperframe. The UE may receive data bursts between subframes. Numerous other aspects are described.

Description

Technical Field

[0001] (Cross - Reference to Related Applications)

[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 366,204, filed on June 10, 2022, entitled "DISCONTINUOUS RECEPTION METHODOLOGY", and U.S. Non - Provisional Patent Application No. 18 / 296,952, filed on April 06, 2023, entitled "RESOURCE CYCLE METHODOLOGY", which are hereby incorporated by reference in their entirety.

[0002] Introduction

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatus for addressing resource cycles and other applications.

[0003]

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system can adopt a multiple access technology that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standards published by the Third Generation Partnership Project (3GPP).

[0004]

[0004] A wireless network may include one or more base stations that support communication of a single user equipment (UE) or multiple UEs. The UE may communicate with the base station via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the base station to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the base station. As will be described in more detail herein, the BS may be referred to as Node B, gNB, access point (AP), radio head, transmit receive point (TRP), New Radio (NR) BS, 5G Node B, and the like.

[0005]

[0005] The above multi-connectivity technology has been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, and / or global scale. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access through improvements in spectral efficiency, cost reduction, service improvement, utilization of new spectrum, and the use of orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, and the use of CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, better integration with other open standards, and support for beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. Since the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful.

Summary of the Invention

[0006] [

[0006] ] Some aspects described herein relate to a method for wireless communication in a user equipment (UE). The method may include waking up at the start of a subframe based at least in part on a subframe index of a resource cycle and a system frame number (SFN) wrap-around offset considering the cumulative length of a hyperframe. The method may include receiving a data burst between subframes.

[0007] [

[0007] ] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to wake up at the start of a subframe based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset considering the cumulative length of a hyperframe. The one or more processors may be configured to receive a data burst between subframes.

[0008] [

[0008] ] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to wake up at the start of a subframe based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset considering the cumulative length of a hyperframe. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a data burst between subframes.

[0009]

[0009] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for waking up at the start of a subframe, based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset taking into account the cumulative length of a hyperframe. The apparatus may include means for receiving a data burst between subframes.

[0010]

[0010] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include sleeping in relation to a discontinuous reception (DRX) cycle. The method may include waking up at the start of a subframe, based at least in part on a specified time offset added to an on-duration of a DRX cycle based at least in part on a number of DRX cycles of the DRX cycle and a length of the DRX cycle, where the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset. The method may include receiving a multimedia data burst between subframes.

[0011]

[0011] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include sleeping in relation to a DRX cycle. The method may include waking up at the start of a subframe, based at least in part on a specified time offset added to an on-duration of a DRX cycle based at least in part on a number of DRX cycles of the DRX cycle and a DRX time reference SFN, where the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset. The method may include receiving a multimedia data burst between subframes.

[0012]

[0012] Some aspects described herein relate to methods of wireless communication performed by a UE. The method may include sleeping in relation to a resource cycle. The method may include waking up at the start of a subframe, at least in part based on a specified time offset added to an instance of the resource cycle, at least in part based on the number of resource cycles of the resource cycle and the length of the resource cycle, where the specified time offset is at least in part based on the periodicity of the multimedia data burst, and the number of resource cycles is at least in part based on the specified time offset. The method may include receiving a multimedia data burst between subframes.

[0013]

[0013] Some aspects described herein relate to methods of wireless communication performed by a network entity. The method may include preparing to communicate with a UE according to a DRX cycle. The method may include transmitting a data burst at the start of a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is at least in part based on the periodicity of the multimedia data burst, and the number of DRX cycles is at least in part based on the specified time offset.

[0014]

[0014] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include preparing to communicate with a UE according to a DRX cycle. The method may include transmitting a data burst at a start in a subframe based at least in part on a number of DRX cycles of the DRX cycle and a specified time offset added to an on-duration of the DRX cycle based at least in part on a length of the DRX cycle, the specified time offset being based at least in part on periodicity of a multimedia data burst, the number of DRX cycles being based at least in part on the specified time offset.

[0015]

[0015] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include preparing to communicate with a UE according to a resource cycle. The method may include transmitting a data burst at a start in a subframe based at least in part on a number of resource cycles of the resource cycle and a specified time offset added to an instance of the resource cycle based at least in part on a length of the resource cycle, the specified time offset being based at least in part on periodicity of a multimedia data burst, the number of resource cycles being based at least in part on the specified time offset, the number of resource cycles being based at least in part on the specified time offset.

[0016]

[0016] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to put the UE to sleep in relation to a DRX cycle. The one or more processors may be configured to wake up the UE at the start in a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and at least in part based on the length of the DRX cycle, the specified time offset being at least in part based on the periodicity of the multimedia data burst, and the number of DRX cycles being at least in part based on the specified time offset. The one or more processors may be configured to receive a multimedia data burst between subframes.

[0017]

[0017] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to put the UE to sleep in relation to a DRX cycle. The one or more processors may be configured to wake up the UE at the start in a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and at least in part based on the DRX time reference SFN, the specified time offset being at least in part based on the periodicity of the multimedia data burst, and the number of DRX cycles being at least in part based on the specified time offset. The one or more processors may be configured to receive a multimedia data burst between subframes.

[0018]

[0018] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to sleep in relation to a resource cycle. The one or more processors may be configured to wake up the UE at the start in a subframe at least partially based on a specified time offset added to an instance of the resource cycle at least partially based on the number of resource cycles of the resource cycle and the length of the resource cycle, where the specified time offset is at least partially based on the periodicity of the multimedia data burst and the number of resource cycles is at least partially based on the specified time offset. The one or more processors may be configured to receive a multimedia data burst between subframes.

[0019]

[0019] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to prepare to communicate with a UE according to a DRX cycle. The one or more processors may be configured to transmit a data burst at the start in a subframe at least partially based on a specified time offset added to the on-duration of the DRX cycle at least partially based on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is at least partially based on the periodicity of the multimedia data burst and the number of DRX cycles is at least partially based on the specified time offset.

[0020]

[0020] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to prepare to communicate with a UE according to a DRX cycle. The one or more processors may be configured to transmit a data burst at the start in a subframe, at least in part based on a specified time offset added to an on-duration of the DRX cycle, at least in part based on a number of DRX cycles of the DRX cycle and a length of the DRX cycle. The specified time offset is at least in part based on a periodicity of a multimedia data burst, and the number of DRX cycles is at least in part based on the specified time offset.

[0021]

[0021] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to prepare to communicate with a UE according to a resource cycle. The one or more processors may be configured to transmit a data burst at the start in a subframe, at least in part based on a specified time offset added to an instance of the resource cycle, at least in part based on a number of resource cycles of the resource cycle and a length of the resource cycle. The specified time offset is at least in part based on a periodicity of a multimedia data burst, the number of resource cycles is at least in part based on the specified time offset, and the number of resource cycles is at least in part based on the specified time offset.

[0022]

[0022] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to sleep in relation to a DRX cycle. The set of instructions, when executed by one or more processors of the UE, may cause the UE to wake up at the start in a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is at least in part based on the periodicity of multimedia data bursts, and the number of DRX cycles is at least in part based on the specified time offset. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a multimedia data burst between subframes.

[0023]

[0023] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to sleep in relation to a DRX cycle. The set of instructions, when executed by one or more processors of the UE, may cause the UE to wake up at the start in a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the DRX time reference SFN, where the specified time offset is at least in part based on the periodicity of multimedia data bursts, and the number of DRX cycles is at least in part based on the specified time offset. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a multimedia data burst between subframes.

[0024] [

[0024] ] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to sleep in relation to a resource cycle. The set of instructions, when executed by one or more processors of the UE, may cause the UE to wake up at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of resource cycles being based at least in part on the specified time offset. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a multimedia data burst between subframes.

[0025] [

[0025] ] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to prepare to communicate with a UE according to a DRX cycle. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles being based at least in part on the specified time offset.

[0026]

[0026] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to prepare to communicate with a UE according to a DRX cycle. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit a data burst at the start in a subframe based at least in part on a specified time offset added to an on-duration of the DRX cycle based at least in part on a number of DRX cycles of the DRX cycle and a length of the DRX cycle, the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles being based at least in part on the specified time offset.

[0027]

[0027] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to prepare to communicate with a UE according to a resource cycle. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit a data burst at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on a number of resource cycles of the resource cycle and a length of the resource cycle, the specified time offset being based at least in part on the periodicity of a multimedia data burst, the number of resource cycles being based at least in part on the specified time offset, and the number of resource cycles being based at least in part on the specified time offset.

[0028] [

[0028] ]Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sleeping in relation to a DRX cycle. The apparatus may include means for waking up at the start in a subframe, at least in part based on a specified time offset added to the on-duration of a DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is at least in part based on the periodicity of a multimedia data burst, and the number of DRX cycles is at least in part based on the specified time offset. The apparatus may include means for receiving a multimedia data burst between subframes.

[0029] [

[0029] ]Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sleeping in relation to a DRX cycle. The apparatus may include means for waking up at the start in a subframe, at least in part based on a specified time offset added to the on-duration of a DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the DRX time reference system frame number (SFN), where the specified time offset is at least in part based on the periodicity of a multimedia data burst, and the number of DRX cycles is at least in part based on the specified time offset. The apparatus may include means for receiving a multimedia data burst between subframes.

[0030]

[0030] Some aspects described in this specification relate to an apparatus for wireless communication. The apparatus may include means for sleeping in relation to a resource cycle. The apparatus may include means for waking up at the start in a subframe, at least in part based on a specified time offset added to an instance of the resource cycle, at least in part based on the number of resource cycles of the resource cycle and the length of the resource cycle, where the specified time offset is at least in part based on the periodicity of the multimedia data burst, and the number of resource cycles is at least in part based on the specified time offset. The apparatus may include means for receiving a multimedia data burst between subframes.

[0031]

[0031] Some aspects described in this specification relate to an apparatus for wireless communication. The apparatus may include means for preparing to communicate with a UE according to a DRX cycle. The apparatus may include means for transmitting a data burst at the start in a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is at least in part based on the periodicity of the multimedia data burst, and the number of DRX cycles is at least in part based on the specified time offset.

[0032]

[0032] Some aspects described in this specification relate to an apparatus for wireless communication. The apparatus may include means for preparing to communicate with a UE according to a DRX cycle. The apparatus may include means for transmitting a data burst at the start in a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is at least in part based on the periodicity of the multimedia data burst, and the number of DRX cycles is at least in part based on the specified time offset.

[0033]

[0033] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for preparing to communicate with a UE according to a resource cycle. The apparatus may include means for transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle, based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, where the specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of resource cycles is based at least in part on the specified time offset, and the number of resource cycles is based at least in part on the specified time offset.

[0034]

[0034] Aspects generally include, as substantially fully described herein with reference to the drawings and this specification, and as shown by the drawings and this specification, a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, wireless communication device, and / or processing system.

[0035]

[0035] Above, for better understanding of the following "Modes for Carrying Out the Invention", the features and technical advantages of the examples according to the present disclosure have been outlined rather extensively. Additional features and advantages are described below. The concepts and specific examples of the disclosure can be readily utilized as a basis for modifying or designing other structures to achieve the same objectives of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of both the organization and the method of operation of the concepts disclosed herein, and the advantages associated therewith, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings is provided for illustration and explanation purposes, rather than as a definition of the limitations of the claims.

[0036] Aspects are described in this disclosure by way of several examples, and those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented via integrated chip embodiments or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, and / or artificial intelligence-enabled devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers) for analog and digital applications. The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and structures.

Brief Description of the Drawings

[0037]

[0037] To better understand the above-listed features of the present disclosure in detail, a more detailed description, briefly summarized above, may be obtained by referring to some of the aspects shown in the accompanying drawings. However, it should be noted that the accompanying drawings show only certain exemplary aspects of the present disclosure and, therefore, should not be considered as limiting the scope of the present disclosure, as the description may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

Figure 1

[0038] A diagram showing an example of a wireless network according to the present disclosure.

Figure 2

[0039] A diagram showing an example of a base station communicating with a user equipment (UE) within a wireless network according to the present disclosure.

Figure 3

[0040] A diagram showing an example of a device designed for low-latency applications according to the present disclosure.

Figure 4

[0041] A diagram showing examples of low-latency traffic and power states according to the present disclosure.

Figure 5

[0042] An example of the mismatch between an intermittent reception (DRX) cycle and the periodicity of extended reality traffic according to the present disclosure is shown.

Figure 6

[0043] An example of an anchor cycle using a leap DRX cycle according to the present disclosure is shown.

Figure 7

[0044] An example of a DRX configuration using dynamic offset adjustment to support a DRX technique with a non-uniform cycle duration according to the present disclosure is shown.

Figure 8

[0045] A diagram showing an example of using a short cadence value for DRX according to the present disclosure.

Figure 9

[0046] A diagram showing an example of using a short cadence value for DRX regarding slot position according to the present disclosure.

Figure 10

[0047] A diagram showing an example of using a short cadence value for DRX according to the present disclosure.

Figure 11

[0048] A diagram showing an example of using different short cadence values according to the present disclosure.

Figure 12

[0049] A diagram showing an example of using a short cadence value for DRX according to the present disclosure.

Figure 13

[0050] A diagram showing an example of using short cadence values for DRX according to the present disclosure.

Figure 14

[0051] A diagram showing an example of system frame number wraparound according to the present disclosure.

Figure 15

[0052] A diagram showing an example of setting a hyperframe length according to the present disclosure.

Figure 16

[0053] A diagram showing an example of a radio resource control (RRC) configuration for a DRX cycle according to the present disclosure.

Figure 17

[0054] A diagram showing an example of aligning a DRX cycle with multimedia periodicity according to the present disclosure.

Figure 18

[0055] A diagram showing an example associated with the use of a specified time offset according to the present disclosure.

Figure 19

[0056] A diagram showing an example of a non-aggregated base station according to the present disclosure.

Figure 20

[0057] A diagram showing an exemplary process performed, for example, by a UE according to the present disclosure.

Figure 21

[0058] A diagram showing an exemplary process performed, for example, by a UE according to the present disclosure.

Figure 22

[0059] A diagram showing an exemplary process performed, for example, by a UE according to the present disclosure.

Figure 23

[0060] A diagram showing an exemplary process performed, for example, by a base station according to the present disclosure.

Figure 24

[0061] A diagram showing an exemplary process performed, for example, by a base station according to the present disclosure.

Figure 25

[0062] A diagram showing an exemplary process performed, for example, by a base station according to the present disclosure.

Figure 26

[0063] Block diagram of an exemplary apparatus for wireless communication according to the present disclosure.

Figure 27

[0064] Figure showing an example of a hardware implementation form for an apparatus using a processing system.

Figure 28

[0065] Figure showing an exemplary implementation form of code and circuitry for an apparatus according to the present disclosure.

Figure 29

[0066] Block diagram of an exemplary apparatus for wireless communication according to the present disclosure.

Figure 30

[0067] Figure showing an example of a hardware implementation form for an apparatus using a processing system.

Figure 31

[0068] Figure showing an exemplary implementation form of code and circuitry for an apparatus according to the present disclosure.

Figure 32

[0069] Figure showing an example of a leap - off - set pattern according to the present disclosure.

Figure 33A

[0070] Figure showing an example of a sub - frame index according to the present disclosure.

Figure 33B

[0071] Figure showing an example of a sub - frame index according to the present disclosure.

Figure 34

[0072] Figure showing an example of backward compatibility according to the present disclosure.

Figure 35

[0073] Figure showing an example of dealing with backward compatibility according to the present disclosure.

Figure 36

[0074] Figure showing an example associated with the use of an SFN wrap - around offset according to the present disclosure.

Figure 37

[0075] Figure showing an example of using an SFN wrap - around offset according to the present disclosure.

Figure 38

[0076] Figure showing an exemplary process, for example, implemented by a UE according to the present disclosure.

Figure 39

[0077] FIG. is an illustration of an exemplary apparatus for wireless communication according to the present disclosure.

Figure 40

[0078] FIG. shows an example of a hardware implementation for an apparatus using a processing system.

Figure 41

[0079] FIG. shows an example of a code and circuit implementation for an apparatus according to the present disclosure.

DETAILED DESCRIPTION

[0038]

[0080] The power consumption of a user equipment (UE), such as an extended reality (XR) device, can be reduced by limiting the amount of time that the UE's processing resources are active for computing and power consumption. Some wireless communication systems may support a discontinuous reception (DRX) mode. A UE in the DRX mode can transition between a sleep state for power saving and an active state for data transmission and reception. The sleep state involves a reduction in the use of resources (power saving) for receiving or transmitting communication. The active state includes an increase in the amount of resources used for receiving and transmitting communication or the recovery of resources. The active state for data transmission and reception is sometimes referred to as the DRX "on-duration". A DRX cycle may be a duration that includes the sleep state and the active on-duration state for the UE. The DRX cycle can start at the start of the on-duration and end at the start of the next on-duration. In some aspects, the DRX cycle may be referred to as a "DRX long cycle".

[0039]

[0081] However, there are DRX multimedia timing mismatches that prevent such alignment and prevent the successful use of DRX. For example, according to one or more aspects, the update rate for the UE can be, for example, 120 Hz or 60 Hz, and thus result in downlink traffic burst arrival periodicities of 8.333 ms or 16.667 ms, respectively. However, the DRX configuration can have a granularity of 1 millisecond as the finest granularity for the DRX cycle, and the start of the on-duration may be aligned to the millisecond time boundary. These partial millisecond differences, combined with each traffic burst of the XR traffic cycle, can cause a mismatch between the DRX cycle and the multimedia traffic periodicity. For example, the XR traffic cycle (the time when the XR traffic data burst arrives) may drift to the middle of the DRX cycle. The mismatch between the time when the XR traffic burst arrives and the time when the UE wakes up during the on-duration of the DRX cycle can cause an increase in latency and power consumption because if the XR traffic burst arrives when the UE is not awake, the XR traffic burst may have to be retransmitted or it will result in a waste of power and signaling resources.

[0040]

[0082] The techniques described in more detail below improve the alignment of DRX cycles with multimedia traffic in order to reduce the mismatch between multimedia burst traffic and DRX-on duration. For example, a UE may use wake-up conditions to determine when to wake up, which may include adding a specified time offset, which may be a fixed time shift, to the on-duration of a DRX cycle (e.g., the next on-duration). The wake-up conditions may be at least partially based on the subframe number of a subframe, which in one or more aspects may be a subframe of a frame identified by a system frame number (SFN). The specified time offset may be added based at least partially on the number of DRX cycles and the DRX cycle length of the DRX cycle. In some aspects, the DRX cycle may be a leap cycle that adds a leap offset or amount of time (e.g., 1 ms) to align an XR traffic burst with the DRX-on duration. In some aspects, the UE may be configured using a leap offset pattern that indicates to which DRX-on duration the leap offset should be applied. The leap offset pattern may be applied for each leap cycle, which may include a certain amount of DRX-on duration. An anchor cycle may include a plurality of leap cycles.

[0041]

[0083] According to one or more aspects, a UE may configure a DRX cycle for the cadence of data bursts, such as every 8.33 ms at 120 Hz, although the cadence of data bursts may be associated with a 1000 ms periodicity. In one or more examples, using a 1000 ms multimedia periodicity and a 10240 ms DRX cycle (1024 SFNs per hyperframe at 10 ms intervals), the hyperframe of DRX (formed by a certain amount of SFNs, such as 1024 SFNs) may be inconsistent with the frame of the multimedia server every 10.24 seconds. In some aspects, the wake-up condition may address this SFN wrap-around problem where the end of the hyperframe (end of 1024 SFNs) causes an inconsistency between the subframe index and the traffic burst. For example, the UE may wake up based at least in part on an SFN wrap-around offset that adjusts the inconsistency caused by the end of the hyperframe. As a result, the UE may not miss traffic bursts and communication performance may be improved.

[0042]

[0084] The various aspects described herein apply to examples with a DRX cycle, although the various aspects described herein may also apply to other resource cycles.

[0043]

[0085] Various aspects of the present disclosure will now be described more fully with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be understood by those skilled in the art that the scope of the disclosure herein is intended to cover any other aspect of the disclosure, whether implemented independently of or in combination with any other aspect of the disclosure herein. For example, any number of the aspects described herein can be used to implement an apparatus or practice a method. In addition, the scope of the present disclosure is intended to cover such an apparatus or method practiced using other structures, functions, or a combination of structures and functions in addition to, or other than, the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0044]

[0086] Next, some aspects of a telecommunications system are shown with reference to various devices and techniques. These devices and techniques are described in the context of implementing the following invention and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or as software depends on the specific application example and the design constraints imposed on the overall system.

[0045]

[0087] Aspects may be described herein using terms commonly associated with 5G or New Radio (NR) radio access technology (RAT), but aspects of the present disclosure can be applied to other RATs such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0046]

[0088] FIG. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be, among other examples, a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements thereof. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE120a, UE120b, UE120c, UE120d, and UE120e), and / or other network entities. A base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term “cell” may refer to the coverage area of the base station 110 and / or the base station subsystem providing services to this coverage area, depending on the context in which the term is used.

[0047]

[0089] The base station 110 may provide communication coverage to a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell can cover a relatively large geographical area (e.g., several kilometers in radius) and may enable unrestricted access by the UE 120 subscribed to the service. A pico cell can cover a relatively small geographical area and may enable unrestricted access by the UE 120 subscribed to the service. A femto cell can cover a relatively small geographical area (e.g., a home) and may enable restricted access by the UE 120 associated with the femto cell (e.g., the UE 120 within a closed subscriber group (CSG)). The base station 110 for a macro cell may be referred to as a macro base station. The base station 110 for a pico cell may be referred to as a pico base station. The base station 110 for a femto cell may be referred to as a femto base station or a home base station. In the example shown in FIG. 1, BS110a can be a macro base station for the macro cell 102a, BS110b can be a pico base station for the pico cell 102b, and BS110c can be a femto base station for the femto cell 102c. A base station may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "node B", "5G NB", and "cell" may be used interchangeably herein.

[0048]

[0090] In some examples, the cell may not necessarily be fixed, and the geographical area of the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or with one or more other base stations 110 or network nodes (not shown) within the wireless network 100 through various types of backhaul interfaces such as direct physical connections or virtual networks using any suitable transport network.

[0049]

[0091] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a centralized base station, a non-centralized base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more of their components. For example, in some aspects, the "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to one device configured to perform one or more functions, such as the functions described herein with respect to base station 110. In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function or to replicate the operation of at least a portion of a function, and the term "base station" or "network entity" may refer to any one or more of those different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions and not another. In this way, a single device may include two or more base stations.

[0050]

[0092] Wireless network 100 may include one or more relay stations. A relay station is an entity capable of receiving the transmission of data from an upstream station (e.g., base station 110 or UE 120) and transmitting the transmission of that data to a downstream station (e.g., UE 120 or base station 110). The relay station may be a UE 120 capable of relaying the transmissions of other UEs 120. In the example shown in FIG. 1, BS110d (e.g., relay base station) can communicate with BS110a and UE120d to facilitate communication between BS110a (e.g., macro base station) and UE120d. A base station 110 that relays communication may be referred to as a relay station, relay base station, repeater, etc.

[0051]

[0093] Wireless network 100 can be a heterogeneous network including different types of base stations 110 such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmission power levels, different coverage areas, and / or different impacts on interference within wireless network 100. For example, a macro base station may have a high transmission power level (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmission power levels (e.g., 0.1 to 2 watts).

[0052]

[0094] Network controller 130 can be coupled to or communicate with a set of base stations 110 and can provide adjustment and control to these base stations 110. Network controller 130 can communicate with base stations 110 via a backhaul communication link. Base stations 110 can communicate with each other directly or indirectly via a wireless backhaul communication link or a wireline backhaul communication link.

[0053]

[0095] UE120 may be distributed throughout the wireless network 100, and each UE120 may be fixed or mobile. UE120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component, or a sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0054]

[0096] Some of the UEs 120 may be regarded as machine-type communication (MTC) UEs, or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with, for example, a base station, another device (such as a remote device), or some other entity. The wireless node may provide connectivity for a network (such as a wide area network like the Internet or a cellular network) or connectivity to the network via, for example, a wired communication link or a wireless communication link. Some of the UEs 120 may be regarded as Internet-of-Things (IoT) devices and / or may be implemented as narrowband IoT (NB-IoT) devices. Some of the UEs 120 may be regarded as customer premise equipment. The UEs 120 may be included inside a housing that houses components of the UEs 120, such as processor components and / or memory components. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (such as one or more processors) and the memory component (such as memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0055]

[0097] Generally, any number of wireless networks 100 can be deployed in a given geographic area. Each wireless network 100 can support a specific RAT and operate on one or more frequencies. The RAT can be referred to as a wireless technology, an air interface, etc. The frequency can be referred to as a carrier, a frequency channel, etc. To avoid interference between wireless networks of different RATs, each frequency can support a single RAT in a given geographic area. In some cases, an NR network or a 5G RAT network may be deployed.

[0056]

[0098] In some examples, two or more UEs 120 (shown, for example, as UEs 120a and 120e) can communicate directly using one or more sidelink channels (for example, without using the base station 110 as an intermediary to communicate with each other). For example, the UE 120 can use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which can include, for example, vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or a mesh network to communicate. In such examples, the UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by the base station 110.

[0057]

[0099] Devices in the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc. by frequency or wavelength. For example, devices in the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Note that although a portion of FR1 is higher than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band. Similar nomenclature issues can arise with FR2, which is often (interchangeably) referred to as the "millimeter wave" band, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) specified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

[0058]

[0100] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands included within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus, in effect, extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands are identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is included within the EHF band.

[0059]

[0101] With the above examples in mind, unless otherwise specified, terms such as "sub-6 GHz" when used in this specification may be broader in meaning to represent frequencies that may be less than 6 GHz, may be within FR1, or may include intermediate band frequencies. Further, unless otherwise specified, terms such as "millimeter wave" when used in this specification may be broader in meaning to represent frequencies that may include intermediate band frequencies, may be within FR2, FR4, FR4-a, or FR4-1, and / or FR5, or may be within the EHF band. The frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be subject to modification, and the techniques described in this specification are intended to be applicable to those modified frequency ranges.

[0060]

[0102] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere in this specification, the communication manager 140 may sleep in relation to a DRX cycle and wake up at the start of a subframe at least in part based on a specified time offset added to the on-duration of the DRX cycle at least in part based on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is at least in part based on the periodicity of multimedia data bursts, the number of DRX cycles is at least in part based on the specified time offset, and the communication manager 140 may receive multimedia data bursts during the subframes.

[0061]

[0103] In some aspects, communication manager 140 may sleep in relation to a DRX cycle and wake up at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the DRX time reference system frame number (SFN), where the specified time offset is based at least in part on the periodicity of the multimedia data burst, the number of DRX cycles is based at least in part on the specified time offset, and communication manager 140 may receive a multimedia data burst during the subframe.

[0062]

[0104] In some aspects, communication manager 140 may sleep in relation to a resource cycle and wake up at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, where the specified time offset is based at least in part on the periodicity of the multimedia data burst, the number of resource cycles is based at least in part on the specified time offset, and communication manager 140 may receive a multimedia data burst during the subframe. Additionally, alternatively, communication manager 140 may perform one or more other operations described herein.

[0063]

[0105] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere in this specification, the communication manager 150 prepares to communicate with a UE according to a DRX cycle, and based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, may transmit a data burst at the start in a subframe. The specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset.

[0064]

[0106] In some aspects, the communication manager 150 prepares to communicate with a UE according to a DRX cycle, and based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, may transmit a data burst at the start in a subframe. The specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset.

[0065]

[0107] In some aspects, the communication manager 150 prepares to communicate with a UE according to a resource cycle, and based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, may transmit a data burst at the start in a subframe. The specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of resource cycles is based at least in part on the specified time offset, and the number of resource cycles is based at least in part on the specified time offset. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0066]

[0108] As described above, FIG. 1 is provided as an example. Other examples may be different from those described with respect to FIG. 1.

[0067]

[0109] FIG. 2 is a diagram showing an example 200 of a base station 110 communicating with a UE 120 within a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a - 234t, and the UE 120 may be equipped with R antennas 252a - 252r, where generally T≥1 and R≥1.

[0068]

[0110] At base station 110, transmit processor 220 can receive data targeted at UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 can select one or more modulation and coding schemes (MCSs) for UE 120, at least partially based on one or more channel quality indicators (CQIs) received from UE 120. Base station 110 can process (e.g., encode and modulate) data for UE 120, at least partially based on the selected MCS(s) for UE 120, and can provide data symbols to UE 120. Transmit processor 220 can process system information and control information (e.g., CQI requests, grants, and / or upper layer signaling, e.g., regarding semi-static resource partitioning information (SRPI)), and can provide overhead symbols and control symbols. Transmit processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple input multiple output (MIMO) processor 230 can perform spatial processing (e.g., precoding), if applicable, on data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a - 232t. For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232.Each modem 232 may use individual modulator components to obtain an output sample stream and to process individual output symbol streams (e.g., for OFDM). Each modem 232 may further use individual modulator components to process (e.g., analog-convert, amplify, filter, and / or up-convert) the output sample stream to obtain a downlink signal. Modems 232a - 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) shown as antennas 234a - 234t.

[0069]

[0111] In UE120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from base station 110 and / or other base stations 110, and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) shown as modems 254a to 254r. For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use individual demodulator components to adjust (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain input samples. Each modem 254 can use demodulator components to further process the input samples to obtain received symbols (e.g., for OFDM). The MIMO detector 256 can obtain received symbols from the modems 254, perform MIMO detection on the received symbols when applicable, and provide the detected symbols. The receiving processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE120 to the data sink 260, and provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine, among other examples, the reference signal received power (RSRP) parameter, the received signal strength indicator (RSSI) parameter, the reference signal received quality (RSRQ) parameter, and / or the CQI parameter. In some examples, one or more components of UE120 can be included within the housing 284.

[0070]

[0112] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices within a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0071]

[0113] One or more antennas (e.g., antennas 234a - 234t and / or antennas 252a - 252r) may include, among other examples, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, or may be included therein. The antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements, a set of coplanar antenna elements, a set of non - coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmission components and / or reception components such as one or more components of FIG. 2, within a single housing or multiple housings.

[0072]

[0114] On the uplink, at UE 120, transmission processor 264 can receive and process data from data source 262 and control information (such as for reporting including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmission processor 264 can generate reference symbols for one or more reference signals. Symbols from transmission processor 264 can be precoded by TX MIMO processor 266 when applicable and further processed by modem 254 (such as for DFT-s-OFDM or CP-OFDM) and transmitted to base station 110. In some examples, modem 254 of UE 120 can include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver can include any combination of antenna(s) 252, modem(s) 254, MIMO detector 256, receive processor 258, transmission processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (such as controller / processor 280) and memory 282 to perform any aspect of the methods described herein (see, e.g., FIGS. 3 - 31).

[0073]

[0115] At base station 110, uplink signals from UE 120 and / or other UEs are received by antenna 234, processed by modem 232 (e.g., the demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 when applicable, and may be further processed by receive processor 238 to obtain the decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 for scheduling one or more UEs 120 for downlink communication and / or uplink communication. In some examples, modem 232 of base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform any aspect of the methods described herein (e.g., see FIGS. 3-31).

[0074]

[0116] As will be described in more detail elsewhere in this specification, the controller / processor 240 of a network entity (e.g., base station 110), the controller / processor 280 of UE 120, and / or any other component(s) of FIG. 2 may perform one or more techniques associated with a method for DRX, such as setting a hyperframe length for DRX. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component(s) of FIG. 2 may execute or instruct the operation of, for example, process 2000 of FIG. 20, process 2100 of FIG. 21, process 2200 of FIG. 22, process 2300 of FIG. 23, process 2400 of FIG. 24, process 2500 of FIG. 25, and / or other processes described herein. Memory 242 and memory 282 may store data and program code for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when the one or more instructions are executed by one or more processors of base station 110 and / or UE 120 (e.g., directly or after being compiled, converted, and / or interpreted), the one or more processors, UE 120, and / or base station 110 may execute or instruct the operation of, for example, process 2000 of FIG. 20, process 2100 of FIG. 21, process 2200 of FIG. 22, process 2300 of FIG. 23, process 2400 of FIG. 24, process 2500 of FIG. 25, and / or other processes as described herein. In some embodiments, executing the instructions may include, among other examples, running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions.

[0075]

[0117] In some aspects, a UE (e.g., UE 120) includes means for sleeping in relation to a DRX cycle, means for waking up at the start in a subframe based at least in part on a specified time offset added to the on - duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is based at least in part on the periodicity of a multimedia data burst and the number of DRX cycles is based at least in part on the specified time offset, and / or means for receiving a multimedia data burst between subframes. The means for causing the UE to perform the operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0076]

[0118] In some aspects, a UE includes means for sleeping in relation to a DRX cycle, means for waking up at the start in a subframe based at least in part on a specified time offset added to the on - duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the DRX time reference system frame number (SFN), where the specified time offset is based at least in part on the periodicity of a multimedia data burst and the number of DRX cycles is based at least in part on the specified time offset, and / or means for receiving a multimedia data burst between subframes.

[0077]

[0119] In some aspects, the UE has means for sleeping in relation to a resource cycle, means for waking up at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, where the specified time offset is based at least in part on the periodicity of a multimedia data burst and the number of resource cycles is based at least in part on the specified time offset, and / or means for receiving a multimedia data burst between subframes.

[0078]

[0120] In some aspects, a network entity (e.g., base station 110) has means for preparing to communicate with the UE according to a DRX cycle and / or means for transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is based at least in part on the periodicity of a multimedia data burst and the number of DRX cycles is based at least in part on the specified time offset. In some aspects, the means for causing the network entity to perform the operations described herein may include, for example, one or more of communication manager 150, transmission processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, reception processor 238, controller / processor 240, memory 242, or scheduler 246.

[0079]

[0121] In some aspects, the network entity includes means for preparing to communicate with the UE according to a DRX cycle, and / or means for transmitting a data burst at the start in a subframe, based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle and at least in part on a specified time offset added to the on-duration of the DRX cycle, the specified time offset being based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles being based at least in part on the specified time offset.

[0080]

[0122] In some aspects, the network entity includes means for preparing to communicate with the UE according to a resource cycle, and / or means for transmitting a data burst at the start in a subframe, based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle and at least in part on a specified time offset added to an instance of the resource cycle, the specified time offset being based at least in part on the periodicity of the multimedia data burst, the number of resource cycles being based at least in part on the specified time offset, and the number of resource cycles being based at least in part on the specified time offset.

[0081]

[0123] Although the blocks in FIG. 2 are shown as separate components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be executed by or under the control of the controller / processor 280.

[0082]

[0124] Although the blocks in FIG. 2 are shown as separate components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to the transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be implemented by or under the control of the controller / processor 280.

[0083]

[0125] As described above, FIG. 2 is provided as an example. Other examples may be different from those described with respect to FIG. 2.

[0084]

[0126] FIG. 3 is a diagram showing an example 300 of a device designed for low-latency applications according to the present disclosure.

[0085]

[0127] Some devices, including devices for XR, may require low-latency traffic between an edge server or cloud environment. Example 300 shows communication between an XR device and an edge server or cloud environment via a base station (e.g., gNB). The XR device may be an augmented reality (AR) glass device, a virtual reality (VR) glass device, or other gaming device. The XR device is expected to have the battery life of a smartphone (e.g., full-day use), but the battery capacity may be limited. Even when the XR device is connected to a smartphone and uses the same smartphone battery, battery power becomes an issue. The power consumption of the XR device may be limited, resulting in an unpleasant user experience and / or a shortened battery life.

[0086]

[0128] As described above, FIG. 3 is provided as an example. Other examples may be different from those described with respect to FIG. 3.

[0087]

[0129] FIG. 4 is a diagram showing an example 400 of low-latency traffic and power state according to the present disclosure.

[0088]

[0130] Power loss can be reduced by limiting the amount of time that the processing resources of the XR device are active with respect to computation and power consumption. Some wireless communication systems may support UEs such as XR devices that operate in DRX mode. A UE in DRX mode can transition between sleep and wake-up. Going to sleep can include entering a DRX-inactive state (e.g., sleep state, power-saving mode) for power saving, or being in a DRX-inactive state. Waking up can include entering a DRX-active state (e.g., active time) from a DRX-inactive state for data transmission and reception. The active state for data transmission and reception may be referred to as the DRX "on-duration". A DRX cycle can be a duration that includes a sleep state and an active on-duration state for the UE. A DRX cycle can start at the start of an on-duration and end at the start of the next on-duration. Each different DRX cycle can have a different length (e.g., 8 milliseconds (ms), 16 ms). UEs using different DRX cycles can have non-uniform cycle durations within a DRX time period that is a larger duration including multiple DRX cycles. Such non-uniform cycle durations can result in a DRX on-duration that is aligned with the periodicity of downlink traffic to the UE. In some cases, the DRX time period can correspond to an anchor cycle across a set of DRX cycles, and a subset of the set of DRX cycles can have a different cycle duration from other DRX cycles in the set of DRX cycles. In some cases, an on-duration offset value can be indicated for one or more DRX cycles within a DRX time period (e.g., via downlink control information (DCI) or MAC CE).

[0089]

[0131] By offloading some calculations to the edge server, the XR device can conserve processing resources. Example 400 shows a scenario where the XR device can split the calculations of an application with an edge server on the other side of the base station. The edge server can render video frames such as intra-coded (I) frames and predicted (P) frames, encode the video frames, align the video frames with user pose information, and perform other related calculations. However, this means that there can be more traffic between the XR device and the edge server, which will cause the XR device to consume more power and signaling resources. XR downlink traffic (e.g., video frames) can have a periodic pattern corresponding to the frame rate of the transmitted video data (e.g., H.264 / H.265 encoded video). Such downlink traffic may be quasi-periodic with data bursts for each frame at 1 frame per second (1 / fps), or may have "eye buffers" shifted by two cases per frame at 1 / (2 * fps). For example, XR downlink traffic can include 100+ kilobytes (KB) of data every 45, 60, 75, or 90 frames per second (e.g., every 11 ms, 13 ms, 16 ms, or 22 ms). XR uplink traffic can include controller information for the game, information for VR split rendering, and / or user pose information. XR uplink traffic can include 100 bytes every 2 ms (500 Hz). The XR device can reduce this periodicity to align XR uplink traffic with XR downlink traffic.

[0090]

[0132] For low-latency applications, the DRX cycle and the start offset of the DRX cycle should be time-aligned with the arrival of downlink traffic. For example, an XR device can provide services to a user, enter a short sleep state in the DRX cycle, and do the above between video frames. The XR device and the edge server can attempt to align the uplink DRX cycle and the downlink DRX cycle as part of connected DRX (CDRX). However, there are DRX multimedia timing mismatches that prevent such alignment and the successful use of CDRX. For example, the update rate can be, for example, 120 Hz or 60 Hz, and thus result in downlink traffic burst arrival periodicities of 8.333 ms or 16.667 ms, respectively. However, conventional DRX configurations can have 1 millisecond as the finest granularity for the DRX cycle, and the start of the on-duration can be aligned with the millisecond time boundary. These partial millisecond differences can, in combination with each instance of the cycle, cause a misalignment between the DRX cycle and the XR traffic periodicity. For example, the XR traffic cycle can drift to the middle of the DRX cycle. This causes an increase in latency and power consumption.

[0091]

[0133] As described above, FIG. 4 is provided as an example. Other examples may be different from those described with respect to FIG. 4.

[0092]

[0134] FIG. 5 shows an example 500 of a misalignment between a DRX cycle and XR traffic periodicity according to the present disclosure. Example 500 shows a downlink traffic burst arrival 505 that can include several downlink traffic bursts 510 transmitted according to a periodic pattern. Example 500 also shows a first conventional DRX configuration 515 and a second conventional DRX configuration 520.

[0093]

[0135] The downlink traffic burst 510 may include XR downlink traffic having a periodic pattern corresponding to, for example, the frame rate of transmitted data (e.g., H.264 / H.265 encoded video). The update rate may be, for example, 120 Hz or 60 Hz, and thus, result in downlink traffic burst arrival periodicities of 8.333 ms or 16.667 ms, respectively. However, the first conventional DRX configuration 515 and the second conventional DRX configuration 520 may have 1 millisecond as the finest granularity for the DRX cycle, and the start of the on-duration may be aligned with the millisecond time boundary.

[0094]

[0136] In the example of FIG. 5, a 120 Hz update rate is shown for the burst arrival 505, and thus, an 8.333 ms periodicity for the downlink traffic burst 510 is resulted. If the first conventional DRX configuration 515 is selected and the initial DRX cycle has an on-duration aligned with the first downlink traffic burst 510-a, the second downlink traffic burst 510-b and the third downlink traffic burst 510-a are also each within the subsequent two on-durations. However, the fourth downlink burst 510-d will occur 0.333 seconds after the end of the fourth on-duration, and thus, will miss the fourth on-duration. If the second conventional DRX configuration 520 is selected instead, the result is that the first downlink traffic burst 510-a will be aligned with the on-duration, but the subsequent downlink traffic bursts 510-b, 510-c, and 510-d will each miss the on-duration.

[0095]

[0137] Furthermore, when the DRX configuration is modified to have the finest granularity corresponding to a slot or a symbol, such inconsistencies may continue to occur due to the periodicity of the burst arrival 505 not being a multiple of the slot or symbol duration. For example, the traffic burst interval (120 Hz or 60 Hz) expressed in milliseconds has a coefficient of 3 in the denominator, so the numerator cannot be divided by the denominator (i.e., 1000 / 120 = X / 3, where X is an integer such as 25 for a 120 Hz update rate or 50 for a 60 Hz update rate). More generally, when the DRX cycle granularity can be defined in slot units, the expression is the number of slots in one second divided by the source update rate in Hz. The inconsistency between the downlink traffic burst 510 and the on-duration can add additional latency to the communication, and the additional latency is periodic. For example, in the first missed on-duration of an 8 ms DRX configuration, the downlink traffic burst can be resent in the next on-duration that occurs 7 ms later than the missed on-duration. Subsequent downlink traffic bursts will have lower latency, reducing each cycle by 0.333 ms until the downlink traffic burst is aligned again with the on-duration in the 21st cycle. Such alignment lasts for 3 cycles. Therefore, the alignment and misalignment of the downlink traffic burst in such an example are periodic, with a period of 24 cycles and an average latency of about 3 ms. In some cases, to reduce latency, the DRX cycle duration may be shortened, in which case, due to the extra on-duration, there will be an increase in the corresponding power consumption. As a result, the XR device may consume additional processing resources.

[0096]

[0138] As described above, FIG. 5 is provided as an example. Other examples may be different from those described with respect to FIG. 5.

[0097]

[0139] FIG. 6 shows an example 600 of an anchor cycle including a leap DRX cycle according to the present disclosure.

[0098]

[0140] In some scenarios, the UE (e.g., an XR device) and the network may use an anchor cycle that includes a leap DRX cycle to better align DRX cycles in order to reduce latency and save energy consumption. For example, the UE and the network may implement an anchor cycle that includes a leap DRX cycle. The anchor cycle may include a cycle that includes multiple DRX cycles, and one of the DRX cycles is a DRX leap cycle. The DRX leap cycle may occur every specified number of DRC cycles. The DRX leap cycle may be a DRX cycle that adjusts the timing of the on-duration of the DRX cycle (e.g., by using an additional DRX offset to align the on-duration with multimedia periodicity). The downlink traffic burst arrival 605 may include several downlink traffic bursts 610 transmitted according to a periodic pattern. The downlink traffic bursts 610 may include, for example, XR downlink traffic having a periodic pattern with a downlink traffic burst 610 every 8.333 ms. The anchor cycle 620 may span, for example, three DRX cycles 615, and the third DRX cycle may be a leap cycle 625 having a longer cycle duration than the first two DRX cycles. In some cases, the anchor cycle 620, which may be an example of a DRX time period, may span more or fewer DRX cycles and may include one or more leap cycles 625. The anchor cycle 620 may be used as a basis for determining the timing for radio resource management (RRM) functions. In some cases, the leap cycle 625 may include one or more additional slots relative to the other DRX cycles of the anchor cycle 620. The position of the leap cycle(s) 625 can be varied within the anchor cycle 620.Example 600 shows burst arrivals 605 associated with periodic traffic having a 120 Hz update rate, and anchor cycle 620 includes three DRX cycles having durations of 8 ms, 8 ms, and 9 ms, although other configurations may be used for each of the downlink traffic due to different periodicities or patterns. For example, for periodic traffic having a 60 Hz update rate, an anchor cycle having three DRX cycles of 16 ms, 17 ms, 17 ms may be configured, or the three DRX cycles may each have a duration of 16 ms, 16 ms, 18 ms. The order of the leap cycle(s) 625 among the DRX cycles within anchor cycle 620 may also be configured. For example, for a 120 Hz update rate, DRX cycles having durations of (8 ms, 8 ms, 9 ms), (8 ms, 9 ms, 8 ms), or (9 ms, 8 ms, 8 ms) may be configured. Support for such diverse options in ordering may help to time-offset multiple users with respect to their respective on durations in order to better disperse resource utilization over time.

[0099]

[0141] In some cases, the base station may configure the UE using DRX configuration via radio resource control (RRC) signaling. For example, the base station may identify that periodic traffic is being sent to the UE (e.g., based on XR application traffic having a certain update rate or based on historical downlink burst transmissions to the UE) and that the periodic traffic does not align with slot boundaries or subframe boundaries. The base station may determine the anchor cycle duration (e.g., based on the number of cycles of downlink traffic bursts 610 corresponding to millisecond time boundaries such as three 8.333 ms cycles giving an anchor cycle duration of 25 ms), the number of DRX cycles within the anchor cycle 620, and which of the DRX cycles should have different cycle durations. In some cases, the RRC signaling may indicate the anchor cycle duration in milliseconds, the number of DRX cycles in the anchor cycle, and the cycle duration of each DRX cycle (e.g., 8, 8, 9). In some cases, the UE may notify the base station that the UE has the ability to perform a DRX procedure using non-uniform DRX cycles, and the base station may enable that ability when providing the DRX configuration. In other cases, non-uniform DRX cycles may be configured using other techniques, such as by adjusting the start offset of the on-duration of the DRX cycle, as described in connection with FIG. 7.

[0100]

[0142] As described above, FIG. 6 is provided as an example. Other examples may be different from those described with respect to FIG. 6.

[0101]

[0143] FIG. 7 shows an example 700 of a DRX configuration with dynamic offset adjustment that supports DRX techniques using non-uniform cycle durations, according to the present disclosure. Example 700 shows a downlink traffic burst arrival 705 that includes several downlink traffic bursts 710 transmitted according to a periodic pattern. Example 700 also shows a DRX configuration 715 using non-uniform cycle durations.

[0102]

[0144] Downlink traffic burst 710 may include XR downlink traffic having a periodic pattern with a downlink traffic burst 710, for example, every 8.333 ms. In Example 700, the DRX configuration 715 has a configuration where the DRX cycle duration is 8 ms and the on-duration is 1 ms. In the initial DRX cycle of the downlink traffic burst 710, the on-duration may have a 0 millisecond offset so that the first downlink traffic burst 710-a, the second downlink traffic burst 710-b, and the third downlink traffic burst 710-c are aligned with the on-duration. The UE may apply an adjustment 720 to the DRX on-duration start offset following the third downlink burst 710-c, which may increase the on-duration start offset by 1 millisecond in this example, such that the adjusted DRX on-duration is aligned with the fourth downlink traffic burst 710-d. The UE may apply another adjustment to return the on-duration offset following the fourth downlink traffic burst 710-d to the original offset, and thus the DRX cycle may be configured to align the on-duration with the downlink traffic burst 710.

[0103]

[0145] In some cases, the DRX on-duration start offset adjustment may be predefined based on the specification or defined in the DRX configuration (e.g., given in RRC signaling). For example, different types of traffic (e.g., XR traffic) and different periodic DRX start offsets (e.g., based on a 120 Hz or 60 Hz update rate) may be defined according to the pattern in Example 700 etc. (e.g., a 1 ms start offset is added every 4 DRX cycles). In some cases, the DRX start offset may be dynamically indicated during the previous downlink transmission (e.g., based on MAC CE or DCI).

[0104]

[0146] As described above, FIG. 7 is provided as an example. Other examples may differ from those described with respect to FIG. 7.

[0105]

[0147] FIG. 8 is a diagram showing Example 800 that uses a short cadence value for DRX according to the present disclosure. Example 800 shows a traffic burst arrival 810 arriving at a rate of 120 Hz.

[0106]

[0148] The techniques described in connection with FIGS. 3-7 can improve the alignment between the DRX cycle and the XR traffic to reduce the mismatch between burst traffic and the DRX on-duration. However, according to various aspects described herein, the UE (e.g., an XR device) and the network can further improve such alignment by using a DRX short cadence that corresponds to a number of Hz (e.g., instances per second) rather than an integer ms value. The DRX short cadence value can correspond to a number of Hz, for example, by being defined by a number of Hz, or by a value based on or derived from a number of Hz or a similar or related unit. The DRX short cadence (drx-ShortCadence) can be, for example, 45 Hz, 60 Hz, 90 Hz, or 120 Hz so as to align the on-duration of the UE with the traffic bursts received by the UE according to the video frame rate. That is, the DRX short cadence value can be a DRX timing value that corresponds to the same time unit or frequency unit (e.g., video frame rate) in which the traffic bursts are received by the UE. This is in contrast to a normal DRX cycle that is the length (duration) of the DRX cycle and has a DRX long cycle with a unit granularity of milliseconds. The base station (e.g., gNB) can set the DRX short cadence value when it obtains the frame rate of the traffic bursts to the UE or the periodicity of the traffic bursts to the UE. The UE can receive the DRX short cadence value from the base station or obtain the DRX short cadence value based at least in part on the frame rate or periodicity of the traffic.

[0107]

[0149] The UE uses the DRX short cadence value to determine when to wake up during the on-duration and can decode the physical downlink control channel (PDCCH) grant from the base station as part of the DRX short cadence cycle 820. The UE can determine when to wake up for each subframe or for each slot. For example, as indicated by reference numeral 830, the UE can calculate whether a specific criterion is met for the current subframe in the first part of the current subframe (having the subframe identifier n). The criterion may be associated with the DRX short cadence value and the subframe identifier, and the subframe (or slot) that meets the condition may be designed to match the timing or periodicity of the frame rate of the traffic burst received by the UE. Each subframe is 1 ms and may include a plurality of slots (e.g., 2, 6, 8). The criterion may be associated with the system frame number (SFN). For a subframe having a subframe identifier n = [(SFN * 10)+subframe number], the UE may wake up if the first ceiling value of (n * drx-ShortCadence / 1000)+1 (the smallest integer greater than the calculated value) is equal to the second ceiling value of ((n + 1) * (drx-ShortCadence / 1000)). The SFN may be a number between 0 and 1023 of the frame, and the subframe number may be a number between 0 and 9 within the frame. For example, if the DRX cadence value is 120 Hz and the subframe has a subframe number of 5 in a frame where the SFN is 800, the subframe identifier n for the subframe may be (800 * 10)+5, i.e., 8005. The first ceiling value may be the smallest integer of (8005 * 120 / 1000)+1, i.e., 961. The second ceiling value may be (8005 + 1) *The smallest integer of (120 / 1000), i.e., 960, may also be used. The first sealing value and the second sealing value are not equal, and thus the UE does not meet the criteria and does not wake up for this subframe. However, the subframe after the subframe number is 8 has a first sealing value of 961 (the smallest integer of (8008 * 120 / 1000)+1) and a second sealing value of 961 ((8008 + 1) * (the smallest integer of 120 / 1000)), and thus the UE meets the criteria and may wake up during that subframe. The calculation may be performed at the start of each subframe. In some embodiments, multiple calculations for multiple subframes may be performed at once.

[0108]

[0150] In other words, the UE may meet some type of criteria associated with the DRX short cadence (corresponding to Hz) and the subframe identifier of the subframe that uniquely identifies the subframe among consecutive subframes within a cycle or time period. The criteria may be designed to wake up for a subframe according to the frame rate or periodicity of the traffic burst received by the UE using the DRX short cadence, or anything calculated for a given subframe.

[0109]

[0151] As indicated by reference numeral 835, the UE may wake up during the on-duration in the current subframe. When the UE wakes up, the UE may start a DRX on-duration timer (drx-onDurationTimer). The DRX on-duration timer may be the minimum duration for which the UE should remain awake, for example, it may be 1 ms or 2 ms. For example, if the UE wakes up in subframe 8 and the DRX on-duration timer is 2 ms, the UE may remain awake through subframes 8 and 9. If there is no more traffic, the UE may return to sleep. In Example 800, the DRX on-duration timer is 1 ms. The DRX on-duration timer may be started for a DRX group.

[0110]

[0152] In some aspects, similar to the leap cycle technique described with respect to FIG. 6, there may be a leap of one subframe every specified number of cycles. For example, for an 8 ms cycle, when the duty cycle is 8.333 ms for 120 Hz, there may be a leap of one subframe (1 ms) every 3 cycles to adapt to the 1 / 3 subframe portion. That is, for a 120 Hz DRX short cadence, the UE may determine to wake up between subframes n = 8, 16, 25, 33, 41, 50, etc. As indicated by reference numeral 840, after waking up in subframes 8 and 16, the UE may leap one subframe to wake up in subframe 25 instead of subframe 24. If Example 800 continues to show the on-duration subframes, the UE may then wake up in subframe 33 after 8 ms and wake up in subframe 41 after another 8 ms. Instead of waking up in subframe 49 after 8 ms, the UE may leap one subframe and wake up in subframe 50. In some aspects, the UE may skip calculations for one or more subframes after the on-duration until the next possible on-duration approaches.

[0111]

[0153] In some aspects, the UE may use the DRX start offset and / or the DRX slot offset to provide additional granularity as to when to wake up within a subframe to more closely align with the traffic periodicity of the UE. The UE may wake up after the DRX start offset (drx-StartOffset) (n + drx-StartOffset) and / or after the DRX slot offset (drx-SlotOffset) from the start of the subframe to start the DRX on-duration timer. The DRX start offset may be in number of milliseconds or microseconds (μs) (or set to 0 ms or μs if there is no DRX start offset), symbols, or mini-slots. The DRX start offset may be used to temporally shift multiple UEs. The DRX slot offset may be in number of slots. For example, if there are 8 slots in a subframe (such as in the case of mmWave), each slot is 125 μs or 0.125 ms. If the DRX slot offset is 2 slots, the wake-up time is shifted by (2 * 0.125), i.e., 0.250 ms. If the wake-up times at 120 Hz are 8 ms, 16 ms, 25 ms, 33 ms, 41 ms, 50 ms, etc., the UE may use a DRX slot offset of 2 slots for a target of 8.250 ms in subframe 8, a DRX slot offset of 5 slots for a target of 16.625 ms in subframe 16, and no DRX slot offset for a target of 25.000 ms in subframe 25, etc., using the DRX slot offset to better match traffic bursts at 8.33 ms, 16.66 ms, and 25 ms. As a result, the UE may better align the DRX cycle with the traffic period to further reduce latency and conserve signaling resources.

[0112]

[0154] As described above, FIG. 8 is provided as an example. Other examples may differ from those described with respect to FIG. 8.

[0113]

[0155] FIG. 9 is a diagram showing Example 900 that uses a short cadence value for DRX for slot positions according to the present disclosure. Example 900 shows traffic burst 905 among a plurality of burst arrivals 910 that arrive at a rate of 120 Hz. The burst arrivals 910 in Example 900 may be the same as the burst arrivals 810 shown in Example 800 of FIG. 8, except that the time line in Example 900 is expanded to show a plurality of slots for a subframe.

[0114]

[0156] In some aspects, the per-subframe calculation based on the subframe identifier can be extended to the slot position using the slot identifier k. That is, the criterion for wake-up is that the slot identifier k is at least partially based on being equal to (((SFN * 10) + subframe number) * slots per second) + slot number. The UE has a first ceiling value of (k * drx-ShortCadence / 1000 * slots per second) + 1, which is ((k + 1) * (drx-ShortCadence / 1000 *When equal to a second sealing value of the per-second slot)), it is possible to wake up in slot k and start a DRX on-duration timer. The calculation may be per slot instead of per subframe. As indicated by reference numeral 920, the UE may determine whether the calculation for the current slot meets the criteria for wake-up, based at least in part on the DRX short cadence and the slot identifier. As indicated by reference numeral 925, when the UE wakes up, the UE may wake up for a duration 930 that may be a subframe or 8 slots. In some aspects, the calculation may be performed all at once at the start of the subframe. In other words, the UE may meet some criteria associated with the DRX short cadence value (corresponding to Hz) and the slot identifier of the slot that uniquely identifies the slot among consecutive slots within a cycle or time period. The criteria may be anything calculated for a given slot and may be designed to wake up for slots according to the frame rate or periodicity of traffic bursts to the UE, using the DRX short cadence value. In some aspects, the UE may skip the calculation for one or more slots or subframes after the on-duration.

[0115]

[0157] In some aspects, the UE may wake up (n + drx-StartOffset) after the DRX start slot offset (drx-StartSlotOffset) from the start of the subframe and start a DRX on-duration timer. The DRX start slot offset may be in number of ms, microseconds (μs) (or set to 0 ms or μs if there is no DRX start offset), symbols, slots, or minislots. The DRX start slot offset may be used to temporally shift the UE from other UEs. The DRX start slot offset may be updated based at least in part on how many UEs are transmitting, how long the UE stays, and whether there are changes in UE behavior.

[0116]

[0158] As described above, FIG. 9 is provided as an example. Other examples may be different from those described with respect to FIG. 9.

[0117]

[0159] FIG. 10 is a diagram showing Example 1000 that uses a short cadence value for DRX according to the present disclosure. As shown in FIG. 10, a base station 1010 (e.g., base station 110) may communicate with a UE 1020 (e.g., UE 120). The base station 1010 and the UE 1020 may be part of a wireless network (e.g., wireless network 100).

[0118]

[0160] The UE 1020 may obtain a DRX short cadence value that can be defined as a number of Hz. As indicated by reference numeral 1025, the base station 1010 may transmit the DRX short cadence value to the UE 120. The UE 1020 may also obtain the DRX short cadence value from stored configuration information. For example, the UE 1020 may select a DRX short cadence value from among a plurality of DRX short cadence values based at least in part on the determined periodicity (e.g., video frame rate) of a traffic burst transmitted by the base station 1010, as indicated by reference numeral 1030.

[0119]

[0161] As indicated by reference numeral 1035, the UE 1020 may sleep and wake up according to the DRX short cadence value. For example, for each subframe, the UE 1020 may calculate whether the subframe identifier satisfies a criterion for wakeup for the UE 1020 based at least in part on the DRX short cadence value. The DRX short cadence value (drx-ShortCadence) may be, for example, 120 Hz, and the subframe identifier n = [(SFN * 10)+ subframe number] may be used. When the subframe identifier n = 7, ceil(n * drx-ShortCadence / 1000)+1 = 2, and ceil((n + 1) *drx-ShortCadence / 1000)=1. Since 2 is not equal to 1, the criterion is not met (the condition is false). When the subframe identifier n = 8, ceil(n * drx-ShortCadence / 1000)+1 = 2, and ceil((n + 1) * drx-ShortCadence / 1000)=2. Since 2 is equal to 2, the criterion is met (the condition is true). When the subframe identifier n = 9, ceil(n * drx-ShortCadence / 1000)+1 = 3, and ceil((n + 1) * drx-ShortCadence / 1000)=2. Since 3 is not equal to 2, the criterion is not met (the condition is false). In some aspects, UE1020 may use a leap cycle, a slot offset, a timing offset, or any other technique described herein to better match the periodicity of traffic bursts. UE1020 may start an on-duration timer as part of waking up.

[0120]

[0162] In some aspects, UE1020 may perform a calculation for each slot to determine whether the slot identifier causes UE1020 to meet the criterion for waking up, based at least in part on the DRX short cadence value. The DRX short cadence value (drx-ShortCadence) may be, for example, 120 Hz, and the slot identifier k = [((SFN * 10 + subframe number) * slots per second)+slot number]. The number of slots per second (slotPerSec) for 120 Hz may be 8 slots per second. When the slot identifier k = 8 * 8 + 1, ceil(k * drx-ShortCadence / (1000 * slotPerSec))+1 = 2, and ceil((k + 1) * drx-ShortCadence / (1000 *(slotPerSec)) = 1. Since 2 is not equal to 1, the criterion is not met (the condition is false). Slot identifier k = 8 * When it is 8 + 2, ceil(k * drx - ShortCadence / (1000 * slotPerSec)) + 1 = 2, and ceil((k + 1) * drx - ShortCadence / (1000 * slotPerSec)) = 2. Since 2 is equal to 2, the criterion is met (the condition is true). Slot identifier k = 8 * When it is 8 + 3, ceil(k * drx - ShortCadence / (1000 * slotPerSec)) + 1 = 3, and ceil((k + 1) * drx - ShortCadence / (1000 * slotPerSec)) = 2. Since 3 is not equal to 2, the criterion is not met (the condition is false). In some aspects, UE1020 may use a leap cycle, a slot offset, a timing offset, or any other technique described herein to better match the periodicity of the traffic burst.

[0121]

[0163] As described above, FIG. 10 is provided as an example. Other examples may be different from those described with respect to FIG. 10.

[0122]

[0164] FIG. 11 is a diagram showing Example 1100 using different short cadence values according to the present disclosure. FIG. 11 shows a table for different DRX short cadence values, including for 48 Hz, 60 Hz, 80 Hz, and 90 Hz, which correspond to the corresponding frame rates of 48 Hz, 60 Hz, 80 Hz, and 90 Hz. Similar to the table for 120 Hz in FIG. 8, the first column in each table in FIG. 11 shows the periodicity of the traffic burst (corresponding to the ms-frame rate / short cadence value between traffic bursts). The second column in each table shows the wake-up time (in ms) when the criterion is met for the short cadence value so as to match the periodicity in the first column. The third column shows the wake-up time (in ms) when using a slot offset (e.g., in increments of 0.125 ms) to more closely match the periodicity shown in the first column.

[0123]

[0165] In other words, the UE may calculate whether a subframe (or slot) meets the criterion for wake-up based at least in part on the subframe identifier of the subframe (or the slot identifier of the slot) and the DRX short cadence value of 48 Hz, 60 Hz, 80 Hz, 90 Hz, or 120 Hz. The criterion may be designed such that the UE wakes up at the start in the subframe and / or slot that most closely matches or aligns with that traffic burst according to the periodicity of the traffic burst. The UE may use a slot offset to more closely match the periodicity. In this way, while the UE more closely matches the wake-up time with the traffic burst to save power and processing resources, it does not miss any traffic burst during the on-duration. The UE may adjust the on-duration as needed in cooperation with the short cadence value and / or the slot offset value. Note that other DRX short cadence values may be used to match other frame rates such as 45 Hz, 75 Hz frame rates, or other frame rates for applications or services not explicitly enumerated herein.

[0124]

[0166] As described above, FIG. 11 is provided as an example. Other examples may be different from those described with respect to FIG. 11.

[0125]

[0167] FIG. 12 is a diagram showing Example 1200 using a short cadence value for DRX according to the present disclosure. Example 1200 shows the arrival of traffic bursts arriving at a rate of 120 Hz.

[0126]

[0168] There are additional solutions for better matching of multimedia cadence as part of enhanced connected mode DRX (EC-DRX or eCDRX). In one scenario, the base station may detect that the offset between on-duration occasions needs to be changed in order to better match the arrival time of the next data burst. In some aspects, the base station may send a MAC CE to the UE to notify of a change in the offset between on-duration occasions. For example, the MAC CE may indicate that the next offset should be increased by 1 ms or shifted from 8 ms to 9 ms. The MAC CE may indicate an offset value from a list of absolute values or the amount of slots to shift the offset (from a list of relative values).

[0127]

[0169] As described above, FIG. 12 is provided as an example. Other examples may be different from those described with respect to FIG. 12.

[0128]

[0170] FIG. 13 is a diagram showing Example 1300 using a short cadence value for DRX according to the present disclosure. Example 1300 shows the arrival of traffic bursts arriving at a rate of 120 Hz.

[0129]

[0171] DRX may be associated with a DRX short cycle. When the DRX short cycle is used for a DRX group and [(SFN × 10) + subframe number] = (drx-ShortCycle) modulo (drx-ShortCycle), the UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe. [(SFN × 10) + subframe number] may define the subframe index for the DRX cycle. The parameter drx-ShortCycle may define the subframe periodicity of the on-duration cycle, and the parameter drx-StartOffset may define the subframe offset of the on-duration cycle.

[0130]

[0172] DRX may be associated with a DRX long cycle. When the DRX long cycle is used for a DRX group and [(SFN × 10) + subframe number] = drx-StartOffset modulo (drx-LongCycle), the UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

[0131]

[0173] In some aspects, the two-level DRX configuration may define an outer DRX cycle and an inner DRX cycle to construct a leap DRX cycle. The outer DRX may be the same as a legacy DRX that supports only uniform DRX. The inner DRX may support subcycles that may be non-uniform. The start of the first inner DRX cycle may be aligned with the start of the outer DRX, and the end of the last inner DRX cycle may be aligned with the end of the outer DRX. The on-duration, inactivity timer, and other DRX parameters for the configuration of the inner DRX cycle may be the same as those of the outer DRX cycle. If the outer DRX cycle is configured to be 25 ms as an "anchor cycle" that depends on the DRX subframe index of [(SFN×10) + subframe number], the inner DRX cycle may be configured to be (8, 8, 9) ms for a set of subcycles with respect to the on-duration.

[0132]

[0174] In some aspects, the start of the on-duration may be defined for the short DRX cycle and the long DRX cycle. The short DRX cycle may be defined as [(SFN×10) + subframe number] = (drx-StartOffset) modulo (drx-ShortCycle). The long DRX cycle may be defined as [(SFN×10) + subframe number] = drx-StartOffset modulo (drx-LongCycle).

[0133]

[0175] As described above, FIG. 13 is provided as an example. Other examples may be different from those described with respect to FIG. 13.

[0134]

[0176] FIG. 14 is a diagram showing an example 1400 of SFN wraparound according to the present disclosure. Example 1400 shows the arrival of a multimedia data burst arriving at a rate of 120 Hz. In example 1400, drx-StartOffset is set to 0.

[0135]

[0177] The UE may configure a DRX cycle for the cadence of data bursts, such as every 8.33 ms at 120 Hz, but the cadence of data bursts may be associated with a periodicity of 1000 ms. When the multimedia periodicity is 1000 ms and the DRX cycle is 10240 ms (1024 SFNs per hyperframe every 10 ms), the DRX hyperframe may fall out of alignment with the multimedia server's frame every 10.24 seconds. Due to the misalignment between the hyperframe periodicity (10240 ms) and the multimedia periodicity, there is a drift 1404 of 1.666 ms (2 ms in Example 1400) every 10.24 seconds (10240 ms). In other words, the hyperframe periodicity (10240 ms) cannot be divided by the multimedia periodicity (Hz, fps). In the example of 120 Hz XR traffic, 10240 ms / (1000 / 120) ms = 1228.8 frames. The fractional part of 0.8 (or 1 - 0.8 = 0.2) is the remaining partial frame at the end of the hyperframe, and this partial frame causes an SFN wrap-around problem in the next hyperframe. Other multimedia periodicities result in a non - matching number of frames per hyperframe, i.e., 45 Hz (460.8 SFNs), 48 Hz (491.52 SFNs), 60 Hz (614.4 SFNs), or 90 Hz (921.6 SFNs).

[0136]

[0178] Example 1400 indicates the end of the hyperframe (at SFN 1023) and the start of the next hyperframe (at SFN 0), or the point in time when the SFN number wraps around (restarts or returns to 0) for the next hyperframe. When reaching the end of hyperframe 1402, (SFN *10) Wake-up conditions or expressions such as subframe number = 0 for the on-duration can select a subframe for the on-duration between data bursts due to SFN wrap-around. Since the subframe may not be aligned with the data burst, the data burst may not be received. This may cause communication degradation that can consume additional processing and signaling resources.

[0137]

[0179] As described above, FIG. 14 is provided as an example. Other examples may be different from those described with respect to FIG. 14.

[0138]

[0180] FIG. 15 is a diagram showing Example 1500 for setting the hyperframe length according to the present disclosure. Example 1500 shows the arrival of multimedia data bursts arriving at a rate of 120 Hz.

[0139]

[0181] In some aspects, a network entity (e.g., base station 110) may configure a UE (e.g., UE 120) to set a hyperframe length based at least in part on the cadence of multimedia data bursts, as indicated by reference numeral 1505. The cadence of the multimedia data bursts may correspond to a number of Hz, and the number of frames that form the hyperframe length may be a multiple of the temporal periodicity of the number of Hz. For example, the UE may set the hyperframe length to 1000 SFNs instead of 1024 SFNs, and thus, the SFN wraparound that causes an inconsistency in the on-duration occasion calculated in the next hyperframe does not occur at the end of the hyperframe. The hyperframe length may be 1000 frames or 10000 subframes. In some aspects, the UE may maintain an SFN counter for the hyperframe and reset the counter for the next hyperframe when the hyperframe length (at the end of the hyperframe) is reached. The UE may initialize the SFN counter using the current SFN. The SFN counter increments when the SFN is updated. As a result of setting the hyperframe length to match the cadence or periodicity of the multimedia data bursts, there are no timing inconsistencies and frequent drifts when the UE receives multimedia data bursts, as indicated by reference numeral 1510. By adjusting the hyperframe length, the UE may improve communication and align the on-duration occasion with the data bursts to avoid consuming additional processing and signaling resources at the UE. In some aspects, the network entity may select the hyperframe length and transmit the hyperframe length in the configuration information.

[0140]

[0182] The UE may use a configured hyperframe length to determine a subframe identifier of a DRX-on duration subframe for receiving a multimedia data burst by performing a modulo operation using the hyperframe length. The DRX cycle may be configured for the cadence of the multimedia data burst. For example, if a subframe identifier n for calculating the on-duration subframe has been previously determined and n = [(SFN × 10) + subframe number], the UE may then determine a subframe identifier n where n = [(SFN_M × 10) + subframe number]. SFN_M is the SFN after modulo operation using the configured hyperframe length (in SFN units). For example, for a given subframe at sequence N = 50000, the subframe identifier n for the on-duration wake-up condition or equation is 50000 mod 10240, or 9040, and the hyperframe length is 1024 frames (SFN_M = 1024). In contrast, for a given subframe N = 50000, in the on-duration equation, n has 50000 mod 10000, or 0, and the hyperframe length is 1000 frames (SFN_M = 1000).

[0141]

[0183] In some aspects, the on-duration formula for waking up from an on-duration sleep cycle may include waking up at the start in a subframe, based at least in part on the subframe identifier of the subframe and the DRX cycle periodicity corresponding to a multiple of the multimedia periodicity (the reciprocal of the multimedia cadence in units of number of Hz). For example, the formula may be [timeReferenceSFN × numberOfSubframesPerFrame + drx-StartOffset + floor(N × 1000 / drx-ShortCadence)] modulo [(SFN × numberOfSubframesPerFrame) + subframe number within the frame] = (1024 × numberOfSubframesPerFrame). N may be a value used to sequentially search for the DRX cycle on-duration. N is incremented by 1 for each on-duration occasion. There is no SFN wrap-around with the sequential search value N. The parameter drx-timeReferenceSFN may provide an SFN that can be used to offset resources or start a hyperframe. The UE may use the nearest SFN with the indicated number preceding the reception of the eCDRX configuration. In some aspects, a ceiling of (N × 1000 / drx-ShortCadence) may be used instead of the floor. (drx-SlotOffset / 32 × numberOfSlotsPerSubframe) may indicate the slot offset value in slot units when drx-SlotOffset is a value in 1 / 32 ms units, and the ceiling operation may be used instead of the floor. The terms drx-ShortCadence and drx-ShortCycle may have a relationship such as drx-ShortCycle (ms) = 1000 / drx-ShortCadence (fps).

[0142]

[0184] In some aspects, this equation may be [timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset(i)+N×drx-ShortCycle] modulo [(SFN×numberOfSubframesPerFrame)+subframe number within the frame]=(1024×numberOfSubframesPerFrame).

[0143]

[0185] There may be multiple DRX offsets. The index i may be used to indicate one of the multiple DRX start offsets (drx-StartOffset(i)) and / or multiple DRX slot offsets (drx-StartOffset(i)). The index i may be an integer within the RRC information element (e.g., 0 to 10239 for drx-StartOffset(i), 0 to 31 for drx-SlotOffset(i)). The drx-SlotOffset may have a value of 1 / 32 ms for a 480 kilohertz (kHz) subcarrier spacing (SCS), for example. In one example, three DRX start offsets may be defined within drx-ShortCycle,i = [0,1,2], and a drx-StartOffset may be defined for each i. In this example, when the multimedia cadence is 120 Hz, drx-ShortCycle = 25, drx-StartOffset(0)=0, drx-StartOffset(1)=8, and drx-StartOffset(2)=16. Also, drx-SlotOffset(0)=0, drx-SlotOffset(1)=0, and drx-SlotOffset(2)=0. Any one of the three values of drx-StartOffset(i) and drx-SlotOffset(i) activates the drx-onDurationTimer.

[0144]

[0186] There may be multiple DRX start offsets (e.g., unit: subframe, 1 ms) within the drx-ShortCycle. For any i, the drx-onDurationTimer for the DRX group may start after drx-SlotOffset(i) from the start of the subframe. A set of multiple drx-StartOffset and drx-SlotOffset may be configured within the drx-ShortCycle, and the drx-ShortCycle may be set using any integer.

[0145]

[0187] In some aspects, the drx-timeReferenceSFN may be an enumerated value such as SFN 512, which indicates the SFN used for the determination of the offset of the time domain resource. The UE may use the closest SFN with the indicated number preceding the reception of the eCDRX configuration. If the timeReferenceSFN does not exist, the timeReferenceSFN may be 0.

[0146]

[0188] In some aspects, at the slot level, the on-duration formula may be [(SFN × numberOfSlotsPerFrame) + slot number within the frame] = [timeReferenceSFN × numberOfSlotsPerFrame + drx-StartOffset × numberOfSlotsPerSubframe + floor(drx-SlotOffset / 32 × numberOfSlotsPerSubframe) + floor(N × numberOfSlotsPerSubframe × 1000 / drx-ShortCadence)] modulo (1024 × numberOfSlotsPerFrame). The drx-SlotOffset may be a value in units of 1 / 32 ms. In some aspects, instead of the floor, the ceiling of (N × numberOfSlotsPerSubframe × 1000 / drx-ShortCadence) may be used.

[0147]

[0189] In some aspects, this equation may be [(SFN × numberOfSlotsPerFrame) + slot number within the frame] = [timeReferenceSFN × numberOfSlotsPerFrame + drx - StartOffset(i) × numberOfSlotsPerSubframe + floor(drx - SlotOffset(i) / 32 × numberOfSlotsPerSubframe) + N × drx - ShortCycle] modulo (1024 × numberOfSlotsPerFrame). For any i, the drx - onDurationTimer may start for the DRX group at the start of the slot. The DRX timers (e.g., drx - InactivityTimer, drx - HARQ - RTT - Timer) may be set using the slot granularity. The multimedia cadence is 120 Hz (in the example of 30 kHz SCS (0.5 ms), drx - ShortCycle = 25 × 2 slots, drx - StartOffset(0) = 0, drx - StartOffset(1) = 8, and drx - StartOffset(2) = 16).

[0148]

[0190] In some aspects, this equation may be [(SFN × numberOfSlotsPerFrame) + slot number within the frame = (1024 × numberOfSlotsPerFrame) modulo [timeReferenceSFN × numberOfSlotsPerFrame + drx-StartOffset(i) + N × drx-ShortCycle]]. drx-StartOffset can be set using the slot granularity. The value of drx-StartOffset(i) may be, for example, an integer from 0 to 327647. The unit for a plurality of DRX start offsets having drx-ShortCycle may be slots, and drx-SlotOffset can be merged into drx-StartOffset. For a multimedia cadence of 120 Hz (in the example of 30 kHz SCS (0.5 ms), drx-ShortCycle = 25 × 2 slots, drx-StartOffset(0) = 0 slots, drx-StartOffset(1) = 8 × 2 slots, and drx-StartOffset(2) = 16 × 2 slots).

[0149]

[0191] In some aspects, the sequential search DRX cycle equation may involve a rational number for drx-ShortCycle. This equation may be [(SFN × numberOfSubframesPerFrame) + subframe number within the frame] = (1024 × numberOfSsubframesPerFrame) modulo [timeReferenceSFN × numberOfSubframesPerFrame + drx-StartOffset + floor(N × drx-ShortCycle)]. In some aspects, the ceiling of (N × drx-ShortCycle)] may be used.

[0150]

[0192] In some aspects, drx-ShortCycle may be indicated within an RRC information element (IE) and may be an enumerated value such as ms8and1Over3, ms11and1Over9, ms12and1Over2, ms16and2Over3, ms20and5Over6, ms22and2Over9, ms33and1Over3, or ms41and2Over3. These represent rational numbers associated with DRX cycle periodicity. A rational number can represent a non-integer value for drx-ShortCycle, and thus, ms8and1Ove 3 is associated with 120fps XR traffic. In this example where the multimedia cadence (drx-ShortCadence) is 120fps or 120Hz, drx-ShortCycle = ms8and1Over3 and drx-StartOffset = 0. That is, if drx-ShortCycle (ms) = 1000 / drx-ShortCadence (fps) and drx-ShortCadence = 120, then drx-ShortCycle = 1000 / 120 = 25 / 3 = 8 + 1 / 3 (ms8and1Over3). In another example where drx-ShortCadence = 60fps or 60Hz, drx-ShortCycle = 1000 / 60 = 50 / 3 (16and2Over3).

[0151]

[0193] The network entity may configure the UE using the hyperframe length, for example, using additional information elements (e.g., drx-initialSFN) within the RRC message. The network entity may transmit an RRC message having a DRX short cadence value (e.g., drx-ShortCadence) that is an integer from 1 to 1000. The network entity may transmit an RRC message having a DRX SFN modulo (e.g., drx-SFNModulo) value that is less than 1024 SFNs, such as 1 to 1023. The network entity may transmit an RRC message indicating an initial value of SFN_M (e.g., drx-initialSFN) that may be from 0 to 1023 SFNs. The network entity may transmit a MAC CE indicating the initialization value or timing of SFN_M, or any other such value.

[0152]

[0194] Setting the new SFN_M value, or otherwise setting the hyperframe length based at least in part on the cadence of the multimedia data burst, may be used with other solutions for aligning the on-duration occasion with the multimedia data burst, as described in connection with FIGS. 6-13. For example, the UE may set the new hyperframe length (and use the SFN with the new hyperframe length as the law, or n = [(SFN_M × 10) + subframe number]) in the calculation for the outer DRX cycle in the two-level DRX configuration, as well as in the calculation for the short DRX cycle and the long DRX cycle. In some aspects, the MAC entity may consider that the Nth consecutive on-duration cycle occurs in a subframe that is [timeReferenceSFN × numberOfSubframesPerFrame + drx-StartOffset + drx-PeriodicOffset(N)] with [(SFN × numberOfSubframesPerFrame) + subframe number within the frame] = (1024 × numberOfSubframesPerFrame) as the law. When N = 0, drx-PeriodicOffset(0) = 0, and when N > 0, drx-PeriodicOffset(N) = drx-PeriodicOffset(N - 1) + drx-ShortCycleList{(N - 1) modulo SIZE(drx-ShortCycleList)}. The UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffsetList{(N - 1) modulo SIZE(drx-SlotOffset)} from the start of the subframe. The drx-timeReferenceSFN may provide the SFN used to determine the offset of the resources in the time domain. The UE may use the closest SFN with the indicated number preceding the reception of the DRX configuration.The drx-ShortCycleList may be a set of heterogeneous DRX short cycles or may be associated with a set of heterogeneous DRX short cycles (values within 1 ms, e.g., for 120 Hz, drx-ShortCycleList = (8, 8, 9)). The drx-SlotOffsetList may be a set of DRX slot offsets or may be associated with a set of DRX slot offsets. The drx-ShortCycleList may be a sequence having a size from 1 to maxNrofShortCycle (the maximum number of short cycles) of drx-ShortCycle-r18. The drx-ShortCycle-r18 may be a value within 1 ms (subframe) from 1 to 640. The drx-StartOffset may be a value within 1 ms (subframe) from 0 to 10239. This may come from drx-LongCycleStartOffset (see 1024 (SFN) × 10 (subframes) = 10240). The drx-SlotOffset may be a value within 1 / 32 ms (480 kHz SCS) from 1 to 31. The drx-timeReferenceSFN may be an enumerated value such as SFN512. If timeReferenceSFN does not exist, timeReferenceSFN is 0.

[0153]

[0195] In some aspects, the MAC entity may consider that the Nth on-duration cycle in a slot occurs where [(SFN × numberOfSlotsPerFrame) + slot number within the frame] = [timeReferenceSFN × <numberOfSlotsPerFrame + drx-StartOffset × numberOfSlotsPerSubframe + floor(drx-SlotOffset / 32 × numberOfSlotsPerSubframe) + drx-PeriodicOffset(N)] modulo (1024 × numberOfSlotsPerFrame). When N = 0, drx-PeriodicOffset(0) = 0, and when N > 0, drx-PeriodicOffset(N) = drx-ShortCycleList{(N - 1) modulo SIZE(drx-ShortCycleList)} + drx-PeriodicOffset(N - 1). The drx-ShortCycleList may be a set of non-uniform DRX short cycles (values within a slot). The drx-ShortCycle-r18 may be a value within slots 1 to 20479. The UE may start the drx-onDurationTimer for this DRX group at the start of the slot.

[0154]

[0196] In some aspects, the network entity may send a DCI or MAC CE command that compensates for a subframe index mismatch shift (DRX cycle drift) due to SFN wraparound. The network entity may indicate a value for shifting the timing of the DRX cycle based at least in part on the indicated shift, such as a 240 subframe (240 ms) shift, a 10240 subframe (10240 ms) shift, or a specific timing drift (e.g., 2 ms in Example 1400). The value may be a value within a new set of values in a shift table list that can compensate for the subframe index mismatch shift caused by SFN wraparound. The value may be a 1-bit value in a DCI or MAC CE command indicating SFN wraparound. This value may be sent together with a shift value index that references a shift table list or another shift table list. The UE may apply the shift before the first on-duration occasion of the next hyperframe. The UE may use [(SFN × numberOfSubframesPerFrame) + subframe number within the frame] = (1024 × numberOfSubframesPerFrame) modulo (timeReferenceSFN × numberOfSubframesPerFrame + drx-StartOffset + N × drx-ShortCycle) as an equation for the subframe. The UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.The UE may use [timeReferenceSFN×numberOfSlotsPerFrame+drx-StartOffset×numberOfSlotsPerSubframe+floor(drx-SlotOffset / 32×numberOfSlotsPerSubframe)+N×drx-ShortCycle×numberOfSlotsPerSubframe] with the law of [(SFN×numberOfSlotsPerFrame)+slot number in the frame]=(1024×numberOfSlotsPerFrame) as the formula for slots. The UE may start the drx-onDurationTimer for this DRX group drx-SlotOffset after the start of the slot.

[0155]

[0197] In some embodiments, the MAC CE may not be sent due to the predictability of the SFN wrap-around. In such cases, both the network entity and the UE may anticipate a relative shift of 240 ms or 10240 ms whenever the hyperframe changes during the DRX cycle. As a result, the UE may apply the shift before the first on-duration occasion of the next hyperframe without receiving a MAC CE indicating the shift. This implicit method may be triggered by a change in the hyperframe.

[0156]

[0198] In some aspects, the UE may compensate for a timing drift between a DRX on-duration and multimedia burst traffic associated with an inconsistency between a hyperframe length and a periodicity of multimedia data bursts. For example, an SFN wrap-around problem may be solved by compensating for a 240 ms drift in the DRX scheme. 240 subframes may be added per hyperframe in the subframe index, [(SFN × 10) + subframe number + M × 240] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle). M may start from 0 when DRX is first configured, and M may increase by 1 per hyperframe using a time-reference SFN, or may increase by 1 when the SFN returns to 0. To resolve the timing ambiguity of the DRX configuration message, drx-timeReferenceSFN (0 or 512) may further be regarded as an initial reference SFN value.

[0157]

[0199] In some aspects, the SFN wrap-around problem may be solved by accumulating 10240 ms in the DRX scheme. For example, 10240 subframes may be added per hyperframe in the subframe index, [(SFN × 10) + subframe number + M × 10240] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle). M may start from 0 when DRX is first configured, and M may increase by 1 per hyperframe using a time-reference SFN, or may increase by 1 when the SFN returns to 0. To resolve the timing ambiguity of the DRX configuration message, drx-timeReferenceSFN (0 or 512) may further be regarded as an initial reference SFN value. These are examples, and other schemes may add a specified amount of time (e.g., a specified amount of milliseconds) per hyperframe that satisfies a specified scheme including a subframe number and a DRX short cycle.

[0158]

[0200] As described above, FIG. 15 is provided as an example. Other examples may be different from those described with respect to FIG. 15.

[0159]

[0201] FIG. 16 is a diagram showing an example 1600 of an RRC configuration for a DRX cycle according to the present disclosure.

[0160]

[0202] The UE may receive an RRC configuration 1602 indicating DRX cycle information for a hyperframe, including a new timing of an on-duration occasion, from a network entity during the hyperframe. However, if the RRC configuration is received late towards the end of the hyperframe, the DRX configuration may be applied to the next hyperframe instead of the current hyperframe. As a result, the UE and the network entity no longer use the same DRX configuration for the hyperframe and / or the next hyperframe.

[0161]

[0203] As described above, FIG. 16 is provided as an example. Other examples may be different from those described with respect to FIG. 16.

[0162]

[0204] FIG. 17 is a diagram showing an example 1700 of aligning a DRX cycle with multimedia periodicity according to the present disclosure.

[0163]

[0205] Example 1700 shows a plurality of DRX cycles (in particular, among a number of DRX cycles, DRX cycle 1702, DRX cycle 1704, DRX cycle 1706) configured for a UE (e.g., UE 120). DRX cycle 1706 can be a DRX leap cycle that is at least partially based on its DRX number (e.g., DRX number 103). DRX cycle 1706 can have a DRX cycle length 1708 (e.g., 32 ms). On the other hand, data bursts can arrive according to a multimedia cadence based on, for example, 120 Hz. Of course, there is a mismatch due to the discrepancy between the Hz granularity of the multimedia data bursts and the millisecond granularity of the DRX cycles. Without appropriate correction, the mismatch wakes up the UE when the data burst is not being transmitted and puts the UE to sleep when the data burst is being transmitted. As a result, data bursts are lost and communication performance deteriorates.

[0164]

[0206] As indicated by reference numeral 1710, the UE can sleep in relation to a DRX cycle that can be the next DRX cycle 1706. For example, the UE can sleep in the sleep state 1712 of DRX cycle 1704, anticipating the next DRX cycle 1706 that starts at the start of the on-duration 1714. To correct the mismatch prior to waking up, the UE can add a specified time offset 1716 to the on-duration 1714. During the on-duration 1714, there is a subframe 1718 at this new time position. As indicated by reference numeral 1720, the UE can wake up in subframe 1718. Waking up in a subframe can include waking up from sleep so as to be able to receive during the subframe. As indicated by reference numeral 1725, the UE can receive a multimedia data burst in subframe 1718. Subframe 1718 can have a subframe number 1722 within the frame of subframe 1718. In some aspects, a start offset (DRX start offset) can also be added to the on-duration 1714.

[0165]

[0207] According to various aspects described herein, a UE may determine when to wake up using wake-up conditions, which may include applying a specified time offset 1716. The wake-up conditions may be at least partially based on the subframe number 1722 of subframe 1718, which is a subframe of the frame identified by SFN 1736 (e.g., subframe 5 out of 10 subframes in a frame). For example, the UE may wake up at least partially based on the specified time offset 1716 being added to the on-duration 1714. The specified time offset 1716 may be added at least partially based on the number of DRX cycles 1706 in the DRX cycle (e.g., 3) and the DRX cycle length 1708. The number of DRX cycles may be the number of DRX cycles having a longer time period, such as an anchor cycle. The specified time offset 1716 may be a fixed time shift (e.g., 4 ms) relative to the start of the on-duration 1714 and the on-duration timer. The DRX cycle length 1708 may sometimes be referred to as a "DRX long cycle". The specified time offset 1716 may be at least partially based on the periodicity 1726 of the multimedia burst. For example, the UE may wake up when [(SFN × 10) + subframe number 1722] modulo the DRX cycle length 1708 is equal to the start offset 1728 modulo the DRX cycle length 1708 + (n × the specified time offset 1716). The count n may be the count of the anchor cycle or the count of when the DRX leap cycle to which the specified time offset 1716 is applied occurs. The count n may be updated or incremented to n + 1 whenever the current number of DRX cycles modulo the specified number of DRX cycles 1724 is equal to 0. The specified number of DRX cycles 1724 may be the period of the DRX leap cycle or the amount of DRX cycles when the specified time offset 1716 is applied again. For example, if the number of DRX cycles for DRX cycle 1706 is 3 and the specified number of DRX cycles 1724 is 3, the UE may increment count n.When the number of DRX cycles is currently 4, the UE may not increment countn. The specified number of DRX cycles 1724 may be [(SFN × 10) + subframe number 1722] / DRX cycle length 1708.

[0166]

[0208] Some modifications to this wake-up condition may not successfully address the inconsistency between the multimedia data burst and the DRX cycle. For example, [(SFN × 10) + subframe number 1722 + (n × specified time offset 1716)] modulo the DRX cycle length 1708 being equal to the start offset 1728 + (n × specified time offset) modulo the DRX cycle length 1708, such that when (n × specified time offset 1716)] is added to the left side of the modulo, the difference between the DRX cycle on duration and the periodicity 1726 of the multimedia data burst continues to increase each time the specified time offset 1716 is applied. Due to the additional (n × specified time offset 1716) on the left side of the modulo, in a later DRX cycle (e.g., 768 ms), the difference can become equal to the DRX cycle length 1708, thereby resulting in a duration equal to the specified number of DRX cycles 1724 used in the modulo operation (the modulo result is 0). This introduces an incorrect DRX cycle. The difference is 32 ms here instead of being set to 0 ms and is increasing.

[0167]

[0209] The wake-up condition may fail when the amount or count of DRX leap cycles is not taken into account. Thus, in some aspects, the number of DRX cycles of the current DRX cycle used to update n may be at least partially based on the specified time offset 1716. For example, the UE may determine the number of DRX cycles of the current DRX cycle used to update n by dividing [(SFN × 10) + subframe number 1722 + (n × specified time offset 1716)] by the DRX cycle length 1708.

[0168]

[0210] In some aspects, the wake-up condition may be better satisfied when the UE skips the n+1 update every other time. In some aspects, the wake-up condition may be better satisfied when n is updated to n+1 when (DRX cycle length 1708 × specified DRX cycle number 1724 + specified time offset 1716) modulo (10 × SFN + subframe number 1722) is equal to the specified timing value 1734. The specified DRX cycle number 1724 may also be referred to as the "specified amount of DRX cycles". The specified timing value 1734 may be a value used for the condition to update n and may be equal to (DRX cycle length 1708 × specified DRX cycle number 1724) - 1.

[0169]

[0211] In some aspects, the wake-up condition may be able to handle any SFN wrap-around issues. For example, the UE may wake up at least partially based on the SFN wrap-around offset 1730. The SFN wrap-around offset 1730 may be equal to (10240 × m), where m is updated to m+1 when the SFN returns to 0 (reset to 0 at the start of the next hyperframe). In some aspects, the UE may use the SFN wrap-around offset 1730 such that the UE wakes up when (10 × SFN + subframe number 1722 + SFN wrap-around offset 1730) modulo DRX cycle length 1708 is equal to ((n × specified time offset 1716) + start offset 1728) modulo DRX cycle length 1708. The UE may update n to n+1 when (10 × SFN + subframe number 1722 + SFN wrap-around offset 1730) modulo (DRX cycle length 1708 × specified DRX cycle number 1724 + specified time offset 1716) is equal to the specified timing value 1734.

[0170]

[0212] The UE may resolve any timing ambiguity of the RRC message. For example, the RRC message may be received after passing SFN 512 later within the hyperframe, and it may not be clear when the UE should apply the wake-up condition. In some aspects, the UE may receive the DRX time reference SFN 1732 in an instruction from the network (e.g., the RRC message). The DRX time reference SFN 1732 may be the SFN used to adjust the wake-up condition to resolve the message timing ambiguity. The DRX time reference SFN 1732 may be SFN 0 or SFN 512. Taking the DRX cycle length 1728 as the modulus (10×SFN + subframe number 1722 + SFN wrap-around offset 1730), but when it is equal to taking the DRX cycle length 1708 as the modulus [(n×specified time offset 1716) + start offset 1728 + (DRX time reference SFN×10)], the UE may wake up using the DRX time reference SFN 1732. The UE may update n when taking (DRX cycle length 1708×specified DRX cycle number 1724 + specified time offset 1716) as the modulus (10×SFN + subframe number 1722 + SFN wrap-around offset 1730) is equal to the specified timing value 1734. The SFN wrap-around offset 1730 may be 10240×m, and m is updated to m + 1 when the SFN returns to the DRX time reference SFN 1732. The DRX time reference SFN 1732 may be 0 or 512. The UE may receive an instruction of the DRX time reference SFN 1732.

[0171]

[0213] The DRX cycle 1706 may be part of an anchor cycle 1738 of a plurality of DRX cycles indicated by DRX cycles 1702, 1704, 1706, 1740, 1742, and 1744. The anchor cycle 1738 may include one DRX leap cycle such as DRX cycle 1706. In some aspects, the anchor cycle 1738 may include two or more leap cycles, such as both DRX cycle 1706 and DRX cycle 1744. The UE may receive an indication of two or more leap cycles. For example, an RRC message may indicate a set of multiple leap cycles (e.g., for XR traffic at 45 Hz). The indication may indicate the timing or leap period of each leap cycle within the anchor cycle 1738. The timing may be explicit, such as in terms of the number of DRX cycles, an amount of time (e.g., in milliseconds, slots, and / or symbols relative to another DRX cycle), SFN, subframe number, or a combination thereof.

[0172]

[0214] In some aspects, the UE may use different wake-up conditions, and the UE wakes up based at least in part on a specified time offset 1716 added to the on-duration 1714 of the DRX cycle 1706, based at least in part on the number of DRX cycles of the DRX cycle 1706 and the DRX time reference SFN 1732. The specified time offset 1716 may be based at least in part on the periodicity 1726 of the multimedia data burst, and the number of DRX cycles may be based at least in part on the specified time offset 1716. For example, the UE may wake up if (SFN × the amount of subframes per frame) + subframe number 1722 is equal to [(DRX time reference SFN × the amount of subframes per frame) + start offset 1728 + the number of DRX on-duration × DRX cycle length 1708 + floor (the number of DRX on-duration / the specified time offset 1716) × the specified amount of DRX cycles], modulo (1024 × the amount of subframes per frame).

[0173]

[0215] The number N of DRX on - durations may be the number of on - durations within the anchor cycle 1738. The number N of DRX on - durations may correspond to the number of DRX cycles. In some aspects, the number N of DRX on - durations is the Nth eCDRX on - duration cycle that occurs in a sub - frame that is modulo [(SFN_M×10)+sub - frame number 1722] with respect to the DRX cycle length 1708 = modulo [(SFN_M×10)+sub - frame number 1722] with respect to the DRX cycle length 1708 = modulo [(start offset+(n×specified time offset 1716+(DRX time - reference SFN×10))] with respect to the DRX cycle length 1708, where n=n + 1 whenever modulo [(SFN_M×10)+sub - frame number 1722] with respect to (DRX cycle length 1708×specified DRX cycle number 1724+specified time offset 1716)=(DRX cycle length 1708×specified time offset 1716)-1. The specified time offset 1716 may be referred to as the "DRX leap offset". SFN_M may be the SFN after modulo operation using the set hyper - frame length (in SFN units).

[0174]

[0216] In some aspects, the UE may wake up when modulo [(SFN_M×10)+sub - frame number 1722] with respect to the DRX cycle 1706 is equal to modulo [start offset+(n×specified time offset 1716)+(DRX time - reference SFN×10)] with respect to the DRX cycle length 1708, and n is updated to n + 1 when modulo [(SFN_M×10)+sub - frame number] with respect to (DRX cycle length 1708×specified DRX cycle number 1724+specified time offset 1716) is equal to the specified timing value 1734. The specified timing value 1734 may be equal to (DRX cycle length 1708×specified DRX cycle number 1724)-1.

[0175]

[0217] As described above, FIG. 17 is provided as an example. Other examples may be different from those described with respect to FIG. 17.

[0176]

[0218] FIG. 18 is a diagram showing example 1800 associated with the use of a specified time offset according to the present disclosure. As shown in FIG. 18, network entity 1810 (e.g., base station 110) may communicate with UE 1820 (e.g., UE 120). Network entity 1810 and UE 1820 may be part of a wireless network (e.g., wireless network 100).

[0177]

[0219] As indicated by reference numeral 1825, network entity 1810 may transmit traffic bursts according to a periodicity (e.g., video frame rate). Network entity 1810 may also be configured for UE 1820 and transmit data bursts according to wake-up conditions used by UE 1820. As indicated by reference numeral 1830, UE 1820 may sleep and wake up according to a resource cycle and wake-up conditions configured for UE 1820. For example, UE 1020 may calculate for each subframe whether parameters associated with UE 1020 and the resource cycle meet the criteria for wake-up. Examples described herein, such as example 1700, show that the resource cycle may be a DRX cycle and the parameters may be related to the DRX cycle (e.g., SFN, subframe number, DRX cycle length, number of DRX cycles).

[0178]

[0220] However, in some aspects, the wake-up conditions used for DRX may be for other resources including channel state information (CSI)-reference signal (CSI-RS), CSI-interference measurement resource (CSI-IM), sounding reference signal (SRS), scheduling request (SR), configured grant (CG) resources, semi-persistent scheduling (SPS) resources, CSI reports, buffer status reports (BSR), physical downlink control channel (PDCCH) monitoring, and / or for physical uplink control channel (PUCCH) resources.

[0179]

[0221] In some aspects, network entity 1810 may send an indication associated with a resource cycle, as indicated by reference number 1835. The indication may include parameters (e.g., leap cycle, specified time offset) for waking up according to the resource cycle.

[0180]

[0222] In some aspects, network entity 1810 may prepare for communication according to a DRX cycle, as indicated by reference number 1840. This may include determining the DRX cycle to be used by UE 1820, or other preparations for DRX of UE 1820. The preparation may include preparing for transmission during the on-duration of the DRX cycle.

[0181]

[0223] As described above, FIG. 18 is provided as an example. Other examples may be different from those described with respect to FIG. 18.

[0182]

[0224] Aspects will be described with respect to multimedia, but these aspects may also be applicable to other applications involving periodic transmission.

[0183]

[0225] Mathematical symbols used in wake-up conditions or expressions may be interpreted to mean similar concepts. For example, “+” means plus or addition, “−” means minus or subtraction, “×” or “ * ” means multiplication, and “ / ” means division.

[0184]

[0226] FIG. 19 is a diagram showing an example of a non - aggregated base station 1900 according to the present disclosure.

[0185]

[0227] The deployment of a communication system such as a 5G NR system may be configured in a plurality of ways using various components or constituent parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or network devices such as base stations, or one or more units (or one or more components) implementing base station functionality may be implemented in an aggregated or non - aggregated architecture. For example, a BS (such as a Node B, evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell, etc.) may be implemented as an aggregated base station or a non - aggregated base station (also known as a stand - alone BS or a monolithic BS).

[0186]

[0228] The centralized base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. The non-centralized base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., one or more CUs, one or more DUs, or one or more RUs). In some aspects, the CU may be implemented within the RAN node, one or more DUs may be collocated with the CU, or alternatively, one or more DUs may be geographically or virtually distributed across one or more other RAN nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0187]

[0229] The operation or network design of the base station type may consider the aggregation characteristics of the base station functions. For example, the non-centralized base station may be utilized in an IAB network, an open radio access network (such as a network configuration operated by the O-RAN Alliance), or a virtualized radio access network (vRAN) also known as a cloud radio access network (C-RAN). Non-aggregation may include dispersing functions across two or more units at various physical locations, as well as virtually dispersing the functions of at least one unit, which may enable flexibility in network design. The various units of the non-centralized base station, or the non-centralized RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0188]

[0230] The non - centralized base station 1900 architecture can include one or more CUs 1910 that can communicate directly with the core network 1920 via a backhaul link or indirectly with the core network 1920 via one or more non - centralized base station units (such as a quasi - RT RIC 1925 via an E2 link, or a non - RT RIC 1915 associated with a Service Management and Orchestration (SMO) framework 1905, or both). The CU 1910 can communicate with one or more DUs 1930 via respective mid - haul links such as an F1 interface. The DU 1930 can communicate with one or more RUs 1940 via respective front - haul links. The front - haul link, mid - haul link, and backhaul link are sometimes generally referred to as "communication links". The RU 1940 can communicate with respective UEs 120 via one or more RF access links. In some aspects, a UE 120 can be served simultaneously by multiple RUs 1940. The DU 1930 and RU 1940 are sometimes also referred to as "O - RAN DU (O - DUs)" and "O - RAN RU (O - RUs)", respectively. A network entity can include a CU, a DU, an RU, or any combination of a CU, a DU, and an RU. A network entity can include one or more components of a non - centralized base station, such as a non - centralized base station, or a CU, a DU, an RU, or any combination of a CU, a DU, and an RU. A network entity can also include a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or one or more of other components that can provide a network interface for or serve UEs, mobile stations, sensors / actuators, or other wireless devices.

[0189]

[0231] Each of the units (e.g., CU1910, DU1930, RU1940, and quasi-RT RIC1925, non-RT RIC1915, and SMO framework 1905) may include one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium, or may be coupled to one or more interfaces. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of the units, may be configured to communicate with one or more of the other units via the transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver), and the wireless interface is configured to receive signals from, transmit signals to, or both, one or more of the other units via a wireless transmission medium.

[0190]

[0232] In some aspects, CU1910 may host one or more upper layer control functions. Such control functions can include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signals with other control functions hosted by CU1910. CU1910 may be configured to handle user plane functions (i.e., Central Unit - User Plane (CU-UP)), control plane functions (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, CU1910 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. CU1910 can be implemented to communicate with DU1930 as needed for network control and signaling.

[0191]

[0233] DU1930 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU1940. In some embodiments, DU1930 may host one or more of the radio link control (RLC) layer, the MAC layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) at least partially in accordance with a functional split defined by 3GPP. In some embodiments, DU1930 may further host one or more low PHY layers. Each layer (or module) can be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU1930 or with control functions hosted by CU1910.

[0192]

[0234] The lower layer functions can be implemented by one or more RU1940s. In some deployments, the RU1940s controlled by the DU1930 may correspond to logical nodes that host an RF processing function, or a low PHY layer function (such as implementation of fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, at least partially based on function splitting such as lower layer function splitting. In such an architecture, the RU(s) 1940 can be implemented to handle over the air (OTA) communication with one or more UEs120. In some implementations, the real-time and non-real-time aspects of control plane and user plane communication with the RU(s) 1940 can be controlled by the corresponding DU1930. In some scenarios, this configuration can enable the DU(s) 1930 and the CU1910 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0193]

[0235] The SMO framework 1905 may be configured to support the RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. In the case of non-virtualized network elements, the SMO framework 1905 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that can be managed via an operation and maintenance interface (such as the O1 interface). In the case of virtualized network elements, the SMO framework 1905 may be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 1990) in order to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 1910, DU 1930, RU 1940, and the quasi-RT RIC 1925. In some implementations, the SMO framework 1905 may be able to communicate with hardware aspects of 4G RAN, such as the open eNB (O-eNB) 1911, via the O1 interface. Additionally, in some implementations, the SMO framework 1905 may be able to communicate directly with one or more RUs 1940 via the O1 interface. The SMO framework 1905 may also include a non-RT RIC 1915 configured to support the functions of the SMO framework 1905.

[0194]

[0236] The non-RT RIC 1915 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, an artificial intelligence / machine learning (AI / ML) workflow including model training and updating, or policy-based guidance for applications / features in the quasi-RT RIC 1925. The non-RT RIC 1915 may be coupled to the quasi-RT RIC 1925 or communicate with the quasi-RT RIC 1925 (e.g., via an A1 interface). The quasi-RT RIC 1925 may be configured to include a logical function that enables quasi-real-time control and optimization of RAN elements and resources via data collection and actions (e.g., via an E2 interface) through an interface connecting one or more CU 1910, one or more DU 1930, or both, and an O-eNB to the quasi-RT RIC 1925.

[0195]

[0237] In some implementations, the non-RT RIC 1915 may receive parameters or external enrichment information from an external server to generate an AI / ML model deployed in the quasi-RT RIC 1925. Such information may be utilized by the quasi-RT RIC 1925 and may be received from a non-network data source or a network function, in the SMO framework 1905 or in the non-RT RIC 1915. In some examples, the non-RT RIC 1915 or the quasi-RT RIC 1925 may be configured to adjust RAN behavior or RAN performance. For example, the non-RT RIC 1915 may monitor long-term trends and patterns in performance and employ an AI / ML model to implement corrective measures through the SMO framework 1905 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0196]

[0238] As described above, FIG. 19 is provided as an example. Other examples may be different from those described with respect to FIG. 19.

[0197]

[0239] FIG. 20 is a diagram illustrating an exemplary process 2000 that may be performed, for example, by a UE. The exemplary process 2000 is an example in which a UE (e.g., UE120, UE1820) performs operations associated with a DRX method for multimedia.

[0198]

[0240] As shown in FIG. 20, in some aspects, process 2000 may include sleeping in relation to a DRX cycle (block 2010). For example, a UE (e.g., using communication manager 2608 and / or DRX component 2610 shown in FIG. 26) may sleep in relation to a DRX cycle as described above.

[0199]

[0241] As further shown in FIG. 20, in some aspects, process 2000 may include waking up at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles being based at least in part on the specified time offset (block 2020). For example, a UE (e.g., using communication manager 2608 and / or DRX component 2610 shown in FIG. 26) may wake up at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, and as described above, the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset.

[0200]

[0242] As further shown in FIG. 20, in some aspects, process 2000 may include receiving a multimedia data burst between subframes (block 2030). For example, a UE (e.g., using communication manager 140 and / or receiving component 2602 shown in FIG. 26) may receive a multimedia data burst between subframes as described above.

[0201]

[0243] Process 2000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described in connection with one or more other processes described elsewhere in this specification.

[0202]

[0244] In a first aspect, the number of DRX cycles is equal to the value obtained by dividing [(10 × SFN of the frame containing the subframe + subframe number of the subframe) - (n × specified time offset)] by the length of the DRX cycle.

[0203]

[0245] In a second aspect, alone or in combination with the first aspect, waking up includes waking up when (10 × SFN + subframe number) modulo the length of the DRX cycle is equal to ((n × specified time offset) + start offset) modulo the length of the DRX cycle, and n is updated to n + 1 when the number of DRX cycles modulo the specified amount of the DRX cycle is equal to 0.

[0204]

[0246] In a third aspect, alone or in combination with one or more of the first and second aspects, process 2000 includes skipping the n + 1 update every other time.

[0205]

[0247] In a fourth aspect, waking up, alone or in combination with one or more of the first to third aspects, includes waking up when (10×SFN + subframe number), modulo the DRX cycle length, is equal to ((n×specified time offset) + start offset), modulo the DRX cycle length, where n is updated to n + 1 when (10×SFN + subframe number), modulo (DRX cycle length × specified amount of DRX cycle + specified time offset), is equal to the specified timing value.

[0206]

[0248] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the specified timing value is equal to (DRX cycle length × specified amount of DRX cycle) - 1.

[0207]

[0249] In a sixth aspect, waking up, alone or in combination with one or more of the first to fifth aspects, includes waking up based at least in part on an SFN wrap - around offset.

[0208]

[0250] In a seventh aspect, waking up, alone or in combination with one or more of the first to sixth aspects, includes waking up when (10×SFN + subframe number+SFN wrap - around offset), modulo the DRX cycle length, is equal to ((n×specified time offset) + start offset), modulo the DRX cycle length, and n is updated to n + 1 when (10×SFN + subframe number+SFN wrap - around offset), modulo (DRX cycle length × specified amount of DRX cycle + specified time offset), is equal to the specified timing value.

[0209]

[0251] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the SFN wrap-around offset is equal to (10240 × m), where m is updated to m + 1 when the SFN returns to 0.

[0210]

[0252] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, waking up includes waking up when (10 × SFN + subframe number + SFN wrap-around offset) modulo the DRX cycle length is equal to [(n × specified time offset) + start offset + (DRX time reference SFN × 10)] modulo the DRX cycle length, and n is updated to n + 1 when (10 × SFN + subframe number + SFN wrap-around offset) modulo (DRX cycle length × specified amount of the DRX cycle + specified time offset) is equal to the specified timing value.

[0211]

[0253] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the SFN wrap-around offset is 10240 × m, where m is updated to m + 1 when the SFN returns to the DRX time reference SFN, and the DRX time reference SFN is 0 or 512.

[0212]

[0254] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 2000 includes receiving an indication of the DRX time reference SFN.

[0213]

[0255] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the anchor cycle including the DRX cycle also includes two or more leap cycles.

[0214]

[0256] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 2000 includes receiving an indication of two or more leap cycles.

[0215]

[0257] In a 14th aspect, alone or in combination with one or more of the 1st to 13th aspects, process 2000 includes receiving an indication of the timing of two or more leap cycles. In some aspects, the leap cycle offset pattern of two or more leap cycles may include (0 milliseconds (ms), 1 ms, 1 ms) or (1 ms, 1 ms, 0 ms).

[0216]

[0258] FIG. 20 shows exemplary blocks of process 2000, but in some aspects, process 2000 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 20. Additionally, or alternatively, two or more of the blocks of process 2000 may be executed in parallel.

[0217]

[0259] FIG. 21 is a diagram showing an exemplary process 2100 performed, for example, by a UE according to the present disclosure. The exemplary process 2100 is an example in which a UE (e.g., UE120, UE1820) performs operations associated with a DRX method for multimedia.

[0218]

[0260] As shown in FIG. 21, in some aspects, process 2100 may include sleeping in relation to a DRX cycle (block 2110). For example, a UE (e.g., using communication manager 2608 and / or DRX component 2610 shown in FIG. 26) may sleep in relation to a DRX cycle as described above.

[0219]

[0261] As further shown in Figure 21, in some aspects, process 2100 may include waking up at the start in a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the DRX time reference SFN. The specified time offset is at least in part based on the periodicity of the multimedia data burst, and the number of DRX cycles is at least in part based on the specified time offset (block 2120). For example, a UE (e.g., using the communication manager 2608 and / or DRX component 2610 shown in Figure 26) may wake up at the start in a subframe, at least in part based on a specified time offset added to the on-duration of the DRX cycle, at least in part based on the number of DRX cycles of the DRX cycle and the DRX time reference SFN. As described above, the specified time offset is at least in part based on the periodicity of the multimedia data burst, and the number of DRX cycles is at least in part based on the specified time offset.

[0220]

[0262] As further shown in Figure 21, in some aspects, process 2100 may include receiving a multimedia data burst between subframes (block 2130). For example, a UE (e.g., using the communication manager 140 and / or receiving component 2602 shown in Figure 26) may receive a multimedia data burst between subframes as described above.

[0221]

[0263] Process 2100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described in connection with one or more other processes described elsewhere in this specification.

[0222]

[0264] In a first aspect, waking up includes waking up when (SFN of a frame including a subframe × amount of subframes per frame) + subframe number of the subframe is equal to [DRX time reference SFN × amount of subframes per subframe + start offset + number of DRX on durations × length of DRX cycle + floor (number of DRX on durations / specified time offset) × specified amount of DRX cycle] modulo (1024 × amount of subframes per frame).

[0223]

[0265] In a second aspect, alone or in combination with the first aspect, waking up includes waking up when [(modified SFN of a frame including a subframe × 10) + subframe number of the subframe] modulo length of DRX cycle is equal to [start offset + (n × specified time offset) + (DRX time reference SFN × 10)] modulo length of DRX cycle, and n is updated to n + 1 when [(SFN_M × 10) + subframe number] modulo (length of DRX cycle × specified amount of DRX cycle + specified time offset) is equal to a specified timing value.

[0224]

[0266] In a third aspect, alone or in combination with one or more of the first and second aspects, the specified timing value is equal to (length of DRX cycle × specified amount of DRX cycle) - 1.

[0225]

[0267] FIG. 21 shows exemplary blocks of process 2100, but in some aspects, process 2100 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 21. Additionally, or alternatively, two or more of the blocks of process 2100 may be executed in parallel.

[0226]

[0268] FIG. 22 is a diagram illustrating an exemplary process 2200 that may be performed, for example, by a UE. The exemplary process 2200 is an example where a UE (e.g., UE120, UE1820) performs operations associated with a DRX method for multimedia.

[0227]

[0269] As shown in FIG. 22, in some aspects, process 2200 may include sleeping in relation to a resource cycle (block 2210). For example, a UE (e.g., using communication manager 2608 and / or receiving component 2612 shown in FIG. 26) may sleep in relation to a resource cycle as described above.

[0228]

[0270] As further shown in FIG. 22, in some aspects, process 2200 may include waking up at the start in a subframe, at least in part based on a specified time offset added to an instance of a resource cycle, at least in part based on the number of resource cycles and the length of the resource cycle of the resource cycle, where the specified time offset is at least in part based on the periodicity of a multimedia data burst, and the number of resource cycles is at least in part based on the specified time offset (block 2220). For example, a UE (e.g., using communication manager 140 and / or resource component 2612 shown in FIG. 26) may wake up at the start in a subframe, at least in part based on a specified time offset added to an instance of a resource cycle, at least in part based on the number of resource cycles and the length of the resource cycle of the resource cycle, and as described above, the specified time offset is at least in part based on the periodicity of a multimedia data burst, and the number of resource cycles is at least in part based on the specified time offset.

[0229]

[0271] As further shown in FIG. 22, in some aspects, process 2200 may include receiving a multimedia data burst between subframes (block 2230). For example, a UE (e.g., using communication manager 2608 and / or receiving component 2602 shown in FIG. 26) may receive a multimedia data burst between subframes as described above.

[0230]

[0272] Process 2200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described in connection with one or more other processes described elsewhere in this specification.

[0231]

[0273] In a first aspect, the resource cycle is a cycle for one of a CSI reference signal, a CSI interference measurement resource, or a sounding reference signal.

[0232]

[0274] In a second aspect, alone or in combination with the first aspect, the resource cycle is a cycle for a scheduling request.

[0233]

[0275] In a third aspect, alone or in combination with one or more of the first and second aspects, the resource cycle is a cycle for a configured grant resource or a semi-persistent scheduling resource.

[0234]

[0276] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the resource cycle is a cycle for a channel state information report or a buffer status report.

[0235]

[0277] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the resource cycle is a cycle for physical downlink control channel monitoring or a cycle for physical uplink control channel resources.

[0236]

[0278] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the number of resource cycles is equal to the value obtained by dividing [(10 × system frame number (SFN) of the frame including the subframe + subframe number of the subframe) - (n × specified time offset)] by the length of the resource cycle.

[0237]

[0279] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, waking up includes waking up when (10 × SFN + subframe number + SFN wrap - around offset) modulo the length of the resource cycle is equal to ((n × specified time offset) + start offset) modulo the length of the resource cycle, and n is updated to n + 1 when (10 × SFN + subframe number + SFN wrap - around offset) modulo (resource cycle length × specified amount of resource cycle + specified time offset) is equal to the specified timing value.

[0238]

[0280] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the SFN wrap - around offset is 10240 × m, and m is updated to m + 1 when the SFN returns to 0.

[0239]

[0281] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, waking up includes waking up when (10 × SFN + subframe number + SFN wrap - around offset) modulo the length of the resource cycle is equal to [(n × specified time offset) + start offset+(resource time - reference SFN × 10)] modulo the length of the resource cycle, and n is updated to n + 1 when (10 × resource + subframe number + SFN wrap - around offset) modulo (resource cycle length × specified amount of resource cycle + specified time offset) is equal to the specified timing value.

[0240]

[0282] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the SFN wraparound offset is 10240×m, where m is updated to m + 1 when the SFN returns to the resource time reference SFN, and the resource time reference SFN is 0 or 512.

[0241]

[0283] FIG. 22 shows exemplary blocks of process 2200. However, in some aspects, process 2200 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 22. Additionally, or alternatively, two or more of the blocks of process 2200 may be executed in parallel.

[0242]

[0284] FIG. 23 is a diagram showing an exemplary process 2300 implemented by, for example, a network entity according to the present disclosure. The exemplary process 2300 is an example in which a network entity (e.g., base station 110, network entity 1810) performs operations associated with a DRX method for multimedia.

[0243]

[0285] As further shown in FIG. 23, in some aspects, process 2300 may include preparing to communicate with a UE according to a DRX cycle (block 2310). For example, a network entity (e.g., using communication manager 2908 and / or DRX component 2910 shown in FIG. 29) may prepare to communicate with a UE according to a DRX cycle as described above.

[0244]

[0286] As further shown in FIG. 23, in some aspects, process 2300 may include transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, where the specified time offset is based at least in part on the periodicity of the multimedia data burst and the number of DRX cycles is based at least in part on the specified time offset (block 2320). For example, a network entity (e.g., using communication manager 2908 and / or transmission component 2904 shown in FIG. 29) may transmit a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, and as described above, the specified time offset is based at least in part on the periodicity of the multimedia data burst and the number of DRX cycles is based at least in part on the specified time offset.

[0245]

[0287] Process 2300 may include additional aspects such as any single aspect or any combination of aspects described below and / or described in connection with one or more other processes described elsewhere in this specification.

[0246]

[0288] In a first aspect, the number of DRX cycles is equal to the value obtained by dividing [(10×SFN of the frame containing the subframe + subframe number of the subframe)-(n×specified time offset)] by the length of the DRX cycle.

[0247]

[0289] In a second aspect, transmitting a data burst, either alone or in combination with the first aspect, includes transmitting the data burst when (10×SFN + subframe number) modulo the DRX cycle length is equal to ((n×specified time offset) + start offset) modulo the DRX cycle length, and n is updated to n + 1 when the number of DRX cycles modulo a specified amount of the DRX cycle length is equal to 0.

[0248]

[0290] In a third aspect, the process 2300, either alone or in combination with one or more of the first and second aspects, includes skipping the n + 1 update every other time.

[0249]

[0291] In a fourth aspect, transmitting a data burst, either alone or in combination with one or more of the first to third aspects, includes transmitting the data burst when (10×SFN + subframe number) modulo the DRX cycle length is equal to ((n×specified time offset) + start offset) modulo the DRX cycle length, and n is updated to n + 1 when (10×SFN + subframe number) modulo (DRX cycle length × specified amount of the DRX cycle + specified time offset) is equal to a specified timing value.

[0250]

[0292] In a fifth aspect, the specified timing value, either alone or in combination with one or more of the first to fourth aspects, is equal to (DRX cycle length × specified amount of the DRX cycle) - 1.

[0251]

[0293] In a sixth aspect, transmitting a data burst, either alone or in combination with one or more of the first to fifth aspects, further includes transmitting the data burst based at least in part on an SFN wrap-around offset.

[0252]

[0294] In a seventh aspect, transmitting a data burst, either alone or in combination with one or more of the first to sixth aspects, is subject to the length of the DRX cycle being (10×SFN + subframe number + SFN wrap-around offset), and includes transmitting a data burst when the length of the DRX cycle is equal to ((n×specified time offset) + start offset), and when (DRX cycle length × specified amount of the DRX cycle + specified time offset) is equal to the specified timing value subject to (10×SFN + subframe number + SFN wrap-around offset), n is updated to n + 1.

[0253]

[0295] In an eighth aspect, the SFN wrap-around offset is equal to (10240×m), either alone or in combination with one or more of the first to seventh aspects, and m is updated to m + 1 when the SFN returns to 0.

[0254]

[0296] In a ninth aspect, transmitting a data burst, either alone or in combination with one or more of the first to eighth aspects, is subject to the length of the DRX cycle being (10×SFN + subframe number + SFN wrap-around offset) and includes transmitting a data burst when the length of the DRX cycle is equal to [(n×specified time offset) + start offset + (DRX time reference SFN×10)], and when (DRX cycle length × specified amount of the DRX cycle + specified time offset) is equal to the specified timing value subject to (10×SFN + subframe number + SFN wrap-around offset), n is updated to n + 1.

[0255]

[0297] In a tenth aspect, the SFN wrap-around offset is 10240×m, either alone or in combination with one or more of the first to ninth aspects, m is updated to m + 1 when the SFN returns to the DRX time reference SFN, and the DRX time reference SFN is 0 or 512.

[0256]

[0298] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 2300 includes transmitting an indication of a DRX time reference SFN.

[0257]

[0299] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, an anchor cycle including a DRX cycle also includes two or more leap cycles.

[0258]

[0300] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 2300 includes transmitting an indication of two or more leap cycles.

[0259]

[0301] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 2300 includes transmitting an indication of the timing of two or more leap cycles.

[0260]

[0302] FIG. 23 shows exemplary blocks of process 2300, but in some aspects, process 2300 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 23. Additionally, or alternatively, two or more of the blocks of process 2300 may be executed in parallel.

[0261]

[0303] FIG. 24 is a diagram showing an exemplary process 2400 implemented by, for example, a network entity according to the present disclosure. The exemplary process 2400 is an example in which a network entity (e.g., base station 110, network entity 1810) performs operations associated with a DRX method for multimedia.

[0262]

[0304] As further shown in FIG. 24, in some aspects, process 2400 may include preparing to communicate with a UE according to a DRX cycle (block 2410). For example, a network entity (e.g., using communication manager 2908 and / or DRX component 2910 shown in FIG. 29) may prepare to communicate with a UE according to a DRX cycle as described above.

[0263]

[0305] As further shown in FIG. 24, in some aspects, process 2400 may include transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles being based at least in part on the specified time offset (block 2420). For example, a network entity (e.g., using communication manager 2908 and / or DRX component 2910 shown in FIG. 29) may transmit a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, and as described above, the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset.

[0264]

[0306] Process 2400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere in this specification.

[0265]

[0307] In a first aspect, transmitting a data burst includes transmitting a data burst when (SFN of a frame including subframes × amount of subframes per frame) + subframe number of the subframe is equal to [DRX time reference SFN × amount of subframes per subframe + start offset + number of DRX on durations × length of the DRX cycle + floor (number of DRX on durations / specified time offset) × specified amount of the DRX cycle] modulo (1024 × amount of subframes per frame).

[0266]

[0308] In a second aspect, transmitting a data burst, alone or in combination with the first aspect, includes transmitting a data burst when [(modified SFN of a frame including subframes × 10) + subframe number of the subframe] modulo length of the DRX cycle is equal to [start offset + (n × specified time offset) + (DRX time reference SFN × 10)] modulo length of the DRX cycle, and n is updated to n + 1 when [(SFN_M × 10) + subframe number] modulo (length of the DRX cycle × specified amount of the DRX cycle + specified time offset) is equal to a specified timing value.

[0267]

[0309] In a third aspect, transmitting a data burst, alone or in combination with one or more of the first and second aspects, the specified timing value is equal to (length of the DRX cycle × specified amount of the DRX cycle) - 1.

[0268]

[0310] FIG. 24 shows exemplary blocks of process 2400, but in some aspects, process 2400 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 24. Additionally, or alternatively, two or more of the blocks of process 2400 may be executed in parallel.

[0269]

[0311] FIG. 25 is a diagram showing an exemplary process 2500 implemented, for example, by a network entity. The exemplary process 2500 is an example where a network entity (e.g., base station 110, network entity 1810) performs operations associated with a DRX method for multimedia.

[0270]

[0312] As shown in FIG. 25, in some aspects, process 2500 may include preparing to communicate with a UE according to a resource cycle (block 2510). For example, a network entity (e.g., using communication manager 2908 and / or transmission component 2912 shown in FIG. 29) may prepare to communicate with a UE according to a resource cycle as described above.

[0271]

[0313] As further shown in FIG. 25, in some aspects, process 2500 may include transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to an instance of a resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, the specified time offset being based at least in part on the periodicity of the multimedia data burst, the number of resource cycles being based at least in part on the specified time offset, and the number of resource cycles being based at least in part on the specified time offset (block 2520). For example, a network entity (e.g., using communication manager 2908 and / or transmission component 2904 shown in FIG. 29) may transmit a data burst at the start in a subframe based at least in part on a specified time offset added to an instance of a resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, the specified time offset being based at least in part on the periodicity of the multimedia data burst, the number of resource cycles being based at least in part on the specified time offset, and the number of resource cycles being based at least in part on the specified time offset.

[0272]

[0314] Process 2500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described in connection with one or more other processes described elsewhere in this specification.

[0273]

[0315] In a first aspect, the resource cycle is a cycle for one of a CSI reference signal, a CSI interference measurement resource, or a sounding reference signal.

[0274]

[0316] In a second aspect, alone or in combination with the first aspect, the resource cycle is a cycle for a scheduling request.

[0275]

[0317] In a third aspect, alone or in combination with one or more of the first and second aspects, the resource cycle is a cycle for configured grant resources or semi-persistent scheduling resources.

[0276]

[0318] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the resource cycle is a cycle for channel state information reporting or buffer status reporting.

[0277]

[0319] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the resource cycle is a cycle for physical downlink control channel monitoring or a cycle for physical uplink control channel resources.

[0278]

[0320] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the number of resource cycles is equal to the value obtained by dividing [(10 × the system frame number (SFN) of the frame including the subframe + the subframe number of the subframe) - (n × the specified time offset)] by the length of the resource cycle.

[0279]

[0321] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, transmitting a data burst includes transmitting a data burst when (10 × SFN + subframe number + SFN wrap-around offset) modulo the length of the resource cycle is equal to ((n × the specified time offset) + start offset) modulo the length of the resource cycle, and n is updated to n + 1 when (10 × SFN + subframe number + SFN wrap-around offset) modulo (the length of the resource cycle × the specified amount of the resource cycle + the specified time offset) is equal to the specified timing value.

[0280]

[0322] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the SFN wraparound offset is 10240×m, where m is updated to m + 1 when the SFN returns to 0.

[0281]

[0323] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, transmitting a data burst is based on the length of a resource cycle (10×SFN + subframe number + SFN wraparound offset), and includes transmitting a data burst when it is equal to [(n×specified time offset) + start offset + (resource time reference SFN×10)], and n is updated to n + 1 when (length of resource cycle×specified amount of resource cycle + specified time offset) based on (10×resource + subframe number + SFN wraparound offset) is equal to a specified timing value.

[0282]

[0324] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the SFN wraparound offset is 10240×m, where m is updated to m + 1 when the SFN returns to the resource time reference SFN, and the resource time reference SFN is 0 or 512.

[0283]

[0325] FIG. 25 shows exemplary blocks of process 2500, but in some aspects, process 2500 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 25. Additionally, or alternatively, two or more of the blocks of process 2500 may be executed in parallel.

[0284]

[0326] FIG. 26 is a diagram of an exemplary apparatus 2600 for wireless communication according to the present disclosure. The apparatus 2600 may be a UE (e.g., UE120, UE1820), or the UE may include the apparatus 2600. In some aspects, the apparatus 2600 includes a receiving component 2602 and a transmitting component 2604 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 2600 may communicate with another apparatus 2606 (such as a UE, a base station, a network entity, or another wireless communication device) using the receiving component 2602 and the transmitting component 2604. Further shown, the apparatus 2600 may include a communication manager 2608. The communication manager 2608 may control and / or otherwise manage one or more operations of the receiving component 2602 and / or the transmitting component 2604. In some aspects, the communication manager 2608 may include one or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE described in connection with FIG. 2. The communication manager 2608 may be the communication manager 140 shown in FIGS. 1 and 2, or may be similar to the communication manager 140. For example, in some aspects, the communication manager 2608 may be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 2608 may include the receiving component 2602 and / or the transmitting component 2604. The communication manager 2608 may include a DRX component 2610 and / or a resource component 2612, among other examples.

[0285]

[0327] In some aspects, apparatus 2600 may be configured to perform one or more operations described herein with respect to FIGS. 1-18. Additionally or alternatively, apparatus 2600 may be configured to perform one or more processes described herein, such as process 2000 of FIG. 20, process 2100 of FIG. 21, process 2200 of FIG. 22, or combinations thereof. In some aspects, apparatus 2600 and / or one or more components shown in FIG. 26 may include one or more components of the UE described with respect to FIG. 2. Additionally or alternatively, one or more components shown in FIG. 26 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more components of a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be stored in a non-transitory computer-readable medium and implemented as instructions or code executable by a controller or processor to perform the functions or operations of the component.

[0286]

[0328] Receiving component 2602 may receive communications from apparatus 2606, such as a reference signal, control information, data communications, or combinations thereof. Receiving component 2602 may provide the received communications to one or more other components of apparatus 2600. In some aspects, receiving component 2602 may perform signal processing (among other examples, in particular filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and provide the processed signals to one or more other components of apparatus 2600. In some aspects, receiving component 2602 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described with respect to FIG. 2.

[0287]

[0329] The transmitting component 2604 can transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 2606. In some aspects, one or more other components of the device 2600 can generate a communication and provide the generated communication to the transmitting component 2604 for transmission to the device 2606. In some aspects, the transmitting component 2604 can perform signal processing (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communication and transmit the processed signal to the device 2606. In some aspects, the transmitting component 2604 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described with respect to FIG. 2. In some aspects, the transmitting component 2604 may be collocated with the receiving component 2602 in a transceiver.

[0288]

[0330] In some aspects, the DRX component 2610 can cause the device 2600 to sleep in relation to a DRX cycle. The DRX component 2610 can wake up the device 2600 at the start in a subframe based at least in part on the number of DRX cycles of the DRX cycle and a specified time offset added to the on duration of the DRX cycle based at least in part on the length of the DRX cycle, where the specified time offset is based at least in part on the periodicity of the multimedia data burst and the number of DRX cycles is based at least in part on the specified time offset. The receiving component 2602 can receive a multimedia data burst during a subframe.

[0289]

[0331] The receiving component 2602 can receive an indication of a DRX time reference SFN, an indication of two or more leap cycles, and / or an indication of the timing of two or more leap cycles.

[0290]

[0332] In some aspects, the DRX component 2610 may cause the device 2600 to sleep in relation to a DRX cycle. The DRX component 2610 may wake up the device 2600 at the start in a subframe based at least in part on the number of DRX cycles of the DRX cycle and a specified time offset added to the on - duration of the DRX cycle based at least in part on the DRX time reference SFN. The specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset. The receiving component 2602 may receive a multimedia data burst during a subframe.

[0291]

[0333] In some aspects, the resource component 2612 may cause the device 2600 to sleep in relation to a resource cycle. The resource component 2612 may wake up the device 2600 at the start in a subframe based at least in part on the number of resource cycles of the resource cycle and a specified time offset added to an instance of the resource cycle based at least in part on the length of the resource cycle. The specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of resource cycles is based at least in part on the specified time offset. The receiving component 2602 may receive a multimedia data burst during a subframe.

[0292]

[0334] The number and arrangement of the components shown in FIG. 26 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components compared to the components shown in FIG. 26. Further, two or more of the components shown in FIG. 26 may be implemented within a single component, or a single component shown in FIG. 26 may be implemented as a plurality of distributed components. Additionally, alternatively or instead, a set of (one or more) components shown in FIG. 26 may perform one or more functions described as being performed by another set of components shown in FIG. 26.

[0293]

[0335] FIG. 27 is a diagram showing an example 2700 of a hardware implementation form for an apparatus 2705 using a processing system 2710. The apparatus 2705 may be a UE (e.g., UE120, UE1820).

[0294]

[0336] The processing system 2710 may be implemented using a bus architecture, generally represented by a bus 2715. The bus 2715 may include any number of interconnecting buses and bridges, depending on the specific application example of the processing system 2710 and overall design constraints. The bus 2715 links together various circuits including one or more processors and / or hardware components represented by a processor 2720, the illustrated components, and a computer-readable medium / memory 2725. The bus 2715 may also link various other circuits such as a timing source, peripherals, a voltage regulator, and / or a power management circuit.

[0295]

[0337] The processing system 2710 may be coupled to a transceiver 2730. The transceiver 2730 is coupled to one or more antennas 2735. The transceiver 2730 provides means for communicating with various other devices via a transmission medium. The transceiver 2730 receives signals from one or more antennas 2735, extracts information from the received signals, and provides the extracted information to the processing system 2710, specifically the receiving component 2602. In addition, the transceiver 2730 receives information from the processing system 2710, particularly the transmitting component 2604, and generates signals to be applied to one or more antennas 2735 based at least in part on the received information.

[0296]

[0338] The processing system 2710 includes a processor 2720 coupled to a computer-readable medium / memory 2725. The processor 2720 is responsible for general processing including the execution of software stored in the computer-readable medium / memory 2725. The software, when executed by the processor 2720, causes the processing system 2710 to perform the various functions described herein for any particular device. The computer-readable medium / memory 2725 may also be used to store data that is manipulated by the processor 2720 when executing the software. The processing system further includes at least one of the illustrated components. The components may be software modules that are executed in the processor 2720 and reside / stored in the computer-readable medium / memory 2725, one or more hardware modules coupled to the processor 2720, or some combination thereof.

[0297]

[0339] In some aspects, the processing system 2710 may be a component of the UE 120 and may include the memory 282 and / or at least one of the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the apparatus 2705 for wireless communication includes means for sleeping in relation to a DRX cycle and means for waking up at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, wherein the specified time offset is based at least in part on the periodicity of multimedia data bursts and the number of DRX cycles is based at least in part on the specified time offset. The apparatus 2705 includes means for receiving a multimedia data burst between subframes. In some aspects, the apparatus 2705 includes means for sleeping in relation to a DRX cycle, means for waking up at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the DRX time reference system frame number (SFN), wherein the specified time offset is based at least in part on the periodicity of multimedia data bursts and the number of DRX cycles is based at least in part on the specified time offset, and / or means for receiving a multimedia data burst between subframes. In some aspects, the apparatus 2705 includes means for sleeping in relation to a resource cycle, means for waking up at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, wherein the specified time offset is based at least in part on the periodicity of multimedia data bursts and the number of resource cycles is based at least in part on the specified time offset, and / or means for receiving a multimedia data burst between subframes.The above means may be one or more of the above components of the processing system 2710 of the apparatus 2600 and / or the apparatus 2705 configured to perform the functions listed by the above means. As described elsewhere in this specification, the processing system 2710 may include a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280. In one configuration, the foregoing means may be a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280 configured to perform the functions and / or operations recited herein.

[0298]

[0340] FIG. 27 is provided as an example. Other examples may be different from those described in relation to FIG. 27.

[0299]

[0341] FIG. 28 is a diagram illustrating an example 2800 of a code and circuit implementation for an apparatus 2805 according to the present disclosure. The apparatus 2805 may be a UE (e.g., UE120, UE1820), or the UE may include the apparatus 2805.

[0300]

[0342] As shown in FIG. 28, the apparatus 2805 may include circuitry (circuitry 2820) for sleeping in relation to a DRX cycle or a resource cycle. For example, the circuitry 2820 may enable the apparatus 2805 to sleep in relation to a DRX cycle or a resource cycle.

[0301]

[0343] As shown in FIG. 28, the apparatus 2805 may include code (code 2825) for sleeping in relation to a DRX cycle or a resource cycle stored in a computer-readable medium 2725. For example, the code 2825 may cause the transceiver 2730 to sleep in relation to a DRX cycle or a resource cycle when executed by the processor 2720.

[0302]

[0344] As shown in FIG. 28, device 2805 may include circuitry for waking up at the start in a subframe, based at least in part on a specified time offset added to the on-duration of a DRX cycle (or resource cycle) based at least in part on the number of DRX cycles (or resource cycles) of the DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), the specified time offset being based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles (or resource cycles) being based at least in part on the specified time offset (circuitry 2830). For example, circuitry 2830 may enable device 2805 to wake up at the start in a subframe, based at least in part on a specified time offset added to the on-duration of a DRX cycle (or resource cycle) based at least in part on the number of DRX cycles (or resource cycles) of the DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), the specified time offset being based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles (or resource cycles) being based at least in part on the specified time offset.

[0303]

[0345] As shown in FIG. 28, apparatus 2805 may include code for waking up at the start in a subframe, based at least in part on the number of DRX cycles (or resource cycles) of a DRX cycle (or resource cycle) and a specified time offset added to the on-duration of the DRX cycle (or resource cycle), where the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles (or resource cycles) is based at least in part on the specified time offset (code 2835). For example, when executed by processor 2720, code 2835 may cause processor 2720 to wake up transceiver 2730 at the start in a subframe, based at least in part on the number of DRX cycles (or resource cycles) of a DRX cycle (or resource cycle) and a specified time offset added to the on-duration of the DRX cycle (or resource cycle), where the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles (or resource cycles) is based at least in part on the specified time offset.

[0304]

[0346] As shown in FIG. 28, apparatus 2805 may include circuitry for receiving a multimedia data burst during a subframe. For example, circuitry 2840 may enable apparatus 2805 to receive a multimedia data burst during a subframe.

[0305]

[0347] As shown in FIG. 28, apparatus 2805 may include code for receiving a multimedia data burst during a subframe, stored in computer-readable medium 2725. For example, when executed by processor 2720, code 2845 may cause processor 2720 to receive a multimedia data burst during a subframe at transceiver 2730.

[0306]

[0348] FIG. 28 is provided as an example. Other examples may be different from those described in relation to FIG. 28.

[0307]

[0349] FIG. 29 is a diagram of an exemplary apparatus 2900 for wireless communication according to the present disclosure. The apparatus 2900 may be a network entity (e.g., base station 110, network entity 1810), or the network entity may include the apparatus 2900. In some aspects, the apparatus 2900 includes a receiving component 2902 and a transmitting component 2904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 2900 may communicate with another apparatus 2906 (such as a UE, a base station, or another wireless communication device) using the receiving component 2902 and the transmitting component 2904. Further shown, the apparatus 2900 may include a communication manager 2908. The communication manager 2908 may control and / or otherwise manage one or more operations of the receiving component 2902 and / or the transmitting component 2904. In some aspects, the communication manager 2908 may include one or more antennas, a modem, a controller / processor, a memory, or a combination thereof of the network entity described in relation to FIG. 2. The communication manager 2908 may be the communication manager 150 shown in FIGS. 1 and 2, or may be similar to the communication manager 150. For example, in some aspects, the communication manager 2908 may be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 2908 may include the receiving component 2902 and / or the transmitting component 2904. The communication manager 2908 may include, among other examples, a DRX component 2910 and / or a resource component 2912.

[0308]

[0350] In some aspects, apparatus 2900 may be configured to perform one or more operations described herein in connection with FIGS. 1-18. Additionally or alternatively, apparatus 2900 may be configured to implement one or more processes described herein, such as process 2300 of FIG. 23, process 2400 of FIG. 24, process 2500 of FIG. 25, or combinations thereof. In some aspects, apparatus 2900, and / or one or more components shown in FIG. 29, may include one or more components of the network entity described in connection with FIG. 2. Additionally or alternatively, one or more components shown in FIG. 29 may be implemented in one or more components described in connection with FIG. 2. Additionally or alternatively, one or more components of a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0309]

[0351] Receiver component 2902 may receive communications from apparatus 2906, such as a reference signal, control information, data communication, or a combination thereof. Receiver component 2902 may provide the received communication to one or more other components of apparatus 2900. In some aspects, receiver component 2902 may perform signal processing on the received communication (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signal to one or more other components of apparatus 2900. In some aspects, receiver component 2902 may include one or more of the antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the network entity described in connection with FIG. 2.

[0310]

[0352] The transmitting component 2904 may transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 2906. In some aspects, one or more other components of the device 2900 may generate a communication and may provide the generated communication to the transmitting component 2904 for transmission to the device 2906. In some aspects, the transmitting component 2904 may perform signal processing (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communication and may transmit the processed signal to the device 2906. In some aspects, the transmitting component 2904 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network entities described with respect to FIG. 2. In some aspects, the transmitting component 2904 may be collocated with the receiving component 2902 in a transceiver.

[0311]

[0353] In some aspects, the DRX component 2910 may prepare for communication with the UE 120 according to a DRX cycle. The transmitting component 2904 may transmit a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycle counts and the length of the DRX cycle of the DRX cycle, the specified time offset being based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycle counts being based at least in part on the specified time offset.

[0312]

[0354] The transmitting component 2904 may transmit an indication of a DRX time reference SFN, an indication of two or more leap cycles, and / or an indication of the timing of two or more leap cycles.

[0313]

[0355] In some aspects, the DRX component 2910 may prepare to communicate with the UE according to a DRX cycle. The transmission component 2904 may transmit a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle. The specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset.

[0314]

[0356] In some aspects, the resource component 2912 may prepare to communicate with the UE according to a resource cycle. The transmission component 2904 may transmit a data burst at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle. The specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of resource cycles is based at least in part on the specified time offset, and the number of resource cycles is based at least in part on the specified time offset.

[0315]

[0357] The number and configuration of the components shown in FIG. 29 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently configured components compared to the components shown in FIG. 29. Further, two or more of the components shown in FIG. 29 may be implemented within a single component, or a single component shown in FIG. 29 may be implemented as a plurality of distributed components. Additionally, alternatively or instead, a set of (one or more) components shown in FIG. 29 may perform one or more functions described as being performed by another set of components shown in FIG. 29.

[0316]

[0358] FIG. 30 is a diagram showing an example 3000 of a hardware implementation form for an apparatus 3005 using a processing system 3010. The apparatus 3005 may be a network entity (e.g., base station 110, network entity 1810).

[0317]

[0359] The processing system 3010 may be implemented using a bus architecture generally represented by a bus 3015. The bus 3015 may include any number of interconnecting buses and bridges depending on the specific application example of the processing system 3010 and overall design constraints. The bus 3015 links various circuits including one or more processors and / or hardware components represented by a processor 3020, the illustrated components, and a computer-readable medium / memory 3025 to each other. The bus 3015 may also link various other circuits such as a timing source, peripherals, a voltage regulator, and / or a power management circuit.

[0318]

[0360] The processing system 3010 may be coupled to a transceiver 3030. The transceiver 3030 is coupled to one or more antennas 3035. The transceiver 3030 provides means for communicating with various other devices via a transmission medium. The transceiver 3030 receives signals from one or more antennas 3035, extracts information from the received signals, and provides the extracted information to the processing system 3010, specifically to the receiving component 2902. In addition, the transceiver 3030 receives information from the processing system 3010, particularly the transmitting component 2904, and generates signals to be applied to one or more antennas 3035 based at least in part on the received information.

[0319]

[0361] The processing system 3010 includes a processor 3020 coupled to a computer-readable medium / memory 3025. The processor 3020 is responsible for general processing including the execution of software stored in the computer-readable medium / memory 3025. The software, when executed by the processor 3020, causes the processing system 3010 to perform the various functions described herein for any particular device. The computer-readable medium / memory 3025 may also be used to store data that is manipulated by the processor 3020 when executing the software. The processing system further includes at least one of the illustrated components. The components may be software modules executed in the processor 3020 and residing / stored in the computer-readable medium / memory 3025, one or more hardware modules coupled to the processor 3020, or some combination thereof.

[0320]

[0362] In some aspects, the processing system 3010 may be a component of the UE 120 and may include at least one of the memory 282 and / or the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, an apparatus 3005 for wireless communication includes means for preparing to communicate with a UE according to a DRX cycle, and means for transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, wherein the specified time offset is based at least in part on the periodicity of a multimedia data burst and the number of DRX cycles is based at least in part on the specified time offset. In some aspects, the apparatus 3005 may include means for preparing to communicate with a UE according to a DRX cycle, and means for transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, wherein the specified time offset is based at least in part on the periodicity of a multimedia data burst and the number of DRX cycles is based at least in part on the specified time offset. In some aspects, the apparatus 3005 may include means for preparing to communicate with a UE according to a resource cycle and / or means for transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, wherein the specified time offset is based at least in part on the periodicity of a multimedia data burst and the number of resource cycles is based at least in part on the specified time offset and the number of resource cycles is based at least in part on the specified time offset.The above means may be one or more of the above-described components of the processing system 3010 of the apparatus 2900 and / or the apparatus 3005 configured to perform the functions recited by the above means. As described elsewhere herein, the processing system 3010 may include a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280. In one configuration, the foregoing means may be a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280 configured to perform the functions and / or operations recited herein.

[0321]

[0363] FIG. 30 is provided as an example. Other examples may be different from those described in connection with FIG. 30.

[0322]

[0364] FIG. 31 is a diagram illustrating an example 3100 of a code and circuit implementation for an apparatus 3105 according to the present disclosure. The apparatus 3105 may be a network entity (e.g., base station 110, network entity 1810), or the network entity may include the apparatus 3105.

[0323]

[0365] As shown in FIG. 31, the apparatus 3105 may include a circuit (circuit 3120) for preparing to communicate with a UE according to a DRX cycle or a resource cycle. For example, the circuit 3120 may enable the apparatus 3105 to prepare to communicate with the UE according to a DRX cycle or a resource cycle.

[0324]

[0366] As shown in FIG. 31, the apparatus 3105 may include code (code 3125) stored in a computer-readable medium 3025 for preparing to communicate with a UE according to a DRX cycle or a resource cycle. For example, when executed by a processor 3020, the code 3125 may cause the processor 3020 to prepare to communicate with the UE according to a DRX cycle or a resource cycle.

[0325]

[0367] As shown in FIG. 31, apparatus 3105 may include circuitry for transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle (or resource cycle) based at least in part on the number of DRX cycles (or resource cycles) of the DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles (or resource cycles) being based at least in part on the specified time offset (circuitry 3130). For example, circuitry 3130 may enable apparatus 3105 to transmit a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle (or resource cycle) based at least in part on the number of DRX cycles (or resource cycles) of the DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles (or resource cycles) being based at least in part on the specified time offset.

[0326]

[0368] As shown in FIG. 31, apparatus 3105 may include code stored in computer-readable medium 3025 that causes, based at least in part on the number of DRX (or resource cycle) cycles of a DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), a specified time offset added to the on-duration of the DRX cycle (or resource cycle), to transmit a data burst at the start in a subframe, the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles being based at least in part on the specified time offset (code 3135). For example, when executed by processor 3020, code 3135 may cause processor 3020 and transceiver 3030 to transmit a data burst at the start in a subframe, based at least in part on the number of DRX (or resource cycle) cycles of a DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), and based at least in part on a specified time offset added to the on-duration of the DRX cycle (or resource cycle), the specified time offset being based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles being based at least in part on the specified time offset.

[0327]

[0369] As shown in FIG. 31, apparatus 3105 may include circuitry for transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle (or resource cycle) based at least in part on the number of DRX cycles (or resource cycles) of the DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), the specified time offset being based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles (or resource cycles) being based at least in part on the specified time offset (circuitry 3130). For example, circuitry 3130 may enable apparatus 3105 to transmit a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of a DRX cycle (or resource cycle) based at least in part on the number of DRX cycles (or resource cycles) of the DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), the specified time offset being based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles (or resource cycles) being based at least in part on the specified time offset.

[0328]

[0370] As shown in FIG. 31, the apparatus 3105 may include code stored in a computer-readable medium 3025 that, based at least in part on the DRX cycle (or resource cycle) number of a DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), adds a specified time offset to the on-duration of the DRX cycle (or resource cycle), and based at least in part on the specified time offset, transmits a data burst at the start in a subframe, where the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles (or resource cycles) is based at least in part on the specified time offset (code 3135). For example, when executed by a processor 3020, the code 3135 causes the processor 3020 to cause the transceiver 3030 to transmit a data burst at the start in a subframe, based at least in part on the DRX cycle (or resource cycle) number of a DRX cycle (or resource cycle) and the length of the DRX cycle (or resource cycle), adding a specified time offset to the on-duration of the DRX cycle (or resource cycle), where the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles (or resource cycles) is based at least in part on the specified time offset.

[0329]

[0371] FIG. 31 is provided as an example. Other examples may be different from those described in connection with FIG. 31.

[0330]

[0372] FIG. 32 is a diagram showing an example 3200 of a leap offset pattern according to the present disclosure.

[0331]

[0373] In some aspects, the configuration may involve multiple DRX cycles. The DRX cycle may be a DRX long cycle. Example 3200 shows a 16 ms DRX long cycle for 60 fps XR traffic. Example 3200 shows a 2 ms DRX start offset. The total of the three DRX cycles is 50 ms.

[0332]

[0374] The DRX cycle may include a DRX leap offset such as 1 ms. A 1 ms leap offset is added to a 16 ms DRX long cycle to result in a 17 ms DRX cycle. In some aspects, the first leap offset pattern 3202 includes a leap offset pattern of (0 ms, 1 ms, 1 ms). Thus, the DRX cycle lengths are 16 ms, 17 ms, and 17 ms, for a total of 50 ms. The first leap offset pattern 3202 starts from a 16 ms DRX cycle, and thus, the UE wakes up before XR traffic arrives. In some aspects, the first leap offset pattern 3204 includes a leap offset pattern of (1 ms, 1 ms, 0 ms). Thus, the DRX cycle lengths are 17 ms, 17 ms, and 16 ms. The first leap offset pattern 3204 starts from a 17 ms DRX cycle, and thus, the UE wakes up after XR traffic arrives. The UE may further wake up based at least in part on an accumulated DRX offset that includes a DRX offset equal to the DRX start offset, such as drx-Offset(0)=drx-StartOffset and drx-Offset(n)=X(n - 1)+drx-LeapOffset{(n - 1)mod N}, m≧1. In some aspects, the UE may sequentially search the next nth DRX cycle, and the UE may wake up during a subframe if [(SFN×10)+subframe number]=10240 modulo {drx-LongCycle×n+drx-Offset(n)+10×drx-timeReferenceSFN}. In some aspects, the UE may sequentially search the next nth DRX cycle, and the UE may wake up during a subframe if (10240×m)+[(SFN×10)+subframe number]=10240 modulo {drx-LongCycle×n+drx-Offset(n)+10×drx-timeReferenceSFN}.

[0333]

[0375] As described above, FIG. 32 is provided as an example. Other examples may be different from those described with respect to FIG. 32.

[0334]

[0376] FIG. 33A is a diagram showing an example 3300 of a subframe index according to the present disclosure.

[0335]

[0377] Example 3300 shows a table including a leap offset used for a subframe index. The subframe index may correspond to a DRX cycle index. For example, when index n = 1, the subframe index ([SFN × 10) + subframe number]) = 16 and the leap offset = 0. When index n = 2, the subframe index = 33 and the leap offset = 1. When index n = 3, the subframe index = 50 and the leap offset = 1. The leap offset pattern is (0 ms, 1 ms, 1 ms).

[0336]

[0378] As described above, FIG. 33A is provided as an example. Other examples may be different from those described with respect to FIG. 33A.

[0337]

[0379] FIG. 33B is a diagram showing an example 3302 of a subframe index according to the present disclosure.

[0338]

[0380] As described in connection with FIG. 15, the sequential search DRX cycle formula (e.g., the formula for searching for the next nth DRX cycle) may involve a rational number for drx-ShortCycle or the DRX cycle. The rational number (e.g., A / B) may represent a non-integer value for drx-ShortCycle. In an example where drx-ShortCadence = 60 fps or 60 Hz (DRX cycles of 16 ms, 16 ms, and 17 ms), drx-LongCycle = 1000 / 60 = 50 / 3 (16 and 2 Over 3). The DRX start offset may be 0 ms, and the subframe index may start immediately before the XR data burst.

[0339]

[0381] In some aspects, the equation for non-integer DRX cycles may involve a modulo with the hyperframe length (10240) + rational DRX cycles. This equation may include a floor operation that aligns the DRX cycle to the subframe granularity (e.g., 1 ms). A ceiling operation may be used instead of the floor operation. This equation may be [floor(DRX long cycle × n) + DRX start offset + (10 × DRX time reference SFN)] modulo [(SFN × numberOfSubframesPerFrame) + subframe number within the frame] = 10240. The number of subframes per frame may be 10, and the DRX time reference SFN may be 0 or 512 (1 bit). Example 3302 in FIG. 33B shows the values of the subframe index. The table values may be valid when the subframe index, such as (SFN × 10) + subframe number, is greater than 10240.

[0340]

[0382] As described above, FIG. 33B is provided as an example. Other examples may be different from those described with respect to FIG. 33B.

[0341]

[0383] FIG. 34 is a diagram showing an example 3400 of backward compatibility according to the present disclosure.

[0342]

[0384] In some aspects, an extended DRX equation solution for the SFN wrap-around problem, such as adding 10240 × m to the DRX equation, may not be compatible with the legacy DRX equation for some DRX cycles. Some DRX short cycles, such as 3 ms, 6 ms, 7 ms, 14 ms, 30 ms, and 35 ms, may not be compatible with the SFN wrap-around solution. For example, drx-ShortCycle = 6 ms (10240 / 6 = 1706.6666). DRX long cycles of 60 ms and 70 ms may also not have backward compatibility. The legacy DRX equation and the extended DRX equation may behave differently under these DRX cycles.

[0343]

[0385] Example 3400 shows a first table 3402 indicating whether the DRX short cycle has backward compatibility ("O") or does not have backward compatibility ("X"). Example 3400 shows a first table 3404 indicating whether the DRX long cycle has backward compatibility ("O") or does not have backward compatibility ("X").

[0344]

[0386] As described above, FIG. 34 is provided as an example. Other examples may be different from those described with respect to FIG. 34.

[0345]

[0387] FIG. 35 is a diagram showing an example 3500 of dealing with backward compatibility according to the present disclosure.

[0346]

[0388] Example 3500 shows that an extended UE configured to operate after 3GPP standard release 18 can operate using a solution to the SFN wraparound problem, while a legacy UE configured to operate in 3GPP standard releases 15 - 17 cannot operate using a solution to the SFN wraparound problem. This solution may involve an SFN wraparound offset considering the cumulative length of the hyperframe.

[0347]

[0389] In some aspects, the UE may send an indication of the UE's ability to handle the SFN wraparound problem using the SFN wraparound offset in the capability message. The extended UE may indicate the ability, while the legacy UE may not. In some aspects, the indication may be an information element within the capability message. The UE may receive a legacy DRX configuration that does not use the SFN wraparound offset or an extended DRX configuration that uses the SFN wraparound offset.

[0348]

[0390] As described above, FIG. 35 is provided as an example. Other examples may be different from those described with respect to FIG. 35.

[0349]

[0391] FIG. 36 is a diagram showing an example 3600 associated with the use of an SFN wrap-around offset according to the present disclosure. As shown in FIG. 36, a network entity 3610 (e.g., base station 110) may communicate with a UE 3620 (e.g., UE 120). The network entity 3610 and the UE 3620 may be part of a wireless network (e.g., wireless network 100). The UE 3620 may be an extended UE capable of using an SFN wrap-around offset considering the cumulative length of a hyperframe.

[0350]

[0392] As indicated by reference numeral 3625, the UE 3620 may transmit, in a capability message, an indication of the capability of the UE 3620 to use an SFN wrap-around offset. As indicated by reference numeral 3630, the network entity 3610 may transmit a configuration to use an SFN wrap-around offset (for the extended UE) based at least in part on the capability message.

[0351]

[0393] In some aspects, as indicated by reference numeral 3635, the UE may wake up at the start of a subframe based at least in part on a subframe index of a resource cycle (e.g., a DRX cycle) and an SFN wrap-around offset considering the cumulative length of a hyperframe. The SFN wrap-around offset may be equal to the length of the hyperframe × m, and the length of the hyperframe may be equal to 10240. As indicated by reference numeral 3640, the UE may receive a data burst (e.g., a multimedia data burst) between subframes.

[0352]

[0394] In some aspects, UE 3620 may wake up when the subframe index is the subframe index of the subframe that UE 3620 should wake up considering the SFN wrap-around offset. For example, UE 3620 may wake up when [(SFN × 10) + subframe number + 10240 × m × k] modulo (drx-ShortCycle) = [(drx-StartOffset(i)) + (drx-timeReferenceSFN × 10)] modulo (drx-ShortCycle). Since the SFN wrap-around offset (10240 × m) is activated for UE 3620, the value of k is 1. In some aspects, whenever the SFN becomes the reference SFN value (drx-timeReferenceSFN is 0 or 512), the value m = m + 1. That is, the subframe index may be equal to [(SFN of the frame containing the subframe × 10) + subframe number of the subframe], and m is updated to m + 1 when the SFN returns to 0, or when the SFN returns to the time reference SFN which may be 0 or 512. In some aspects, the UE may wake up when (subframe index + SFN wrap-around offset) modulo (resource cycle length) = [(start offset + (time reference SFN × 10)] modulo (resource cycle length). The start offset may be drx-StartOffset.

[0353]

[0395] In some aspects, the network entity 3610 may send an indication of k = 0 and drx - timeReferenceSFN = 0 for legacy DRX calculations and an indication of k = 1 for extended DRX calculations. By setting k = 0, the network entity 3610 may support legacy UEs, and by setting k = 1, the network entity may support extended UEs for XR. The network entity 3610 may set the value of k within the configuration by means of RRC signaling, DCI, or MAC CE. In some aspects, when the SFN becomes the time - reference SFN value and the network entity 3610 configures the extended DRX function, m may increase by 1 only (m = m + 1). Otherwise, m may not increase and may be fixed at 0 (m = 0).

[0354]

[0396] In some aspects, the UE 3620 may not need to change the extended DRX formula, and the network entity 3610 may not configure a DRX cycle that is not backward - compatible with legacy UEs. For example, the configuration may indicate which DRX short cycles the SFN wrap - around offset is applicable to or not applicable to, and which DRX long cycles the SFN wrap - around offset is applicable to or not applicable to. The UE 3620 may then apply the SFN wrap - around offset for applicable DRX short cycles and DRX long cycles, and may not apply the SFN wrap - around offset for inapplicable DRX short cycles and DRX long cycles.

[0355]

[0397] As described above, FIG. 36 is provided as an example. Other examples may be different from those described with respect to FIG. 36.

[0356]

[0398] FIG. 37 is a diagram showing an example 3700 of using the SFN wrap - around offset according to the present disclosure.

[0357]

[0399] Example 3700 indicates the arrival of a multimedia data burst arrival at a rate of 120 Hz. In Example 3700, drx-StartOffset is set to 0. The UE may configure a DRX cycle for the cadence of the data burst, such as every 8.33 ms at 120 Hz, although the cadence of the data burst may be associated with a periodicity of 1000 ms. When the multimedia periodicity is 1000 ms and the DRX cycle is 10240 ms (1024 SFNs per hyperframe every 10 ms), the DRX hyperframe may fall out of alignment with the frames of the multimedia server every 10.24 seconds. Due to the misalignment between the hyperframe periodicity (10240 ms) and the multimedia periodicity, there is a drift 3702 of 1.666 ms (2 ms in Example 3700) every 10.24 seconds (10240 ms). In other words, the hyperframe periodicity (10240 ms) cannot be divided by the multimedia periodicity (Hz, fps). In the example of 120 Hz XR traffic, 10240 ms / (1000 / 120) ms = 1228.8 frames. The fractional part of 0.8 (or 1 - 0.8 = 0.2) is the remaining partial frame at the end of the hyperframe, and this partial frame causes an SFN wrap-around problem in the next hyperframe. Other multimedia periodicities result in other amounts of frames that do not align with the amount of SFNs per hyperframe, i.e., 45 Hz (460.8 SFNs), 48 Hz (491.52 SFNs), 60 Hz (614.4 SFNs), or 90 Hz (921.6 SFNs).

[0358]

[0400] Example 3700 indicates the end of the hyperframe (at SFN 1023) and the start of the next hyperframe (at SFN 0), or the point in time when the SFN number wraps around (restarts or returns to 0) for the next hyperframe. When the end of the hyperframe is reached, (SFN *10) Wake-up conditions or expressions such as subframe number = 0 can select subframes over the on-duration that are between data bursts due to SFN wrap-around. Since the subframe may not be aligned with the data burst, the data burst may not be received. This can cause communication degradation that may consume additional processing resources and signaling.

[0359]

[0401] By adding the SFN wrap-around offset 3704 (e.g., hyperframe length (e.g., 1024) × m) to the subframe index 3706 (e.g., (SFN * 10) + subframe number), the subframe 3708 at which the UE wakes up is aligned with the correct subframe 3710 that matches the burst arrival time of the XR data. As a result, data is not lost and communication does not degrade. Signaling resources are conserved.

[0360]

[0402] As described above, FIG. 37 is provided as an example. Other examples may be different from those described with respect to FIG. 37.

[0361]

[0403] FIG. 38 is a diagram showing an exemplary process 3800 performed, for example, by a UE according to the present disclosure. The exemplary process 3800 is an example where a UE (e.g., UE120, UE1820, UE3620, etc.) performs operations associated with DRX.

[0362]

[0404] As shown in FIG. 38, in some aspects, process 3800 may include waking up at the start of a subframe (block 3810) based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset that takes into account the cumulative length of a hyperframe. For example, a UE (e.g., using communication manager 140 and / or wake-up component 3908 shown in FIG. 39) may wake up at the start of a subframe based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset that takes into account the cumulative length of a hyperframe, as described above.

[0363]

[0405] As further shown in FIG. 38, in some aspects, process 3800 may include receiving a data burst between subframes (block 3820). For example, a UE (e.g., using communication manager 140 and / or receiving component 3902 shown in FIG. 39) may receive a data burst between subframes, as described above.

[0364]

[0406] Process 3800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described elsewhere in this specification in connection with one or more other processes.

[0365]

[0407] In a first aspect, the SFN wrap-around offset is equal to (hyperframe length × m).

[0366]

[0408] In a second aspect, alone or in combination with the first aspect, the hyperframe length is equal to 10240.

[0367]

[0409] In a third aspect, alone or in combination with one or more of the first and second aspects, the subframe index is equal to (10 × SFN of the frame containing the subframe) + subframe number of the subframe.

[0368]

[0410] In the fourth aspect, alone or in combination with one or more of the first to third aspects, the SFN returns to 0 or the time-reference SFN, and when the time-reference SFN is 0 or 512, m is updated to m + 1.

[0369]

[0411] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, waking up is based on the length of the resource cycle (subframe index + SFN wrap-around offset), and includes waking up when it is equal to [(start offset + (time-reference SFN × 10)] based on the length of the resource cycle.

[0370]

[0412] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the resource cycle includes a DRX cycle, and the data burst is a multimedia data burst.

[0371]

[0413] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 3800 includes sending an indication of the ability to use the SFN wrap-around offset.

[0372]

[0414] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 3800 includes activating the SFN wrap-around offset.

[0373]

[0415] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the SFN wrap-around offset is equal to (hyperframe length × m × k), k = 1 to activate the SFN wrap-around offset, and k = 0 to deactivate the SFN wrap-around offset.

[0374]

[0416] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 3800 includes receiving one or more configurations of a DRX short cycle or a DRX long cycle that has backward compatibility for using an SFN wrap-around offset.

[0375]

[0417] FIG. 38 shows exemplary blocks of process 3800, but in some aspects, process 3800 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 38. Additionally, or alternatively, two or more of the blocks of process 3800 may be executed in parallel.

[0376]

[0418] FIG. 39 is a diagram of an exemplary apparatus 3900 for wireless communication according to the present disclosure. Apparatus 3900 may be a UE (e.g., UE120, UE1820, UE3620), or the UE may include apparatus 3900. In some aspects, apparatus 3900 includes a receiving component 3902 and a transmitting component 3904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 3900 may communicate with another apparatus 3906 (such as a UE, a base station, or another wireless communication device) using receiving component 3902 and transmitting component 3904. Further shown, apparatus 3900 may include a communication manager 140. Communication manager 140 may include one or more of wake-up components 3908 among other examples.

[0377]

[0419] In some aspects, apparatus 3900 may be configured to perform one or more operations described herein with respect to FIGS. 17-37. Additionally, or alternatively, apparatus 3900 may be configured to perform one or more processes described herein, such as process 3800 of FIG. 38. In some aspects, apparatus 3900 and / or one or more components shown in FIG. 39 may include one or more components of the UE described with respect to FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 39 may be implemented in one or more components described with respect to FIG. 2. Additionally, or alternatively, one or more of a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0378]

[0420] Receiver component 3902 may receive communications from apparatus 3906, such as a reference signal, control information, data communications, or combinations thereof. Receiver component 3902 may provide the received communications to one or more other components of apparatus 3900. In some aspects, receiver component 3902 may perform signal processing (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding) on the received communications and provide the processed signals to one or more other components of apparatus 3900. In some aspects, receiver component 3902 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controller / processors, memories, or combinations thereof of the UE described with respect to FIG. 2.

[0379]

[0421] The transmitting component 3904 can transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 3906. In some aspects, one or more other components of the device 3900 can generate a communication and provide the generated communication to the transmitting component 3904 for transmission to the device 3906. In some aspects, the transmitting component 3904 can perform signal processing (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communication and transmit the processed signal to the device 3906. In some aspects, the transmitting component 3904 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described with respect to FIG. 2. In some aspects, the transmitting component 3904 may be collocated with the receiving component 3902 in a transceiver.

[0380]

[0422] The wake-up component 3908 can wake up at the start in a subframe based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset considering a cumulative length of a hyperframe. The receiving component 3902 can receive a data burst between subframes.

[0381]

[0423] The transmitting component 3904 can transmit an indication of the ability to use an SFN wrap-around offset. The wake-up component 3908 can activate the SFN wrap-around offset. The receiving component 3902 can receive one or more configurations of a DRX short cycle or a DRX long cycle having backward compatibility for using the SFN wrap-around offset.

[0382]

[0424] The number and configuration of the components shown in FIG. 39 are provided as an example. In practice, there may be additional components, fewer components, different components, or components configured differently compared to the components shown in FIG. 39. Further, two or more components shown in FIG. 39 may be implemented within a single component, or a single component shown in FIG. 39 may be implemented as a plurality of distributed components. Additionally, alternatively or instead, a set of (one or more) components shown in FIG. 39 may perform one or more functions described as being performed by another set of components shown in FIG. 39.

[0383]

[0425] FIG. 40 is a diagram showing an example 4000 of a hardware implementation form for an apparatus 4005 using a processing system 4010. The apparatus 4005 may be a UE (e.g., UE120, UE1820, UE3620).

[0384]

[0426] The processing system 4010 may be implemented in a bus architecture represented as a whole by a bus 4015. The bus 4015 may include any number of interconnecting buses and bridges depending on the specific application example of the processing system 4010 and overall design constraints. The bus 4015 links various circuits including one or more processors and / or hardware components represented by a processor 4020, the illustrated components, and a computer-readable medium / memory 4025 to each other. The bus 4015 may also link various other circuits such as a timing source, peripherals, a voltage regulator, and / or a power management circuit.

[0385]

[0427] The processing system 4010 may be coupled to the transceiver 4030. The transceiver 4030 is coupled to one or more antennas 4035. The transceiver 4030 provides means for communicating with various other devices via a transmission medium. The transceiver 4030 receives signals from one or more antennas 4035, extracts information from the received signals, and provides the extracted information to the processing system 4010, specifically to the receiving component 3902. In addition, the transceiver 4030 receives information from the processing system 4010, particularly from the transmitting component 3904, and generates signals to be applied to one or more antennas 4035 based at least in part on the received information.

[0386]

[0428] The processing system 4010 includes a processor 4020 coupled to a computer-readable medium / memory 4025. The processor 4020 is responsible for general processing including the execution of software stored in the computer-readable medium / memory 4025. The software, when executed by the processor 4020, causes the processing system 4010 to perform the various functions described herein for any particular device. The computer-readable medium / memory 4025 may also be used to store data that is manipulated by the processor 4020 when executing the software. The processing system may further include at least one of the illustrated components. The components may be software modules executed in the processor 4020 and residing / stored in the computer-readable medium / memory 4025, one or more hardware modules coupled to the processor 4020, or some combination thereof.

[0387]

[0429] In some aspects, the processing system 4010 may be a component of the UE 120 and may include at least one of the memory 282 and / or the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the apparatus 4005 for wireless communication includes means for waking up at the start of a subframe and / or means for receiving a data burst between subframes, at least partially based on a subframe index of a resource cycle and an SFN wrap-around offset considering a cumulative length of a hyperframe. The means described above may be one or more of the above-described components of the processing system 4010 of the apparatus 2900 and / or the apparatus 4005 configured to perform the functions enumerated by the means described above. As described elsewhere in this specification, the processing system 4010 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the foregoing means may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations enumerated herein.

[0388]

[0430] FIG. 40 is provided as an example. Other examples may be different from those described in connection with FIG. 40.

[0389]

[0431] FIG. 41 is a diagram showing an example 4100 of a code and circuit implementation for an apparatus 4105 according to the present disclosure. The apparatus 4105 may be a UE, or the UE may include the apparatus 4105.

[0390]

[0432] As shown in FIG. 41, apparatus 4105 may include circuitry (circuitry 4120) for waking up at the start of a subframe, based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset taking into account the cumulative length of a hyperframe. For example, circuitry 4120 may enable apparatus 4105 to wake up at the start of a subframe, based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset taking into account the cumulative length of a hyperframe.

[0391]

[0433] As shown in FIG. 41, apparatus 4105 may include code (code 4125) stored in computer-readable medium 4025 for waking up at the start of a subframe, based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset taking into account the cumulative length of a hyperframe. For example, when executed by processor 4020, code 4125 may cause processor 4020 to wake up transceiver 4030 at the start of a subframe, based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset taking into account the cumulative length of a hyperframe.

[0392]

[0434] As shown in FIG. 41, apparatus 4105 may include circuitry (circuitry 4130) for receiving a data burst between subframes. For example, circuitry 4130 may enable apparatus 4105 to receive a data burst between subframes.

[0393]

[0435] As shown in FIG. 41, apparatus 4105 may include code (code 4135) stored in computer-readable medium 4025 for receiving a data burst between subframes. For example, when executed by processor 4020, code 4135 may cause processor 4020 to receive a data burst between subframes at transceiver 4030.

[0394]

[0436] FIG. 41 is provided as an example. Other examples may differ from those described in relation to FIG. 41.

[0395]

[0437] The following provides an overview of some aspects of the present disclosure.

[0396]

[0438] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising sleeping in relation to a discontinuous reception (DRX) cycle, waking up at the start in a subframe at least partially based on a specified time offset added to the on-duration of the DRX cycle at least partially based on the number of DRX cycles and the length of the DRX cycle of the DRX cycle, wherein the specified time offset is at least partially based on the periodicity of a multimedia data burst, the number of DRX cycles is at least partially based on the specified time offset, starting to wake up, and receiving a multimedia data burst between subframes.

[0397]

[0439] Aspect 2: The method according to aspect 1, wherein the number of DRX cycles is equal to the value obtained by dividing [(10 × the system frame number (SFN) of the frame containing the subframe + the subframe number of the subframe) - (n × the specified time offset)] by the length of the DRX cycle.

[0398]

[0440] Aspect 3: The method according to aspect 2, wherein waking up includes waking up when (10 × SFN + subframe number) modulo the length of the DRX cycle is equal to ((n × the specified time offset) + start offset) modulo the length of the DRX cycle, and n is updated to n + 1 when the number of DRX cycles modulo the specified amount of the DRX cycle is equal to 0.

[0399]

[0441] Aspect 4: The method according to aspect 3, further comprising the step of skipping the n + 1 update every other time.

[0400]

[0442] Aspect 5: The wake-up includes waking up when (10 × SFN + subframe number) modulo the DRX cycle length is equal to ((n × specified time offset) + start offset) modulo the DRX cycle length, and n is updated to n + 1 when (10 × SFN + subframe number) modulo (DRX cycle length × specified amount of DRX cycle + specified time offset) is equal to the specified timing value, the method according to Aspect 2.

[0401]

[0443] Aspect 6: The method according to Aspect 5, wherein the specified timing value is equal to (DRX cycle length × specified amount of DRX cycle) - 1.

[0402]

[0444] Aspect 7: The wake-up includes waking up at least partially based further on the SFN wrap-around offset, the method according to Aspect 2.

[0403]

[0445] Aspect 8: The wake-up includes waking up when (10 × SFN + subframe number + SFN wrap-around offset) modulo the DRX cycle length is equal to ((n × specified time offset) + start offset) modulo the DRX cycle length, and n is updated to n + 1 when (10 × SFN + subframe number + SFN wrap-around offset) modulo (DRX cycle length × specified amount of DRX cycle + specified time offset) is equal to the specified timing value, the method according to Aspect 7.

[0404]

[0446] Aspect 9: The method according to Aspect 7, wherein the SFN wrap-around offset is equal to (10240 × m), and m is updated to m + 1 when the SFN returns to 0.

[0405]

[0447] Aspect 10: Wake-up is based on the length of the DRX cycle (10×SFN + subframe number + SFN wrap-around offset), and includes waking up when it is equal to [(n×specified time offset) + start offset + (DRX time reference SFN×10)] based on the length of the DRX cycle. When (DRX cycle length×specified amount of the DRX cycle + specified time offset) based on (10×SFN + subframe number + SFN wrap-around offset) is equal to the specified timing value, n is updated to n + 1. The method according to aspect 7.

[0406]

[0448] Aspect 11: The SFN wrap-around offset is 10240×m, where m is updated to m + 1 when the SFN returns to the DRX time reference SFN, and the DRX time reference SFN is 0 or 512. The method according to aspect 10.

[0407]

[0449] Aspect 12: The method according to aspect 10, further including receiving an indication of the DRX time reference SFN.

[0408]

[0450] Aspect 13: The anchor cycle including the DRX cycle also includes two or more leap cycles. The method according to any one of aspects 1 to 12.

[0409]

[0451] Aspect 14: The method according to aspect 13, further including receiving an indication of two or more leap cycles.

[0410]

[0452] Aspect 15: The method according to aspect 13 or 14, further including receiving an indication of the timing of two or more leap cycles.

[0411]

[0453] Aspect 16: A method of wireless communication performed by a user equipment (UE), comprising sleeping in relation to a discontinuous reception (DRX) cycle, waking up at the start in a subframe based at least in part on a specified time offset added to an on-duration of the DRX cycle based at least in part on a number of DRX cycles of the DRX cycle and a DRX time reference system frame number (SFN), wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, the number of DRX cycles is based at least in part on the specified time offset, starting to wake up, and receiving a multimedia data burst between subframes.

[0412]

[0454] Aspect 17: The method according to aspect 16, wherein waking up comprises waking up when (SFN of a frame including the subframe × number of subframes per frame) + subframe number of the subframe is equal to [DRX time reference SFN × number of subframes per frame + start offset + number of DRX on-durations × length of the DRX cycle + floor(number of DRX on-durations / specified time offset) × specified amount of the DRX cycle] modulo (1024 × number of subframes per frame).

[0413]

[0455] Aspect 18: The method according to aspect 16, wherein waking up comprises waking up when [(modified SFN of a frame including the subframe × 10) + subframe number of the subframe] modulo length of the DRX cycle is equal to [start offset + (n × specified time offset) + (DRX time reference SFN × 10)] modulo length of the DRX cycle, and n is updated to n + 1 when [(SFN_M × 10) + subframe number] modulo (DRX cycle length × specified amount of the DRX cycle + specified time offset) is equal to a specified timing value.

[0414]

[0456] Aspect 19: The method according to aspect 18, wherein the specified timing value is equal to (length of the DRX cycle × specified amount of the DRX cycle) - 1.

[0415]

[0457] Aspect 20: A method of wireless communication performed by a user equipment (UE), comprising sleeping in relation to a resource cycle, and waking up at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles and the length of the resource cycle of the resource cycle, wherein the specified time offset is based at least in part on the periodicity of a multimedia data burst, the number of resource cycles is based at least in part on the specified time offset, starting to wake up, and receiving a multimedia data burst between subframes.

[0416]

[0458] Aspect 21: The method according to aspect 20, wherein the resource cycle is a cycle for one of a channel state information (CSI) reference signal, a CSI interference measurement resource, or a sounding reference signal.

[0417]

[0459] Aspect 22: The method according to aspect 20 or 21, wherein the resource cycle is a cycle for a scheduling request.

[0418]

[0460] Aspect 23: The method according to any one of aspects 20 to 22, wherein the resource cycle is a cycle for a configured grant resource or a semi-persistent scheduling resource.

[0419]

[0461] Aspect 24: The method according to any one of aspects 20 to 23, wherein the resource cycle is a cycle for a channel state information report or a buffer status report.

[0420]

[0462] Aspect 25: The method according to any one of Aspects 20 to 24, wherein the resource cycle is a cycle for physical downlink control channel monitoring or a cycle for physical uplink control channel resources.

[0421]

[0463] Aspect 26: The method according to any one of Aspects 20 to 25, wherein the number of resource cycles is equal to the value obtained by dividing [(10 × system frame number (SFN) of the frame including the subframe + subframe number of the subframe) - (n × specified time offset)] by the length of the resource cycle.

[0422]

[0464] Aspect 27: The method according to any one of Aspects 20 to 26, including waking up when waking up is modulo the length of the resource cycle (10 × SFN + subframe number + SFN wrap - around offset) and is equal to modulo the length of the resource cycle ((n × specified time offset) + start offset), and n is updated to n + 1 when modulo the length of the resource cycle (resource cycle length × specified amount of the resource cycle + specified time offset) (10 × SFN + subframe number + SFN wrap - around offset) is equal to the specified timing value.

[0423]

[0465] Aspect 28: The method according to Aspect 27, wherein the SFN wrap - around offset is 10240 × m, and m is updated to m + 1 when the SFN returns to 0.

[0424]

[0466] Aspect 29: Wake-up is based on the length of the resource cycle (10×SFN + subframe number + SFN wrap-around offset), and includes wake-up when it is equal to [(n×specified time offset) + start offset + (resource time reference SFN×10)] based on the length of the resource cycle. When (length of resource cycle×specified amount of resource cycle + specified time offset) based on (10×resource + subframe number + SFN wrap-around offset) is equal to the specified timing value, n is updated to n + 1, the method according to any one of Aspects 20 to 26.

[0425]

[0467] Aspect 30: The SFN wrap-around offset is 10240×m, m is updated to m + 1 when the SFN returns to the resource time reference SFN, and the resource time reference SFN is 0 or 512, the method according to Aspect 29.

[0426]

[0468] Aspect 31: A method of wireless communication performed by a network entity, including preparing to communicate with a user equipment (UE) according to an intermittent reception (DRX) cycle, and transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle. The specified time offset is based at least in part on the periodicity of the multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset.

[0427]

[0469] Aspect 32: The number of DRX cycles is equal to the value obtained by dividing [(10×system frame number (SFN) of the frame including the subframe + subframe number of the subframe) - (n×specified time offset)] by the length of the DRX cycle, the method according to Aspect 31.

[0428]

[0470] Aspect 33: Transmitting a data burst includes transmitting a data burst when (10 × SFN + subframe number) modulo the DRX cycle length is equal to ((n × specified time offset) + start offset) modulo the DRX cycle length, and n is updated to n + 1 when the number of DRX cycles modulo the specified amount of the DRX cycle is equal to 0, the method according to aspect 32.

[0429]

[0471] Aspect 34: The method according to aspect 33, further including skipping the n + 1 update every other time.

[0430]

[0472] Aspect 35: Transmitting a data burst includes transmitting a data burst when (10 × SFN + subframe number) modulo the DRX cycle length is equal to ((n × specified time offset) + start offset) modulo the DRX cycle length, and n is updated to n + 1 when (10 × SFN + subframe number) modulo (DRX cycle length × specified amount of the DRX cycle + specified time offset) is equal to the specified timing value, the method according to aspect 32.

[0431]

[0473] Aspect 36: The method according to aspect 35, wherein the specified timing value is equal to (DRX cycle length × specified amount of the DRX cycle) - 1.

[0432]

[0474] Aspect 37: The method according to aspect 32, wherein transmitting a data burst includes transmitting a data burst based at least in part on an SFN wrap-around offset.

[0433]

[0475] Aspect 38: Sending a data burst is based on the length of the DRX cycle (10×SFN + subframe number + SFN wrap-around offset), and includes sending a data burst when it is equal to the DRX cycle length ((n×specified time offset) + start offset). When (DRX cycle length × specified amount of the DRX cycle + specified time offset) is used as the modulus (10×SFN + subframe number + SFN wrap-around offset) and is equal to the specified timing value, n is updated to n + 1. The method according to Aspect 37.

[0434]

[0476] Aspect 39: The SFN wrap-around offset is equal to (10240×m), and m is updated to m + 1 when the SFN returns to 0. The method according to Aspect 37.

[0435]

[0477] Aspect 40: Sending a data burst is based on the length of the DRX cycle (10×SFN + subframe number + SFN wrap-around offset), and includes sending a data burst when it is equal to the DRX cycle length [(n×specified time offset) + start offset + (DRX time reference SFN×10)]. When (DRX cycle length × specified amount of the DRX cycle + specified time offset) is used as the modulus (10×SFN + subframe number + SFN wrap-around offset) and is equal to the specified timing value, n is updated to n + 1. The method according to Aspect 37.

[0436]

[0478] Aspect 41: The SFN wrap-around offset is 10240×m, m is updated to m + 1 when the SFN returns to the DRX time reference SFN, and the DRX time reference SFN is 0 or 512. The method according to Aspect 40.

[0437]

[0479] Aspect 42: Further includes sending an indication of the DRX time reference SFN. The method according to Aspect 40.

[0438]

[0480] Aspect 43: The method according to any one of Aspects 31 to 42, wherein the anchor cycle including the DRX cycle further includes two or more leap cycles.

[0439]

[0481] Aspect 44: The method according to Aspect 43, further including transmitting an indication of two or more leap cycles.

[0440]

[0482] Aspect 45: The method according to Aspect 43 or 44, further including transmitting an indication of the timing of two or more leap cycles.

[0441]

[0483] Aspect 46: The method according to any one of Aspects 43 to 45, wherein the leap cycle offset pattern of two or more leap cycles includes (0 milliseconds (ms), 1 ms, 1 ms) or (1 ms, 1 ms, 0 ms).

[0442]

[0484] Aspect 47: A method of wireless communication performed by a network entity, comprising preparing to communicate with a user equipment (UE) according to an intermittent reception (DRX) cycle, and based at least in part on a specified time offset added to the on-duration of the DRX cycle based at least in part on the number of DRX cycles of the DRX cycle and the length of the DRX cycle, transmitting a data burst at the start in a subframe, wherein the specified time offset is based at least in part on the periodicity of a multimedia data burst, and the number of DRX cycles is based at least in part on the specified time offset.

[0443]

[0485] Aspect 48: The method according to aspect 47, wherein transmitting a data burst includes transmitting a data burst when (SFN of a frame including sub - frames × amount of sub - frames per frame)+sub - frame number of the sub - frame is equal to [DRX time reference SFN × amount of sub - frames per sub - frame+start offset+number of DRX on - duration × length of DRX cycle+floor(number of DRX on - duration / specified time offset)× specified amount of DRX cycle] modulo (1024×amount of sub - frames per frame).

[0444]

[0486] Aspect 49: The method according to aspect 47, wherein transmitting a data burst includes transmitting a data burst when [(modified SFN of a frame including sub - frames × 10)+sub - frame number of the sub - frame] modulo length of DRX cycle is equal to [start offset+(n×specified time offset)+(DRX time reference SFN × 10)] modulo length of DRX cycle, and n is updated to n + 1 when [(SFN_M×10)+sub - frame number] modulo (length of DRX cycle×specified amount of DRX cycle+specified time offset) is equal to the specified timing value.

[0445]

[0487] Aspect 50: The method according to aspect 49, wherein the specified timing value is equal to (length of DRX cycle×specified amount of DRX cycle)-1.

[0446]

[0488] Aspect 51: A method of wireless communication performed by a network entity, comprising preparing to communicate with a user equipment (UE) according to a resource cycle, and transmitting a data burst at the start in a subframe based at least in part on a specified time offset added to an instance of the resource cycle based at least in part on the number of resource cycles of the resource cycle and the length of the resource cycle, wherein the specified time offset is based at least in part on the periodicity of a multimedia data burst, the number of resource cycles is based at least in part on the specified time offset, and the number of resource cycles is based at least in part on the specified time offset.

[0447]

[0489] Aspect 52: The method according to aspect 51, wherein the resource cycle is a cycle for one of a channel state information (CSI) reference signal, a CSI interference measurement resource, or a sounding reference signal.

[0448]

[0490] Aspect 53: The method according to aspect 51 or 52, wherein the resource cycle is a cycle for a scheduling request.

[0449]

[0491] Aspect 54: The method according to any one of aspects 51 to 53, wherein the resource cycle is a cycle for a configured grant resource or a semi-persistent scheduling resource.

[0450]

[0492] Aspect 55: The method according to any one of aspects 51 to 54, wherein the resource cycle is a cycle for a channel state information report or a buffer status report.

[0451]

[0493] Aspect 56: The method according to any one of aspects 51 to 55, wherein the resource cycle is a cycle for physical downlink control channel monitoring or a cycle for physical uplink control channel resources.

[0452]

[0494] Aspect 57: The method according to any one of Aspects 51 to 56, wherein the number of resource cycles is equal to a value obtained by dividing [(10 × system frame number (SFN) of a frame including subframes + subframe number of the subframe) - (n × specified time offset)] by the length of the resource cycle.

[0453]

[0495] Aspect 58: Transmitting a data burst includes transmitting a data burst when (10 × SFN + subframe number + SFN wrap - around offset) modulo the length of the resource cycle is equal to ((n × specified time offset)+ start offset) modulo the length of the resource cycle, and n is updated to n + 1 when (10 × SFN + subframe number + SFN wrap - around offset) modulo (resource cycle length × specified amount of the resource cycle + specified time offset) is equal to the specified timing value, the method according to any one of Aspects 51 to 56.

[0454]

[0496] Aspect 59: The method according to Aspect 58, wherein the SFN wrap - around offset is 10240×m, and m is updated to m + 1 when the SFN returns to 0.

[0455]

[0497] Aspect 60: Transmitting a data burst includes transmitting a data burst when (10 × SFN + subframe number + SFN wrap - around offset) modulo the length of the resource cycle is equal to [(n × specified time offset)+ start offset+(resource - time - reference SFN × 10)] modulo the length of the resource cycle, and n is updated to n + 1 when (10 × resource + subframe number + SFN wrap - around offset) modulo (resource cycle length × specified amount of the resource cycle + specified time offset) is equal to the specified timing value, the method according to any one of Aspects 51 to 56.

[0456]

[0498] Aspect 61: The method according to aspect 60, wherein the SFN wrap-around offset is 10240×m, m is updated to m+1 when the SFN returns to the resource time reference SFN, and the resource time reference SFN is 0 or 512.

[0457]

[0499] Aspect 62: A method for wireless communication in a user equipment (UE), comprising waking up at the start of a subframe based at least in part on a subframe index of a resource cycle and a system frame number (SFN) wrap-around offset considering a cumulative length of a hyperframe, and receiving a data burst between subframes.

[0458]

[0500] Aspect 63: The method according to aspect 62, wherein the SFN wrap-around offset is equal to (hyperframe length×m).

[0459]

[0501] Aspect 64: The method according to any one of aspects 62 and 63, wherein the hyperframe length is equal to 10240.

[0460]

[0502] Aspect 65: The method according to any one of aspects 62 to 64, wherein the subframe index is equal to (SFN of the frame including 10×subframes)+subframe number of the subframe.

[0461]

[0503] Aspect 66: The method according to aspect 65, wherein m is updated to m+1 when the SFN returns to 0.

[0462]

[0504] Aspect 67: The method according to aspect 65, wherein m is updated to m+1 when the SFN returns to the time reference SFN.

[0463]

[0505] Aspect 68: The method according to aspect 67, wherein the time reference SFN is 0 or 512.

[0464]

[0506] Aspect 69: The wake-up is based on the length of the resource cycle (subframe index + SFN wrap-around offset), and when the length of the resource cycle is equal to [(start offset + (time reference SFN × 10)], the method according to any one of Aspects 62 to 68, including waking up.

[0465]

[0507] Aspect 70: The method according to any one of Aspects 62 to 69, wherein the resource cycle includes a discontinuous reception (DRX) cycle and the data burst is a multimedia data burst.

[0466]

[0508] Aspect 71: The method according to any one of Aspects 62 to 70, further including transmitting an indication of the ability to use the SFN wrap-around offset.

[0467]

[0509] Aspect 72: The method according to any one of Aspects 62 to 71, further including activating the SFN wrap-around offset.

[0468]

[0510] Aspect 73: The method according to Aspect 72, wherein the SFN wrap-around offset is equal to (hyperframe length × m × k), k = 1 for activating the SFN wrap-around offset, and k = 0 for deactivating the SFN wrap-around offset.

[0469]

[0511] Aspect 74: The method according to any one of Aspects 62 to 73, wherein one or more processors are configured to receive one or more configurations of a DRX short cycle or a DRX long cycle that are backward compatible for using the SFN wrap-around offset.

[0470]

[0512] Aspect 75: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the device to execute one or more of the methods of Aspects 1 to 74.

[0471]

[0513] Aspect 76: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to execute one or more of the methods of Aspects 1 to 74.

[0472]

[0514] Aspect 77: An apparatus for wireless communication, comprising at least one means for executing one or more of the methods of Aspects 1 to 74.

[0473]

[0515] Aspect 78: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to execute one or more of the methods of Aspects 1 to 74.

[0474]

[0516] Aspect 79: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to execute one or more of the methods of Aspects 1 to 74.

[0475]

[0517] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Modifications and variations can be added in light of the foregoing disclosure or obtained from practice of the aspects.

[0476]

[0518] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. "Software" shall be broadly construed to mean, among other things, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether called by the name software, firmware, middleware, microcode, hardware description language, or another name. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or combinations of hardware and software. The actual specialized control hardware code or software code used to implement these systems and / or methods does not limit the aspects. Thus, those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein. Therefore, in this specification, the operation and behavior of the systems and / or methods are described without reference to specific software code.

[0477]

[0519] As used herein, "meeting a threshold" may, depending on the context, refer to a value being greater than a threshold, being greater than or equal to a threshold, being less than a threshold, being less than or equal to a threshold, being equal to a threshold, not being equal to a threshold, and the like.

[0478]

[0520] Even if certain combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure in various aspects. Many of these features may be combined in ways that are not specifically recited in the claims and / or not disclosed herein. The disclosure in various aspects includes each dependent claim combined with all other claims within the claim set. As used herein, the phrase referring to an enumeration of items “at least one of” refers to any combination of those items, including a single member. By way of example, “at least one of a, b, or c” is intended to include a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple of the same elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other order of a, b, and c).

[0479]

[0521] None of the elements, acts, or instructions used in this specification should be construed as important or essential unless expressly described as such. Also, as used in this specification, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Further, as used in this specification, the definite article "the" is intended to include one or more items referred to by the definite article "the" and may be used interchangeably with "one or more". Additionally, as used in this specification, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more". When only one item is intended, the phrase "only one" or similar words are used. Also, as used in this specification, terms such as "has", "have", "having", etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element "having" A can also have B). Furthermore, the phrase "based on" is intended to mean "at least partially based on" unless otherwise specified. Also, as used in this specification, the term "or" is intended to be inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise specified (e.g., when used in combination with "either" or "only one of").

Claims

1. A device for wireless communication in user equipment (UE), Memory and The system comprises one or more processors coupled to the memory, wherein the processors The device is woken up at the start of a subframe, at least in part, based on a specified index of the subframe, the DRX cycle length, and the DRX start offset, wherein the specified index of the subframe comprises the subframe number in the radio frame, the system frame number (SFN) of the radio frame containing the subframe, and the SFN wraparound offset. A device configured to receive a downlink channel from the subframe during the DRX-ON duration.

2. The apparatus according to claim 1, wherein [(10 × the SFN of the frame including the subframe + the subframe number of the subframe + SFN wraparound offset)] modulo (the length of the DRX cycle) is equal to the DRX start offset.

3. The apparatus according to claim 2, wherein the SFN wraparound offset is equal to (10240 × m), where m is updated to m+1 when the SFN returns to 0, and m is the SFN counter for the hyperframe.

4. The apparatus according to claim 1, wherein one or more processors are configured to wake up the apparatus when (10 × the SFN + the subframe number + the SFN wraparound offset) modulo the length of the DRX cycle is equal to [(n × the specified time offset) + start offset + (DRX time reference SFN × 10)] modulo the length of the DRX cycle, and n is updated to n+1 when (10 × the SFN + the subframe number + the SFN wraparound offset) modulo (the length of the DRX cycle × the specified amount of the DRX cycle + the specified time offset) is equal to a specified timing value.

5. The apparatus according to claim 1, wherein the SFN wrap-around offset is 10240 × m, where m is updated to m+1 when the SFN returns to the DRX time reference SFN, and the DRX time reference SFN is 0 or 512.

6. The apparatus according to claim 1, wherein one or more processors are configured to receive instructions for the DRX time reference SFN.

7. The apparatus according to claim 1, wherein the anchor cycle including the DRX cycle also includes two or more leap cycles.

8. The apparatus according to claim 7, wherein one or more processors are configured to receive instructions for two or more leap cycles, or instructions for the timing of two or more leap cycles.

9. The apparatus according to claim 7, wherein the leap cycle offset pattern of the two or more leap cycles includes (0 milliseconds (ms), 1 ms, 1 ms) or (1 ms, 1 ms, 0 ms).

10. A method for wireless communication in user equipment (UE), Wake up the device at the start of a subframe, at least in part, based on a specified index of the subframe, DRX cycle length, and DRX start offset, wherein the specified index of the subframe comprises a subframe number in a radio frame, a system frame number (SFN) of the radio frame containing the subframe, and an SFN wraparound offset. Receiving a downlink channel from the subframe during the DRX-ON duration, A method that includes [a certain feature].

Images