WO2025060032A1

WO2025060032A1 - Configuration negotiation for sidelink extended discontinuous reception

Info

Publication number: WO2025060032A1
Application number: PCT/CN2023/120597
Authority: WO
Inventors: Jianhua Liu; Hong Cheng; Qing Li
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-09-22
Filing date: 2023-09-22
Publication date: 2025-03-27
Anticipated expiration: 2026-03-22

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a first user equipment (UE) may negotiate, with a second UE, a configuration associated with waking up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs). The first UE may calculate the DFN based at least in part on the configuration. The first UE may wake up in the DFN. The DFN may be an active duration within the active time window. Numerous other aspects are described.

Description

CONFIGURATION NEGOTIATION FOR SIDELINK EXTENDED DISCONTINUOUS RECEPTION

INTRODUCTION

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for sidelink extended discontinuous reception.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like) . 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) .

A wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL” ) refers to a communication link from the network node to the UE, and “uplink” (or “UL” ) refers to a communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL) , a wireless local area network (WLAN) link, and/or a wireless personal area network (WPAN) link, among other examples) .

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, 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 the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) 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, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.

SUMMARY

Some aspects described herein relate to a method of wireless communication performed at a first user equipment (UE) . The method may include negotiating, with a second UE, a configuration associated with waking up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) . The method may include calculating the DFN based at least in part on the configuration. The method may include waking up in the DFN, where the DFN is an active duration within the active time window.

Some aspects described herein relate to a method of wireless communication performed at a network entity. The method may include obtaining one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The method may include transmitting an indication of the one or more parameters to a second UE.

Some aspects described herein relate to an apparatus for wireless communication at a first UE. The apparatus 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 to cause the first UE to negotiate, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The one or more processors may be configured to cause the first UE to calculate the DFN based at least in part on the configuration. The one or more processors may be configured to cause the first UE to wake up in the DFN, where the DFN is an active duration within the active time window.

Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus 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 to cause the network entity to obtain one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The one or more processors may be configured to cause the network entity to transmit an indication of the one or more parameters to a second UE.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a first UE. The set of instructions, when executed by one or more processors of the first UE, may cause the first UE to negotiate, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The set of instructions, when executed by one or more processors of the first UE, may cause the first UE to calculate the DFN based at least in part on the configuration. The set of instructions, when executed by one or more processors of the first UE, may cause the first UE to wake up in the DFN, where the DFN is an active duration within the active time window.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to obtain one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit an indication of the one or more parameters to a second UE.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for negotiating, with another apparatus, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The apparatus may include means for calculating the DFN based at least in part on the configuration. The apparatus may include means for waking up in the DFN, where the DFN is an active duration within the active time window.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The apparatus may include means for transmitting an indication of the one or more parameters to a second UE.

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

The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices) . Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers) . It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

Fig. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

Fig. 4 is a diagram illustrating an example of discontinuous reception (DRX) , in accordance with the present disclosure.

Fig. 5 is a diagram illustrating an example of sidelink communications, in accordance with the present disclosure.

Fig. 6 is a diagram illustrating an example of sidelink communications and access link communications, in accordance with the present disclosure.

Fig. 7 is a diagram illustrating an example of a next-generation radio access network architecture, in accordance with the present disclosure.

Fig. 8A and Fig. 8B are diagrams illustrating examples of control plane protocol stacks for sidelink, in accordance with the present disclosure.

Fig. 9 is a diagram illustrating examples of control plane protocol stacks for UE-to-network (U2N) relay, in accordance with the present disclosure.

Fig. 10 is a diagram illustrating an example of a sidelink extended DRX (eDRX) , in accordance with the present disclosure.

Figs. 11A-11C are diagrams illustrating examples of a system frame number (SFN) -direct frame number (DFN) offset, in accordance with the present disclosure.

Fig. 12 is a diagram illustrating an example of an active time window in a sidelink eDRX cycle, in accordance with the present disclosure.

Fig. 13 is a diagram illustrating an example associated with sidelink eDRX configuration, in accordance with the present disclosure.

Fig. 14 is a diagram illustrating an example process performed, for example, at a first UE or an apparatus of a first UE, in accordance with the present disclosure.

Fig. 15 is a diagram illustrating an example process performed, for example, at a network entity or an apparatus of a network entity, in accordance with the present disclosure.

Fig. 16 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

Fig. 17 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system, in accordance with the present disclosure.

Fig. 18 is a diagram illustrating an example of an implementation of code and circuitry for an apparatus, in accordance with the present disclosure.

Fig. 19 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

Fig. 20 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system, in accordance with the present disclosure.

Fig. 21 is a diagram illustrating an example of an implementation of code and circuitry for an apparatus, in accordance with the present disclosure.

DETAILED DESCRIPTION

According to one or more examples, a user equipment (UE) , such as an extended reality (XR) device, may conserve power using a discontinuous reception (DRX) mode. A UE in a DRX mode may transition between a sleep state for power conservation and an active state for data transmission and reception. A DRX cycle may include an active state duration (active time) and an inactive state duration (inactive time) . In one or more examples, a UE in a sleep state may turn off a radio and one or more other components or functions of the UE. Turning off or switching off a radio may include removing power from the radio such that the radio is not fully operating or not operating with full power. In one or more examples, a UE may wake up to an active state by turning on a radio and one or more other components or functions of the UE. Other components may include, for example, buffers, timers, memories, and/or processors. Functions of the UE may include, for example, communications, application operations, and/or configurations. Turning on or switching on a radio may include providing power to the radio such that the radio is fully operating (e.g., all applications or functions may have sufficient power to execute) and/or operating with full power. As used herein, the active state for data transmission and reception may be referred to as a DRX “ON-duration” (or “on-duration” ) . The DRX cycle may start at the beginning of an ON-duration and end at the beginning of the next ON-duration. In some aspects, a DRX cycle may be referred to as a “DRX long cycle. ”

In some examples, the UE may use a wake-up condition to determine at which ON-duration of a DRX cycle to wake up. The wake-up condition may be based at least in part on the subframe number of a subframe, which in one or more aspects may be a subframe of a frame identified by a system frame number (SFN) . The SFN may be part of a hyper SFN (H-SFN) of multiple SFNs. The H-SFN may include 1024 SFNs that wrap around (H-SFN restarts and increments after 1024 SFNs) . An extended DRX (eDRX) cycle may include multiple H-SFNs. The UE may wake up every eDRX cycle to monitor paging. The eDRX cycle for a Uu interface may be introduced in a UE inactive (idle) state with a maximum eDRX cycle that is 3 hours. The UE may wake up to monitor a paging occasion (PO) every eDRX cycle or up to every 3 hours.

In some examples, sidelink UEs may support sidelink DRX (SL DRX) . A direct frame number (DFN) may be used in sidelink communication. A DFN is similar to the SFN used in uplink and downlink communications. The DFN may be 10 bits and 10 ms. A hyper-DFN (H-DFN) may include 1024 DFNs (10.24 seconds) . The H-DFN may increment when the DFN wraps around (after 1024 DFNs) . The H-DFN may be comparable to a hyperframe or H-SFN used for DRX. In connected mode sidelink DRX, UEs may maintain a sidelink connection during DRX cycles.

In some examples, two peer UEs may calculate the active time at which to wake up for sidelink communications. The active time may be a select DFN. A UE can derive a DFN to wake up at using two ways: 1) derive the DFN from global navigation satellite system (GNSS) timing; or 2) receive the DFN from sidelink synchronization signal (SLSS) signaling. Requiring the UE to monitor for the GNSS signal consumes power. In some aspects, the UE can obtain the DFN from SLSS signaling. The two UEs may synchronize times in order to enter a sleep state, and then each UE may rely on a UE internal clock to calculate the time in which to wake up. That is, the UE may not have to rely on monitoring GNSS timing.

In some examples, a UE may be enabled to use sidelink in two scenarios: direct sidelink (non-relay) communication or in UE-to-network (U2N) relay. Direct sidelink communication involves communications between two UEs without a relay UE to a network entity. U2N relay involves a remote UE and a relay UE that relays communications between the remote UE and a network entity.

In a scenario with direct sidelink communication on a sidelink interface, a UE may be configured for sidelink DRX, where the active time may be calculated based on the DFN. There are 1024 DFNs in an H-DFN and thus the maximum sidelink DRX cycle is 10.24 seconds, if using DFN to calculate active time. According to one example, for direct sidelink communication, the two UEs may be RedCap UEs or internet of things (IoT) devices, and the two UEs may attempt to conserve power. However, a maximum of 10.24 seconds for a DRX cycle may not enough time for the UE to maximize power conservation. The UE may only conserve power during the inactive time of a DRX cycle and thus the UE may conserve power up to a maximum of 5.12 seconds in an H-DFN. Without a comparable eDRX for sidelink (where the UE may sleep for a time duration longer than allowed for connected sidelink DRX, such as up to 3 or more hours) , the UE may not be able to conserve as much power with a sidelink interface as can be conserved with a Uu interface.

In a scenario with U2N relay, the remote UE wakes up to monitor POs every DRX cycle on the Uu interface. The relay UE also monitors POs of the remote UE. In sidelink DRX, active time is calculated based on a DFN, with a maximum DRX cycle length of 10.24 seconds if using DFN to calculate active time. In an inactive (idle) state, the remote UE has a connection with the relay UE, and the relay UE forwards a received paging message to the remote UE (e.g., the remote UE not being able to receive the paging message due to being out of coverage of the network entity) . As described above for the direct sidelink communication scenario, if a remote UE is in an inactive state and there is no eDRX on sidelink, the remote UE has to monitor sidelink per DRX cycle. That is, in one example, the remote UE and the relay UE may not be able to sleep longer than allowed for connected mode sidelink DRX (e.g., up to 3 or more hours) and instead may wake up every DRX cycle. The remote UE and the relay UE can conserve power only during an inactive time of a DRX cycle. Waking up every DRX cycle consumes the power of both the remote UE and the relay UE.

According to various aspects described herein, sidelink UEs may conserve more power in both a direct sidelink communication scenario and a U2N scenario by introducing eDRX for sidelink. A sidelink eDRX may include a set of H-DFNs. A set of H-DFNs may include one or more H-DFNs. A UE (e.g., sidelink UE, remote UE, relay UE) may calculate the DFN during which to wake up, and the DFN may be within a sidelink eDRX cycle. The DFN may be within an active time window (ATW) in a sidelink eDRX cycle. The use of an active time window with the sidelink eDRX cycle allows the UEs to sleep for longer periods of time and conserve more power, because the sidelink eDRX cycle is a large cycle (e.g., up to 3 or more hours) . Therefore, a sleep time of a UE is not limited to half of a 10.24 ms H-DFN. Rather, the sleep time of the UE (outside of the active time window in the eDRX cycle) may be longer than for connected mode sidelink DRX or may include multiple inactive DFNs in a sidelink eDRX that add up to more sleep time than just half of the H-DFNs. The power saving may assist battery constrained devices, such as RedCap UEs.

