Resource recycling method

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may wake up starting at a subframe based at least in part on a subframe index of a resource cycle and a system frame number (SFN) rewinding offset that accounts for a cumulative length of a superframe. The UE may receive a data burst during the subframe. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 313,825, filed on May 8, 2023, entitled “RESOURCE CYCLEMETHODOLOGY,” which is a continuation-in-part of U.S. Patent Application No. 18 / 296,952, filed on April 6, 2023, entitled “RESOURCE CYCLE METHODOLOGY,” which claims priority to U.S. Provisional Patent Application No. 63 / 366,204, filed on June 10, 2022, entitled “DISCONTINUOUS RECEPTION METHODOLOGY,” all of which are assigned to the assignee of this patent application. The disclosures of these prior applications are considered part of and incorporated by reference into this patent application. Background Art

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for handling resource recycling and other applications.

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies 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 standard promulgated by the Third Generation Partnership Project (3GPP).

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

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method for wireless communication at a user equipment (UE). The method may include: waking up at a subframe based at least in part on a subframe index of a resource cycle and a system frame number (SFN) wraparound offset that illustrates a cumulative length of a superframe. The method may include: receiving a data burst during the subframe.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to wake up at a subframe based at least in part on a subframe index of a resource cycle and an SFN wrap-around offset that describes a cumulative length of a superframe. The one or more processors may be configured individually or collectively to receive a data burst during a subframe.

[0009] 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 a subframe based at least in part on a subframe index of a resource cycle and a SFN wrap-around offset that describes a cumulative length of a superframe. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a data burst during the subframe.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for waking up at a subframe based at least in part on a subframe index of a resource cycle and a SFN wrap-around offset that illustrates a cumulative length of a superframe. The apparatus may include means for receiving a data burst during the subframe.

[0011] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: sleeping in association with a discontinuous reception (DRX) cycle. The method may include: waking up based at least in part on a specified time offset starting at a subframe, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The method may include: receiving a multimedia data burst during the subframe.

[0012] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: sleeping in association with a DRX cycle. The method may include: waking up based at least in part on a specified time offset starting at a subframe, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number and a DRX time reference SFN of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The method may include: receiving a multimedia data burst during the subframe.

[0013] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: sleeping in association with a resource cycle. The method may include: waking up based at least in part on a specified time offset starting at a subframe, the specified time offset being added to an instance of the resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the resource cycle number is based at least in part on the specified time offset. The method may include: receiving a multimedia data burst during the subframe.

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

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

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

[0017] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to cause the UE to sleep in association with a DRX cycle. The one or more processors may be configured to wake up the UE starting at a subframe based at least in part on a specified time offset, the specified time offset being added to the on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The one or more processors may be configured individually or collectively to receive a multimedia data burst during a subframe.

[0018] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to cause the UE to sleep in association with a DRX cycle. The one or more processors may be configured individually or collectively to wake up the UE based at least in part on a specified time offset starting at a subframe, the specified time offset being added to the on-duration of the DRX cycle based at least in part on a DRX cycle number and a DRX time reference SFN of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The one or more processors may be configured individually or collectively to receive a multimedia data burst during a subframe.

[0019] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to cause sleep associated with a resource cycle. The one or more processors may be configured individually or collectively to wake up the UE based at least in part on a specified time offset starting at a subframe, the specified time offset being added to an instance of the resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the resource cycle number is based at least in part on a specified time offset. The one or more processors may be configured individually or collectively to receive a multimedia data burst during a subframe.

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

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

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

[0023] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to sleep in association with a DRX cycle. The instruction set, when executed by one or more processors of the UE, may cause the UE to wake up the UE starting at a subframe based at least in part on a specified time offset, the specified time offset being added to the on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a multimedia data burst during a subframe.

[0024] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to sleep in association with a DRX cycle. The instruction set, when executed by one or more processors of the UE, may cause the UE to wake up the UE starting at a subframe based at least in part on a specified time offset, the specified time offset being added to the on-duration of the DRX cycle based at least in part on a DRX cycle number and a DRX time reference SFN of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a multimedia data burst during a subframe.

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

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

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

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

[0029] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sleeping in association with a DRX cycle. The apparatus may include means for waking up at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The apparatus may include means for receiving a multimedia data burst during a subframe.

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

[0031] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sleeping in association with a resource cycle. The apparatus may include means for waking up at a subframe based at least in part on a specified time offset, the specified time offset being added to an instance of the resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a burst of multimedia data, and wherein the resource cycle number is based at least in part on the specified time offset. The apparatus may include means for receiving a burst of multimedia data during a subframe.

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

[0033] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for preparing for communication with a UE according to a DRX cycle. The apparatus may include means for starting to send a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset.

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

[0035] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings and description and as illustrated in the accompanying drawings and description.

[0036] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above in order to better understand the subsequent specific embodiments. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0037] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. 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 purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0039] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0040] Figure 2 is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0041] Figure 3 is a diagram illustrating an example of a device designed for low-latency applications according to the present disclosure.

[0042] Figure 4 is a diagram illustrating an example of low-latency traffic and power states according to the present disclosure.

[0043] Figure 5 Examples of misalignment of discontinuous reception (DRX) cycles and extended reality traffic periodicity according to the present disclosure are illustrated.

[0044] Figure 6An example of an anchor cycle with a skipped DRX cycle according to the present disclosure is illustrated.

[0045] Figure 7 An example of a DRX configuration with dynamic offset adjustment supporting DRX techniques with non-uniform cycle durations according to the present disclosure is illustrated.

[0046] Figure 8 is a diagram illustrating an example of using a short cadence value for DRX according to the present disclosure.

[0047] Fig. 9 is a diagram illustrating an example of using a short cadence value for DRX for slot positioning according to the present disclosure.

[0048] Fig.10 is a diagram illustrating an example of using a short cadence value for DRX according to the present disclosure.

[0049] Fig.11 is a diagram illustrating an example of using different short rhythm values ​​according to the present disclosure.

[0050] Fig.12 is a diagram illustrating an example of using a short cadence value for DRX according to the present disclosure.

[0051] Fig.13 is a diagram illustrating an example of using a short cadence value for DRX according to the present disclosure.

[0052] Fig.14 is a diagram illustrating an example of system frame number wrapping according to the present disclosure.

[0053] Fig.15 is a diagram illustrating an example of setting a superframe length according to the present disclosure.

[0054] Fig.16 is a diagram illustrating an example of a radio resource control (RRC) configuration for a DRX cycle according to the present disclosure.

[0055] Fig.17 is a diagram illustrating an example of aligning a DRX cycle and multimedia periodicity according to the present disclosure.

[0056] Fig.18 is a diagram illustrating an example associated with using a specified time offset according to the present disclosure.

[0057] Fig.19 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0058] Fig. 20 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0059] Fig.21 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0060] Fig. 22 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0061] Fig.23 is a diagram illustrating an example process performed, for example, by a base station according to the present disclosure.

[0062] Fig.24 is a diagram illustrating an example process performed, for example, by a base station according to the present disclosure.

[0063] Fig.25 is a diagram illustrating an example process performed, for example, by a base station according to the present disclosure.

[0064] Fig.26 is a block diagram of an example apparatus for wireless communications according to the present disclosure.

[0065] Fig. 27 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0066] Fig.28 is a diagram illustrating an example of a specific implementation of code and circuits for an apparatus according to the present disclosure.

[0067] Fig.29 is a block diagram of an example apparatus for wireless communications according to the present disclosure.

[0068] Fig.30 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0069] Fig.31 is a diagram illustrating an example of a specific implementation of code and circuits for an apparatus according to the present disclosure.

[0070] Fig.32 is a diagram illustrating an example of a jump offset mode according to the present disclosure.

[0071] Fig.33A is a diagram illustrating an example of a subframe index according to the present disclosure.

[0072] Fig.33B is a diagram illustrating an example of a subframe index according to the present disclosure.

[0073] Fig.34 is a diagram illustrating an example of backward compatibility according to the present disclosure.

[0074] Fig.35is a diagram illustrating an example of handling backward compatibility according to the present disclosure.

[0075] Fig.36 is a diagram illustrating an example associated with using SFN wrap-around offset according to the present disclosure.

[0076] Fig.37A is a diagram illustrating an example of using SFN wrap-around offset according to the present disclosure.

[0077] Fig.37B is a diagram illustrating an example of receiving a configuration for resource recycling according to the present disclosure.

[0078] Fig.37C is a diagram illustrating an example of receiving a configuration for resource recycling according to the present disclosure.

[0079] Fig.37D is a diagram illustrating an example of receiving a configuration for resource recycling according to the present disclosure.

[0080] Fig.37E is a diagram illustrating an example of receiving a configuration for resource recycling according to the present disclosure.

[0081] Fig.37F is a diagram illustrating an example of receiving a configuration for resource recycling according to the present disclosure.

[0082] Fig.38 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0083] Fig.39 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0084] Fig.40 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0085] Fig.41 is a diagram illustrating an example of a specific implementation of code and circuits for an apparatus according to the present disclosure. DETAILED DESCRIPTION

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

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

[0088] The techniques described in more detail below improve the alignment of the DRX cycle and multimedia traffic to reduce the mismatch between multimedia burst traffic and the DRX on duration. For example, the UE may use a wake-up condition to determine when to wake up, which may include adding a specified time offset to the on duration of the DRX cycle (e.g., the next on duration), which may be a fixed time shift. The wake-up condition may be based at least in part on a subframe number of a subframe of a frame that may be identified by a system frame number (SFN) in one or more aspects. The specified time offset may be added based at least in part on the DRX cycle number and the DRX cycle length of the DRX cycle. In some aspects, the DRX cycle may be a jump cycle that adds a jump offset or time amount (e.g., 1 ms) to realign the XR traffic burst with the DRX on duration. In some aspects, the UE may be configured with a jump offset pattern for which DRX on durations the jump offset is to be applied. The jump offset pattern may be applied per jump cycle, which may include a certain number of DRX on durations. The anchor cycle may include multiple jump cycles.

[0089] According to one or more aspects, a UE may configure a DRX cycle for a cadence of data bursts, such as every 8.33 ms at 120 Hz, but the cadence of the data bursts may be associated with a periodicity of 1000 ms. In one or more examples, with a multimedia periodicity of 1000 ms and a DRX cycle of 10240 ms (1024 SFNs per superframe at 10 ms), a superframe of DRX (formed by a number of SFNs, such as 1024 SFNs) may be misaligned with a frame of a multimedia server every 10.24 seconds. When the SFN returns to 0 at the end of a superframe, an SFN wraparound occurs. Due to the difference between the periodicity of the data burst (e.g., 1000 ms) and the length of the superframe (e.g., 10240 ms), the SFN wraparound may cause the on-duration of the DRX cycle to be misaligned with the data burst. In some aspects, a wake-up condition may illustrate such a SFN wraparound problem in which the end of a superframe (the end of 1024 SFNs) causes a misalignment of a subframe index and a traffic burst. For example, the UE may wake up based at least in part on the SFN wrap-around offset adjusted for the misalignment caused by the end of the superframe. As a result, the UE may not miss traffic bursts and communication performance may improve.

[0090] In some aspects, the SFN wrap offset may be based at least in part on the counter m. The initial value of m may be based at least in part on when the resource cycle configuration is received. Thus, the UE may apply the correct SFN wrap offset. The UE may not miss traffic bursts and communication performance may be improved.

[0091] Although various aspects described herein apply to examples having a DRX cycle, various aspects described herein may also apply to other resource cycles.

[0092] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0093] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0094] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0095] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, as well as other examples. 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, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The 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, a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0096] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, BS110a may be a macro base station for macrocell 102a, BS110b may be a pico base station for picocell 102b, and BS110c may be a femto base station for femtocell 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.

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

[0098] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "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 a device configured to perform one or more functions, such as those described herein in conjunction with 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 repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these 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 but not the other. In this way, a single device may include more than one base station.

[0099] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. A base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.

[0100] The wireless network 100 may 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 transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0101] The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly or indirectly with each other via wireless or wired backhaul communication links.

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

[0103] Some UEs 120 may be considered as machine type communication (MTC) 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 may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, a connection to a network (e.g., a wide area network such as the Internet or a cellular network) or a connection to a network via a wired or wireless communication link. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0105] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0106] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that FR1 is often (interchangeably) referred to as the "sub-6 GHz" band, although portions of FR1 are greater than 6 GHz. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0107] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0108] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0109] In some aspects, the UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may sleep in association with a DRX cycle; wake up starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset; and receive a multimedia data burst during the subframe.

[0110] In some aspects, the communication manager 140 may sleep in association with a DRX cycle; wake up starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on duration of the DRX cycle based at least in part on a DRX cycle number and a DRX time reference system frame number (SFN) of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset; and receive a multimedia data burst during the subframe.

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

[0112] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may prepare for communication with the UE according to a DRX cycle; and begin sending a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-Duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset.

[0113] In some aspects, the communication manager 150 may prepare for communication with the UE according to a DRX cycle; and start sending a data burst at a subframe based at least in part on a specified time offset, wherein the specified time offset is added to the on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of the multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset.

[0114] In some aspects, the communication manager 150 may prepare for communication with the UE according to the resource cycle; and begin sending a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an instance of the resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of the multimedia data burst, wherein the resource cycle number is based at least in part on the specified time offset, and wherein the resource cycle number 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.

[0115] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0116] Figure 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0117] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may 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 to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 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 to 234t).

[0118] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may 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 may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide 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 may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0120] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0121] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 (eg, one or more memories) to perform the operations described herein (eg, with reference to Figures 3 to 41 ) or any aspects of any of the methods described herein.

[0122] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be configured by a processor (e.g., controller / processor 240) and memory 242 (e.g., one or more memories) to perform operations described herein (e.g., with reference to FIG. 1 ). Figures 3 to 41 ) or any aspects of any of the methods described herein.

[0123] A controller / processor 240 of a network entity (e.g., base station 110), a controller / processor 280 of UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of may perform or direct e.g. Fig. 20 The process of 2000, Fig.21 Process 2100, Fig. 22 The process 2200 Fig.23 Process 2300, Fig.24 The process 2400 Fig.25 The process of 2500 Fig.38 3800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes 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, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion and / or interpretation), may cause the one or more processors, UE 120 and / or base station 110 to perform or direct, for example, Fig. 20 The process of 2000, Fig.21 Process 2100, Fig. 22 The process 2200 Fig.23 Process 2300, Fig.24 The process 2400 Fig.25 The process of 2500 Fig.38 The process 3800 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0124] In some aspects, a UE (e.g., UE 120) includes: means for sleeping in association with a DRX cycle; means for waking up at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset; and / or means for receiving a multimedia data burst during a subframe. Means for the UE to perform operations described herein may include, for example, one or more of the following: communications 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.

[0125] In some aspects, the UE includes: means for sleeping in association with a DRX cycle; means for waking up starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number and a DRX time reference system frame number (SFN) of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset; and / or means for receiving a multimedia data burst during the subframe.

[0126] In some aspects, the UE includes: means for sleeping in association with a resource cycle; means for waking up starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an instance of the resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a burst of multimedia data, and wherein the resource cycle number is based at least in part on the specified time offset; and / or means for receiving a burst of multimedia data during the subframe.

[0127] In some aspects, a network entity (e.g., a base station 110) includes: means for preparing for communication with a UE according to a DRX cycle; and / or means for starting to send a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. In some aspects, means for a network entity to perform operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0128] In some aspects, the network entity includes: means for preparing communications with a UE according to a DRX cycle; and / or means for sending a data burst starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset.

[0129] In some aspects, the network entity includes: means for preparing communications with a UE in accordance with a resource cycle; and / or means for starting sending a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an instance of the resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, wherein the resource cycle number is based at least in part on the specified time offset, and wherein the resource cycle number is based at least in part on the specified time offset.

[0130] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by the controller / processor 280 or under the control of the controller / processor.

[0131] Although Figure 2The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by the controller / processor 280 or under the control of the controller / processor.

[0132] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0133] Figure 3 is a diagram illustrating an example 300 of a device designed for low-latency applications according to the present disclosure.

[0134] Some devices, including those for XR, may require low-latency traffic to and from an edge server or cloud environment. Example 300 illustrates communication between an XR device and an edge server or cloud environment via a base station (e.g., a gNB). The XR device may be an augmented reality (AR) glasses device, a virtual reality (VR) glasses device, or other gaming device. The XR device may have limited battery capacity while being expected to have the battery life of a smartphone (e.g., all-day use). Even if the XR device is connected to a smartphone and uses the same smartphone battery, battery power is an issue. XR device power consumption may be limited and may result in an uncomfortable user experience and / or short battery life.

[0135] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0136] Figure 4 is a diagram illustrating an example 400 of low-latency traffic and power states according to the present disclosure.

[0137] Power consumption can be reduced by limiting the amount of active time that the processing resources of the XR device are used for computing and power consumption. Some wireless communication systems may support UEs operating in DRX mode, such as XR devices. A UE in DRX mode can transition between sleep and wakeup. Sleep may include entering or being in a DRX inactive state (e.g., sleep state, power saving mode) to achieve power saving. Wakeup may 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 a DRX "on duration". A DRX cycle may be a duration including a sleep state and an active on duration state of the UE. A DRX cycle may start at the beginning of the on duration and end at the beginning of the next on duration. Different DRX cycles may have different lengths (e.g., 8 milliseconds (ms), 16ms). UEs using different DRX cycles may have non-consistent cycle durations within a DRX time period, which is a larger duration including multiple DRX cycles. This inconsistent cycle duration may provide a DRX on duration that is aligned with the periodicity of downlink traffic to the UE. In some cases, the DRX period may correspond to an anchor cycle that spans a DRX cycle set, and a subset of the DRX cycle set may have a different cycle duration than other DRX cycles in the DRX cycle set. In some cases, an on-duration offset value may be indicated for one or more DRX cycles within the DRX period (e.g., via downlink control information (DCI) or MAC CE).

[0138] By offloading some computations to the edge server, the XR device can save processing resources. Example 400 shows a scenario in which the XR device can split the computation of the application with the 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 video frames, align video frames with user posture information, and perform other related calculations. However, this means that there may 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) may have a periodic pattern corresponding to the frame rate of the video data sent (e.g., H.264 / H.265 encoded video). This downlink traffic can be quasi-periodic, with one data burst per frame at a rate of one frame per second (1 / fps), or two "eye buffers" per frame at a rate of 1 / (2*fps) that may be interleaved. For example, XR downlink traffic may include more than 100 kilobytes (KB) of data at 45, 60, 75, or 90 frames per second (e.g., every 11 ms, 13 ms, 16 ms, or 22 ms). XR uplink traffic may include controller information for gaming, information for VR split rendering, and / or user gesture information. XR uplink traffic may include 100 bytes every 2 ms (500 Hz). XR devices may reduce this periodicity to align XR uplink traffic with XR downlink traffic.

[0139] For low-latency applications, the DRX cycle and the start offset of the DRX cycle will be aligned with the downlink traffic arrival time. For example, an XR device may serve a user and enter a short sleep state in a DRX cycle, and do so between video frames. XR devices and edge servers may attempt to align uplink and downlink DRX cycles as part of connected DRX (CDRX). However, there is a DRX multimedia timing mismatch, which prevents such alignment and prevents the successful use of CDRX. For example, the update rate may be, for example, 120Hz or 60Hz, resulting in a downlink traffic burst arrival periodicity of 8.333ms or 16.667ms, respectively. However, a conventional DRX configuration may have one millisecond as the finest granularity of the DRX cycle, and the start of the on-duration may be aligned with a millisecond time boundary. These partial millisecond differences may be compounded with each instance of the cycle to misalign the DRX cycle with the XR traffic periodicity. For example, the XR traffic cycle may drift to the middle of the DRX cycle. This results in increased latency and power consumption.

[0140] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0141] Figure 5An example 500 of misalignment of DRX cycles and XR traffic periodicity according to the present disclosure is illustrated. Example 500 shows a downlink traffic burst arrival 505, which may include multiple downlink traffic bursts 510 sent according to a periodic pattern. Example 500 also shows a first regular DRX configuration 515 and a second regular DRX configuration 520.

[0142] The downlink traffic bursts 510 may include, for example, XR downlink traffic with a periodic pattern corresponding to the frame rate of the transmitted data (e.g., H.264 / H.265 encoded video). The update rate may be, for example, 120 Hz or 60 Hz, resulting in a downlink traffic burst arrival periodicity 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 one millisecond as the finest granularity of the DRX cycle, and the start of the on-duration may be aligned with a millisecond time boundary.

[0143] exist Figure 5 In the example of , an update rate of 120 Hz is illustrated for the burst arrival 505, resulting in an 8.333 ms periodicity for the downlink traffic burst 510. Where 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 will also each be within the subsequent two on-durations. However, the fourth downlink burst 510-d will miss the fourth on-duration because it will occur 0.333 seconds after the end of the fourth on-duration. Where the second conventional DRX configuration 520 is selected instead, the result will be 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.

[0144] Furthermore, in the case where the DRX configuration is to be modified to have the finest granularity corresponding to a slot or symbol, this misalignment may continue to occur due to the fact that the burst arrival 505 has a periodicity that is not a multiple of the slot or symbol duration. For example, since the traffic burst interval (120 Hz or 60 Hz) expressed in milliseconds has a factor of 3 in the denominator, which does not divide the numerator (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, in the case where the DRX cycle granularity can be defined in slots, the expression would be the number of slots per second divided by the source update rate in Hz. The misalignment between the downlink traffic burst 510 and the on-duration may add additional latency to the communication, where the additional latency is cyclic. For example, in the first missed on-duration of an 8 ms DRX configuration, the downlink traffic burst may be retransmitted at the next on-duration that occurs 7 ms later than the missed on-duration. Subsequent downlink traffic bursts will have lower latency that decreases by 0.333 ms per cycle until the downlink traffic burst is again aligned with the on-duration in 21 cycles, where this alignment lasts for three cycles. Thus, in this example, the alignment and misalignment of the downlink traffic bursts will be cyclical, 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 reduced, which also results in a corresponding increase in power consumption due to the additional on-duration. Thus, the XR device may consume additional processing resources.

[0145] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0146] Figure 6 An example 600 of an anchor cycle with skipped DRX cycles according to the present disclosure is illustrated.

[0147] In some scenarios, the UE (e.g., an XR device) and the network may use an anchor cycle with a skip DRX cycle to better align the DRX cycles to reduce latency and save energy consumption. For example, the UE and the network may implement an anchor cycle with a skip DRX cycle. The anchor cycle may include a cycle with multiple DRX cycles, one of which is a DRX skip cycle. A DRX skip cycle may occur every specified number of DRC cycles. The DRX skip cycle may be a DRX cycle whose timing of the on-duration is adjusted (e.g., by using an additional DRX offset that aligns the on-duration with the multimedia periodicity). The downlink traffic burst arrival 605 may include multiple downlink traffic bursts 610 sent according to a periodic pattern. The downlink traffic burst 610 may include, for example, XR downlink traffic having, for example, a periodic pattern of a downlink traffic burst 610 every 8.333 ms. The anchor cycle 620 may, for example, span three DRX cycles 615, and the third DRX cycle may be a skip cycle 625 having a cycle duration longer than the initial 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 skip cycles 625. The anchor cycle 620 may be used as a basis for determining the timing of radio resource management (RRM) functions. In some cases, the skip cycle 625 may include one or more additional time slots compared to other DRX cycles of the anchor cycle 620. The position of the skip cycle 625 may vary within the anchor cycle 620. Although the example 600 shows a burst arrival 605 associated with periodic traffic with a 120 Hz update rate, and the anchor cycle 620 includes three DRX cycles with durations of 8 ms, 8 ms, and 9 ms, other configurations may be used for different periodicities or patterns of downlink traffic. For example, for periodic traffic with a 60 Hz update rate, an anchor cycle with three DRX cycles of 16 ms, 17 ms, 17 ms may be configured, or the three DRX cycles may have durations of 16 ms, 16 ms, 18 ms, respectively. The order of the skip cycles 625 among the DRX cycles within the anchor cycle 620 may also be configured. For example, for a 120 Hz update rate, a DRX cycle with durations of (8ms,8ms,9ms), (8ms,9ms,8ms), or (9ms,8ms,8ms) can be configured. Support for such variation options in sequencing can help offset the corresponding on-durations of multiple users in time to better distribute resource utilization over time.

[0148] In some cases, the base station may configure the DRX configuration for the UE 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 with a specific update rate, or based on historical downlink burst transmissions to the UE), and that the periodic traffic is not aligned with a slot or subframe boundary. 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 providing a 25 ms anchor cycle duration), the number of DRX cycles within the anchor cycle 620, and which of the DRX cycles will 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 signal to the base station that the UE has the ability to perform DRX procedures with inconsistent DRX cycles, and the network node may enable this capability when providing the DRX configuration. In other cases, other techniques may be used to configure inconsistent DRX cycles, such as by adjusting the start offset of the on-duration of the DRX cycle, such as in conjunction with Figure 7 discussed.

[0149] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0150] Figure 7 An example 700 of a DRX configuration with dynamic offset adjustment according to the present disclosure that supports a DRX technique with inconsistent cycle duration is illustrated. Example 700 shows a downlink traffic burst arrival 705 that includes multiple downlink traffic bursts 710 sent according to a periodic pattern. Example 700 also shows a DRX configuration 715 with inconsistent cycle duration.

[0151] The downlink traffic burst 710 may include, for example, XR downlink traffic having a periodic pattern of a downlink traffic burst 710 every 8.333 ms. In example 700, the DRX configuration 715 has a configuration of an 8 ms DRX cycle duration and a 1 ms on-duration. In the initial DRX cycle of the downlink traffic burst 710, the on-duration may have a zero 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 adjust 720 the DRX on-duration start offset after the third downlink burst 710-c, which in this example may increase the on-duration start offset by one millisecond so that the adjusted DRX on-duration is aligned with the fourth downlink traffic burst 710-d. After the fourth downlink traffic burst 710-d, the UE may make another adjustment to the on-duration offset to return to the original offset, so that the DRX cycle may be configured to align the on-duration with the downlink traffic burst 710.

[0152] In some cases, the DRX on-duration start offset adjustment may be predefined based on a specification, or defined in the DRX configuration (e.g., provided in RRC signaling). For example, different types of traffic (e.g., XR traffic) and different periodicities (e.g., based on 120 Hz or 60 Hz update rates) may define a DRX start offset according to a pattern such as in example 700 (e.g., a start offset of 1 ms is increased every 4 DRX cycles). In some cases, the DRX start offset may be dynamically indicated (e.g., based on a MAC CE or DCI) in a previous downlink transmission.

[0153] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0154] Figure 8 is a diagram illustrating an example 800 of using short cadence values ​​for DRX in accordance with the present disclosure. Example 800 shows a burst of traffic arriving 810 at a rate of 120 Hz.

[0155] Combination Figures 3 to 7The described techniques may improve the alignment of the DRX cycle and 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., XR device) and the network may further improve such alignment by using a DRX short cadence corresponding to a number of Hz (e.g., number of instances per second) instead of an integer value ms. The DRX short cadence value may correspond to a number of Hz, for example, by being defined by a number of Hz or by being defined by a value derived from a number based on Hz or a similar or related unit or from a number based on Hz or a similar or related unit. The DRX short cadence (drx-ShortCadence) may 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 burst received by the UE according to the video frame rate. That is, the DRX short cadence value may be a DRX timing value corresponding to the same time unit or frequency unit (e.g., video frame rate) at which the UE receives the traffic burst. This is in contrast to a conventional DRX cycle having a DRX long cycle that is the length (duration) of the DRX cycle and has a unit granularity of milliseconds. Once the base station (e.g., gNB) obtains the frame rate of the traffic burst to the UE or the periodicity of the traffic burst to the UE, the base station may set the DRX short rhythm value. The UE may receive the DRX short rhythm value from the base station or obtain the DRX short rhythm value based at least in part on the frame rate or the periodicity of the traffic.

[0156] The UE may use the DRX short cadence value to determine when to wake up and decode a physical downlink control channel (PDCCH) grant from the base station within the on-duration as part of the DRX short cadence cycle 820. The UE may determine when to wake up on a subframe-by-subframe basis or on a time slot-by-time slot basis. For example, as shown in reference numeral 830, the UE may calculate in the first part of the current subframe (with a subframe identifier n) whether the current subframe meets a specific criterion. The criterion may be associated with the DRX short cadence value and the subframe identifier, and may be designed so that the subframes (or time slots) that meet the condition are aligned with the timing of the frame rate or the periodicity of the traffic bursts received by the UE. Each subframe may be 1 ms and include multiple time slots (e.g., 2, 6, 8). The criterion may be associated with a system frame number (SFN). For a subframe with a subframe identifier n=[(SFN*10)+subframe number], the UE may wake up when a first upper limit value (the smallest integer higher than the calculated value) of (n*drx-ShortCadence / 1000)+1 is equal to a second upper limit value of (n+1)*(drx-ShortCadence / 1000). SFN may be a number between 0 and 1023 of a frame, and the subframe number may be a number between 0 and 9 within a frame. For example, when the DRX cadence value is 120 Hz and the subframe number is 5 in a frame with SFN of 800, the subframe identifier n of the subframe may be (800*10)+5 or 8005. The first upper limit value may be a minimum integer of (8005*120 / 1000)+1, or 961. The second upper limit value may be a minimum integer of (8005+1)*(120 / 1000), or 960. The first upper limit value and the second upper limit value are not equal, and therefore the UE does not meet the criterion and wakes up within the subframe. However, a later subframe with subframe number 8 may render the first upper limit value 961 (the smallest integer of (8008*120 / 1000)+1) and the second upper limit value 961 (the smallest integer of (8008+1)*(120 / 1000)), and therefore the UE may meet the criterion and wake up during the subframe. This calculation may be performed at the beginning of each subframe. In some aspects, multiple calculations may be performed for multiple subframes at once.

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

[0158] As shown by reference numeral 835, the UE may wake up within the on-duration at 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 that the UE will be awake, and may be, for example, 1 ms or 2 ms. For example, in the case where the UE wakes up at subframe 8 and the DRX on-duration timer is 2 ms, the UE may remain awake through subframes 8 and 9. In the event that 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 is started for the DRX group.

[0159] In some aspects, there may be a skip of 1 subframe per a specified number of cycles, similar to combining Figure 6 The skip cycle technique described. For example, for an 8 ms cycle, when the duty cycle is 8.333 ms for 120 Hz, there may be a jump of 1 subframe (1 ms) every 3 cycles to accommodate the 1 / 3 subframe portion. That is, for a 120 Hz DRX short rhythm, the UE may determine to wake up in subframes n=8, 16, 25, 33, 41, 50, etc. As shown by reference numeral 840, after waking up at subframes 8 and 16, the UE may skip 1 subframe to wake up at subframe 25 instead of waking up at subframe 24. In the case where example 800 continues to show the on-duration subframe, the UE may then wake up at subframe 33 after 8 ms and at subframe 41 after another 8 ms. The UE may skip 1 subframe and wake up at subframe 50 instead of waking up at subframe 49 after 8 ms. In some aspects, the UE may skip calculations for one or more subframes after the on-duration until the next possible on-duration is approached.

[0160] In some aspects, the UE may use a DRX start offset and / or a DRX slot offset to provide greater granularity about when to wake up within a subframe to more closely align with the UE's traffic periodicity. The UE may wake up and start the DRX on duration timer after a DRX start offset (drx-StartOffset) and / or a DRX slot offset (drx-SlotOffset) from the beginning of the subframe (n+drx-StartOffset). The DRX start offset may be a number of ms or microseconds (μs) (or set to zero ms or μs for no DRX start offset), a symbol, a slot, or a microslot. The DRX start offset may be used to stagger multiple UEs in time. The DRX slot offset may be the number of slots. For example, in the case of 8 slots in a subframe (such as for mmWave), each slot is 125μs or 0.125ms. In the case of a DRX slot offset of 2 slots, the wake-up time is offset by (2*0.125) or 0.250ms. In the case where the wake-up time is 8ms, 16ms, 25ms, 33ms, 41ms, 50ms, etc. according to 120Hz, the UE may use DRX slot offsets to better match traffic bursts at 8.33ms, 16.66ms, and 25ms by using a DRX slot offset of 8.250ms for 2 slots at subframe 8, a DRX slot offset of 16.625ms for 5 slots at subframe 16, a no DRX slot offset of 25.000ms at subframe 25, etc. Figure 8 As shown in the table for 120 Hz in , the UE can therefore better align the DRX cycle with the traffic cycle to further reduce latency and save signaling resources.

[0161] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0162] Fig. 9 9 is a diagram illustrating an example 900 of using a short cadence value of DRX for time slot positioning according to the present disclosure. Example 900 shows a traffic burst 905 among multiple burst arrivals 910 arriving at a rate of 120 Hz. The burst arrivals 910 in example 900 may be similar to Figure 8 The burst arrival 810 shown in example 800 is the same.

[0163] In some aspects, the calculation based on the subframe identifier per subframe can be extended to the time slot positioning with the time slot identifier k. That is, the criteria for waking up can be based at least in part on the time slot identifier k being equal to (((SFN*10)+subframe number)*number of time slots per second)+time slot number. In the case where the first upper limit value of (k*drx-ShortCadence / 1000*number of time slots per second)+1 is equal to the second upper limit value of ((k+1)*(drx-ShortCadence / 1000*number of time slots per second)), the UE can wake up at time slot k and start the DRX on duration timer. The calculation can be per time slot instead of per subframe. As shown by reference numeral 920, the UE can determine whether the calculation for the current time slot based at least in part on the DRX short rhythm and the time slot identifier meets the criteria for waking up. As shown by reference numeral 925, in the case where the UE is to wake up, the UE can wake up within the on duration 930, which can be a subframe or 8 time slots. In some aspects, the calculation can be performed simultaneously at the beginning of the subframe. In other words, the UE may meet a certain criterion associated with a DRX short cadence value (corresponding to Hz) and a slot identifier for the slot that uniquely identifies the slot among consecutive slots in a cycle or time period. This criterion or any criterion calculated for a given slot may be designed to use the DRX short cadence value to wake up within the slot based on the frame rate or periodicity of the traffic burst to the UE. In some aspects, the UE may skip calculations for one or more slots or subframes after the on-duration.

[0164] In some aspects, the UE may wake up after a DRX start slot offset (drx-StartSlotOffset) from the beginning of a subframe (n+drx-StartOffset) and start a DRX on duration timer. The DRX start slot offset may be a number of ms, microseconds (μs) (or set to zero ms or μs for no DRX start offset), symbols, slots, or microslots. The DRX start slot offset may be used to stagger the UE in time with other UEs. The DRX start slot offset may be updated based at least in part on how many UEs are transmitting, how long the UEs stay, and whether there is a change in UE behavior.

[0165] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 The examples described are different.

[0166] Fig.10 1 is a diagram illustrating an example 1000 of using a short cadence value for DRX according to the present disclosure. Fig.10As shown, a base station 1010 (e.g., base station 110) can communicate with a UE 1020 (e.g., UE 120). Base station 1010 and UE 1020 can be part of a wireless network (e.g., wireless network 100).