In some aspects, the UEs may negotiate a configuration between themselves for the sidelink eDRX cycle. For example, a transmit UE (TX UE) may determine sidelink eDRX cycle parameters and send the parameters to a receive UE (RX UE) using a sidelink message (e.g., PC5-RRC message or a sidelink MAC CE) . Additionally, or alternatively, the RX UE may send sidelink eDRX assistance information to the TX UE. The assistance information may include a UE identifier (ID) (e.g., a 5G serving temporary mobile subscriber identity (5G-S-TMSI) , a subscription concealed identifier (SUCI) , a hash of a UE ID (UE_ID_H) , or a UE L2 ID) , an indication of the sidelink eDRX cycle (optional) , and/or an indication of the active time window. That is, if the TX is using a TX UE ID to calculate an active time, then the TX UE may send the TX UE ID (5G-S-TMSI, SUCI, UE_ID_H, UE L2 ID) to the RX UE. In some aspects, the TX UE may send eDRX parameters (eDRX cycle, active time window) to its serving gNB, and the serving gNB may provide the sidelink eDRX parameters to the TX UE. In some aspects, the sidelink eDRX parameters may be within an existing sidelink configuration information element (IE) or external to the existing sidelink configuration IE.

By negotiating a sidelink eDRX cycle configuration, the UEs may align when the UEs are to wake up in an active time window of a sidelink eDRX cycle. The UEs may avoid missed communications while conserving power.

In some aspects, the parameters may also include an indication of a starting point of the sidelink eDRX cycle and/or an eDRX offset (e.g., time after an indication to enter sidelink eDRX mode, SFN-DFN offset) . By providing the starting point or the eDRX offset, the UEs may coordinate a timing of the sidelink eDRX with a timing of the Uu eDRX. As a result, the UEs may wake up at the same time within each eDRX cycle and thus wake up fewer times, which conserves power.

In some aspects, the sidelink eDRX cycle mode may involve calculating an active time window within the sidelink eDRX cycle. The calculation may include information for the active time window, such as a UE ID or a hash of the UE ID. A UE may calculate a start of the active time window based at least in part on the UE ID or the hash of the UE ID. In some aspects, the information may include a start offset from a start of the sidelink eDRX cycle, and the UE may use the start offset to calculate the active window. In some aspects, the information may include an offset between an active time window of the Uu eDRX cycle and an active time window of a sidelink eDRX cycle. Two UEs may share this information for aligning each other’s active time window. By aligning the active time windows, the UE’s may communicate with each other during active times and conserve power during the inactive times.

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than 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 a claim.

Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses 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, or the like (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT) , aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G) .

Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE) ) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 110d) , a UE 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e) , and/or other entities. A network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit) . As another example, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) .

In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs. A network node 110 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 transmission reception point (TRP) , a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.

In some examples, a network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP) , the term “cell” can refer to a coverage area of a network node 110 and/or a network node subsystem serving this coverage area, depending on the context in which the term is used. A network node 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., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG) ) . A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. A network node may support one or multiple (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node) .

In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a CU, a DU, an 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 terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “base station” or “network node” may refer to one or more virtual base stations 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 terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110) . A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in Fig. 1, the network node 110d (e.g., a relay network node) may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.

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

A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A 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, 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 vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and/or any other suitable device that is configured to communicate via a wireless or wired medium.

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

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

In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a network node 110 as an intermediary to communicate with one another) . For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol) , and/or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the network node 110. In some examples, UE 120a and UE 120e may communicate directly as part od direct sidelink communication. In some examples, UE 120a may act as a relay UE, UE 120e may act as a remote UE, and network node 110a may be a next generation (NG) RAN network node as part of a UE-to-network (U2N) relay.

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, 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 although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz –24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz –71 GHz) , FR4 (52.6 GHz –114.25 GHz) , and FR5 (114.25 GHz –300 GHz) . Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent 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 techniques described herein are applicable to those modified frequency ranges.

In some aspects, a UE (e.g., a UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may negotiate, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The communication manager 140 may calculate the DFN based at least in part on the configuration. The communication manager 140 may wake up in the DFN, where the DFN is an active duration within the active time window. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, a network entity (e.g., a network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may obtain one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The communication manager 150 may transmit an indication of the one or more parameters to a second UE. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1) . The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1) . The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.

At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120) . The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS (s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning 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., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS) ) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) ) . A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if 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 through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 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 through 234t.

At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the downlink signals from the network node 110 and/or other network nodes 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 through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a 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 modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, or may 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, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig. 2.

On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM) , and transmitted to the network node 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 the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 4-21) .

At the network node 110, the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232) , detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 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 network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 4-21) .

The controller/processor of a network entity (e.g., the controller/processor 240 of the network node 110) , the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with negotiating a configuration for a sidelink eDRX cycle, as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 1400 of Fig. 14, process 1500 of Fig. 15, and/or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and/or the 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 (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 1400 of Fig. 14, process 1500 of Fig. 15, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a first UE (e.g., a UE 120) includes means for negotiating, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs; means for calculating the DFN based at least in part on the configuration; and/or means for waking up in the DFN, where the DFN is an active duration within the active time window. The means for the first UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, a network entity (e.g., a network node 110) includes means for obtaining one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs; and/or means for transmitting an indication of the one or more parameters to a second UE. In some aspects, the means for the network entity to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

In some aspects, an individual processor may perform all of the functions described as being performed by the one or more processors. In some aspects, one or more processors may collectively perform a set of functions. For example, a first set of (one or more) processors of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig. 2. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig. 2. For example, functions described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.

As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples) , or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more Cus, one or more DUs, one or more RUs, or a combination thereof) .

An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit) . A disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs) . In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples.

Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both) . A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.

Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit –User Plane (CU-UP) functionality) , control plane functionality (for example, Central Unit –Control Plane (CU-CP) functionality) , or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT) , an inverse FFT (iFFT) , digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

Each RU 340 may implement lower-layer functionality. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3GPP) , such as a lower layer functional split. In such an architecture, each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, Cus 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more Cus 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies) .

As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

Fig. 4 is a diagram illustrating an example 400 of DRX, in accordance with the present disclosure. As shown in Fig. 4, example 400 includes a UE 120 in communication with a network entity (e.g., network node (NN) 110) . In some examples, the UE 120 may be in a connected state (e.g., an RRC connected state) with the network node 110.

In one or more examples, a UE may conserve power using a DRX mode. A UE in a DRX mode may transition between a sleep state for power conservation and an active state for data transmission and reception. A DRX cycle may include an active state duration and an inactive state duration. In one or more examples, a UE in a sleep state may turn off a radio and one or more other components or functions of the UE. Turning off or switching off a radio may include removing power from the radio such that the radio is not fully operating or not operating with full power. In one or more examples, a UE may wake up to an active state by turning on a radio and one or more other components or functions of the UE. Other components may include, for example, buffers, timers, memories, and/or processors. Functions of the UE may include, for example, communications, application operations, and/or configurations. Turning on or switching on a radio may include providing power to the radio such that the radio is fully operating (e.g., all applications or functions may have sufficient power to execute) and/or operating with full power. As used herein, the active state for data transmission and reception may be referred to as a DRX “ON-duration” (or “on-duration” ) . The DRX cycle may start at the beginning of an ON-duration and end at the beginning of the next ON-duration. In some aspects, a DRX cycle may be referred to as a “DRX long cycle. ” Each DRX cycle may correspond to a DRX on-duration timer (length of an on-duration) and a DRX inactivity timer (how long after new data is received before the UE sleeps) .

In some examples, the UE may use a wake-up condition to determine when to wake up. The wake-up condition may be based at least in part on the subframe number of a subframe, which in one or more aspects may be a subframe of a frame identified by an SFN.

As shown in example 400, the network node 110 may transmit a DRX configuration to the UE 120. The configuration may indicate an inactive time 405 for a DRX cycle 410. The configuration may indicate a starting time of the inactive time 405 (e.g., a time offset) , a duration of the inactive time 405, a length of the DRX cycle 410, and/or a periodicity of the DRX cycle 410, among other examples. The UE 120 may be expected not to monitor or receive particular channels or signals during the inactive time 405. In this way, the UE 120 may enter a sleep state during the inactive time 405. The network node 110 may not transmit during an inactive time 405 of the UE 120. Downlink channels or signals restricted during the inactive time 405 may include periodic and/or semi-persistent channel state information (CSI) reference signals (CSI-RSs) (e.g., including tracking reference signals (TRSs) ) , positioning reference signals (PRSs) , physical downlink control channel (PDCCH) communications scrambled with a UE-specific radio network temporary identifier (RNTI) , PDCCHs in a type-3 common search space (CSS) (e.g., a group-common PDCCH) , and/or semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) communications, among other examples. Physical channel or signal restrictions applicable to the inactive time 405 may not be applicable to the active time 415.

As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.

Fig. 5 is a diagram illustrating an example 500 of sidelink communications, in accordance with the present disclosure.

As shown in Fig. 5, a first UE 505-1 may communicate with a second UE 505-2 (and one or more other UEs 505) via one or more sidelink channels 510. The UEs 505-1 and 505-2 may communicate using the one or more sidelink channels 510 for P2P communications, D2D communications, V2X communications (e.g., which may include V2V communications, V2I communications, and/or V2P communications) and/or mesh networking. In some aspects, the UEs 505 (e.g., UE 505-1 and/or UE 505-2) may correspond to one or more other UEs described elsewhere herein, such as UE 120. In some aspects, the one or more sidelink channels 510 may use a PC5 interface and/or may operate in a high frequency band (e.g., the 5.9 GHz band) . Additionally, or alternatively, the UEs 505 may synchronize timing of transmission time intervals (TTIs) (e.g., frames, subframes, slots, or symbols) using GNSS timing.

As further shown in Fig. 5, the one or more sidelink channels 510 may include a physical sidelink control channel (PSCCH) 515, a physical sidelink shared channel (PSSCH) 520, and/or a physical sidelink feedback channel (PSFCH) 525. The PSCCH 515 may be used to communicate control information, similar to a PDCCH and/or a physical uplink control channel (PUCCH) used for cellular communications with a network node 110 via an access link or an access channel. The PSSCH 520 may be used to communicate data, similar to a PDSCH and/or a physical uplink shared channel (PUSCH) used for cellular communications with a network node 110 via an access link or an access channel. For example, the PSCCH 515 may carry sidelink control information (SCI) 530, which may indicate various control information used for sidelink communications, such as one or more resources (e.g., time resources, frequency resources, and/or spatial resources) where a transport block (TB) 535 may be carried on the PSSCH 520. The TB 535 may include data. The PSFCH 525 may be used to communicate sidelink feedback 540, such as hybrid automatic repeat request (HARQ) feedback (e.g., acknowledgement or negative acknowledgement (ACK/NACK) information) , transmit power control (TPC) , and/or a scheduling request (SR) .

Although shown on the PSCCH 515, in some aspects, the SCI 530 may include multiple communications in different stages, such as a first stage SCI (SCI-1) and a second stage SCI (SCI-2) . The SCI-1 may be transmitted on the PSCCH 515. The SCI-2 may be transmitted on the PSSCH 520. The SCI-1 may include, for example, an indication of one or more resources (e.g., time resources, frequency resources, and/or spatial resources) on the PSSCH 520, information for decoding sidelink communications on the PSSCH, a quality of service (QoS) priority value, a resource reservation period, a PSSCH DMRS pattern, an SCI format for the SCI-2, a beta offset for the SCI-2, a quantity of PSSCH DMRS ports, and/or an MCS. The SCI-2 may include information associated with data transmissions on the PSSCH 520, such as a HARQ process ID, a new data indicator (NDI) , a source identifier, a destination identifier, and/or a CSI report trigger.

In some aspects, the one or more sidelink channels 510 may use resource pools. For example, a scheduling assignment (e.g., included in SCI 530) may be transmitted in sub-channels using specific resource blocks (RBs) across time. In some aspects, data transmissions (e.g., on the PSSCH 520) associated with a scheduling assignment may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing) . In some aspects, a scheduling assignment and associated data transmissions are not transmitted on adjacent RBs.

In some aspects, a UE 505 may operate using a sidelink transmission mode (e.g., Mode 1) where resource selection and/or scheduling is performed by a network node 110 (e.g., a base station, a CU, or a DU) . For example, the UE 505 may receive a grant (e.g., in downlink control information (DCI) or in an RRC message, such as for configured grants) from the network node 110 (e.g., directly or via one or more network nodes) for sidelink channel access and/or scheduling. In some aspects, a UE 505 may operate using a transmission mode (e.g., Mode 2) where resource selection and/or scheduling is performed by the UE 505 (e.g., rather than a network node 110) . In some aspects, the UE 505 may perform resource selection and/or scheduling by sensing channel availability for transmissions. For example, the UE 505 may measure a received RSSI parameter (e.g., a sidelink-RSSI (S-RSSI) parameter) associated with various sidelink channels, may measure an RSRP parameter (e.g., a PSSCH-RSRP parameter) associated with various sidelink channels, and/or may measure an RSRQ parameter (e.g., a PSSCH-RSRQ parameter) associated with various sidelink channels, and may select a channel for transmission of a sidelink communication based at least in part on the measurement (s) .

Additionally, or alternatively, the UE 505 may perform resource selection and/or scheduling using SCI 530 received in the PSCCH 515, which may indicate occupied resources and/or channel parameters. Additionally, or alternatively, the UE 505 may perform resource selection and/or scheduling by determining a channel busy ratio (CBR) associated with various sidelink channels, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE 505 can use for a particular set of subframes) .

In the transmission mode where resource selection and/or scheduling is performed by a UE 505, the UE 505 may generate sidelink grants, and may transmit the grants in SCI 530. A sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks to be used for the upcoming sidelink transmission on the PSSCH 520 (e.g., for TBs 535) , one or more subframes to be used for the upcoming sidelink transmission, and/or an MCS to be used for the upcoming sidelink transmission. In some aspects, a UE 505 may generate a sidelink grant that indicates one or more parameters for SPS, such as a periodicity of a sidelink transmission. Additionally, or alternatively, the UE 505 may generate a sidelink grant for event-driven scheduling, such as for an on-demand sidelink message.

As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

Fig. 6 is a diagram illustrating an example 600 of sidelink communications and access link communications, in accordance with the present disclosure.

As shown in Fig. 6, a transmitter (Tx) /receiver (Rx) UE 605 and an Rx/Tx UE 610 may communicate with one another via a sidelink, as described above in connection with Fig. 5. As further shown, in some sidelink modes, a network node 110 may communicate with the Tx/Rx UE 605 (e.g., directly or via one or more network nodes) , such as via a first access link. In some examples, the Tx/Rx UE 605 may be a relay UE that relays communications between the Rx/Tx UE 610 (remote UE) . The Tx/Rx UE 605 and/or the Rx/Tx UE 610 may correspond to one or more UEs described elsewhere herein, such as the UE 120 of Fig. 1. Thus, a direct link between UEs 120 (e.g., via a PC5 interface) may be referred to as a sidelink, and a direct link between a network 110 and a UE 120 (e.g., via a Uu interface) may be referred to as an access link. Sidelink communications may be transmitted via the sidelink, and access link communications may be transmitted via the access link. An access link communication may be either a downlink communication (from a network node 110 to a UE 120) or an uplink communication (from a UE 120 to a network node 110) .

As indicated above, Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.

Fig. 7 is a diagram illustrating an example 700 of a next-generation radio access network (NG-RAN) architecture, in accordance with the present disclosure.

Example 700 shows network nodes in an NG-RAN, such as gNB 705 and NG-eNB 710. The network nodes may have Uu links to UE 715 and UE 720, which are in NG-RAN coverage. UE 715 and UE 720 may communicate via a sidelink (e.g., PC5 interface) . UE 720 is outside of NG-RAN coverage and may communicate with UE 715 and UE 720 via sidelinks. UE 715 and/or UE 720 may operate as a relay UE to UE 720 (remote UE) as part of U2N relay. U2N relay may be single hop or multi-hop. Sidelink transmission and reception over a PC5 interface may be supported when a UE is inside NG-RAN coverage, irrespective of which RRC state the UE is in, and when the UE is outside NG-RAN coverage.

As indicated above, Fig. 7 is provided as an example. Other examples may differ from what is described with regard to Fig. 7.

Fig. 8A shows an access stratum (AS) protocol stack 802 for the control plane for a sidelink control channel for RRC in the PC5 interface. The protocol stack between UE 715 and UE 720 may include respective PHY layers, MAC layers, RLC layers, PDCP layers, and RRC layers. A control plane function may handle transport of control information between UEs. Generally, a first layer is referred to as higher than a second layer if the first layer is further from the PHY layer than the second layer. For example, the PHY layer may be referred to as a lowest layer, and the SDAP/PDCP/RLC/MAC layer may be referred to as higher than the PHY layer and lower than the RRC layer. An application (APP) layer, not shown in Fig. 8A, may be higher than the RRC/PDCP/RLC/MAC layer. In some cases, an entity may handle the services and functions of a given layer (e.g., a PDCP entity may handle the services and functions of the PDCP layer) , though the description herein refers to the layers themselves as handling the services and functions.

The RRC layer may handle communications related to configuring and operating the UEs 120, such as establishment, maintenance, security, and detection of and recovery from radio link failure. The RRC layer is frequently referred to as Layer 3 (L3) .

The PDCP layer, RLC layer, and MAC layer may be collectively referred to as Layer 2 (L2) . Thus, in some cases, the PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2.

The PDCP layer may provide data, in the form of PDCP protocol data units (PDUs) , to the RLC layer via RLC channels. The RLC layer may handle transfer of upper layer PDUs to the MAC and/or PHY layers, sequence numbering independent of PDCP sequence numbering, error correction via automatic repeat requests (ARQ) , segmentation and re-segmentation, reassembly of a service data unit (SDU) , RLC SDU discard, and RLC re-establishment.

The RLC layer may provide data, mapped to logical channels, to the MAC layer. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer as described below) , multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from TBs delivered to/from the physical layer on transport channels, scheduling information reporting, error correction through HARQ, priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of one UE by means of logical channel prioritization, and padding.

The MAC layer may package data from logical channels into TBs, and may provide the TBs on one or more transport channels to the PHY layer. The PHY layer may handle various operations relating to transmission of a data signal, as described in more detail in connection with Fig. 2. The PHY layer is frequently referred to as Layer 1 (L1) .

On the receiving side, the operations may be similar to those described for the transmitting side, but reversed. For example, the PHY layer may receive TBs and may provide the TBs on one or more transport channels to the MAC layer. The MAC layer may map the transport channels to logical channels and may provide data to the RLC layer via the logical channels. The RLC layer may map the logical channels to RLC channels and may provide data to the RRC layer via the RLC channels. The PDCP layer may map the RLC channels to radio bearers and may provide data to the RRC layer via the radio bearers.

Data may be passed between the layers in the form of PDUs and SDUs. An SDU is a unit of data that has been passed from a layer or sublayer to a lower layer. For example, the PDCP layer may receive a PDCP SDU. A given layer may then encapsulate the unit of data into a PDU and may pass the PDU to a lower layer. For example, the PDCP layer may encapsulate the PDCP SDU into a PDCP PDU and may pass the PDCP PDU to the RLC layer. The RLC layer may receive the PDCP PDU as an RLC SDU, may encapsulate the RLC SDU into an RLC PDU, and so on. In effect, the PDU carries the SDU as a payload.

Control plane protocol stack 804 in Fig. 8B is similar to AS protocol stack 802, except that a PC5 sidelink (PC5-S) layer is on top of the PDCP layer. The UEs may transmit and receive control signaling and data at the PC5-S layer.

As indicated above, Fig. 8A and Fig. 8B are provided as examples. Other examples may differ from what is described with regard to Fig. 8A and Fig. 8B.

Fig. 9 is a diagram illustrating examples 900 and 902 of control plane protocol stacks for U2N relay, in accordance with the present disclosure.

Example 900 shows a control plane protocol stack for L2 U2N relay between remote UE 720 and an access and mobility management function (AMF) 910 in the core network. The AMF 910 may include one or more devices that act as a termination point for non-access stratum (NAS) signaling and/or mobility management, among other examples. The remote UE 720 may establish security with the AMF 910 via one or more NAS operations. A NAS level operation may include an authentication operation that is performed between the remote UE 720 and the AMF 910.