[0167] UE 1020 may obtain a DRX short cadence value, which may be defined as a number of Hz. As shown in reference numeral 1025, base station 1010 may send the DRX short cadence value to UE 120. UE 1020 may also obtain the DRX short cadence value from the stored configuration information. For example, UE 1020 may select the DRX short cadence value from a plurality of DRX short cadence values ​​based at least in part on the periodicity of the traffic bursts (e.g., video frame rate) determined to be sent by base station 1010, as shown in reference numeral 1030.

[0168] As shown by reference numeral 1035, the UE 1020 may sleep and wake up according to the DRX short cadence value. For example, the UE 1020 may calculate, for each subframe, whether the subframe identifier causes the UE 1020 to meet the criteria 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 subframe identifier n=[(SFN*10)+subframe number]. In the case of 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 criteria are not met (the condition is false). In the case of 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 satisfied (the condition is true). In the case of 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 satisfied (the condition is false). In some aspects, the UE 1020 may use a hopping cycle, a slot offset, a timing offset, or any other technique described herein to better match the periodicity of the traffic burst. As part of the wake-up, the UE 1020 may start an on-duration timer.

[0169] In some aspects, the UE 1020 may perform a calculation for each time slot to determine whether the time slot identifier causes the UE 1020 to meet the criteria 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 time slot identifier k=[((SFN*10+subframe number)*number of time slots per second)+time slot number]. The number of time slots per second (slotPerSec) for 120 Hz may be 8 time slots per second. In the case of the time 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 criteria is not met (the condition is false). In the case of time slot identifier k=8*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 satisfied (the condition is true). In the case of time slot identifier k=8*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 satisfied (the condition is false). In some aspects, the UE 1020 may use hopping cycles, time slot offsets, timing offsets, or any other technique described herein to better match the periodicity of traffic bursts.

[0170] As indicated above, Fig.10 are provided as examples. Other examples can be found in the Fig.10 The examples described are different

[0171] Fig.11 is a diagram illustrating an example 1100 of using different short tempo values ​​according to the present disclosure. Fig.11 Tables for different DRX short cadence values ​​are shown, including tables for 48 Hz, 60 Hz, 80 Hz and 90 Hz to match the corresponding frame rates of 48 Hz, 60 Hz, 80 Hz and 90 Hz. Figure 8 For the 120Hz table, Fig.11The first column in each table of indicates the periodicity of the traffic bursts (ms between traffic bursts - corresponds to the frame rate / short cadence value). The second column in each table indicates the wake-up time (in ms) when the criteria are met for the short cadence value to match the periodicity in the first column. The third column indicates (in ms) the wake-up time when a slot offset (e.g., 0.125 ms increments) is used to more closely match the periodicity indicated in the first column.

[0172] In other words, the UE may calculate whether a subframe (or time slot) meets the criteria for wake-up based at least in part on a subframe identifier for a subframe (or a time slot identifier for a time slot) and a DRX short cadence value of 48 Hz, 60 Hz, 80 Hz, 90 Hz, or 120 Hz. The criteria may be designed so that the UE starts waking up at the subframe and / or time slot that is the closest match or alignment to the traffic burst according to the periodicity of the traffic burst. The UE may use a time slot offset to closely match the periodicity. In this way, the UE matches the wake-up time more closely to the traffic burst in order to save power and processing resources while not missing any traffic burst during the on-duration period. The UE may adjust the on-duration period in coordination with the short cadence value and / or the time slot offset value as necessary. Note that other DRX short cadence values ​​may be used to match frame rates of 45 Hz, 75 Hz, or other frame rates for applications or services not explicitly listed herein.

[0173] As indicated above, Fig.11 are provided as examples. Other examples can be found in the Fig.11 The examples described are different.

[0174] Fig.12 is a diagram illustrating an example 1200 of using short cadence values ​​for DRX in accordance with the present disclosure. Example 1200 shows a burst of traffic arriving at a rate of 120 Hz.

[0175] As part of enhanced connected mode DRX (EC-DRX or eCDRX), there is an additional solution for better matching multimedia cadence. In one scenario, the base station may detect that the offset between the on-duration opportunities needs to be changed 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 signal the change in the offset between the on-duration opportunities. For example, the MAC CE may indicate that the next offset will increase by 1 ms, or shift from 8 ms to 9 ms. The MAC CE may indicate an offset value from a list of absolute values ​​or the number of time slots used to shift the offset (from a list of relative values).

[0176] As indicated above, Fig.12 are provided as examples. Other examples can be found in the Fig.12 The examples described are different.

[0177] Fig.13 is a diagram illustrating an example 1300 of using short cadence values ​​for DRX according to the present disclosure. Example 1300 shows a burst of traffic arriving at a rate of 120 Hz.

[0178] DRX may involve a DRX short cycle. In case a DRX short cycle is used for a DRX group where [(SFN×10)+subframe number] modulo(drx-ShortCycle)=(drx-StartOffset) modulo(drx-ShortCycle), the UE may start a drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of a 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.

[0179] DRX may involve a DRX long cycle. In case a DRX long cycle is used for a DRX group where [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset, the UE may start a drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of a subframe.

[0180] In some aspects, a two-level DRX configuration may define an outer DRX cycle and an inner DRX cycle to construct a skip DRX cycle. The outer DRX may be the same as traditional DRX that only supports consistent DRX. The inner DRX may support sub-cycles that may be non-consistent. The start of the first inner DRX cycle may be aligned to the start of the outer DRX, and the end of the last inner DRX cycle may be aligned to the end of the outer DRX. The configured on-duration, inactivity timer, and other DRX parameters for the inner DRX cycle may be the same as the on-duration, inactivity timer, and other DRX parameters of the outer DRX cycle. In the case where the outer DRX cycle is configured as 25ms 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 sub-cycles within the on-duration.

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

[0182] As indicated above, Fig.13 are provided as examples. Other examples can be found in the Fig.13 The examples described are different.

[0183] Fig.14 is a diagram illustrating example 1400 of SFN wrapping according to the present disclosure. Example 1400 shows a burst of multimedia data arriving at a rate of 120 Hz. In example 1400, drx-StartOffset is set to 0.

[0184] The UE may configure a DRX cycle for a 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. In the case where the multimedia periodicity is 1000 ms and the DRX cycle is 10240 ms (1024 SFNs per superframe at 10 ms), the superframe of the DRX may be misaligned with the frame of the multimedia server every 10.24 seconds. Due to the misalignment between the superframe periodicity (10240 ms) and the multimedia periodicity, there is a drift 1404 of 1.666 ms (2 ms in the example 1400) every 10.24 seconds (10240 ms). In other words, the superframe 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 superframe, and this partial frame causes the SFN wraparound problem in the next superframe. Other multimedia periodicities result in other numbers of frames per superframe that are not aligned with a certain number of SFNs as follows: 45 Hz (460.8 SFNs), 48 Hz (491.52 SFNs), 60 Hz (614.4 SFNs), or 90 Hz (921.6 SFNs).

[0185] Example 1400 shows the end of a superframe (at SFN 1023) and the beginning of the next superframe (at SFN 0) or when the SFN number wraps around (restarts or returns to 0) for the next superframe. When the end of superframe 1402 is reached, an on-duration wake-up condition or formula such as (SFN*10)+subframe number=0 may select a subframe within the on-duration between data bursts due to the SFN wraparound. Because the subframes may not align with the data bursts, the data bursts may not be received. This may result in degradation of communications which may consume additional processing resources and signaling resources.

[0186] As indicated above, Fig.14 are provided as examples. Other examples can be found in the Fig.14 The examples described are different.

[0187] Fig.15 is a diagram illustrating an example 1500 of setting a superframe length according to the present disclosure. Example 1500 shows a burst of multimedia data arriving at a rate of 120 Hz.

[0188] In some aspects, a network entity (e.g., base station 110) may configure a UE (e.g., UE 120) to set a superframe length based at least in part on a cadence of multimedia data bursts, as shown by reference numeral 1505. The cadence of multimedia data bursts may correspond to a number of Hz, and the number of frames forming the superframe length may be a multiple of the time periodicity of the number of Hz. For example, the UE may set the superframe length to 1000 SFNs instead of 1024 SFNs, so that there is no SFN wraparound at the end of the superframe, which would cause the calculated on-duration timing in the next superframe to be misaligned. The superframe length may also be 1000 frames or 10,000 subframes. In some aspects, the UE may maintain an SFN counter for the superframe and reset the counter for the next superframe when the superframe length (end of the superframe) is reached. The UE may initialize the SFN counter with the current SFN. The SFN counter is incremented when the SFN is updated. As a result of setting the superframe length to match the rhythm or periodicity of the multimedia data burst, there will be no misalignment and frequent drift in timing when the UE receives the multimedia data burst, as shown by reference numeral 1510. By adjusting the superframe length, the UE can align the on-duration opportunity with the data burst to improve communication and enable the UE to avoid consuming additional processing resources and signaling resources. In some aspects, the network entity can select the superframe length and send the superframe length in the configuration information.

[0189] The UE may use the set superframe length to determine a subframe identifier of a DRX on-duration subframe for receiving a multimedia data burst by performing a modulo operation with the superframe length, and may configure a DRX cycle for the cadence of the multimedia data burst. For example, where a subframe identifier n for calculating the on-duration subframe was previously determined, where n=[(SFN×10)+subframe number], the UE may now determine the subframe identifier n using n=[(SFN_M×10)+subframe number], where SFN_M is the SFN after performing a modulo operation with the set superframe length (in units of SFN). For example, for a given subframe N=50000 in a sequence, the subframe identifier n used for the on-duration wake-up condition or formula would be 50000 mod 10240 or 9040 when the superframe length is 1024 frames (SFN_M=1024). In contrast, for a given subframe N=50000, for the on-duration formula, n will be 50000 mod 10000 or 0 in the case of a superframe length of 1000 frames (SFN_M=1000).

[0190] In some aspects, an on-duration formula for waking up from an on-duration sleep cycle may include waking up at a subframe starting at least in part based on a subframe identifier of the subframe and a DRX cycle periodicity corresponding to a multiple of the multimedia periodicity (the inverse of the multimedia cadence in number of Hz). For example, the formula may be [(SFN×numberOfSubframesPerFrame)+subframe number in frame]=[timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset+floor(N×1000 / drx-ShortCadence)]modulo(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 opportunity. There is no SFN wraparound with a sequential search value of N. The parameter drx-timeReferenceSFN may provide an SFN that may be used to offset resources or start a superframe. The UE may use the closest SFN with the indicated number before receiving the eCDRX configuration. In some aspects, an upper limit of (N×1000 / drx-ShortCadence) may be used instead of a lower limit. When drx-SlotOffset is a value in units of 1 / 32 ms, (drx-SlotOffset / 32×numberOfSlotsPerSubframe) may indicate a slot offset value in a slot, and an upper limit operation may be used instead of a lower limit operation. The terms drx-ShortCadence and drx-ShortCycle may have a relationship such as drx-ShortCycle (ms) = 1000 / drx-ShortCadence (fps).

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

[0192] There may be multiple DRX offsets. Index i may be used to indicate one of multiple DRX start offsets (drx-StartOffset(i)) and / or multiple DRX slot offsets (drx-StartOffset(i)). Index i may be an integer in an RRC information element (e.g., 0 to 10239 for drx-StartOffset(i) and 0 to 31 for drx-SlotOffset(i)). For a 480 kilohertz (kHz) subcarrier spacing (SCS), drx-SlotOffset may have a value of, for example, 1 / 32 ms. In one example, three DRX start offsets may be defined within drx-ShortCycle,i=[0,1,2], and 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. In addition, drx-SlotOffset(0) = 0, drx-SlotOffset(1) = 0, and drx-SlotOffset(2) = 0. Any of the three values ​​of drx-StartOffset(i) and drx-SlotOffset(i) will activate drx-onDurationTimer.

[0193] There may be multiple DRX start offsets (e.g., units: subframe, 1 ms) within drx-ShortCycle. For any i, the drx-onDurationTimer for the DRX group may be started after drx-SlotOffset(i) from the beginning of the subframe. Multiple sets of drx-StartOffset and drx-SlotOffset may be configured within drx-ShortCycle, and drx-ShortCycle may be set with any integer.

[0194] In some aspects, drx-timeReferenceSFN may be an enumeration value, such as SFN 512, indicating the SFN used to determine the offset of the time domain resources. The UE may use the closest SFN with the indicated number before receiving the eCDRX configuration. In the event that timeReferenceSFN does not exist, timeReferenceSFN may be 0.

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

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

[0197] In some aspects, the formula may be [(SFN×numberOfSlotsPerFrame)+time slot number in frame]=[timeReferenceSFN×numberOfSlotsPerFrame+drx-StartOffset(i)+N×drx-ShortCycle]modulo(1024×numberOfSlotsPerFrame). drx-StartOffset may be set at the granularity of time slots. For example, the value of drx-StartOffset(i) may be an integer between 0 and 327647. The unit for multiple DRX start offsets with drx-ShortCycle may be time slots, and drx-SlotOffset may be merged into drx-StartOffset. In the example where the multimedia cadence is 120 Hz (30 KHz SCS (0.5 ms)), drx-ShortCycle = 25 x 2 slots, drx-StartOffset(0) = 0 slots, drx-StartOffset(1) = 8 x 2 slots, and drx-StartOffset(2) = 16 x 2 slots.

[0198] In some aspects, the sequential search DRX cycle formula may involve a rational number for drx-ShortCycle. The formula may be [(SFN×numberOfSubframesPerFrame)+subframe number in frame]=[timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset+floor(N×drx-ShortCycle)]modulo(1024×numberOfSsubframesPerFrame). In some aspects, an upper limit of (N×drx-ShortCycle)] may be used.

[0199] In some aspects, drx-ShortCycle may be indicated in 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 the DRX cycle periodicity. Rational numbers may represent non-integer values ​​for drx-ShortCycle and thus ms8and1Over3 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, in the case of drx-ShortCycle(ms)=1000 / drx-ShortCadence(fps) and drx-ShortCadence=120, drx-ShortCycle=1000 / 120=25 / 3=8+1 / 3(ms8and1Over3). In another example of drx-ShortCadence=60fps or 60Hz, drx-ShortCycle=1000 / 60=50 / 3(16and2Over3).

[0200] The network entity may configure the UE with a superframe length, such as configuring the UE with an additional information element in an RRC message (e.g., drx-initialSFN). For example, the network entity may send an RRC message with a DRX short cadence value (e.g., drx-ShortCadence) that is an integer between 1 and 1000. The network entity may send an RRC message with a DRX SFN modulus (e.g., drx-SFNModulo) value that is less than 1024 SFNs (such as between 1 and 1023). The network entity may send an RRC message (e.g., drx-initialSFN) indicating an initial value of SFN_M, which may be between 0 SFNs and 1023 SFNs. The network entity may send a MAC CE indicating an initial value or timing of SFN_M or any other such value.

[0201] This new SFN_M value or other ways of setting the superframe length based at least in part on the cadence of multimedia data bursts can be used with other solutions for aligning on-duration opportunities with multimedia data bursts, such as in conjunction with Figures 6 to 13As described. For example, the UE may set a new superframe length (and use SFN modulo the new superframe length, or n = [(SFN_M×10) + subframe number]) in the calculations for the outer DRX cycle in a two-level DRX configuration and in the calculations for the short DRX cycle and the long DRX cycle. In some aspects, the MAC entity may consider that a sequential Nth on-duration cycle occurs in the subframe of [(SFN×numberOfSubframesPerFrame)+subframe number in the frame]=[timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset+drx-PeriodicOffset(N)]modulo(1024×numberOfSubframesPerFrame). 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 drx-onDurationTimer for this DRX group after drx-SlotOffsetList{(N-1) modulo SIZE(drx-SlotOffset)} from the beginning of the subframe. drx-timeReferenceSFN may provide an SFN for determining the offset of resources in the time domain. The UE may use the closest SFN with the indicated number before receiving the DRX configuration. drx-ShortCycleList may be or may be associated with a set of non-uniform DRX short cycles (values ​​in 1 ms, e.g., for 120 Hz drx-ShortCycleList = (8, 8, 9)). drx-SlotOffsetList may be or may be associated with a set of DRX slot offsets. drx-ShortCycleList may be a sequence of maxNrofShortCycle (maximum number of short cycles) of size 1 to drx-ShortCycle-r18. drx-ShortCycle-r18 may be a value in 1 ms (subframe) between 1 and 640. drx-StartOffset may be a value in 1 ms (subframe) between 0 and 10239. This may come from drx-LongCycleStartOffset (reference 1024(SFN)×10(subframe)=10240).drx-SlotOffset may be a value in units of 1 / 32 ms (480 KHz SCS) between 1 and 31. drx-timeReferenceSFN may be an enumerated value, such as SFN 512. In the case that timeReferenceSFN does not exist, timeReferenceSFN is 0.

[0202] In some aspects, the MAC entity may consider that the sequential Nth on-duration cycle occurs in the time slot of [(SFN×numberOfSlotsPerFrame)+time slot number in 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). drx-ShortCycleList may be a set of non-uniform DRX short cycles (value in slots). drx-ShortCycle-r18 may be a value in slots between 1 and 20479. The UE may start drx-onDurationTimer for this DRX group from the beginning of the slot.

[0203] In some aspects, a network entity may send a DCI or MAC CE command that compensates for a subframe index misalignment shift (DRX cycle shift) due to SFN wraparound. The network entity may indicate a value for a timing shift for DRX cycling based at least in part on an indicated shift, such as a 240 subframe (240 ms) shift, a 10240 subframe (10240 ms) shift, or a specific timing drift (2 ms in example 1400). The value may be a value in a new set of values ​​in a shift table list that may compensate for a subframe index misalignment shift caused by SFN wraparound. The value may be a 1-bit value in a DCI or MAC CE command that indicates SFN wraparound. This value may be sent along with a shift value index that references a shift table list or another shift table list. The UE may apply the shift prior to the first on-duration opportunity of the next superframe. As a formula for the subframe, the UE may use [(SFN×numberOfSubframesPerFrame)+subframe number in frame]=(timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset+N×drx-ShortCycle)modulo(1024×numberOfSubframesPerFrame). The UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe. As a formula for the timeslot, the UE may use [(SFN×numberOfSlotsPerFrame)+slot number in frame]=[timeReferenceSFN×numberOfSlotsPerFrame+drx-StartOffset×numberOfSlotsPerSubframe+floor(drx-SlotOffset / 32×numberOfSlotsPerSubframe)+N×drx-ShortCycle×numberOfSlotsPerSubframe]modulo(1024×numberOfSlotsPerFrame). The UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the timeslot.

[0204] In some aspects, due to the predictability of SFN wraparound, a MAC CE may not be sent. In such cases, the network entity and the UE may both anticipate a relative shift of 240ms or 10240ms whenever a superframe changes during a DRX cycle. As a result, the UE may apply the shift before the first on-duration opportunity of the next superframe without receiving a MAC CE indicating the shift. This implicit approach may be triggered by a superframe change.

[0205] In some aspects, the UE may compensate for a timing drift between the DRX on duration and the multimedia burst traffic associated with a misalignment between the superframe length and the periodicity of the multimedia data burst. For example, the SFN wraparound problem may be addressed by compensating for a drift of 240 ms in the DRX formula. 240 subframes may be added per superframe in subframe index [(SFN×10)+subframe number+M×240] modulo(drx-ShortCycle)=(drx-StartOffset) modulo(drx-ShortCycle). M may start at 0 when DRX is initially configured, and M may increase by 1 for each superframe with a time reference SFN or when the SFN returns to 0. To resolve the timing ambiguity of the DRX configuration message, the drx-timeReferenceSFN (0 or 512) may be further considered as the initial reference SFN value.

[0206] In some aspects, the SFN wraparound problem may be resolved by accumulating 10240 ms in the DRX formula. For example, 10240 subframes may be added per superframe in subframe index [(SFN×10)+subframe number+M×10240] modulo(drx-ShortCycle)=(drx-StartOffset) modulo(drx-ShortCycle). M may start at 0 when DRX is initially configured, and M may increase by 1 for each superframe with a time reference SFN or when the SFN returns to 0. To resolve the timing ambiguity of the DRX configuration message, the drx-timeReferenceSFN (0 or 512) may be further considered to be the initial reference SFN value. These are examples, and other formulas may add a specified amount of time (e.g., a specified number of milliseconds) per superframe that satisfies the specified formula involving the subframe number and the DRX short cycle.

[0207] As indicated above, Fig.15 are provided as examples. Other examples can be found in the Fig.15 The examples described are different.

[0208] Fig.16 is a diagram illustrating an example 1600 of an RRC configuration for a DRX cycle according to the present disclosure.

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

[0210] As indicated above, Fig.16 are provided as examples. Other examples can be found in the Fig.16 The examples described are different.

[0211] Fig.17 is a diagram illustrating an example 1700 of aligning a DRX cycle with multimedia periodicity according to the present disclosure.

[0212] Example 1700 shows multiple DRX cycles (DRX cycle 1702, DRX cycle 1704, DRX cycle 1706, and other DRX cycles) configured for a UE (e.g., UE 120). DRX cycle 1706 may be a DRX skip cycle based at least in part on its DRX number (e.g., DRX number 103). DRX cycle 1706 may have a DRX cycle length 1708 (e.g., 32 ms). In addition, data bursts may arrive according to a multimedia cadence based on, for example, 120 Hz. Due to the mismatch between the Hz granularity of the multimedia data bursts and the millisecond granularity of the DRX cycle, there is naturally a misalignment. Without proper correction, the misalignment will cause the UE to wake up when a data burst is not transmitted and sleep when a data burst is transmitted. As a result, data bursts will be lost and communication performance will be degraded.

[0213] As indicated by reference numeral 1710, the UE may sleep in association with a DRX cycle, which may be an upcoming DRX cycle 1706. For example, the UE may sleep in a sleep state 1712 of a DRX cycle 1704 in anticipation of an upcoming DRX cycle 1706 that will begin at the beginning of an on-duration 1714. To correct the misalignment before waking up, the UE may add a specified time offset 1716 to the on-duration 1714. At this new time position within the on-duration 1714 there will be a subframe 1718. As indicated by reference numeral 1720, the UE may wake up at the subframe 1718. Waking up at the subframe may include waking up from sleep in time to receive during the subframe. As indicated by reference numeral 1725, the UE may receive a burst of multimedia data at the subframe 1718. The subframe 1718 may have a subframe number 1722 within the frame of the subframe 1718. In some aspects, a start offset (DRX start offset) may also be added to the on-duration 1714.

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

[0215] Some modifications to this wake-up condition may not successfully resolve the misalignment of the multimedia data burst with the DRX cycle. For example, where (n×specified time offset 1716)] is added to the left side of modulo so that the wake-up condition is [(SFN×10)+subframe number 1722+(n×specified time offset 1716)] modulo DRX cycle length 1708 equals start offset 1728+(n×specified time offset) modulo DRX cycle length 1708, the difference between the DRX cycle in duration and the periodicity 1726 of the multimedia data burst will continue to increase for each application of the specified time offset 1716. Due to the addition (n×specified time offset 1716) on the left side of modulo, at a later DRX cycle (e.g., 768 ms), the difference may be equal to the DRX cycle length 1708, which will result in a duration equal to the specified DRX cycle number 1724 being used for the modulo operation (the modulo result will be 0). This introduces a false DRX cycle. Instead of the difference being set to 0ms, the difference is now 32ms and increasing.