In some aspects, the AMF 910 may request a network slice selection function (NSSF) to select network slice instances for the UE 120, e.g., at least partially in response to a request for data service from the UE 120. The NSSF may include one or more devices that select network slice instances for the UE 120. Network slicing is a network architecture model in which logically distinct network slices operate using common network infrastructure.

The remote UE 720 may communicate with the AMF 910 on a NAS mobility management (MM) layer. The remote UE 720 may communicate with a session management function (SMF) 915 on a NAS session management (SM) layer. The SMF 915 may include one or more devices that support the establishment, modification, and release of communication sessions in the wireless telecommunications system. For example, the SMF 915 may configure traffic steering policies at a user plane function (UPF) 920 and/or enforce UE internet protocol (IP) address allocation and policies, among other examples. In some aspects, the SMF 915 may provision the network slice instances selected by the NSSF for the remote UE 720.

Example 900 shows protocol layers for the remote UE 720, such as a PC5-PHY, PC5-MAC, and PC5-RLC. Relay UE 715 may use these layers over a PC5 interface with UE 720. UE 715 may use Uu-RLC, Uu-MAC, Uu-PHY, and adaptation layers over a Uu interface with the NG-RAN 905. The adaptation layer may transmit information (e.g., master information block (MIB) , system information black (SIB) ) for an upper layer (e.g., RRC layer) to initiate initial access, may be provided by adaptation layer, or the upper layer may skip the step to check such information (e.g., RRC layer may always consider that the RRC layer has valid information) . The remote UE 720 and the relay UE 715 may use a PC5-adaptation layer for similar signaling. The NG-RAN 905 may use a N2 interface stack. Elements of a 5G core network may communicate over various interfaces, such as an N2 interface, an N3 interface, an N4 interface, an N6 interface, an N9 interface, and an N11 interface. Some of these interfaces may involve a next generation application protocol (NGAP) , a stream control transmission protocol (SCTP) , a packet forwarding control protocol (PFCP) , and a general packet radio system (GPRS) tunnelling protocol user plane (GTP-U) . The AMF 910 may use an N2 interface stack and an N11 interface stack. The SMF 915 may use an N11 interface stack.

Example 902 shows a user plane protocol stack for L2 U2N relay, where the remote UE 720 may use a PDU layer with a UPF 920 to communicate data. The UPF 920 may include one or more devices that serve as an anchor point for intraRAT and/or interRAT mobility. In some aspects, the UPF 920 may apply rules to packets, such as rules pertaining to packet routing, traffic reporting, and/or handling user plane QoS, among other examples.

Other layers in the user plane may include an SDAP layer in L2. Thus, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (e.g., if the UE 120 is transmitting an uplink communication or the network node 110 is transmitting a downlink communication) , the SDAP layer may receive a data flow in the form of a QoS flow. The SDAP layer, or the RRC/NAS layer, may map QoS flows or control information to radio bearers. Thus, the SDAP layer may be said to handle QoS flows on the transmitting side. The SDAP layer may provide the QoS flows to the PDCP layer via the corresponding radio bearers. Layers for communications between the NG-RAN 905 and the UPF 920 over an N3 interface may include GTP-U, user datagram protocol (UDP) , IP, L2, and L1.

In some examples, when both the relay UE 715 and the remote UE 720 are in RRC IDLE or RRC INACTIVE, the relay UE 715 monitors paging occasions (POs) of its connected remote UE 720. When the relay UE 715 needs to monitor paging for the remote UE 720, the relay UE 715 may monitor all POs of the remote UE 720. When the relay UE 715 is in RRC_CONNECTED and the remote UE 720 is in RRC_IDLE or RRC_INACTIVE, there are two options for paging delivery. The relay UE 715 may monitor POs of its connected remote UE 720 if the active downlink bandwidth part (BWP) of the relay UE 715 is configured with a control resource set (CORESET) and a paging search space.

The delivery of the remote UE’s 720 paging can be performed through a dedicated RRC message from a network node of the NG-RAN 905 to the relay UE 715. The dedicated RRC message for delivering remote UE paging to the RRC_CONNECTED relay UE 715 may contain one or more remote UE IDs. It is up to network implementation to decide which of the above two options to use. The relay UE 715 in RRC_CONNECTED, if configured with paging search space, may determine whether to monitor POs for the remote UE 720 based on the indication within the PC5- RRC signalling received from the remote UE 720 (e.g., 5G-S-TMSI, inactive radio network temporary identifier (I-RNTI) ) .

The remote UE 720 in RRC_IDLE may provide a 5G-S-TMSI and a UE-specific DRX cycle (configured by upper layer) to the relay UE 715 for requesting to perform PO monitoring. The remote UE 720 in RRC_INACTIVE provides the minimum value of two UE-specific DRX cycles (configured respectively by upper layer and NG-RAN) , 5G-S-TMSI, and I-RNTI to the relay UE 715 for PO monitoring. The relay UE 715 in RRC_CONNECTED can notify the remote UE 720 information (i.e., 5G-S-TMSI/I-RNTI) to the gNB via a SidelinkUEInformationNR message for paging delivery purpose. The relay UE 715 receives paging messages to check the 5G-S-TSMI/I-RNTI and sends relevant paging record to the remote UE 720 accordingly. The relay UE 720 may use unicast signalling to send paging to the remote UE 720 via PC5.

As indicated above, Fig. 9 is provided as an example. Other examples may differ from what is described with regard to Fig. 9.

In some examples, sidelink may support sidelink DRX (SL DRX) for unicast, groupcast, and broadcast. For unicast, SL DRX is configured per pair of source L2 ID and destination L2 ID. A UE maintains a set of SL DRX timers for each direction per pair of source L2 ID and destination L2 ID. The SL DRX configuration for a pair of source/destination L2 IDs for a direction may be negotiated between the UEs in the AS layer. For SL DRX configuration of each direction, where one UE is the TX UE and the other is the receiving (RX) UE, the RX UE may send assistance information, which includes its desired SL on-duration timer, SL DRX start offset, and SL DRX cycle, to the TX UE and the mode 2 TX UE may use the assistance information to determine the SL DRX configuration for the RX UE. The TX UE in RRC_IDLE /RRC_INACTIVE /out of coverage (OOC) , or in RRC_CONNECTED and using mode 2 resource allocation, determines the SL DRX configuration for the RX UE. For a TX UE in RRC_CONNECTED and using mode 1 resource allocation, the SL DRX configuration for the RX UE is determined by the serving gNB of the TX UE. The TX UE sends the SL DRX configuration to be used by the RX UE to the RX UE. The RX UE may accept or reject the SL DRX configuration. A default SL DRX configuration for groupcast/broadcast can be used for direct communication request (DCR) messages.

When the TX UE is in RRC_CONNECTED, the TX UE may report the received assistance information to its serving gNB and send the SL DRX configuration to the RX UE upon receiving the SL DRX configuration in dedicated RRC signalling from the gNB. When the RX UE is in RRC_CONNECTED, the RX UE can report the received SL DRX configuration to its serving gNB (e.g., for alignment of the Uu and SL DRX configurations) .

An SL on-duration timer, an SL inactivity-timer, an SL HARQ round trip time (RTT) timer, and an SL HARQ retransmission timer are supported in unicast. An SL HARQ RTT timer and an SL HARQ retransmission timer are maintained per SL process at the RX UE. In addition to (pre) configured values for each of these timers, an SL HARQ RTT timer value can be derived from the retransmission resource timing when SCI indicates more than one transmission resource. SL DRX MAC CE is introduced for SL DRX operation in unicast only.

In some examples, a DFN is used in sidelink communication. A DFN is similar to the SFN used in uplink and downlink communications. The DFN may be 10 bits and 10 ms. An H-DFN may include 1024 subframes or 10.24 seconds. The H-DFN may increment when the DFN wraps around (after 1024 DFNs) . An extended DRX (eDRX) may include multiple H-SFNs. The H-DFN may be comparable to a hyperframe or hyper SFN (H-SFN) used for DRX.

In some examples, two peer UEs may calculate the active time on sidelink using DFN. Currently, a UE can derive a DFN using two ways: 1) derive from GNSS timing; or 2) receive the DFN from SLSS signaling. Requiring the UE to monitor for the GNSS signal consumes power. In some aspects, if the UE can obtain the DFN from SLSS signaling. The two UEs may firstly sync up on the time to sleep and then each UE may rely on a UE internal clock to calculate the time in which to wake up. That is, the UE may not have to rely on monitoring GNSS timing.

A UE may be configured to use an eDRX cycle in an inactive (idle) state for monitoring paging messages. The eDRX cycle extends a DRX cycle up to about 3 hours by including multiple H-SFNs (10 bit) . One H-SFN may include 1024 SFNs. A UE may wake up during the paging time window (PTW) every extended DRX cycle. A paging hyperframe (PH) refers to the H-SFN in which the UE starts monitoring paging DRX during the PTW used in RRC_IDLE. The PH and PTW are determined based on a formula known by the AMF, the UE, and the NG-RAN. H-SFN, PH and PTW are used if the eDRX cycle is greater than 10.24 seconds.

Fig. 10 is a diagram illustrating an example 1000 of a sidelink eDRX, in accordance with the present disclosure.

In a scenario with direct sidelink communication on a sidelink interface, a UE may be configured for In sidelink DRX, where the active time may be calculated based on the DFN. There are 1024 DFNs in an H-DFN and thus the maximum sidelink DRX cycle is 10.24 seconds, if using DFN to calculate active time. According to one example, for direct sidelink communication, the two UEs may be RedCap UEs or internet of things (IoT) devices, and the two UEs may attempt to conserve power. However, a maximum of 10.24 seconds for a DRX cycle is not enough time for the UE to maximize power conservation . The UE may only conserve power during the inactive time of a DRX cycle and thus the UE may conserve power up to a maximum of 5.12 seconds in an H-DFN. Without a comparable eDRX for sidelink (where the UE may sleep and not wake up for up a longer period of time than connected mode sidelink DRX) , the UE may not be able to conserve as much power with a sidelink interface as can be conserved with a Uu interface.

In a scenario with U2N relay , the remote UE wakes up to monitor POs every DRX cycle on the Uu interface. The relay UE also monitors POs of the remote UE. In existing sidelink DRX, active time is calculated based on a DFN, with a maximum DRX cycle length of 10.24 seconds if using DFN to calculate active time . In an inactive (idle) state, the remote UE has a connection with the relay UE, and the relay UE forwards a received paging message to the remote UE (e.g., remote UE was not able to receive the paging message) . As described above for the direct sidelink communication scenario, if a remote UE is in an inactive state and there is no eDRX on sidelink, the remote UE has to monitor sidelink per DRX cycle . The remote UE and the relay UE may not sleep longer than connected mode sidelink DRX and instead may have to wake up every DRX cycle. The remote UE and the relay UE can conserve power only during an inactive time of a DRX cycle. Waking up every DRX cycle consumes the power of both the remote UE and the relay UE.

According to various aspects described herein, sidelink UEs may conserve more power. A UE may calculate the DFN during which to wake up, and the DFN may be within a sidelink eDRX cycle. The DFN may be within an active time window in a sidelink eDRX cycle. The use of an active time window with the sidelink eDRX cycle allows the UEs to sleep for longer periods of time and conserve more power, because the sidelink eDRX cycle is a large cycle (e.g., up to 3 or more hours) . Therefore, a sleep time of a UE is not limited to half of a 10.24 ms H-DFN. Rather, the sleep time of the UE (outside of the active time window in the eDRX cycle) may be longer than for connected mode sidelink DRX (e.g., up to 3 or more hours) and or may include thus may have multiple inactive DFNs in a sidelink eDRX that add up to more sleep time than just half of the HDFNs. The power saving may assist battery constrained devices, such as RedCap UEs.

In a direct sidelink scenario, the two UEs may wake up at the same time to communicate with each other using a sidelink eDRX cycle. In a U2N relay scenario, the remote UE and the relay UE may wake up at the same time to communicate with each other using the sidelink eDRX cycle. Using the sidelink eDRX cycle, the UEs may calculate an active time window in which to wake up.

The active time window in the sidelink eDRX may be aligned with an active time window in Uu eDRX cycle. In an H-DFN setting for direct communication, if an H-SFN is received, a UE may set the H-DFN to be the same number as an H-SFN. If an H-SFN is not received, the UE may set the H-DFN by implementation or according to the H-DFN received from other UE. In an H-DFN sync-up, a UE may indicate a current H-DFN in an RRCReconfigurationSidelink message or in SCI or a sidelink MAC CE to the peer UE. Alternatively, a UE may indicate an H-SFN in an SLSS message.

Example 1000 shows a sidelink eDRX cycle 1002 that includes multiple H-DFNs 1004. The UE may wake up in an H-DFN 1004 made up of 1024 DFNs. In some aspects, the UE may calculate an active time window 1008 in the H-DFN 1004 that includes active DRX cycles. The UE may calculate to wake up in DFN 1010. The DFN 1010 may be an on-duration of a DRX cycle 1012 (short DRX cycle) . The active time window 1008 may start after an offset (Start_Offset) 1014 within the eDRX cycle 1002. The start of the active time window 1008 (ATW_start) 1008 may be a PO starting within the eDRX cycle 1002. The end of the active time window 1008 (ATW_end) may end in the eDRX cycle 1002. In some aspects, the ATW_start calculation may be a (Tcurrent –Tref) mod eDRX cycle = Start_Offset, where Tcurrent is the current universal time coordinated (UTC) time obtained from GNSS, and Tref is the reference UTC time 00: 00: 00 on a Gregorian calendar date 1 January, 1900, in ms. The ATW_end calculation may be ATW_end = ATW_start + On_Duration. For U2N relay, the core network and the gNB may calculate the PO as above to align Uu POs and SL POs.

In some aspects, the UEs may negotiate a sidelink eDRX configuration between themselves. For example, a TX UE may determine sidelink eDRX parameters and send the parameters to an RX UE using a sidelink message, such as a PC5-RRC message (e.g., RRCReconfigurationSidelink) or a sidelink MAC CE. Optionally, the RX UE may send sidelink eDRX assistance information to the TX UE. The assistance information may include a UE ID (e.g., 5G-S-TMSI, a SUCI, hash of a UE ID (UE_ID_H) , or a UE L2 ID) , an indication of the sidelink eDRX cycle (optional) , and/or an indication of the active time window. That is, if the TX is using a TX UE ID to calculate an active time, then the TX UE may send the UE ID (5G-S-TMSI, SUCI, UE_ID_H, UE L2 ID) to the RX UE. In some aspects, the TX UE may send eDRX parameters (eDRX cycle, active time window) to its serving gNB, and the serving gNB may provide the sidelink eDRX parameters to the TX UE. In some aspects, the sidelink eDRX parameters may be within an existing sidelink configuration IE or external to the existing sidelink configuration IE.

In some aspects associated with direct sidelink communication, a UE may calculate the active time in an H-DFN for direct sidelink communication. For example, the active time may be calculated as H-DFN mod T_{eDRX_SL} = (UE_ID_H mod T_{eDRX_SL}) , where UE_ID_H is the 13 most significant bits of the hashed ID UE_ID_H, T_{eDRX_SL} is an RX UE-specific sidelink eDRX cycle in H-DFN (T_{eDRX_SL} = 2, …, 1024 hyper DFN) . ATW_start denotes the first DFN of the H-DFN that is part of the active time window and has a DFN satisfying the following equation: DFN = 128 × i_{eDRX_SL}, where i_{eDRX_SL} = floor (UE_ID_H /T_{eDRX_SL}) mod 8. ATW_end is the last DFN of the ATW and has a DFN satisfying the following equation: DFN = (ATW_start + L × 100 -1) mod 1024, where L = the length of the active time window (in seconds) . UE_ID_H may be the same as a Uu hashed ID for the 5G-S-TMSI. If there is no 5G-S-TMSI, then the SUCI can be used to derive a hashed ID. UE_ID_H can also be a UE L2 ID.

In some aspects associated with U2N relay, the remote UE may calculate the active time window in each sidelink eDRX cycle and wake up in the active time window to monitor paging. The calculated sidelink active time window may be aligned with a Uu active time window for paging monitoring. The relay UE may set the H-DFN number to be the same as the H-SFN number. In some aspects, there may be an offset between the Uu SFN and the sidelink DFN. For the sidelink eDRX configuration negotiation, the remote UE may send sidelink eDRX parameters to the relay UE using a PC5 RRC message (e.g., RRCReconfigurationSidelink) , a PC5-S message, or a sidelink MAC CE. The sidelink eDRX parameters may include a remote UE ID (e.g., 5G-S-TMSI, UE_ID_H, eDRX cycle number, active time window) . The remote UE’s sidelink eDRX cycle number and active time window may be provided at the NAS layer.

In some aspects associated with U2N relay, the remote UE may calculate the active time as H-DFN’ mod T_{eDRX_SL}= (UE_ID_H mod T_{eDRX_SL}) . ATW_start may denote the first DFN of the H-DFN that is part of the active time window and has a DFN satisfying the following equation: DFN’ = 128 *i_{eDRX_SL}, where i_{eDRX_SL} =floor (UE_ID_H /T_{eDRX_SL}) mod 8.

By negotiating a sidelink eDRX configuration, the UEs may align when the UEs are to wake up in an active time window of a sidelink eDRX cycle. The UEs may avoid missed communications while conserving power.

As indicated above, Fig. 10 is provided as an example. Other examples may differ from what is described with regard to Fig. 10.

Figs. 11A-11C are diagrams illustrating examples 1100, 1102, and 1104 of an SFN-DFN offset, in accordance with the present disclosure.

If an SFN-DFN offset is indicated and if the SFN-DFN offset > 0, the ATW_start may be the n^th direct radio frame prior to DFN’ , where n is the SFN-DFN offset 1106 shown in example 1100 of Fig. 11A. If the SFN-DFN offset < 0, ATW_start may be the n^th direct radio frame after DFN’ , where n is SFN-DFN offset 1106 shown in example 1102 of Fig. 11B. If the SFN-DFN offset = 0, ATW_start may be at DFN’ .

Additionally, if a subframe offset or a slot offset 1108 is indicated, the ATW_start may be one direct radio frame earlier compared with the calculated ATW_start above, as shown in example 1104 of Fig. 11C. ATW_end may be the last DFN of the ATW and has a DFN satisfying the following equation: DFN = (ATW_start + L × 100 -1) mod 1024.

As indicated above, Figs. 11A-11C provide some examples. Other examples may differ from what is described with regard to Figs. 11A-11C.

Fig. 12 is a diagram illustrating an example 1200 of an active time window in a sidelink eDRX cycle, in accordance with the present disclosure. Example 1200 shows a sidelink eDRX cycle 1202 that includes an active time window 1204 with an ATW_start 1206 and an ATW_end 1208. There may be an eDRX offset 1210 between a time eDRX 1212 and an eDRX start 1214.

In some aspects associated with direct sidelink communication, two sidelink UEs may calculate an active time based on the coordinated enabling of sidelink eDRX. The two UEs may coordinate the eDRX starting point, and calculate active time window in each sidelink eDRX cycle. Each UE may wake up in the active time window 1204 in each sidelink eDRX cycle 1202 to transmit or receive sidelink data. In some aspects, legacy SL DRX may be used during the active time window 1204.

In some aspects, the UEs may negotiate a sidelink eDRX configuration. For example, a TX UE may determine sidelink eDRX parameters (e.g., indicating a sidelink eDRX cycle and/or an active time window) and send the parameters to an RX UE using a sidelink message (e.g., a PC5-RRC message or a sidelink MAC CE) . Optionally, the RX UE may send eDRX assistance information to the TX UE. The assistance information may include an eDRX cycle and/or an active time window. Optionally, the TX UE may send the sidelink eDRX parameters (e.g., indicating a sidelink eDRX cycle, an ATW) to its serving gNB, and the serving gNB may provide the modified sidelink eDRX parameters to the TX UE. The TX UE may determine the starting point (eDRX start 1214) to enter eDRX mode and send the related configurations to the RX UE. The eDRX offset 1210 may be compared with the time (time eDRX 1212) at which the UE receives an indication to enter a sidelink eDRX mode. The TX UE may send a PC5-RRC message to the RX UE indicating to enter the sidelink eDRX mode. If the starting point (eDRX_offset 1210) is indicated, the TX and the RX UE may enter the sidelink eDRX mode after the eDRX_offset 1210 time. The eDRX_offset 1210 may be a unit of a second, a millisecond, or a direct radio frame. If the starting point (eDRX_offset 1210) is not indicated, the TX and the RX UE may enter the eDRX mode directly. Optionally, the TX UE may send an indication to its serving gNB, requesting to enter the sidelink eDRX mode. The gNB may send an indication of the eDRX_offset 1210 to the TX UE.

In some aspects, the two UEs may calculate ATW_start 1206 and ATW_end 1208 using eDRX_start 1214: Time_eDRX + eDRX_offset as the timing to enter eDRX mode. ATW_start may be eDRX_start + Start_offset + (n -1) × eDRX cycle, where n is the nth cycle after entering the sidelink eDRX mode. ATW_end may be ATW_start + ATW.