[0216] Without specifying the number or count of DRX skip cycles, the wake-up condition may not be successful. Thus, in some aspects, the DRX cycle number used to update the current DRX cycle of n may be based at least in part on the specified time offset 1716. For example, the UE may determine the DRX cycle number used to update the current DRX cycle of n by dividing [(SFN×10)+subframe number 1722+(n×specified time offset 1716)] by the DRX cycle length 1708.

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

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

[0219] The UE may resolve any timing ambiguity of the RRC message. For example, an RRC message may be received in a superframe across SFN 512, and it may not be clear when the UE will apply the wake-up condition. In some aspects, the UE may receive a DRX time reference SFN 1732 in an indication (e.g., an RRC message) from the network. The DRX time reference SFN 1732 may be a 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. In the case where (10×SFN+subframe number 1722+SFN wrap offset 1730) modulo DRX cycle length 1728 is equal to [(n×specified time offset 1716)+start offset 1728+(DRX time reference SFN×10)] modulo DRX cycle length 1708, the UE may use the DRX time reference SFN 1732 to wake up. When (10×SFN+subframe number 1722+SFN wrap offset 1730) modulo(DRX cycle length 1708×specified DRX cycle number 1724+specified time offset 1716) equals specified timing value 1734, the UE may update n. SFN wrap offset 1730 may be 10240×m, where m is updated to m+1 when SFN returns to DRX time reference SFN 1732. Counter m may be used to determine the size of the SFN wrap offset. DRX time reference SFN 1732 may be 0 or 512. The UE may receive an indication of the DRX time reference SFN 1732.

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

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

[0222] The DRX OnDuration number N may be the number of the OnDuration in the anchor cycle 1738. The DRX OnDuration number N may correspond to the DRX cycle number. In some aspects, the DRX On Duration number N may be the Nth DRX On Duration cycle occurring in a subframe of [(SFN_M×10)+subframe number 1722] modulo DRX cycle length 1708=modulo DRX cycle length 1708=[start offset+(n×specified time offset 1716+(DRX time reference SFN×10)] modulo DRX cycle length 1708, where n=n+1 whenever [(SFN_M×10)+subframe number 1722] modulo (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 a “DRX hop offset”. SFN_M may be the SFN after modulo operation with the set superframe length (in units of SFN).

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

[0224] As indicated above, Fig.17 are provided as examples. Other examples can be found in the Fig.17 The examples described are different.

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

[0226] As shown by reference numeral 1825, the network entity 1810 may send traffic bursts according to a periodicity (e.g., a video frame rate). The network entity 1810 may also send data bursts according to a wake-up condition configured for and used by the UE 1820. As shown by reference numeral 1830, the UE 1820 may sleep and wake up according to a resource cycle and a wake-up condition configured for the UE 1820. For example, the UE 1020 may calculate, for each subframe, whether a parameter associated with the UE 1020 and the resource cycle meets the criteria for waking up. The 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, DRX cycle number).

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

[0228] In some aspects, the network entity 1810 may send an indication associated with the resource cycle, as shown by reference numeral 1835. The indication may include parameters for waking up according to the resource cycle (eg, skipping cycles, specifying a time offset).

[0229] In some aspects, the network entity 1810 may prepare for communications according to the DRX cycle, as indicated by reference numeral 1840. This may include determining a DRX cycle to be used by the UE 1820 or other preparation for DRX of the UE 1820. Preparation may include preparing to transmit during an OnDuration of the DRX cycle.

[0230] As indicated above, Fig.18 are provided as examples. Other examples can be compared with Fig.18 The examples described are different.

[0231] Although various aspects are described with respect to multimedia, various aspects may also be applicable to other applications involving periodic transmissions.

[0232] Mathematical symbols used for wake-up conditions or formulas may be interpreted to mean similar concepts. For example, "+" may refer to addition or addition, "-" may refer to subtraction or subtraction, "×" or "*" may refer to multiplication, and " / " may refer to division.

[0233] Fig.19is a diagram illustrating an example of a decomposed base station 1900 according to the present disclosure.

[0234] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0235] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0236] Base station type operations or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0237] The decomposed base station 1900 architecture may include one or more CUs 1910 that may communicate directly with a core network 1920 via a backhaul link, or indirectly with a core network 1920 through one or more decomposed base station units (such as a near-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 may communicate with one or more DUs 1930 via corresponding midhaul links (such as an F1 interface). The DU 1930 may communicate with one or more RUs 1940 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 1940 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served by multiple RUs 1940 simultaneously. DU 1930 and RU 1940 may also be referred to as “O-RAN DU (O-DU)” and “O-RAN RU (O-RU)”, respectively. A network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0238] Each of these units (e.g., CU 1910, DU 1930, RU 1940, and near-RT RIC 1925, non-RT RIC 1915, and SMO framework 1905) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send 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, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0239] In some aspects, CU 1910 may host one or more higher layer control functions. Such control functions may include RRC, Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 1910. CU 1910 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 1910 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 1910 may be implemented to communicate with DU 1930 for network control and signaling.

[0240] DU 1930 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 1940. In some aspects, DU 1930 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, DU 1930 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 1930 or with control functions hosted by CU 1910.

[0241] The lower layer functionality may be implemented by one or more RUs 1940. In some deployments, the RU 1940 controlled by the DU 1930 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 1940 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 1940 may be controlled by the corresponding DU 1930. In some scenarios, this configuration may enable the DU 1930 and the CU 1910 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0243] The non-RT RIC 1915 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 1925. The non-RT RIC 1915 may be coupled to or in communication with the near-RT RIC 1925 (such as via an A1 interface). The near-RT RIC 1925 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 1910, one or more DUs 1930, or both, and the O-eNB with the near-RT RIC 1925.

[0244] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 1925, the non-RT RIC 1915 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 1925 and may be received from a non-network data source or from a network function at the SMO framework 1905 or the non-RT RIC 1915. In some examples, the non-RT RIC 1915 or the near-RT RIC 1925 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 1915 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO framework 1905 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0245] As indicated above, Fig.19 are provided as examples. Other examples can be found in the Fig.19 The examples described are different.

[0246] Fig. 20 2 is a diagram illustrating an example process 2000 performed, for example, by a UE according to the present disclosure. Example process 2000 is an example in which a UE (eg, UE 120, UE 1820) performs operations associated with a DRX method for multimedia.