In some aspects associated with U2N relay, a network entity may configure the remote UE and/or the relay UE with sidelink eDRX starting point parameters. The remote UE and the relay UE may send the modified eDRX starting point parameters to the relay UE or the remote UE. The remote UE may calculate the active time window in each sidelink eDRX cycle and wake up in the active time window in each sidelink eDRX cycle to monitor paging. In some aspects, legacy SL DRX could be used during the active time window.

In some aspects, the two UEs may negotiate a sidelink eDRX configuration. The network entity may configure the remote UE and the relay UE with sidelink eDRX starting point parameters (eDRX_offset) using an RRC message or a SL MAC CE. The remote UE and the relay UE may send the modified eDRX_offset to the relay UE and/or the remote UE using a PC5-RRC message or a sidelink MAC CE. The modified eDRX_offset may take into account the processing time in the remote UE or the relay UE to receive or transmit messages. The remote UE or the relay UE may send a PC5-RRC message to the relay UE or the remote UE, indicating to enter the sidelink eDRX mode. The relay UE or remote UE may enter the eDRX mode after a eDRX_offset time. If the starting point (eDRX_offset) is not indicated, the remote UE and the relay UE may enter sidelink eDRX mode directly. The remote UE may send sidelink eDRX parameters to the relay UE. The sidelink eDRX parameters may include an indication of the eDRX cycle and/or an indication of the active time window. The UEs may calculate ATW_start and ATW_end as described above for the direction communication scenario.

In some aspects, whenever the UEs wake up, the two UE check whether the sidelink (e.g., PC5) connection is available by sending a keep alive message to the peer UE. If the PC5 connection is not available, the UE may release the PC5 connection locally.

As indicated above, Fig. 12 is provided as an example. Other examples may differ from what is described with regard to Fig. 12.

Fig. 13 is a diagram illustrating an example 1300 associated with sidelink eDRX configuration, in accordance with the present disclosure. As shown in Fig. 13, a network entity 1310 (e.g., network node 110) and a UE 1320 (e.g., UE 120, UE 715) may communicate with one another on a wireless network (e.g., wireless network 100) . The UE 1320 may communication with a UE 1330 (e.g., UE 120, UE 720) on a sidelink (e.g., PC5 link) . In one scenario, the UE 1320 and the UE 1330 communicate directly. In another scenario, the UE 1320 operates as a relay UE for UE 1330, which may be a remote UE out of coverage of the network entity 1310. Example 1330 may be applicable to both scenarios.

As shown by reference number 1335, the network entity 1310 may transmit sidelink eDRX cycle parameters for a sidelink eDRX cycle configuration 1336 (e.g., length of the sidelink eDRX cycle as a quantity of H-DFNs) . As shown by reference number 1340, relay UE 1320 and remote UE 1330 may negotiate the sidelink eDRX cycle configuration 1336. The sidelink eDRX cycle may include a set of H-DFNs, which may include one or more H-DFNs.

In some aspects, the negotiation may include UE 1320 transmitting the parameters. The parameters may also include an indication of a starting point of the sidelink eDRX cycle and/or an eDRX offset (e.g., time after an indication to enter sidelink eDRX mode, SFN-DFN offset) . As shown by reference number 1342, UE 1320 may select the parameters. As shown by reference number 1344, UE 1320 may transmit, and UE 1330 may receive, the parameters. As shown by reference number 1346, UE 1330 may transmit, and UE 1320 may receive, a response. The response may indicate acceptance, rejection, or modification of the parameters. The response may include an indication to enter the sidelink eDRX cycle mode, which is a DRX mode that uses a sidelink eDRX cycle (e.g., as sidelink eDRX cycle 1202 in example 1200 of Fig. 12) .

In some aspects, the sidelink eDRX cycle mode may involve calculating an active window within the sidelink eDRX cycle 1202 (e.g., active time window 1204 in example 1200) . The configuration may include information for the active time window, such as a UE ID or a hash of the UE ID. A UE may calculate a start of the active time window based at least in part on the UE ID or the hash of the UE ID.

In some aspects, the negotiation may alternatively involve UE 1330 transmitting, and UE 1320 receiving, parameters in assistance information, as shown by reference number 1348. The assistance information may include a length of the sidelink eDRX cycle, a UE ID, and/or a hash of the UE ID. As shown by reference number 1350, UE 1320 may transmit, and UE 1330, a response. The response may indicate whether the parameters in the assistance information are accepted, rejected, or modified.

As shown by reference number 1355, the UE 1330 may calculate the DFN in which to wake up. This may involve calculating the H-DFN in the sidelink eDRX cycle and/or the active time window. The calculated DFN may be an active duration of a short DRX cycle within the active time window.

As shown by reference number 1360, UE 1330 may wake up at the DFN to receive a communication in an active duration of a short DRX cycle. As shown by reference number 1365, UE 1320 may also calculate the DFN to wake up at the same time. As shown by reference number 1370, UE 1320 may wake up at the calculated DFN. As shown by reference number 1375, UE 1320 may transmit a communication during the active duration.

By negotiating and using a sidelink eDRX cycle, the UEs may coordinate to communicate and conserve more power than if a sidelink eDRX cycle and its active time window are not used.

As indicated above, Fig. 13 is provided as an example. Other examples may differ from what is described with regard to Fig. 13.

Fig. 14 is a diagram illustrating an example process 1400 performed, for example, at a first UE or an apparatus of a first UE, in accordance with the present disclosure. Example process 1400 is an example where the apparatus or the first UE (e.g., UE 120, UE 715, UE 720, UE 1320, UE 1330) performs operations associated with negotiating a configuration for sidelink eDRX.

As shown in Fig. 14, in some aspects, process 1400 may include negotiating, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs (block 1410) . For example, the first UE (e.g., using communication manager 140 and/or configuration component 1608, depicted in Fig. 16) may negotiate, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs, as described above.

As further shown in Fig. 14, in some aspects, process 1400 may include calculating the DFN based at least in part on the configuration (block 1420) . For example, the first UE (e.g., using communication manager 140 and/or calculation component 1610, depicted in Fig. 16) may calculate the DFN based at least in part on the configuration, as described above.

As further shown in Fig. 14, in some aspects, process 1400 may include waking up in the DFN, the DFN being an active duration within the active time window (block 1430) . For example, the first UE (e.g., using communication manager 140 and/or reception component 1602, depicted in Fig. 16) may wake up in the DFN, where the DFN is an active duration within the active time window, as described above.

Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the configuration includes a length of the sidelink eDRX cycle.

In a second aspect, alone or in combination with the first aspect, process 1400 includes calculating the active time window based at least in part on a length of the sidelink eDRX cycle.

In a third aspect, alone or in combination with one or more of the first and second aspects, the configuration includes information for determining the active time window.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the information for the active time window includes a UE ID or a hash of the UE ID, and process 1400 includes calculating a start of the active time window based at least in part on the UE ID or the hash of a UE ID.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, negotiating the configuration includes selecting one or more parameters for the sidelink eDRX cycle, transmitting an indication of the one or more parameters, and receiving a response to the indication.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, negotiating the configuration includes receiving assistance information, and selecting the one or more parameters includes selecting the one or more parameters based at least in part on the assistance information.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the assistance information includes one or more of a UE ID, a hash of the UE ID, a length of the sidelink eDRX cycle, or information for the active time window.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, negotiating the configuration includes receiving an indication of one or more parameters for the sidelink eDRX cycle, and transmitting a response to the indication.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, negotiating the configuration includes transmitting assistance information including one or more of a UE ID, a hash of the UE ID, a length of the sidelink eDRX cycle, or information for the active time window.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the active time window is based at least in part on an offset from a Uu active time window.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the configuration indicates a starting point for the sidelink eDRX cycle.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the starting point is an eDRX offset after a starting indication to start a sidelink eDRX mode.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process 1400 includes receiving information for the eDRX offset.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the first UE is a remote UE that is configured to communicate with a network entity via the second UE.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the first UE is a relay UE that is configured to relay communications between the second UE and a network entity.

Although Fig. 14 shows example blocks of process 1400, in some aspects, process 1400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 14. Additionally, or alternatively, two or more of the blocks of process 1400 may be performed in parallel.

Fig. 15 is a diagram illustrating an example process 1500 performed, for example, at a network entity or an apparatus of a network entity, in accordance with the present disclosure. Example process 1500 is an example where the apparatus or the network entity (e.g., network node 110, network entity 1310) performs operations associated with a configuration for sidelink eDRX.

As shown in Fig. 15, in some aspects, process 1500 may include obtaining one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs (block 1510) . For example, the network entity (e.g., using communication manager 150 and/or configuration component 1908, depicted in Fig. 19) may obtain one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs, as described above.

As further shown in Fig. 15, in some aspects, process 1500 may include transmitting an indication of the one or more parameters to a second UE (block 1520) . For example, the network entity (e.g., using communication manager 150 and/or transmission component 1904, depicted in Fig. 19) may transmit an indication of the one or more parameters to a second UE, as described above.

Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, process 1500 includes transmitting information for an eDRX offset associated with starting a sidelink eDRX mode after a starting indication to start a sidelink eDRX mode.

In a second aspect, alone or in combination with the first aspect, process 1500 includes transmitting information for a starting point of a sidelink eDRX mode.

Although Fig. 15 shows example blocks of process 1500, in some aspects, process 1500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 15. Additionally, or alternatively, two or more of the blocks of process 1500 may be performed in parallel.

Fig. 16 is a diagram of an example apparatus 1600 for wireless communication, in accordance with the present disclosure. The apparatus 1600 may be a first UE, or a first UE may include the apparatus 1600. In some aspects, the apparatus 1600 includes a reception component 1602 and a transmission component 1604, which may be in communication with one another (for example, via one or more buses and/or one or more other components) . As shown, the apparatus 1600 may communicate with another apparatus 1606 (such as a UE, a base station, or another wireless communication device) using the reception component 1602 and the transmission component 1604. As further shown, the apparatus 1600 may include the communication manager 140. The communication manager 140 may include a configuration component 1608 and/or a calculation component 1610, among other examples.

In some aspects, the apparatus 1600 may be configured to perform one or more operations described herein in connection with Figs. 1-13. Additionally, or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as process 1400 of Fig. 14. In some aspects, the apparatus 1600 and/or one or more components shown in Fig. 16 may include one or more components of the first UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 16 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The reception component 1602 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1606. The reception component 1602 may provide received communications to one or more other components of the apparatus 1600. In some aspects, the reception component 1602 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1600. In some aspects, the reception component 1602 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the first UE described in connection with Fig. 2.

The transmission component 1604 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1606. In some aspects, one or more other components of the apparatus 1600 may generate communications and may provide the generated communications to the transmission component 1604 for transmission to the apparatus 1606. In some aspects, the transmission component 1604 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1606. In some aspects, the transmission component 1604 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the first UE described in connection with Fig. 2. In some aspects, the transmission component 1604 may be co-located with the reception component 1602 in one or more transceivers.

The configuration component 1608 may negotiate, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The calculation component 1610 may calculate the DFN based at least in part on the configuration. The reception component 1602 may wake up in the DFN, where the DFN is an active duration within the active time window.

The calculation component 1610 may calculate the active time window based at least in part on a length of the sidelink eDRX cycle. The reception component 1602 may receive information for the eDRX offset.

The number and arrangement of components shown in Fig. 16 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 16. Furthermore, two or more components shown in Fig. 16 may be implemented within a single component, or a single component shown in Fig. 16 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 16 may perform one or more functions described as being performed by another set of components shown in Fig. 16.

Fig. 17 is a diagram illustrating an example 1700 of a hardware implementation for an apparatus 1705 employing a processing system 1710, in accordance with the present disclosure. The apparatus 1705 may be a first UE or may be at (e.g., included in) a first UE.

The processing system 1710 may be implemented with a bus architecture, represented generally by the bus 1715. The bus 1715 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1710 and the overall design constraints. The bus 1715 links together various circuits including one or more processors and/or hardware components, represented by the processor (or processing circuitry) 1720, the illustrated components, and the computer-readable medium/memory (or memory circuitry) 1725. The processor 1720 may include multiple processors, such as processor 1720a, memory 1720b, and memory 1720c. The memory 1725 may include multiple memories, such as memory 1725a, memory 1725b, and memory 1725c. The bus 1715 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and/or power management circuits.

The processing system 1710 may be coupled to one or more transceivers 1730. A transceiver 1730 is coupled to one or more antennas 1735. The transceiver 1730 provides a means for communicating with various other apparatuses over a transmission medium. The transceiver 1730 receives a signal from the one or more antennas 1735, extracts information from the received signal, and provides the extracted information to the processing system 1710, specifically the reception component 1602. In addition, the transceiver 1730 receives information from the processing system 1710, specifically the transmission component 1604, and generates a signal to be applied to the one or more antennas 1735 based at least in part on the received information.

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

In some aspects, the processing system 1710 may be a component of the UE 120 and may include one or more memories, such as the memory 282, and/or may include one or more processors, such as at least one of the TX MIMO processor 266, the RX processor 258, and/or the controller/processor 280. In some aspects, the apparatus 1705 for wireless communication includes means for negotiating, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs; means for calculating the DFN based at least in part on the configuration; and means for waking up in the DFN, the DFN being an active duration within the active time window. The aforementioned means may be one or more of the aforementioned components of the apparatus 1600 and/or the processing system 1710 of the apparatus 1705 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1710 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.

Fig. 17 is provided as an example. Other examples may differ from what is described in connection with Fig. 17.

Fig. 18 is a diagram illustrating an example 1800 of an implementation of code and circuitry for an apparatus 1805, in accordance with the present disclosure. The circuity may include processing circuitry and memory circuitry. The apparatus 1805 may be a first UE, or a first UE may include the apparatus 1805.

As shown in Fig. 18, the apparatus 1805 may include circuitry for negotiating, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs (circuitry 1820) . For example, the circuitry 1820 may enable the apparatus 1805 to negotiate, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs.

As shown in Fig. 18, the apparatus 1805 may include, stored in computer-readable medium 1725, code for negotiating, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs (code 1825) . For example, the code 1825, when executed by processor 1720, may cause processor 1720 to cause transceiver 1730 to negotiate, with a second UE, a configuration associated with waking up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs.

As shown in Fig. 18, the apparatus 1805 may include circuitry for calculating the DFN based at least in part on the configuration (circuitry 1830) . For example, the circuitry 1830 may enable the apparatus 1805 to calculate the DFN based at least in part on the configuration.

As shown in Fig. 18, the apparatus 1805 may include, stored in computer-readable medium 1725, code for calculating the DFN based at least in part on the configuration (code 1835) . For example, the code 1835, when executed by processor 1720, may cause processor 1720 to calculate the DFN based at least in part on the configuration.

As shown in Fig. 18, the apparatus 1805 may include circuitry for waking up in the DFN, the DFN being an active duration within the active time window (circuitry 1840) . For example, the circuitry 1840 may enable the apparatus 1805 to wake up in the DFN, the DFN being an active duration within the active time window.

As shown in Fig. 18, the apparatus 1805 may include, stored in computer-readable medium 1725, code for waking up in the DFN, the DFN being an active duration within the active time window (code 1845) . For example, the code 1845, when executed by processor 1720, may cause processor 1720 to cause transceiver 1730 to wake up in the DFN, the DFN being an active duration within the active time window.

Fig. 18 is provided as an example. Other examples may differ from what is described in connection with Fig. 18.

Fig. 19 is a diagram of an example apparatus 1900 for wireless communication, in accordance with the present disclosure. The apparatus 1900 may be a network entity, or a network entity may include the apparatus 1900. In some aspects, the apparatus 1900 includes a reception component 1902 and a transmission component 1904, which may be in communication with one another (for example, via one or more buses and/or one or more other components) . As shown, the apparatus 1900 may communicate with another apparatus 1906 (such as a UE, a base station, or another wireless communication device) using the reception component 1902 and the transmission component 1904. As further shown, the apparatus 1900 may include the communication manager 150. The communication manager 150 may include a configuration component 1908, among other examples.

In some aspects, the apparatus 1900 may be configured to perform one or more operations described herein in connection with Figs. 1-13. Additionally, or alternatively, the apparatus 1900 may be configured to perform one or more processes described herein, such as process 1500 of Fig. 15. In some aspects, the apparatus 1900 and/or one or more components shown in Fig. 19 may include one or more components of the network entity described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 19 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The reception component 1902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1906. The reception component 1902 may provide received communications to one or more other components of the apparatus 1900. In some aspects, the reception component 1902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1900. In some aspects, the reception component 1902 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network entity described in connection with Fig. 2.

The transmission component 1904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1906. In some aspects, one or more other components of the apparatus 1900 may generate communications and may provide the generated communications to the transmission component 1904 for transmission to the apparatus 1906. In some aspects, the transmission component 1904 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1906. In some aspects, the transmission component 1904 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network entity described in connection with Fig. 2. In some aspects, the transmission component 1904 may be co-located with the reception component 1902 in one or more transceivers.

The configuration component 1908 may obtain one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs. The transmission component 1904 may transmit an indication of the one or more parameters to a second UE.

The transmission component 1904 may transmit information for an eDRX offset associated with starting a sidelink eDRX mode after a starting indication to start a sidelink eDRX mode. The transmission component 1904 may transmit information for a starting point of a sidelink eDRX mode.

The number and arrangement of components shown in Fig. 19 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 19. Furthermore, two or more components shown in Fig. 19 may be implemented within a single component, or a single component shown in Fig. 19 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 19 may perform one or more functions described as being performed by another set of components shown in Fig. 19.

Fig. 20 is a diagram illustrating an example 2000 of a hardware implementation for an apparatus 2005 employing a processing system 2010, in accordance with the present disclosure. The apparatus 2005 may be a network entity or may be at (e.g., included in) a network entity.

The processing system 2010 may be implemented with a bus architecture, represented generally by the bus 2015. The bus 2015 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 2010 and the overall design constraints. The bus 2015 links together various circuits including one or more processors and/or hardware components, represented by the processor (or processing circuitry) 2020, the illustrated components, and the computer-readable medium/memory (or memory circuitry) 2025. The processor 2020 may include multiple processors, such as processor 2020a, memory 2020b, and memory 2020c. The memory 2025 may include multiple memories, such as memory 2025a, memory 2025b, and memory 2025c. The bus 2015 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and/or power management circuits.

The processing system 2010 may be coupled to one or more transceivers 2030. A transceiver 2030 is coupled to one or more antennas 2035. The transceiver 2030 provides a means for communicating with various other apparatuses over a transmission medium. The transceiver 2030 receives a signal from the one or more antennas 2035, extracts information from the received signal, and provides the extracted information to the processing system 2010, specifically the reception component 1902. In addition, the transceiver 2030 receives information from the processing system 2010, specifically the transmission component 1904, and generates a signal to be applied to the one or more antennas 2035 based at least in part on the received information.

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

In some aspects, the processing system 2010 may be a component of the network node 110 and may include one or more memories, such as the memory 242, and/or may include one or more processors, such as at least one of the TX MIMO processor 230, the RX processor 238, and/or the controller/processor 240. In some aspects, the apparatus 2005 for wireless communication includes means for obtaining one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs; and means for transmitting an indication of the one or more parameters to a second UE. The aforementioned means may be one or more of the aforementioned components of the apparatus 1900 and/or the processing system 2010 of the apparatus 2005 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 2010 may include the TX MIMO processor 230, the receive processor 238, and/or the controller/processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and/or the controller/processor 240 configured to perform the functions and/or operations recited herein.

Fig. 20 is provided as an example. Other examples may differ from what is described in connection with Fig. 20.

Fig. 21 is a diagram illustrating an example 2100 of an implementation of code and circuitry for an apparatus 2105, in accordance with the present disclosure. The apparatus 2105 may be a network entity, or a network entity may include the apparatus 2105.

As shown in Fig. 21, the apparatus 2105 may include circuitry for obtaining one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs (circuitry 2120) . For example, the circuitry 2120 may enable the apparatus 2105 to obtain one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs.

As shown in Fig. 21, the apparatus 2105 may include, stored in computer-readable medium 2025, code for obtaining one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs (code 2125) . For example, the code 2125, when executed by processor 2020, may cause processor 2020 to cause transceiver 2030 to obtain one or more parameters of a configuration associated with configuring a first UE to wake up in a DFN in an active time window in a sidelink eDRX cycle including a set of H-DFNs.

As shown in Fig. 21, the apparatus 2105 may include circuitry for transmitting an indication of the one or more parameters to a second UE (circuitry 2130) . For example, the circuitry 2130 may enable the apparatus 2105 to transmit an indication of the one or more parameters to a second UE.

As shown in Fig. 21, the apparatus 2105 may include, stored in computer-readable medium 2025, code for transmitting an indication of the one or more parameters to a second UE (code 2135) . For example, the code 2135, when executed by processor 2020, may cause processor 2020 to cause transceiver 2030 to transmit an indication of the one or more parameters to a second UE.