[0247] like Fig. 20 As shown, in some aspects, process 2000 may include: sleeping in association with a DRX cycle (block 2010). For example, a UE (e.g., using Fig.26 The communication manager 2608 and / or DRX component 2610 depicted in FIG. 2 may sleep in association with a DRX cycle, as described above.

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

[0249] like Fig. 20 As further shown, in some aspects, process 2000 may include receiving a multimedia data burst during a subframe (block 2030). For example, a UE (e.g., using Fig.26 The communication manager 140 and / or receiving component 2602 depicted in FIG. 2 may receive a burst of multimedia data during a subframe, as described above.

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

[0251] In a first aspect, the DRX cycle number is equal to [(10×SFN of the frame including the subframe+subframe number of the subframe)−(n×specified time offset)] divided by the length of the DRX cycle.

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

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

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

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

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

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

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

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

[0260] 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 DRX time reference SFN, and the DRX time reference SFN is 0 or 512.

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

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

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

[0264] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 2000 includes receiving an indication of timing of two or more skip cycles. In some aspects, the skip cycle offset pattern of the two or more skip cycles may include (0 milliseconds (ms), 1 ms, 1 ms) or (1 ms, 1 ms, 0 ms).

[0265] although Fig. 20 An example block diagram of process 2000 is shown, but in some aspects, process 2000 may include Fig. 20 The blocks depicted in the process 2000 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 2000. Additionally or alternatively, two or more blocks in the blocks of the process 2000 may be performed in parallel.

[0266] Fig.21 2 is a diagram illustrating an example process 2100 performed, for example, by a UE according to the present disclosure. Example process 2100 is an example in which a UE (eg, UE 120, UE 1820) performs operations associated with a DRX method for multimedia.

[0267] like Fig.21 As shown, in some aspects, process 2100 may include: sleeping in association with a DRX cycle (block 2110). For example, a UE (e.g., using Fig.26 The communication manager 2608 and / or DRX component 2610 depicted in FIG. 2 may sleep in association with a DRX cycle, as described above.

[0268] like Fig.21 As further shown, in some aspects, process 2100 may include: starting waking up at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of a DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a DRX time reference SFN, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset (block 2120). For example, a UE (e.g., using Fig.26The communication manager 2608 and / or the DRX component 2610 depicted in the figure may start waking up at a subframe at least in part based on a specified time offset, which is added to the on duration of the DRX cycle based at least in part on a DRX cycle number and a DRX time reference SFN of the DRX cycle, wherein the specified time offset is at least in part based on the periodicity of the multimedia data bursts, and wherein the DRX cycle number is at least in part based on the specified time offset, as described above.

[0269] like Fig.21 As further shown, in some aspects, process 2100 may include receiving a multimedia data burst during a subframe (block 2130). For example, a UE (e.g., using Fig.26 The communication manager 140 and / or receiving component 2602 depicted in FIG. 2 may receive a burst of multimedia data during a subframe, as described above.

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

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

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

[0273] In a third aspect, alone or in combination with one or more of the first aspect and the second aspect, the designated timing value is equal to (length of the DRX cycle×designated DRX cycle number)−1.

[0274] although Fig.21 An example block diagram of process 2100 is shown, but in some aspects, process 2100 may include Fig.21The blocks depicted in the process 2100 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 2100. Additionally or alternatively, two or more blocks in the blocks of the process 2100 may be executed in parallel.

[0275] Fig. 22 2 is a diagram illustrating an example process 2200 performed, for example, by a UE according to the present disclosure. Example process 2200 is an example in which a UE (eg, UE 120, UE 1820) performs operations associated with a DRX method for multimedia.

[0276] like Fig. 22 As shown, in some aspects, process 2200 may include: sleeping in association with resource cycling (block 2210). For example, a UE (e.g., using Fig.26 The communication manager 2608 and / or resource component 2612 depicted in FIG. 2 may sleep in association with a resource cycle, as described above.

[0277] like Fig. 22 As further shown, in some aspects, process 2200 may include: waking up at a subframe based at least in part on a specified time offset, the specified time offset being added to an instance of a resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a burst of multimedia data, and wherein the resource cycle number is based at least in part on the specified time offset (block 2220). For example, a UE (e.g., using Fig.26 The communication manager 140 and / or resource component 2612 depicted in the figure may begin waking up at a subframe based at least in part on a specified time offset, which is added to an instance of a resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on the periodicity of the multimedia data bursts, and wherein the resource cycle number is based at least in part on the specified time offset, as described above.

[0278] like Fig. 22 As further shown, in some aspects, process 2200 may include receiving a multimedia data burst during a subframe (block 2230). For example, a UE (e.g., using Fig.26 The communication manager 2608 and / or receiving component 2602 depicted in FIG. 2 may receive a burst of multimedia data during a subframe, as described above.

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

[0280] 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.

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

[0282] 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 configuring granted resources or semi-persistently scheduled resources.

[0283] 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.

[0284] 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 for physical uplink control channel resources.

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

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

[0287] 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, and when the SFN returns to 0 (zero), m is updated to m+1.

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

[0289] 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.

[0290] although Fig. 22 An example block diagram of process 2200 is shown, but in some aspects, process 2200 may include Fig. 22 The blocks depicted in the process 2200 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 2200. Additionally or alternatively, two or more blocks in the blocks of the process 2200 may be executed in parallel.

[0291] Fig.23 is a diagram illustrating an example process 2300 performed, for example, by a network entity according to the present disclosure. The example process 2300 is an example in which a network entity (eg, base station 110, network entity 1810) performs operations associated with a DRX method for multimedia.

[0292] like Fig.23 As shown, in some aspects, process 2300 may include preparing for communication with a UE according to a DRX cycle (block 2310). For example, a network entity (e.g., using Fig.29 The communication manager 2908 and / or DRX component 2910 depicted in FIG. 2 may prepare for communications with the UE according to the DRX cycle, as described above.

[0293] like Fig.23 As further shown, in some aspects, process 2300 may include: starting to transmit a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of a DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset (block 2320). For example, a network entity (e.g., using Fig.29 The communication manager 2908 and / or the sending component 2904 depicted in the figure may start sending a data burst at a subframe based at least in part on a specified time offset, wherein the specified time offset is added to the on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is at least in part based on the periodicity of the multimedia data burst, and wherein the DRX cycle number is at least in part based on the specified time offset, as described above.

[0294] Process 2300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0295] In a first aspect, the DRX cycle number is equal to [(10×SFN of the frame including the subframe+subframe number of the subframe)−(n×specified time offset)] divided by the length of the DRX cycle.

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

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

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

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

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

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

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

[0303] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, sending a data burst includes: sending a data burst when the length of the DRX cycle (10×SFN+subframe number+SFN wrap offset) modulo is equal to the length of the DRX cycle [(n×specified time offset)+start offset+(DRX time reference SFN×10] modulo, and when (10×SFN+subframe number+SFN wrap offset) modulo (length of the DRX cycle×specified number of DRX cycles+specified time offset) is equal to the specified timing value, n is updated to n+1.

[0304] 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 DRX time reference SFN, and the DRX time reference SFN is 0 or 512.

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

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

[0307] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the process 2300 includes sending an indication of two or more skip cycles.

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

[0309] although Fig.23 An example block diagram of process 2300 is shown, but in some aspects, process 2300 may include Fig.23 The blocks depicted in the process 2300 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 2300. Additionally or alternatively, two or more blocks in the blocks of the process 2300 may be executed in parallel.

[0310] Fig.24is a diagram illustrating an example process 2400 performed, for example, by a network entity according to the present disclosure. The example process 2400 is an example in which a network entity (eg, base station 110, network entity 1810) performs operations associated with a DRX method for multimedia.

[0311] like Fig.24 As shown, in some aspects, process 2400 may include preparing for communication with a UE according to a DRX cycle (block 2410). For example, a network entity (e.g., using Fig.29 The communication manager 2908 and / or DRX component 2910 depicted in FIG. 2 may prepare for communications with the UE according to the DRX cycle, as described above.

[0312] like Fig.24 As further shown, in some aspects, process 2400 may include: starting to send a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of a DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset (block 2420). For example, a network entity (e.g., using Fig.29 The communication manager 2908 and / or the DRX component 2910 depicted in the figure may start sending a data burst at a subframe based at least in part on a specified time offset, wherein the specified time offset is added to the on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is at least in part based on the periodicity of the multimedia data burst, and wherein the DRX cycle number is at least in part based on the specified time offset, as described above.

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

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

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

[0316] In a third aspect, alone or in combination with one or more of the first aspect and the second aspect, the designated timing value is equal to (length of the DRX cycle×designated DRX cycle number)−1.

[0317] although Fig.24 An example block diagram of process 2400 is shown, but in some aspects, process 2400 may include Fig.24 The blocks depicted in the process 2400 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 2400. Additionally or alternatively, two or more blocks in the blocks of the process 2400 may be performed in parallel.

[0318] Fig.25 is a diagram illustrating an example process 2500 performed, for example, by a network entity according to the present disclosure. Example process 2500 is an example in which a network entity (eg, base station 110, network entity 1810) performs operations associated with a DRX method for multimedia.

[0319] like Fig.25 As shown, in some aspects, process 2500 may include preparing for communication with a UE according to resource cycling (block 2510). For example, a network entity (e.g., using Fig.29 The communication manager 2908 and / or resource component 2912 depicted in FIG. 2 may prepare for communications with the UE according to a resource cycle, as described above.

[0320] like Fig.25 As further shown, in some aspects, process 2500 may include: starting at a subframe to transmit a data burst based at least in part on a specified time offset, the specified time offset being added to an instance of a resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, wherein the resource cycle number is based at least in part on the specified time offset, and wherein the resource cycle number is based at least in part on the specified time offset (block 2520). For example, a network entity (e.g., using Fig.29The communication manager 2908 and / or the sending component 2904 depicted in the figure may begin sending a data burst at a subframe based at least in part on a specified time offset, wherein the specified time offset is added to an instance of a resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of the multimedia data burst, wherein the resource cycle number is based at least in part on the specified time offset, and wherein the resource cycle number is based at least in part on the specified time offset, as described above.

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

[0322] 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.

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

[0324] 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 configuring granted resources or semi-persistently scheduled resources.

[0325] 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.

[0326] 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 for physical uplink control channel resources.

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

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

[0329] 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, and when the SFN returns to 0 (zero), m is updated to m+1.

[0330] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, sending a data burst includes: sending a data burst when the length of the resource cycle (10×SFN+subframe number+SFN wrap offset) modulo is equal to the length of the resource cycle [(n×specified time offset)+start offset+(resource time reference SFN×10] modulo, and when (10×resource+subframe number+SFN wrap offset) modulo(length of the resource cycle×specified number of resource cycles+specified time offset) is equal to the specified timing value, n is updated to n+1.

[0331] 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, wherein m is updated to m+1 when the SFN returns to the resource time reference SFN, and wherein the resource time reference SFN is 0 or 512.

[0332] although Fig.25 An example block diagram of process 2500 is shown, but in some aspects, process 2500 may include Fig.25 The blocks depicted in the process 2500 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 2500. Additionally or alternatively, two or more blocks in the blocks of the process 2500 may be performed in parallel.

[0333] Fig.26 is a diagram of an example apparatus 2600 for wireless communication according to the present disclosure. Apparatus 2600 may be a UE (e.g., UE 120, UE 1820), or a UE may include apparatus 2600. In some aspects, apparatus 2600 includes a receiving component 2602 and a sending component 2604, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 2600 may use receiving component 2602 and sending component 2604 to communicate with another apparatus 2606 (such as a UE, a base station, a network entity, or another wireless communication device). As further shown, apparatus 2600 may include a communications manager 140. Communications manager 2608 may control and / or otherwise manage one or more operations of receiving component 2602 and / or sending component 2604. In some aspects, communications manager 2608 may include a communication manager 140. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. The communication manager 2608 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communications manager 2608 may be configured to perform one or more of the functions described as being performed by the communications manager 140. In some aspects, the communications manager 2608 may include a receiving component 2602 and / or a sending component 2604. The communications manager 2608 may include a DRX component 2610 and / or a resource component 2612, among others.

[0334] In some aspects, the apparatus 2600 may be configured to perform Figures 1 to 18 Additionally or alternatively, the apparatus 2600 may be configured to perform one or more processes described herein, such as Fig. 20 The process of 2000, Fig.21 Process 2100, Fig. 22 In some aspects, Fig.26 The device 2600 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.26 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set 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 can be executed by a controller or processor to perform the function or operation of the component.

[0335] The receiving component 2602 may receive communications from the apparatus 2606, such as reference signals, control information, data communications, or a combination thereof. The receiving component 2602 may provide the received communications to one or more other components of the apparatus 2600. In some aspects, the receiving component 2602 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 2600. In some aspects, the receiving component 2602 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

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

[0337] In some aspects, the DRX component 2610 can cause the device 2600 to sleep in association with the DRX cycle. The DRX component 2610 can wake up the device 2600 starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The receiving component 2602 can receive a multimedia data burst during a subframe.

[0338] Receiving component 2602 can receive an indication of a DRX time reference SFN, an indication of two or more hopping cycles, and / or an indication of a timing of the two or more hopping cycles.

[0339] In some aspects, the DRX component 2610 can cause the device 2600 to sleep in association with the DRX cycle. The DRX component 2610 can wake up the device 2600 starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a DRX time reference SFN, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The receiving component 2602 can receive a multimedia data burst during a subframe.

[0340] In some aspects, the resource component 2612 can cause the device 2600 to sleep in association with a resource cycle. The resource component 2612 can begin waking up the device 2600 at 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 resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a burst of multimedia data, and wherein the resource cycle number is based at least in part on the specified time offset. The receiving component 2602 can receive a burst of multimedia data during a subframe.

[0341] Fig.26 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.26 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.26 Two or more components shown in the figure may be implemented in a single component, or Fig.26 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.26 The component set (one or more components) shown in FIG. 1 may perform the operations described by Fig.26 One or more functions performed by another set of components shown in the figure.

[0342] Fig. 27 2700 is a diagram illustrating an example hardware implementation for an apparatus 2705 employing a processing system 2710. The apparatus 2705 may be a UE (eg, UE 120, UE 1820).

[0343] The processing system 2710 may be implemented with a bus architecture, generally represented by bus 2715. Bus 2715 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 2710 and the overall design constraints. Bus 2715 links together various circuits including one or more processors and / or hardware components (represented by processor 2720, illustrated components, and computer readable media / memory 2725). Bus 2715 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0344] The processing system 2710 can be coupled to a transceiver 2730. The transceiver 2730 is coupled to one or more antennas 2735. The transceiver 2730 provides a means for communicating with various other devices through 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 (specifically, the transmitting component 2604) and generates a signal to be applied to one or more antennas 2735 based at least in part on the received information.

[0345] 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 executing software stored on the computer readable medium / memory 2725. The software, when executed by the processor 2720, causes the processing system 2710 to perform various functions described herein for any particular device. The computer readable medium / memory 2725 can also be used to store data manipulated by the processor 2720 when executing the software. The processing system also includes at least one of the illustrated components. These components can be software modules running in the processor 2720, resident / stored in the computer readable medium / memory 2725, one or more hardware modules coupled to the processor 2720, or some combination thereof.

[0346] In some aspects, the processing system 2710 can be a component of the UE 120 and can 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 association with a DRX cycle; and means for waking up at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. The apparatus 2705 includes: means for receiving a multimedia data burst during a subframe. In some aspects, the apparatus 2705 includes: means for sleeping in association with a DRX cycle; means for waking up at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number and a DRX time reference system frame number (SFN) of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a burst of multimedia data, and wherein the DRX cycle number is based at least in part on the specified time offset; and / or means for receiving a burst of multimedia data during a subframe. In some aspects, the apparatus 2705 includes: means for sleeping in association with a resource cycle; means for waking up at a subframe based at least in part on a specified time offset, the specified time offset being added to an instance of a resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a burst of multimedia data, and wherein the resource cycle number is based at least in part on the specified time offset; and / or means for receiving a burst of multimedia data during a subframe. The aforementioned means may be one or more of the aforementioned components of the processing system 2710 of the apparatus 2600 and / or the apparatus 2705 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 2710 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned 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 recited herein.

[0347] Fig. 27 is provided as an example. Other examples can be combined with Fig. 27 The examples described are different.

[0348] Fig.282800 is a diagram illustrating an example implementation of code and circuits for an apparatus 2805 according to the present disclosure. The apparatus 2805 may be a UE (eg, UE 120, UE 1820), or a UE may include the apparatus 2805.

[0349] like Fig.28 As shown, the device 2805 may include circuitry (circuitry 2820) for sleeping in association with a DRX cycle or a resource cycle. For example, the circuitry 2820 may enable the device 2805 to sleep in association with a DRX cycle or a resource cycle.

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

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

[0352] like Fig.28As shown, device 2805 may include code stored in computer-readable medium 2725 for starting to wake up at a subframe at least in part based on a specified time offset, the specified time offset being added to the on duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is at least in part based on the periodicity of multimedia data bursts, and wherein the DRX cycle (or resource cycle) number is at least in part based on the specified time offset (code 2835). For example, code 2835, when executed by processor 2720, may cause processor 2720 to cause transceiver 2730 to wake up starting at a subframe based at least in part on a specified time offset, wherein the specified time offset is added to the on duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on the periodicity of multimedia data bursts, and wherein the DRX cycle (or resource cycle) number is based at least in part on the specified time offset.

[0353] like Fig.28 As shown, the device 2805 may include circuitry for receiving a burst of multimedia data during a subframe. For example, the circuitry 2840 may enable the device 2805 to receive a burst of multimedia data during a subframe.

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

[0355] Fig.28 is provided as an example. Other examples can be combined with Fig.28 The examples described are different.

[0356] Fig.29is a diagram of an example apparatus 2900 for wireless communication according to the present disclosure. Apparatus 2900 may be a network entity (e.g., base station 110, network entity 1810), or a network entity may include apparatus 2900. In some aspects, apparatus 2900 includes a receiving component 2902 and a transmitting component 2904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 2900 may communicate with another apparatus 2906 (such as a UE, a base station, or another wireless communication device) using receiving component 2902 and transmitting component 2904. As further shown, apparatus 2900 may include a communication manager 2908. Communication manager 2908 may control and / or otherwise manage one or more operations of receiving component 2902 and / or transmitting component 2904. In some aspects, communication manager 2908 may include a communication manager 2908 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network entities. The communications manager 2908 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communications manager 2908 may be configured to perform one or more of the functions described as being performed by the communications manager 150. In some aspects, the communications manager 2908 may include a receiving component 2902 and / or a sending component 2904. The communications manager 2908 may include a DRX component 2910 and / or a resource component 2912, among others.

[0357] In some aspects, the apparatus 2900 may be configured to perform Figures 1 to 18 Additionally or alternatively, the apparatus 2900 may be configured to perform one or more processes described herein, such as Fig.23 The process 2300 Fig.24 The process 2400 Fig.25 In some aspects, Fig.29 The apparatus 2900 and / or one or more components shown in FIG. 2 may include a combination of Figure 2 Additionally or alternatively, Fig.29 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set 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 can be executed by a controller or processor to perform the function or operation of the component.

[0358] The receiving component 2902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 2906. The receiving component 2902 may provide the received communications to one or more other components of the apparatus 2900. In some aspects, the receiving component 2902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 2900. In some aspects, the receiving component 2902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

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

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

[0361] Transmitting component 2904 can transmit an indication of a DRX time reference SFN, an indication of two or more hopping cycles, and / or an indication of a timing of two or more hopping cycles.

[0362] In some aspects, the DRX component 2910 can prepare for communication with the UE according to the DRX cycle. The transmitting component 2904 can begin transmitting the data burst at the subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of the multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset.

[0363] In some aspects, resource component 2912 may prepare for communication with the UE according to a resource cycle. Transmitting component 2904 may begin transmitting a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an instance of the resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, wherein the resource cycle number is based at least in part on the specified time offset, and wherein the resource cycle number is based at least in part on the specified time offset.

[0364] Fig.29 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.29 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.29 Two or more components shown in the figure may be implemented in a single component, or Fig.29 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.29 The component set (one or more components) shown in FIG. 1 may perform the operations described as being performed by Fig.29 One or more functions performed by another set of components shown in the figure.

[0365] Fig.30 is a diagram illustrating an example 3000 of a hardware implementation for an apparatus 3005 employing a processing system 3010. The apparatus 3005 may be a network entity (eg, base station 110, network entity 1810).

[0366] The processing system 3010 may be implemented with a bus architecture, generally represented by bus 3015. Bus 3015 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 3010 and the overall design constraints. Bus 3015 links together various circuits including one or more processors and / or hardware components (represented by processor 3020, illustrated components, and computer readable media / memory 3025). Bus 3015 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0367] The processing system 3010 can be coupled to a transceiver 3030. The transceiver 3030 is coupled to one or more antennas 3035. The transceiver 3030 provides a means for communicating with various other devices through 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, the receiving component 2902). In addition, the transceiver 3030 receives information from the processing system 3010 (specifically, the transmitting component 2904) and generates a signal to be applied to the one or more antennas 3035 based at least in part on the received information.

[0368] 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 executing software stored on the computer readable medium / memory 3025. The software, when executed by the processor 3020, causes the processing system 3010 to perform various functions described herein for any particular device. The computer readable medium / memory 3025 can also be used to store data manipulated by the processor 3020 when executing the software. The processing system also includes at least one of the illustrated components. These components can be software modules running in the processor 3020, resident / stored in the computer readable medium / memory 3025, one or more hardware modules coupled to the processor 3020, or some combination thereof.

[0369] In some aspects, the processing system 3010 can be a component of the UE 120 and can 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 3005 for wireless communication includes: means for preparing for communication with the UE according to the DRX cycle; and / or means for starting to send a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. In some aspects, the apparatus 3005 may include: means for preparing for communication with the UE in accordance with the DRX cycle; and / or means for starting at a subframe to send a data burst based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset. In some aspects, the apparatus 3005 may include: means for preparing for communication with the UE in accordance with a resource cycle; and / or means for starting at a subframe to send a data burst based at least in part on a specified time offset, the specified time offset being added to an instance of a resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, wherein the resource cycle number is based at least in part on the specified time offset, and wherein the resource cycle number is based at least in part on the specified time offset. The aforementioned means may be one or more of the aforementioned components of the processing system 3010 of the apparatus 2900 and / or the apparatus 3005 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 3010 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned 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 recited herein.

[0370] Fig.30 is provided as an example. Other examples can be combined with Fig.30 The examples described are different.

[0371] Fig.313100 is a diagram illustrating an example implementation of code and circuits for an apparatus 3105 according to the present disclosure. The apparatus 3105 may be a network entity (eg, a base station 110, a network entity 1810), or a network entity may include the apparatus 3105.

[0372] like Fig.31 As shown, the device 3105 may include a circuit (circuit 3120) for preparing for communication with the UE according to the DRX cycle or the resource cycle. For example, the circuit 3120 may enable the device 3105 to prepare for communication with the UE according to the DRX cycle or the resource cycle.

[0373] like Fig.31 As shown, the device 3105 may include a code (code 3125) for preparing for communication with the UE according to the DRX cycle or resource cycle stored in the computer-readable medium 3025. For example, when the code 3125 is executed by the processor 3020, the processor 3020 may prepare for communication with the UE according to the DRX cycle or resource cycle.

[0374] like Fig.31 As shown, the apparatus 3105 may include: a circuit for starting to send a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on a periodicity of the multimedia data burst, and wherein the DRX cycle (or resource cycle) number is based at least in part on the specified time offset (circuitry 3130). For example, the circuit 3130 may enable the apparatus 3105 to start to send a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on a periodicity of the multimedia data burst, and wherein the DRX cycle (or resource cycle) number is based at least in part on the specified time offset.

[0375] like Fig.31As shown, the device 3105 may include code stored in a computer-readable medium 3025 for sending a data burst starting at a subframe based at least in part on a specified time offset, the specified time offset being added to the start duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on the periodicity of the multimedia data burst, and wherein the DRX cycle (or resource cycle) number is based at least in part on the specified time offset (code 3135). For example, code 3135, when executed by processor 3020, may cause processor 3020 to cause transceiver 3030 to send a data burst starting at a subframe based at least in part on a specified time offset, wherein the specified time offset is added to the on duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on the periodicity of the multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset.

[0376] like Fig.31 As shown, the apparatus 3105 may include: a circuit for starting to send a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on a periodicity of the multimedia data burst, and wherein the DRX cycle (or resource cycle) number is based at least in part on the specified time offset (circuitry 3130). For example, the circuit 3130 may enable the apparatus 3105 to start to send a data burst at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on a periodicity of the multimedia data burst, and wherein the DRX cycle (or resource cycle) number is based at least in part on the specified time offset.

[0377] like Fig.31As shown, the device 3105 may include code stored in a computer-readable medium 3025 for sending a data burst starting at a subframe based at least in part on a specified time offset, the specified time offset being added to the start duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on the periodicity of the multimedia data burst, and wherein the DRX cycle (or resource cycle) number is based at least in part on the specified time offset (code 3135). For example, code 3135, when executed by processor 3020, may cause processor 3020 to cause transceiver 3030 to send a data burst starting at a subframe based at least in part on a specified time offset, wherein the specified time offset is added to the on duration of the DRX cycle (or resource cycle) based at least in part on a DRX cycle (or resource cycle) number and a length of the DRX cycle (or resource cycle), wherein the specified time offset is based at least in part on the periodicity of the multimedia data burst, and wherein the DRX cycle (or resource cycle) number is based at least in part on the specified time offset.

[0378] Fig.31 is provided as an example. Other examples can be combined with Fig.31 The examples described are different.

[0379] Fig.32 is a diagram illustrating an example 3200 of a jump offset pattern according to the present disclosure.

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

[0381] The DRX cycle may include a DRX jump offset, such as 1ms. A 16ms DRX long cycle plus a 1ms jump offset is a 17ms DRX cycle. In some aspects, the first jump offset pattern 3202 includes a jump offset pattern of (0ms, 1ms, 1ms). The DRX cycle length is therefore 16ms, 17ms, and 17ms to obtain a total of 50ms. The first jump offset pattern 3202 starts with a 16ms DRX cycle, and thus the UE wakes up before the XR traffic arrives. In some aspects, the first jump offset pattern 3204 includes a jump offset pattern of (1ms, 1ms, 0ms). The DRX cycle length is therefore 17ms, 17ms, and 16ms. The first jump offset pattern 3204 starts with a 17ms DRX cycle, and thus the UE wakes up after the XR traffic arrives. The UE may further wake up based at least in part on a cumulative DRX offset, the cumulative DRX offset comprising a DRX offset equal to a DRX start offset, such as drx-Offset(0)=drx-StartOffset and drx-Offset(n)=X(n-1)+drx-LeapOffset{(n-1)modN}, m≥1. In some aspects, the UE may sequentially search for the next nth DRX cycle and, with a subframe index of [(SFN×10)+subframe number]={drx-LongCycle×n+drx-Offset(n)+10×drx-timeReferenceSFN}modulo10240, the UE may wake up for a subframe. In some aspects, the UE may sequentially search for the next nth DRX cycle, and in the case where (10240×m)+[(SFN×10)+subframe number]={drx-LongCycle×n+drx-Offset(n)+10×drx-timeReferenceSFN} modulo 10240, the UE may wake up for the subframe.

[0382] As indicated above, Fig.32 are provided as examples. Other examples can be found in the Fig.32 The examples described are different.

[0383] Fig.33A is a diagram illustrating example 3300 of subframe indexing according to the present disclosure.

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

[0385] As indicated above, Fig.33A are provided as examples. Other examples can be found in the Fig.33A The examples described are different.

[0386] Fig.33B is a diagram illustrating example 3302 of subframe indexing according to the present disclosure.

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

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

[0389] As indicated above, Fig.33B are provided as examples. Other examples can be found in the Fig.33B The examples described are different.

[0390] Fig.34 is a diagram illustrating example 3400 of backward compatibility according to the present disclosure.

[0391] In some aspects, the enhanced DRX formula solution for the SFN wraparound problem (such as adding 10240×m in the DRX formula) may not be compatible with the legacy DRX formula for certain DRX cycles. Some DRX short cycles such as 3ms, 6ms, 7ms, 14ms, 30ms, and 35ms may not be compatible with the SFN wraparound solution. For example, for drx-ShortCycle=6ms (10240 / 6=1706.6666). DRX long cycles of 60ms and 70ms may also not be backward compatible. The legacy DRX formula and the enhanced DRX formula work differently under these DRX cycles.

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

[0393] As indicated above, Fig.34 are provided as examples. Other examples can be found in the Fig.34 The examples described are different.

[0394] Fig.35 is a diagram illustrating example 3500 of handling backward compatibility according to the present disclosure.

[0395] Example 3500 illustrates an enhanced UE configured to operate with 3GPP standard Release 18 or later that can operate using a solution to the SFN wrap problem, and a legacy UE configured to operate with 3GPP standard Releases 15-17 that cannot operate using a solution to the SFN wrap problem. The solution may involve an SFN wrap offset that accounts for the cumulative length of a superframe.

[0396] In some aspects, a UE may send an indication of the UE's ability to use SFN wrap offsets to resolve SFN wrap issues in a capability message. An enhanced UE may indicate this capability, whereas a legacy UE may not indicate this capability. In some aspects, the indication may be an information element in a capability message. The UE may receive a legacy DRX configuration that does not use SFN wrap offsets or an enhanced DRX configuration that uses SFN wrap offsets.

[0397] As indicated above, Fig.35 are provided as examples. Other examples can be found in the Fig.35The examples described are different.

[0398] Fig.36 3600 is a diagram illustrating an example associated with using SFN wrap-around offset according to the present disclosure. Fig.36 As shown, a network entity 3610 (e.g., base station 110) may communicate with a UE 3620 (e.g., UE 120). Network entity 3610 and UE 3620 may be part of a wireless network (e.g., wireless network 100). UE 3620 may be an enhanced UE capable of using a SFN wrap-around offset that accounts for the cumulative length of a superframe.

[0399] As indicated by reference numeral 3625, UE 3620 may send an indication of the ability of UE 3620 to use SFN wrap offset in a capability message. As indicated by reference numeral 3630, network entity 3610 may send a configuration to use SFN wrap offset (for enhanced UEs) based at least in part on the capability message.

[0400] In some aspects, as indicated by reference numeral 3635, the UE may begin waking up at a subframe based at least in part on a subframe index of a resource period (e.g., a DRX cycle) and a SFN wrap offset that illustrates a cumulative length of a superframe. The SFN wrap offset may be equal to the length of the superframe×m. The length of the superframe may be equal to 10240. As indicated by reference numeral 3640, the UE may receive a data burst (e.g., a multimedia data burst) during the subframe.

[0401] In some aspects, taking into account the SFN wrap-around offset, the UE 3620 may wake up if the subframe index is a subframe for which the UE 3620 is to wake up. For example, the UE 3620 may wake up if [(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 the UE 3620, the value of k is 1. In some aspects, whenever the SFN changes to the reference SFN value (drx-timeReferenceSFN is 0 or 512), the value m=m+1. That is, the subframe index may be equal to [(10×SFN of the frame including the subframe)+subframe number of the subframe], where m is updated to m+1 when the SFN returns to 0 (zero), 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 the length of the (subframe index+SFN wrap offset) modulo resource cycle is equal to the length of the [(start offset+(time reference SFN×10)] modulo resource cycle. The start offset may be drx-StartOffset.

[0402] In some aspects, the network entity 3610 may send an indication of k=0 and drx-timeReferenceSFN=0 for legacy DRX operation and an indication of k=1 for enhanced DRX operation. By setting k=0, the network entity 3610 may support legacy UEs, and by setting k=1, the network entity may support enhanced UEs for XR. The network entity 3610 may set the value k in the configuration via RRC signaling, DCI, or MAC CE. In some aspects, when SFN becomes a time reference SFN value and the network entity 3610 configures the enhanced DRX feature, m may increase by 1 (m=m+1). Otherwise, m may not increase and be fixed to 0 (m=0).

[0403] In some aspects, the UE 3620 may not change the enhanced 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 and which DRX long cycles the SFN wraparound offset is applicable to or not applicable to. The UE 3620 may then apply the SFN wraparound offset for applicable DRX short cycles and DRX long cycles, and not apply the SFN wraparound offset for inapplicable DRX short cycles and DRX long cycles.

[0404] As indicated above, Fig.36are provided as examples. Other examples can be found in the Fig.36 The examples described are different.

[0405] Fig.37A is a diagram illustrating example 3700 of using SFN wrap-around offset according to the present disclosure.

[0406] Example 3700 shows the arrival of multimedia data bursts arriving at a rate of 120 Hz. In example 3700, drx-StartOffset is set to 0. The UE may configure the DRX cycle for the cadence of the data bursts (such as every 8.33 ms at 120 Hz), but the cadence of the data bursts may be associated with a periodicity of 1000 ms. In the case of a multimedia periodicity of 1000 ms and a DRX cycle of 10240 ms (1024 SFNs per superframe at 10 ms), the superframe of the DRX may be misaligned with the frame of the multimedia server every 10.24 seconds. Due to the misalignment between the superframe 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 superframe periodicity (10240 ms) cannot be divided by the multimedia periodicity (Hz, fps). In the example of 120Hz XR traffic, 10240ms / (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 superframe, and this partial frame causes the SFN wraparound problem in the next superframe. Other multimedia periodicities result in other numbers of frames per superframe that are not aligned with a certain number of SFNs as follows: 45Hz (460.8 SFNs), 48Hz (491.52 SFNs), 60Hz (614.4 SFNs), or 90Hz (921.6 SFNs).

[0407] Example 3700 shows the end of a superframe (at SFN 1023) and the beginning of the next superframe (at SFN 0), or when the SFN number wraps around (restarts or returns to 0) for the next superframe. When the end of the superframe is reached, an on-duration wake-up condition or formula such as (SFN*10)+subframe number=0 may select a subframe within the on-duration between data bursts due to the SFN wraparound. Because the subframes may not be aligned with the data bursts, the data bursts may not be received. This may result in degradation of communications which may consume additional processing resources and signaling.

[0408] By adding the SFN wrap offset 3704 (e.g., the length of the superframe (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 communications are not degraded. Signaling resources are conserved.

[0409] As indicated above, Fig.37A are provided as examples. Other examples can be found in the Fig.37A The examples described are different.

[0410] Fig.37B is a diagram illustrating an example 3720 of receiving a configuration for resource recycling according to the present disclosure.

[0411] Example 3720 shows that the UE can operate with resource cycles 3722. The UE can receive configurations for future resource cycles 3724 (e.g. Fig.16 3726). The RRC configuration 1602 may indicate information about future resource cycles 3724, such as the length of the resource cycle 3726. The UE may begin using the RRC configuration 1602 in a superframe based at least in part on when the RRC configuration 1602 is received. For example, the length of the superframe 3728 may be 1024 SFNs. However, in the event that the RRC configuration 1602 is received later in the superframe (e.g., after SFN 512 of the superframe), there may be some ambiguity about the initial value of m for applying the SFN wrap offset. The SFN wrap offset may be equal to (the length of the superframe × m). The counter m may be used to determine the size of the SFN wrap offset. In the event that the initial value of m is incorrect, the SFN wrap offset may not be the correct size, and communications may be degraded if a traffic burst is not received at the on-duration of the resource cycle. Degraded communications waste signaling resources and increase latency.

[0412] In some aspects, the UE may wake up based at least in part on a time reference SFN. The time reference SFN may indicate when an initial resource cycle begins. For example, the time reference SFN may indicate that the reference timing of an initial resource cycle (e.g., an initial DRX cycle) is SFN 512 (not SFN 0). Even if the RRC reconfiguration 1602 is completed in the next superframe (superframe n+1), the UE may expect the initial DRX cycle to start from SFN 512 of superframe n. In the case where the UE receives the RRC configuration 1602 between SFN 512 of superframe 0 and SFN 512 of superframe 1, there is no ambiguity around SFN 0. Note that the suboptimal transmission time of the RRC configuration 1602 may be less than 5.12 seconds (half of a superframe).

[0413] As indicated above, Fig.37B are provided as examples. Other examples can be found in the Fig.37B The examples described are different.

[0414] Fig.37C are diagrams illustrating examples 3730 and 3732 of receiving a configuration for resource recycling according to the present disclosure.

[0415] The time reference SFN (e.g., drx-TimeReferenceSFN in eCDRX) may be set to 0 or 512 (e.g., a 1-bit RRC message). When the RRC configuration 1602 with eCDRX is generated by a network entity (e.g., a gNB), SFN-GNB may be a SFN. When the UE successfully receives the RRC configuration 1602 with eCDRX, SFN-UE may be a SFN. In the case where 0≤SFN-GNB<512, the network entity may set the drx-timeReferenceSFN to 0, or in the case where 512≤SFN-GNB<1024, the network entity may set the drx-timeReferenceSFN to 512. The network entity may set the starting offset value (e.g., drx-StartOffset shown by DRX Offset 3734) according to the drx-timeReferenceSFN (SFN 0 or SFN 512).

[0416] In some aspects, the UE may set an initial value of m to 0, where m is increased by 1 each time the SFN changes to drx-timeReferenceSFN (SFN 0 or SFN 512). As shown in example 3730, in the case of drx-timeReferenceSFN=0, m may be set to 0 regardless of when the UE receives the RRC configuration 1602. As shown in example 3732, in the case of drx-timeReferenceSFN=512, m may be set to 0 regardless of when the UE receives the RRC configuration 1602. According to one or more aspects, 5.12 seconds (sufficient time) may be provided to the network entity to deliver the RRC configuration 1602. By correctly setting the initial value of m based at least in part on when the RRC configuration 1602 is received, the UE may apply a correct SFN wraparound offset (e.g., a correct SFN wraparound offset because the initial value m is set as described above), and when a traffic burst matches the on-duration of a resource cycle, communication may be improved. The improved communication saves signaling resources and reduces latency.

[0417] As indicated above, Fig.37C Some examples are provided. Other examples can be found in the Fig.37C The examples described are different.

[0418] Fig.37D are diagrams illustrating examples 3740 and 3742 of receiving a configuration for resource recycling according to the present disclosure.

[0419] In some aspects, regardless of the time reference SFN (e.g., drx-timeReferenceSFN), when generating the RRC configuration, the network entity may set the start offset value (e.g., drx-StartOffset) according to SFN = 0 and m = 0. Whenever the SFN wraps around (SFN returns to 0), the counter m may be increased by 1.

[0420] In some aspects, to reduce computational complexity, m may wrap around by a particular integer configured by the network. For example, where the network entity configures the wrap value to be k, when the next value of m becomes k, m wraps around to 0 (e.g., m=(m+1) modulo k whenever the SFN wraps around). The network entity may determine a value of k that may be aligned with the current frame rate. For example, the network entity may determine a value of k that may be divided by the current frame periodicity, such as (10240 ms×k superframes) / (1000 ms / X), where X is associated with the current frame periodicity.

[0421] In some aspects, m may wrap around by an integer multiple of 25 (e.g., 25, 50, 75, 100, 1000). For example, in the case where m wraps around by 25, when the next value of m reaches 25, m returns to or is reset to 0 (i.e., m=(m+1) modulo25). Since any integer frame rate can be aligned within 25 superframes (e.g., assuming f is an integer frame rate (fps, Hz), (10240 ms*25 superframes) / (1000 ms / f)=f×256), if m has a range of 0 to 24, m can support any integer frame rate.

[0422] In some aspects, the UE may wake up based at least in part on a length of a (subframe index + SFN wrap offset) modulo resource cycle (e.g., DRX long cycle) being equal to a starting offset. In some aspects, the UE may wake up based at least in part on a length of a (subframe index + SFN wrap offset) modulo resource cycle (e.g., DRX short cycle) being equal to a length of a starting offset modulo resource cycle (e.g., DRX short cycle).

[0423] In some aspects, the SFN wrap offset may be equal to (length of superframe×m), where the initial value of m is based at least in part on the time reference SFN and the SFN in which the configuration for resource cycling is received. For example, as shown in example 3742, the time reference SFN is 512, and based at least in part on the SFN being less than 512 (e.g., 0≤SFN-UE<512 or delivered in the next superframe), the initial value of m is 1, or based at least in part on the SFN being 0 or between 512 and the length of the superframe (e.g., 512≤SFN-UE<1024), the initial value of m is 0. As shown in example 3740, in the case where the time reference SFN is 0, the initial value of m is 0 regardless of the SFN in which the RRC configuration is received.

[0424] As indicated above, Fig.37D Some examples are provided. Other examples can be found in the Fig.37D The examples described are different.

[0425] Fig.37E are diagrams illustrating examples 3750 and 3752 of receiving a configuration for resource recycling according to the present disclosure.

[0426] In some aspects, the UE may wake up based at least in part on the length of the (subframe index + SFN wrap offset) modulo resource cycle being equal to the length of the (start offset + (time reference SFN × 10)) modulo resource cycle. The resource cycle may be, for example, a DRX long cycle or a DRX short cycle. In some aspects, the SFN wrap offset may be equal to (length of the superframe × m), where the initial value of m is based at least in part on the time reference SFN and the SFN in which the configuration for the resource cycle is received. For example, as shown in example 3752, the time reference SFN is 512, and based at least in part on the SFN being less than 512 (e.g., 0≤SFN-UE<512 or delivered in the next superframe), the initial value of m is 1, or based at least in part on the SFN being 0 or between 512 and the length of the superframe (e.g., 512≤SFN-UE<1024), the initial value of m is 0. As shown in example 3750, in the case where the time reference SFN is 0, the initial value of m is 0 regardless of the SFN in which the RRC configuration is received.

[0427] As indicated above, Fig.37E Some examples are provided. Other examples can be found in the Fig.37E The examples described are different.

[0428] Fig.37F are diagrams illustrating examples 3760 and 3762 of receiving a configuration for resource recycling according to the present disclosure.

[0429] In some aspects, the UE may wake up based at least in part on a length of a (subframe index + SFN wrap offset) modulo resource cycle (e.g., DRX long cycle) being equal to a starting offset. In some aspects, the UE may wake up based at least in part on a length of a (subframe index + SFN wrap offset) modulo resource cycle (e.g., DRX short cycle) being equal to a length of a starting offset modulo resource cycle (e.g., DRX short cycle).

[0430] In some aspects, a time reference HFN (e.g., drx-timeReferenceHFN) may indicate when a new counter m starts from 0 with a HFN (e.g., an RRC configuration generated by a network entity). When the RRC message is generated by a network entity, the time reference HFN may be the least significant bit (LSB) of the HFN. The HFN may also be referred to as a super SFN (HSFN). When an RRC configuration message (even or odd) is generated, a time reference HFN (0 or 1) may be indicated. For example, the drx-TimeReferenceHFN in eCDRX may be set to 0 or 1 (1-bit RRC message). When the RRC configuration with eCDRX is generated by a network entity (e.g., a gNB), the HFN-GNB may be the HFN. When the UE successfully receives the RRC configuration with eCDRX, the HFN-UE may be the HFN.

[0431] In some aspects, in the case where HFN-GNB is an even number, the network entity may set the time reference HFN (e.g., drx-timeReferenceHFN) to 0 (e.g., LSB 1 bit of HFN-GNB). In the case where HFN-GNB is an odd number, the network entity may set the time reference HFN to 1. Regardless of the time reference HFN, the network entity may set the start offset value (e.g., drx-StartOffset) according to SFN=0. Counter m may be 0 when generating the RRC configuration and may be incremented by 1 when the SFN wraps around (returns to 0).

[0432] In some aspects, the UE may set an initial value of m (e.g., drx-timeReferenceHFN) based at least in part on the time reference HFN. For example, as shown in example 3760, in the case where the time reference HFN is 0 (even) and HFN-UE is odd (delivered in the next HFN), the UE may set m to 1. As shown in example 3762, in the case where the time reference HFN is 1 (odd) and HFN-UE is even (delivered in the next HFN), the UE may set m to 1. Otherwise, in the case where the RRC configuration is delivered in the same HFN, the UE may set m to 0. Each time the SFN wraps around (0), the counter m may be increased by one. Therefore, the network entity may deliver the RRC configuration within 10.24 seconds (enough time). In some aspects, the time reference HFN may be a plurality of LSBs that may provide more delivery time margin (e.g., 2 bits provide 20.48 seconds).

[0433] As indicated above, Fig.37F Some examples are provided. Other examples can be found in the Fig.37F The examples described are different.

[0434] Fig.38 38 is a diagram illustrating an example process 3800 performed, for example, by a UE according to the present disclosure. Example process 3800 is an example in which a UE (eg, UE 120, UE 1820, UE 3620) performs operations associated with DRX.

[0435] like Fig.38 As shown, in some aspects, process 3800 may include waking up at a subframe based at least in part on a subframe index of a resource cycle and a SFN wrap offset that describes a cumulative length of a superframe (block 3810). Fig.39 The communication manager 140 and / or wake-up component 3908 depicted in FIG. 3 may begin waking up at a subframe based at least in part on a subframe index of a resource period and a SFN wrap-around offset that illustrates a cumulative length of a superframe, as described above.

[0436] like Fig.38 As further shown, in some aspects, process 3800 may include receiving a data burst during a subframe (block 3820). For example, a UE (e.g., using Fig.39 The communication manager 140 and / or receiving component 3902 depicted in FIG. 3 may receive a burst of data during a subframe, as described above.

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

[0438] In a first aspect, the SFN wrap offset is equal to (length of superframe x m).

[0439] In a second aspect, alone or in combination with the first aspect, waking up comprises waking up based at least in part on a length of a (subframe index+SFN wrap offset) modulo resource cycle being equal to a length of a start offset modulo resource cycle.

[0440] In a third aspect, alone or in combination with one or more of the first and second aspects, the SFN wrap offset is equal to (length of superframe×m), and the initial value of m is based at least in part on the time reference SFN and the SFN in which the configuration for resource cycling is received.

[0441] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the time reference SFN is 512, and based at least in part on the SFN being less than 512, the initial value of m is 1, or based at least in part on the SFN being between 512 and the length of the superframe, the initial value of m is 0.

[0442] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the time reference SFN is 0, and the initial value of m is 0.

[0443] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the SFN wrap offset is equal to (length of superframe×m), and the initial value of m is based at least in part on the time reference HFN and the HFN in which the configuration for resource cycling is received.

[0444] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the time reference HFN indicates 0, and based at least in part on the fact that HFN is an odd number, an initial value of m is 1, or based at least in part on the fact that HFN is an even number, an initial value of m is 0; or the time reference HFN indicates 1, and based at least in part on the fact that HFN is an even number, an initial value of m is 1, or based at least in part on the fact that HFN is an odd number, an initial value of m is 0.

[0445] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the length of the superframe is equal to 10240.

[0446] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the subframe index is equal to (10×SFN of the frame including the subframe)+the subframe number of the subframe.

[0447] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the SFN wrap-around offset is equal to (the length of the superframe × m), where m is updated to m+1 when the SFN returns to 0 (zero) or the time reference SFN, and the time reference SFN is 0 or 512.

[0448] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, waking up includes: waking up when the length of the (subframe index + SFN wrap offset) modulo resource cycle is equal to the length of the [(start offset + (time reference SFN×10)] modulo resource cycle.

[0449] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the SFN wrap offset is equal to (length of the superframe × m), and the initial value of m is based at least in part on the time reference SFN and the SFN of the frame including the subframe in which the configuration for resource cycling is received.

[0450] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the time reference SFN is 512, and based at least in part on the SFN being less than 512, the initial value of m is 1, or based at least in part on the SFN being between 512 and the length of the superframe, the initial value of m is 0.

[0451] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the time reference SFN is 0, and the initial value of m is 0.

[0452] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the resource cycle comprises a DRX cycle, and the data burst is a multimedia data burst.

[0453] In a sixteenth aspect, either alone or in combination with one or more of the first through fifteenth aspects, process 3800 includes sending an indication of an ability to use a SFN wrap-around offset.

[0454] In a seventeenth aspect, either alone or in combination with one or more of the first through sixteenth aspects, process 3800 includes activating a SFN wrap-around offset.

[0455] In the eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, the SFN wrap offset is equal to (length of superframe × m × k), where k = 1 for activation of the SFN wrap offset and k = 0 for deactivation of the SFN wrap offset.

[0456] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the process 3800 includes receiving a configuration of one or more of a DRX short cycle or a DRX long cycle for backward compatibility to use a SFN wrap-around offset.

[0457] In a twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, m is reset to 0 based at least in part on the next value of m being a configured value (eg, an integer multiple of 25).

[0458] although Fig.38 An example block diagram of process 3800 is shown, but in some aspects, process 3800 may include Fig.38 The boxes depicted in the process 3800 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner than those depicted in the process 3800. Additionally or alternatively, two or more boxes in the boxes of the process 3800 may be executed in parallel.

[0459] Fig.39 3900 for wireless communication according to the present disclosure. The device 3900 may be a UE (e.g., UE 120, UE 1820, UE 3620), or the UE may include the device 3900. In some aspects, the device 3900 includes a receiving component 3902 and a sending component 3904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the device 3900 may communicate with another device 3906 (such as a UE, a base station, or another wireless communication device) using the receiving component 3902 and the sending component 3904. As further shown, the device 3900 may include a communication manager 140. The communication manager 140 may include one or more of a wake-up component 3908, etc.

[0460] In some aspects, the apparatus 3900 may be configured to perform Figure 17 to Figure 3 Additionally or alternatively, the apparatus 3900 may be configured to perform one or more processes described herein, such as Fig.38 The process 3800. In some aspects, Fig.39 The apparatus 3900 and / or one or more components shown in FIG. 3 may include a combination of Figure 2 Additionally or alternatively, Fig.39 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set 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 can be executed by a controller or processor to perform the function or operation of the component.

[0461] The receiving component 3902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 3906. The receiving component 3902 may provide the received communications to one or more other components of the device 3900. In some aspects, the receiving component 3902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 3900. In some aspects, the receiving component 3902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

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

[0463] The waking component 3908 can begin waking up at a subframe based at least in part on a subframe index of a resource cycle and a SFN wrap-around offset that illustrates a cumulative length of a superframe. The receiving component 3902 can receive a burst of data during a subframe.

[0464] Transmitting component 3904 can transmit an indication of the ability to use SFN wrap offset. Wake-up component 3908 can activate SFN wrap offset. Receiving component 3902 can receive configuration of one or more of a DRX short cycle or a DRX long cycle for backward compatibility to use SFN wrap offset.

[0465] Fig.39 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.39 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.39 Two or more components shown in the figure may be implemented in a single component, or Fig.39 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.39 The component set (one or more components) shown in FIG. 1 may perform the operations described by Fig.39 One or more functions performed by another set of components shown in the figure.

[0466] Fig.40 is a diagram illustrating an example 4000 of a hardware implementation for an apparatus 4005 employing a processing system 4010. The apparatus 4005 may be a UE (eg, UE 120, UE 1820, UE 3620).

[0467] The processing system 4010 may be implemented with a bus architecture, generally represented by bus 4015. Bus 4015 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 4010 and the overall design constraints. Bus 4015 links together various circuits including one or more processors and / or hardware components (represented by processor 4020, illustrated components, and computer readable media / memory 4025). Bus 4015 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0468] The processing system 4010 may be coupled to a transceiver 4030. The transceiver 4030 is coupled to one or more antennas 4035. The transceiver 4030 provides a means for communicating with various other devices through 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, the receiving component 3902). In addition, the transceiver 4030 receives information from the processing system 4010 (specifically, the transmitting component 3904) and generates a signal to be applied to the one or more antennas 4035 based at least in part on the received information.

[0469] 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 executing software stored on the computer readable medium / memory 4025. The software, when executed by the processor 4020, causes the processing system 4010 to perform various functions described herein for any particular device. The computer readable medium / memory 4025 can also be used to store data manipulated by the processor 4020 when executing the software. The processing system also includes at least one of the illustrated components. These components can be software modules running in the processor 4020, resident / stored in the computer readable medium / memory 4025, one or more hardware modules coupled to the processor 4020, or some combination thereof.

[0470] In some aspects, the processing system 4010 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 4005 for wireless communication includes: a means for waking up at a subframe based at least in part on a subframe index of a resource period and an SFN wrap-around offset that describes the cumulative length of a superframe; and / or a means for receiving a data burst during a subframe. The aforementioned means may be one or more of the aforementioned components of the apparatus 2900 and / or the processing system 4010 of the apparatus 4005 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, 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 aforementioned 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 recited herein.

[0471] Fig.40 is provided as an example. Other examples can be combined with Fig.40 The examples described are different.

[0472] Fig.41 is a diagram illustrating an example 4100 of a specific implementation of code and circuits for an apparatus 4105 according to the present disclosure. The apparatus 4105 may be a UE, or a UE may include the apparatus 4105.

[0473] like Fig.41As shown, the device 4105 may include a circuit (circuit 4120) for waking up at the beginning of a subframe based at least in part on a subframe index of a resource cycle and a SFN wrap offset that describes a cumulative length of a superframe. For example, the circuit 4120 may enable the device 4105 to wake up at the beginning of a subframe based at least in part on a subframe index of a resource cycle and a SFN wrap offset that describes a cumulative length of a superframe.

[0474] like Fig.41 As shown, the apparatus 4105 may include code (code 4125) stored in the computer-readable medium 4025 for waking up at the beginning of a subframe based at least in part on a subframe index of a resource cycle and a SFN wrap offset that specifies a cumulative length of a superframe. For example, the code 4125, when executed by the processor 4020, may cause the processor 4020 to cause the transceiver 4030 to wake up at the beginning of a subframe based at least in part on a subframe index of a resource cycle and a SFN wrap offset that specifies a cumulative length of a superframe.

[0475] like Fig.41 As shown, the device 4105 may include circuitry (circuitry 4130) for receiving a burst of data during a subframe. For example, the circuitry 4130 may enable the device 4105 to receive a burst of data during a subframe.

[0476] like Fig.41 As shown, the apparatus 4105 may include code (code 4135) for receiving a data burst during a subframe stored in the computer-readable medium 4025. For example, the code 4135, when executed by the processor 4020, may cause the processor 4020 to cause the transceiver 4030 to receive a data burst during a subframe.

[0477] Fig.41 is provided as an example. Other examples can be combined with Fig.41 The examples described are different.

[0478] The following provides an overview of some aspects of the disclosure:

[0479] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: sleeping in association with a discontinuous reception (DRX) cycle; waking up starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset; and receiving a multimedia data burst during the subframe.

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

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

[0482] Aspect 4: According to the method of aspect 3, the method further comprises: skipping every n+1 updates.

[0483] Aspect 5: A method according to Aspect 2, wherein waking up includes: waking up when (10×the SFN+the subframe number) modulo the length of the DRX cycle is equal to ((n×the specified time offset)+the starting offset) modulo the length of the DRX cycle, and wherein when (10×the SFN+the subframe number) modulo (the length of the DRX cycle×the specified number of DRX cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

[0484] Aspect 6: The method according to aspect 5, wherein the designated timing value is equal to (the length of the DRX cycle×the designated DRX cycle number)-1.

[0485] Aspect 7: The method of aspect 2, wherein waking up comprises waking up based further at least in part on a SFN wrap-around offset.

[0486] Aspect 8: A method according to Aspect 7, wherein waking up includes: waking up when (10×the SFN+the subframe number+the SFN wrap offset) 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 wherein when (10×the SFN+the subframe number+the SFN wrap offset) modulo (the length of the DRX cycle×the specified number of DRX cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

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

[0488] Aspect 10: A method according to Aspect 7, wherein waking up includes: waking up when (10×the SFN+the subframe number+the SFN wrap 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 wherein when (10×the SFN+the subframe number+the SFN wrap offset) modulo (the length of the DRX cycle×the specified number of DRX cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

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

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

[0491] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the anchor cycle including the DRX cycle further includes two or more skip cycles.

[0492] Aspect 14: The method according to aspect 13, the method further comprising: receiving an indication of the two or more skip cycles.

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

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

[0495] Aspect 17: A method according to Aspect 16, wherein waking up includes: waking up when (SFN of the frame including the subframe × the number of subframes per frame) + the subframe number of the subframe is equal to [the DRX time reference SFN × the number of subframes per subframe + starting offset + DRX on duration number × the length of the DRX cycle + floor (the DRX on duration number / the specified time offset) × the specified number of DRX cycles] modulo (1024 × the number of subframes per frame).

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

[0497] Aspect 19: The method according to Aspect 18, wherein the designated timing value is equal to (the length of the DRX cycle×the designated DRX cycle number)-1.

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

[0499] 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.

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

[0501] Aspect 23: The method according to any one of Aspects 20 to 22, wherein the resource cycle is a cycle for configuring granted resources or semi-persistently scheduled resources.

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

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

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

[0505] Aspect 27: A method according to any one of Aspects 20 to 26, wherein waking up includes: waking up when (10×the SFN+the subframe number+SFN wrap 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 wherein when (10×the SFN+the subframe number+the SFN wrap offset) modulo (the length of the resource cycle×the specified number of resource cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

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

[0507] Aspect 29: A method according to any one of Aspects 20 to 26, wherein waking up includes: waking up when (10×the SFN+the subframe number+SFN wrap offset) modulo the length of the resource cycle is equal to [(n×the specified time offset)+start offset+(resource time reference SFN×10] modulo the length of the resource cycle, and wherein when (10×the resource+the subframe number+the SFN wrap offset) modulo (the length of the resource cycle×the specified number of resource cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

[0508] Aspect 30: The method according to aspect 29, wherein the SFN wraparound offset is 10240×m, wherein when the SFN returns to the resource time reference SFN, m is updated to m+1, and wherein the resource time reference SFN is 0 or 512.

[0509] Aspect 31: A method of wireless communication performed by a network entity, the method comprising: preparing communication with a user equipment (UE) according to a discontinuous reception (DRX) cycle; and sending a data burst starting at a subframe based at least in part on a specified time offset, the specified time offset being added to a start duration of the DRX cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is at least in part based on the periodicity of a multimedia data burst, and wherein the DRX cycle number is at least in part based on the specified time offset.

[0510] Aspect 32: A method according to Aspect 31, wherein the DRX cycle number is equal to [(10×system frame number (SFN) of the frame including the subframe + subframe number of the subframe)-(n×the specified time offset)] divided by the length of the DRX cycle.

[0511] Aspect 33: A method according to Aspect 32, wherein sending the data burst comprises: sending the data burst when the length of the DRX cycle (10×the SFN+the subframe number) modulo is equal to the length of the DRX cycle ((n×the specified time offset)+start offset) modulo, and wherein when the DRX cycle number modulo the specified DRX cycle number is equal to 0 (zero), n is updated to n+1.

[0512] Aspect 34: According to the method of Aspect 33, the method further comprises: skipping every n+1 updates.

[0513] Aspect 35: A method according to Aspect 32, wherein sending the data burst comprises: sending the data burst when (10×the SFN+the subframe number) modulo the length of the DRX cycle is equal to ((n×the specified time offset)+the start offset) modulo the length of the DRX cycle, and wherein when (10×the SFN+the subframe number) modulo (the length of the DRX cycle×the specified number of DRX cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

[0514] Aspect 36: The method according to Aspect 35, wherein the designated timing value is equal to (the length of the DRX cycle×the designated DRX cycle number)-1.

[0515] Aspect 37: The method of aspect 32, wherein sending the data burst comprises sending the data burst based further at least in part on a SFN wrap-around offset.

[0516] Aspect 38: A method according to Aspect 37, wherein sending the data burst comprises: sending the data burst when the length of the DRX cycle (10×the SFN+the subframe number+the SFN wrap offset) modulo is equal to the length of the DRX signal ((n×the specified time offset)+the start offset) modulo, and wherein when (10×the SFN+the subframe number+the SFN wrap offset) modulo (the length of the DRX cycle×the specified number of DRX cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

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

[0518] Aspect 40: A method according to Aspect 37, wherein sending the data burst includes: sending the data burst when (10×the SFN+the subframe number+the SFN wrap 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 wherein when (10×the SFN+the subframe number+the SFN wrap offset) modulo (the length of the DRX cycle×the specified number of DRX cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

[0519] Aspect 41: The method according to aspect 40, wherein the SFN wraparound offset is 10240×m, wherein when the SFN returns to the DRX time reference SFN, m is updated to m+1, and wherein the DRX time reference SFN is 0 or 512.

[0520] Aspect 42: According to the method of aspect 40, the method further includes: sending an indication of the DRX time reference SFN.

[0521] 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 skip cycles.

[0522] Aspect 44: The method according to aspect 43, the method further comprising: sending an indication of the two or more skip cycles.

[0523] Aspect 45: The method according to aspect 43 or 44, the method further comprising: sending an indication of the timing of the two or more hopping cycles.

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

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

[0526] Aspect 48: A method according to Aspect 47, wherein sending the data burst includes: sending the data burst when (SFN of the frame including the subframe × the number of subframes per frame) + the subframe number of the subframe is equal to [the DRX time reference SFN × the number of subframes per subframe + starting offset + DRX on duration number × the length of the DRX cycle + floor (the DRX on duration number / the specified time offset) × the specified number of DRX cycles] modulo (1024 × the number of subframes per frame).

[0527] Aspect 49: A method according to Aspect 47, wherein sending the data burst includes: sending the data burst when [(modified SFN of the frame including the subframe×10)+subframe number of the subframe] modulo the length of the DRX cycle is equal to [start offset+(n×the specified time offset)+(the DRX time reference SFN×10)] modulo the length of the DRX cycle, and wherein when [(SFN_M×10)+the subframe number] modulo (the length of the DRX cycle×the specified number of DRX cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

[0528] Aspect 50: A method according to aspect 49, wherein the designated timing value is equal to (the length of the DRX cycle×the designated DRX cycle number)-1.

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

[0530] 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.

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

[0532] Aspect 54: The method according to any one of Aspects 51 to 53, wherein the resource cycle is a cycle for configuring granted resources or semi-persistently scheduled resources.

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

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

[0535] Aspect 57: A method according to any one of Aspects 51 to 56, wherein the resource cycle number is equal to [(10×the system frame number (SFN) of the frame including the subframe+the subframe number of the subframe)-(n×the specified time offset)] divided by the length of the resource cycle.

[0536] Aspect 58: A method according to any one of Aspects 51 to 56, wherein sending the data burst comprises: sending the data burst when the length of the resource cycle (10×the SFN+the subframe number+SFN wrap offset) modulo is equal to the length of the resource cycle ((n×the specified time offset)+start offset) modulo), and wherein when (10×the SFN+the subframe number+the SFN wrap offset) modulo (the length of the resource cycle×the specified number of resource cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

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

[0538] Aspect 60: A method according to any one of Aspects 51 to 56, wherein sending the data burst comprises: sending the data burst when the length of the resource cycle (10×the SFN+the subframe number+SFN wrap offset) modulo is equal to the length of the resource cycle [(n×the specified time offset)+start offset+(resource time reference SFN×10] modulo, and wherein when (10×the resource+the subframe number+the SFN wrap offset) modulo (the length of the resource cycle×the specified number of resource cycles+the specified time offset) is equal to the specified timing value, n is updated to n+1.

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

[0540] Aspect 62: A method for wireless communication at a user equipment (UE), the method comprising: starting to wake up at a subframe based at least in part on a subframe index of a resource cycle and a system frame number (SFN) wrap offset indicating a cumulative length of a superframe; and receiving a data burst during the subframe.

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

[0542] Aspect 64: A method according to Aspect 62 or 63, wherein waking up includes waking up based at least in part on (the subframe index + the SFN wrap offset) modulo the length of the resource cycle being equal to the starting offset modulo the length of the resource cycle.

[0543] Aspect 65: A method according to Aspect 64, wherein the SFN wrap-around offset is equal to (the length of the superframe×m), and wherein the initial value of m is based at least in part on a time reference SFN and the SFN in which the configuration for the resource cycling is received.

[0544] Aspect 66: A method according to Aspect 65, wherein the time reference SFN is 512, and wherein: at least partially based on the SFN being less than 512, the initial value of m is 1, or at least partially based on the SFN being between 512 and the length of the superframe, the initial value of m is 0.

[0545] Aspect 67: The method according to aspect 65, wherein the time reference SFN is 0, or the initial value of m is 0.

[0546] Aspect 68: A method according to aspect 62, wherein the SFN wrap offset is equal to (the length of the superframe×m), and wherein the initial value of m is based at least in part on a time reference superframe number (HFN) and the HFN in which the configuration for the resource cycling is received.

[0547] Aspect 69: A method according to Aspect 68, wherein: the time reference HFN indicates 0, and based at least in part on the fact that the HFN is an odd number, the initial value of m is 1, or based at least in part on the fact that the HFN is an even number, the initial value of m is 0; or the time reference HFN indicates 1, and based at least in part on the fact that the HFN is an even number, the initial value of m is 1, or based at least in part on the fact that the HFN is an odd number, the initial value of m is 0.

[0548] Aspect 70: A method according to any one of Aspects 62 to 69, wherein the length of the superframe is equal to 10240.

[0549] Aspect 71: A method according to any one of Aspects 62 to 70, wherein the subframe index is equal to (10×SFN of the frame including the subframe)+subframe number of the subframe.

[0550] Aspect 72: The method according to Aspect 71, wherein when the SFN returns to 0 (zero), m is updated to m+1.

[0551] Aspect 73: The method according to Aspect 71, wherein when the SFN returns to the time reference SFN, m is updated to m+1.

[0552] Aspect 74: The method according to aspect 73, wherein the time reference SFN is 0 or 512.

[0553] Aspect 75: A method according to any one of Aspects 62 to 74, wherein waking up includes: waking up when (the subframe index + the SFN wrap offset) modulo the length of the resource cycle is equal to [(starting offset + (time reference SFN×10)] modulo the length of the resource cycle.

[0554] Aspect 76: A method according to Aspect 75, wherein the SFN wrap-around offset is equal to (the length of the superframe × m), and wherein the initial value of m is based at least in part on the time reference SFN and the SFN of the frame including the subframe in which the configuration for resource cycling is received.

[0555] Aspect 77: A method according to Aspect 76, wherein the time reference SFN is 512, and wherein the initial value of m is 1, at least partially based on the SFN being less than 512, or the initial value of m is 0, at least partially based on the SFN being between 512 and the length of the superframe.

[0556] Aspect 78: The method according to Aspect 76, wherein the time reference SFN is 0 and the initial value of m is 0.

[0557] Aspect 79: A method according to any one of aspects 62 to 69, wherein the resource cycle comprises a discontinuous reception (DRX) cycle, and the data burst is a multimedia data burst.

[0558] Aspect 80: The method according to any one of aspects 62 to 70, the method further comprising: sending an indication of the ability to use the SFN wrap-around offset.

[0559] Aspect 81: According to any one of aspects 62 to 71, the method further includes: activating the SFN wrap-around offset.

[0560] Aspect 82: A method according to Aspect 72, wherein the SFN wrap offset is equal to (the length of the superframe×m×k), wherein for activation of the SFN wrap offset, k=1, and for deactivation of the SFN wrap offset, k=0.

[0561] Aspect 83: A method according to any one of aspects 62 to 73, wherein the one or more processors are configured to receive a configuration of one or more of a DRX short cycle or a DRX long cycle for backward compatibility to use the SFN wrap-around offset.

[0562] Aspect 84: A method according to any one of Aspects 62 to 83, wherein m is reset to 0 based at least in part on the next value of m being the configured value.

[0563] Aspect 85: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 84.

[0564] Aspect 86: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 84.

[0565] Aspect 87: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 84.

[0566] Aspect 88: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 84.

[0567] Aspect 89: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 84.

[0568] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0569] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0570] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0571] Although the specific combination of features is stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically stated in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, 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 ordering of a, b and c).

[0572] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more entries, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries, and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. In addition, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless otherwise clearly stated. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise clearly stated (for example, if used in combination with "any" or "only one").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to: waking up the apparatus starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of a discontinuous reception (DRX) cycle based at least in part on a DRX cycle number of the DRX cycle and a length of the DRX cycle, wherein the specified time offset is based at least in part on a periodicity of a multimedia data burst, and wherein the DRX cycle number is based at least in part on the specified time offset; and A multimedia data burst is received during the subframe.

2. The apparatus of claim 1, wherein the DRX cycle number is equal to [(10×system frame number (SFN) of a frame including the subframe+subframe number of the subframe)-(n×the specified time offset)] divided by the length of the DRX cycle.

3. The apparatus of claim 2, wherein to wake up the apparatus, the one or more processors are configured to wake up the apparatus further based at least in part on a SFN wrap-around offset.

4. The apparatus of claim 3, wherein the SFN wrap-around offset is equal to (10240×m), and wherein when the SFN returns to 0 (zero), m is updated to m+1.

5. The apparatus according to claim 3, wherein in order to wake up the apparatus, the one or more processors are configured to: wake up the apparatus when (10×the SFN+the subframe number+the SFN wrap 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 wherein when (10×the SFN+the subframe number+the SFN wrap offset) modulo (the length of the DRX cycle×the specified number of DRX cycles+the specified time offset) is equal to a specified timing value, n is updated to n+1. 6 . The apparatus of claim 5 , wherein the SFN wraparound offset is 10240×m, wherein m is updated to m+1 when the SFN returns to the DRX time reference SFN, and wherein the DRX time reference SFN is 0 or 512.

7. The apparatus of claim 5, wherein the one or more processors are configured to receive an indication of the DRX time reference (SFN).

8. The apparatus of claim 1, wherein an anchor cycle including the DRX cycle further includes two or more skip cycles.

9. The apparatus of claim 8, wherein the one or more processors are configured to receive an indication of the two or more skip cycles or an indication of a timing of the two or more skip cycles.

10. The apparatus of claim 8, wherein a skip cycle offset pattern of the two or more skip cycles comprises (0 milliseconds (ms), 1 ms, 1 ms) or (1 ms, 1 ms, 0 ms).

11. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to: waking up the apparatus starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an on-duration of a discontinuous reception (DRX) cycle based at least in part on a DRX cycle number 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 multimedia data bursts, and wherein the DRX cycle number is based at least in part on the specified time offset; and A multimedia data burst is received during the subframe.

12. The apparatus according to claim 11, wherein in order to wake up the apparatus, the one or more processors are configured to: wake up the apparatus when (SFN of the frame including the subframe × the number of subframes per frame) + the subframe number of the subframe is equal to [the DRX time reference SFN × the number of subframes per subframe + starting offset + DRX on duration number × the length of the DRX cycle + floor (the DRX on duration number / the specified time offset) × the specified DRX cycle number] modulo (1024 × the number of subframes per frame).

13. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to: waking up the device starting at a subframe based at least in part on a specified time offset, the specified time offset being added to an instance of a resource cycle based at least in part on a resource cycle number of the resource cycle and a length of the resource cycle, wherein the specified time offset is based at least in part on a periodicity of a burst of multimedia data, and wherein the resource cycle number is based at least in part on the specified time offset; and A multimedia data burst is received during the subframe.

14. The apparatus of claim 13, 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. The apparatus of claim 13 , wherein the resource cycle is a cycle for scheduling requests. 16 . The apparatus according to claim 13 , wherein the resource cycle is a cycle for configuring a granted resource or a semi-persistently scheduled resource.

17. The apparatus of claim 13, wherein the resource cycle is a cycle for channel state information reporting or buffer status reporting.

18. The apparatus of claim 13, wherein the resource cycle is a cycle for physical downlink control channel monitoring or for physical uplink control channel resources.

19. The apparatus of claim 13, wherein in order to wake up the apparatus, the one or more processors are configured to: wake up the apparatus when (10×system frame number (SFN) of a frame including the subframe+subframe number of the subframe+SFN wrap 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, wherein when (10×the SFN+the subframe number+the SFN wrap offset) modulo (the length of the resource cycle×the specified number of resource cycles+the specified time offset) is equal to a specified timing value, n is updated to n+1, wherein the SFN wrap offset is 10240×m, and wherein when the SFN returns to 0 (zero), m is updated to m+1.

20. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to: waking up at a subframe starting at least in part based on a subframe index of a resource cycle and a system frame number (SFN) wrap-around offset that describes a cumulative length of a superframe; and A burst of data is received during the subframe.

21. The apparatus of claim 20, wherein the SFN wrap offset is equal to (length of the superframe x m).

22. The apparatus of claim 20, wherein to wake up, the one or more processors are configured to wake up based at least in part on (the subframe index + the SFN wrap offset) modulo the length of the resource cycle being equal to a start offset modulo the length of the resource cycle.

23. The apparatus of claim 22, wherein the SFN wrap offset is equal to (length of the superframe x m), and wherein an initial value of m is based at least in part on a time reference SFN and a SFN in which the configuration for the resource cycling is received.

24. The apparatus of claim 23, wherein: The time reference SFN is 512, and based at least in part on the SFN being less than 512, the initial value of m is 1, The time reference SFN is 512, and based at least in part on the SFN being between 512 and the length of the superframe, the initial value of m is 0, or The time reference SFN is 0, and the initial value of m is 0.

25. The apparatus of claim 22, wherein the SFN wrap offset is equal to (length of the superframe x m), and wherein an initial value of m is based at least in part on a time reference superframe number (HFN) and the HFN in which the configuration for the resource cycling is received.

26. The apparatus of claim 25, wherein: The time reference HFN indicates 0, and based at least in part on the HFN being an odd number, the initial value of m is 1, or based at least in part on the HFN being an even number, the initial value of m is 0, or The time reference HFN indicates 1, and based at least in part on the HFN being an even number, the initial value of m is 1, or based at least in part on the HFN being an odd number, the initial value of m is 0.

27. The apparatus of claim 20, wherein the length of the superframe is equal to 10240.

28. The apparatus of claim 20, wherein the subframe index is equal to (10 x SFN of a frame including the subframe) + a subframe number of the subframe.

29. The apparatus of claim 28, wherein the SFN wrap-around offset is equal to (the length of the superframe×m), wherein m is updated to m+1 when the SFN returns to 0 (zero) or a time reference SFN, and wherein the time reference SFN is 0 or 512.

30. The apparatus of claim 29, wherein m is reset to 0 based at least in part on the next value of m being the configured value.

31. An apparatus according to claim 20, wherein, in order to wake up, the one or more processors are configured to: wake up when (the subframe index + the SFN wrap offset) modulo the length of the resource cycle is equal to [(start offset + (time reference SFN×10)] modulo the length of the resource cycle.

32. The apparatus of claim 31 , wherein the SFN wrap offset is equal to (the length of the superframe x m), and wherein an initial value of m is based at least in part on the time reference SFN and the SFN of a frame including the subframe in which the configuration for resource cycling is received.

33. The apparatus of claim 32, wherein: The time reference SFN is 512, and based at least in part on the SFN being less than 512, the initial value of m is 1, The time reference SFN is 512, and based at least in part on the SFN being between 512 and the length of the superframe, the initial value of m is 0, or The time reference SFN is 0, and the initial value of m is 0.

34. The apparatus of claim 20, wherein the resource cycle comprises a discontinuous reception (DRX) cycle and the data burst is a multimedia data burst.

35. The apparatus of claim 20, wherein the one or more processors are configured to send an indication of an ability to use the SFN wrap-around offset.

36. The apparatus of claim 20, wherein the one or more processors are configured to activate the SFN wrap-around offset.

37. The apparatus of claim 20, wherein the SFN wrap offset is equal to (length of the superframe x m x k), wherein k = 1 for activation of the SFN wrap offset and k = 0 for deactivation of the SFN wrap offset.

38. The apparatus of claim 20, wherein the one or more processors are configured to receive a configuration of one or more of a DRX short cycle or a DRX long cycle that is backward compatible to use the SFN wrap-around offset.

Images