Fig. 21 is provided as an example. Other examples may differ from what is described in connection with Fig. 21.

The following provides an overview of some Aspects of the present disclosure:

Aspect 1: A method of wireless communication performed at a first user equipment (UE) , comprising: negotiating, with a second UE, a configuration associated with waking up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ; calculating the DFN based at least in part on the configuration; and waking up in the DFN, where the DFN is an active duration within the active time window.

Aspect 2: The method of Aspect 1, wherein the configuration includes a length of the sidelink eDRX cycle.

Aspect 3: The method of Aspect 2, further comprising calculating the active time window based at least in part on a length of the sidelink eDRX cycle.

Aspect 4: The method of any of Aspects 1-3, wherein the configuration includes information for determining the active time window.

Aspect 5: The method of Aspect 4, wherein the information for the active time window includes a UE identifier (ID) , and wherein the method includes calculating a start of the active time window based at least in part on the UE ID.

Aspect 6: The method of Aspect 4, wherein the information for the active time window includes a hash of a UE identifier (ID) , and wherein the method includes calculating a start of the active time window based at least in part on the hash of a UE ID.

Aspect 7: The method of any of Aspects 1-6, wherein negotiating the configuration includes: selecting one or more parameters for the sidelink eDRX cycle; transmitting an indication of the one or more parameters; and receiving a response to the indication.

Aspect 8: The method of Aspect 7, wherein negotiating the configuration includes receiving assistance information, and wherein selecting the one or more parameters includes selecting the one or more parameters based at least in part on the assistance information.

Aspect 9: The method of Aspect 8, wherein the assistance information includes a UE identifier (ID) .

Aspect 10: The method of Aspect 8, wherein the assistance information includes a hash of the UE identifier (ID) .

Aspect 11: The method of Aspect 8, wherein the assistance information includes a length of the sidelink eDRX cycle.

Aspect 12: The method of Aspect 8, wherein the assistance information includes information for the active time window.

Aspect 13: The method of any of Aspects 1-12, wherein negotiating the configuration includes: receiving an indication of one or more parameters for the sidelink eDRX cycle; and transmitting a response to the indication.

Aspect 14: The method of any of Aspects 1-13, wherein negotiating the configuration includes transmitting assistance information including one or more of a UE identifier (ID) , a hash of the UE ID, a length of the sidelink eDRX cycle, or information for the active time window.

Aspect 15: The method of any of Aspects 1-14, wherein the active time window is based at least in part on an offset from a Uu active time window.

Aspect 16: The method of any of Aspects 1-15, wherein the configuration indicates a starting point for the sidelink eDRX cycle.

Aspect 17: The method of Aspect 16, wherein the starting point is an eDRX offset after a starting indication to start a sidelink eDRX mode.

Aspect 18: The method of Aspect 17, further comprising receiving information for the eDRX offset.

Aspect 19: The method of Aspect 16, wherein the first UE is a remote UE that is configured to communicate with a network entity via the second UE.

Aspect 20: The method of Aspect 16, wherein the first UE is a relay UE that is configured to relay communications between the second UE and a network entity.

Aspect 21: A method of wireless communication performed at a network entity, comprising: obtaining one or more parameters of a configuration associated with configuring a first user equipment (UE) to wake up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ; and transmitting an indication of the one or more parameters to a second UE.

Aspect 22: The method of Aspect 21, further comprising transmitting information for an eDRX offset associated with starting a sidelink eDRX mode after a starting indication to start a sidelink eDRX mode.

Aspect 23: The method of any of Aspects 21-22, further comprising transmitting information for a starting point of a sidelink eDRX mode.

Aspect 24: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-23.

Aspect 25: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-23.

Aspect 26: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-23.

Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-23.

Aspect 28: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-23.

Aspect 29: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-23.

Aspect 30: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-23.

Aspect 31: An apparatus for wireless communication at a first user equipment (UE) , comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the network entity to perform the method of one or more of Aspects 1-20.

Aspect 32: An apparatus for wireless communication at a network entity, comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the network entity to perform the method of one or more of Aspects 21-23.

Aspect 33: An apparatus for wireless communication at a first user equipment (UE) , comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to cause the first UE to: negotiate, with a second UE, a configuration associated with waking up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ; calculate the DFN based at least in part on the configuration; and wake up in the DFN, the DFN being an active duration within the active time window.

Aspect 34: The apparatus of Aspect 33, wherein the one or more processors are configured, individually or collectively, to cause the first UE to: negotiate, with a second UE, a configuration associated with waking up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ; calculate the DFN based at least in part on the configuration; and wake up in the DFN, the DFN being an active duration within the active time window.

Aspect 35: An apparatus for wireless communication at a network entity, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to cause the network entity to: obtain one or more parameters of a configuration associated with configuring a first user equipment (UE) to wake up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ; and transmit an indication of the one or more parameters to a second UE.

Aspect 36: The apparatus of Aspect 35, wherein the one or more processors are configured, individually or collectively, to cause the network entity to: obtain one or more parameters of a configuration associated with configuring a first user equipment (UE) to wake up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ; and transmit an indication of the one or more parameters to a second UE.

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 the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

The hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single-or multi-chip processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some aspects, particular processes and methods may be performed by circuitry that is specific to a given function.

As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

Even though particular combinations of features are recited 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 may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. 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, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a +a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c) .

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more. ” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B) . Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of” ) .

Claims

An apparatus for wireless communication at a first user equipment (UE) , comprising:

one or more memories; and

one or more processors, coupled to the one or more memories, configured to cause the first UE to:

negotiate, with a second UE, a configuration associated with waking up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ;

calculate the DFN based at least in part on the configuration; and

wake up in the DFN, wherein the DFN is an active duration within the active time window.
The apparatus of claim 1, wherein the configuration includes a length of the sidelink eDRX cycle.
The apparatus of claim 2, wherein the one or more processors are further configured to cause the first UE to calculate the active time window based at least in part on a length of the sidelink eDRX cycle.
The apparatus of claim 1, wherein the configuration includes information for determining the active time window.
The apparatus of claim 4, wherein the information for the active time window includes a UE identifier (ID) or a hash of the UE ID, and wherein the one or more processors are configured to cause the first UE to calculate a start of the active time window based at least in part on the UE ID or the hash of a UE ID.
The apparatus of claim 1, wherein to negotiate the configuration, the one or more processors are configured to cause the first UE to:

select one or more parameters for the sidelink eDRX cycle;

transmit an indication of the one or more parameters; and

receive a response to the indication.
The apparatus of claim 6, wherein to negotiate the configuration, the one or more processors are configured to cause the first UE to receive assistance information, and wherein to select the one or more parameters, the one or more processors are configured to cause the first UE to select the one or more parameters based at least in part on the assistance information.
The apparatus of claim 7, wherein the assistance information includes one or more of a UE identifier (ID) , a hash of the UE ID, a length of the sidelink eDRX cycle, or information for the active time window.
The apparatus of claim 1, wherein to negotiate the configuration, the one or more processors are configured to cause the first UE to:

receive an indication of one or more parameters for the sidelink eDRX cycle; and

transmit a response to the indication.
The apparatus of claim 1, wherein to negotiate the configuration, the one or more processors are configured to cause the first UE to transmit assistance information including one or more of a UE identifier (ID) , a hash of the UE ID, a length of the sidelink eDRX cycle, or information for the active time window.
The apparatus of claim 1, wherein the active time window is based at least in part on an offset from a Uu active time window.
The apparatus of claim 1, wherein the configuration indicates a starting point for the sidelink eDRX cycle.
The apparatus of claim 12, wherein the starting point is an eDRX offset after a starting indication to start a sidelink eDRX mode.
The apparatus of claim 13, wherein the one or more processors are further configured to cause the first UE to receive information for the eDRX offset.
The apparatus of claim 12, wherein the first UE is a remote UE that is configured to communicate with a network entity via the second UE.
The apparatus of claim 12, wherein the first UE is a relay UE that is configured to relay communications between the second UE and a network entity.
An apparatus for wireless communication at a network entity, comprising:

one or more memories; and

one or more processors, coupled to the one or more memories, configured to cause the network entity to:

obtain one or more parameters of a configuration associated with configuring a first user equipment (UE) to wake up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ; and

transmit an indication of the one or more parameters to a second UE.
The apparatus of claim 17, wherein the one or more processors are further configured to cause the network entity to transmit information for an eDRX offset associated with starting a sidelink eDRX mode after a starting indication to start a sidelink eDRX mode.
The apparatus of claim 17, wherein the one or more processors are further configured to cause the network entity to transmit information for a starting point of a sidelink eDRX mode.
A method of wireless communication performed at a first user equipment (UE) , comprising:

negotiating, with a second UE, a configuration associated with waking up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ;

calculating the DFN based at least in part on the configuration; and

waking up in the DFN, wherein the DFN is an active duration within the active time window.
The method of claim 20, wherein the configuration includes a length of the sidelink eDRX cycle.
The method of claim 21, further comprising calculating the active time window based at least in part on a length of the sidelink eDRX cycle.
The method of claim 20, wherein the configuration includes information for determining the active time window.
The method of claim 23, wherein the information for the active time window includes a UE identifier (ID) or a hash of the UE ID, and wherein the method includes calculating a start of the active time window based at least in part on the UE ID or the hash of a UE ID.
The method of claim 20, wherein negotiating the configuration includes:

selecting one or more parameters for the sidelink eDRX cycle;

transmitting an indication of the one or more parameters; and

receiving a response to the indication.
The method of claim 25, wherein negotiating the configuration includes receiving assistance information, and wherein selecting the one or more parameters includes selecting the one or more parameters based at least in part on the assistance information.
The method of claim 26, wherein the assistance information includes one or more of a UE identifier (ID) , a hash of the UE ID, a length of the sidelink eDRX cycle, or information for the active time window.
The method of claim 20, wherein negotiating the configuration includes:

receiving an indication of one or more parameters for the sidelink eDRX cycle; and

transmitting a response to the indication.
The method of claim 20, wherein negotiating the configuration includes transmitting assistance information including one or more of a UE identifier (ID) , a hash of the UE ID, a length of the sidelink eDRX cycle, or information for the active time window.
A method of wireless communication performed at a network entity, comprising:

obtaining one or more parameters of a configuration associated with configuring a first user equipment (UE) to wake up in a direct frame number (DFN) in an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle including a set of hyper DFNs (H-DFNs) ; and

transmitting an indication of the one or more parameters to a second UE.