Configuration negotiation for sidelink extended discontinuous reception

Abstract

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

Description

Background Technology

[0001] All aspects of this disclosure relate to wireless communication in general, and to techniques and apparatus for sidelink extended discontinuous reception.

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0004] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0005] Some aspects described herein relate to a method for wireless communication performed at a first user equipment (UE). The method may include negotiating with a second UE a configuration associated with wake-up within a DFN in an active time window comprising a set of super direct frame numbers (DFNs) (H-DFNs). The method may include calculating the DFN based at least in part on this configuration. The method may include wake-up within a DFN, where the DFN is the activity duration within the active time window.

[0006] Some aspects described herein relate to a method for performing wireless communication at a network entity. The method may include obtaining one or more parameters associated with a configuration for waking up in a DFN within an active time window of a sidelink eDRX cycle comprising a set of H-DFNs. The method may include sending an indication of one or more parameters to a second UE.

[0007] 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 wake-up in a DFN within an active time window comprising a set of H-DFNs in a sidelink eDRX cycle. The one or more processors may be configured to cause the first UE to calculate the DFN at least in part based on the configuration. The one or more processors may be configured to cause the first UE to wake up in a DFN, where the DFN is the activity duration within the active time window.

[0008] 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 associated with a configuration for waking up in a DFN within an active time window of a sidelink eDRX cycle comprising a set of H-DFNs. The one or more processors may be configured to cause the network entity to send indications of the one or more parameters to a second UE.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first UE. When executed by one or more processors of the first UE, the set of instructions enables the first UE to negotiate with a second UE a configuration associated with wake-up in a DFN within an active time window comprising a set of H-DFNs in a side-link eDRX cycle. When executed by one or more processors of the first UE, the set of instructions enables the first UE to calculate the DFN at least in part based on the configuration. When executed by one or more processors of the first UE, the set of instructions enables the first UE to wake up in a DFN, where the DFN is the activity duration within the active time window.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. When executed by one or more processors of the network entity, the set of instructions enables the network entity to obtain one or more parameters of a configuration associated with waking up in a DFN within an active time window of a sidelink eDRX cycle comprising a set of H-DFNs. When executed by one or more processors of the network entity, the set of instructions enables the network entity to send instructions on one or more parameters to a second UE.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for negotiating with a second UE a configuration associated with wake-up in a DFN within an active time window comprising a set of H-DFNs in a side-link eDRX cycle. The apparatus may include components for calculating the DFN based at least in part on the configuration. The apparatus may include components for wake-up in a DFN, where the DFN is the activity duration within the active time window.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for obtaining one or more parameters associated with a configuration for waking up in a DFN within an active time window of a sidelink eDRX cycle comprising a set of H-DFNs. The apparatus may include components for transmitting an indication of one or more parameters to a second UE.

[0013] The entirety of the terms includes methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0014] The features and technical advantages of the examples according to this disclosure have been summarized rather broadly above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0015] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the 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). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0016] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

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

[0018] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0020] Figure 4 This is a diagram illustrating an example of discontinuous reception (DRX) according to this disclosure.

[0021] Figure 5 This is a diagram illustrating an example of sidelink communication according to this disclosure.

[0022] Figure 6 This is a diagram illustrating examples of sidelink communication and access link communication according to this disclosure.

[0023] Figure 7 This is a diagram illustrating an example of a next-generation radio access network architecture according to the present disclosure.

[0024] Figure 8A and Figure 8B This is a diagram illustrating an example of a control plane protocol stack for a side link according to this disclosure.

[0025] Figure 9 This is a diagram illustrating an example of a control plane protocol stack for UE-to-network (U2N) relay according to this disclosure.

[0026] Figure 10 This is a diagram illustrating an example of a sidelink extended DRX (eDRX) according to this disclosure.

[0027] Figures 11A to 11C This is a diagram illustrating an example of the System Frame Number (SFN) - Direct Frame Number (DFN) offset according to this disclosure.

[0028] Figure 12 This is a diagram illustrating an example of an active time window in a sidelink eDRX loop according to this disclosure.

[0029] Figure 13 This is a diagram illustrating an example of a side-link eDRX configuration associated with this disclosure.

[0030] Figure 14 This is a diagram illustrating an example process performed, for example, at a first UE or a device of the first UE, according to this disclosure.

[0031] Figure 15 This is a diagram illustrating an example process performed, for example, at a network entity or a device of a network entity, according to the present disclosure.

[0032] Figure 16 This is a diagram of an example device for wireless communication according to the present disclosure.

[0033] Figure 17This is a diagram illustrating an example of a hardware implementation of a device for employing a processing system according to the present disclosure.

[0034] Figure 18 The diagram illustrates an example of the implementation of code and circuitry for a device according to this disclosure.

[0035] Figure 19 This is a diagram of an example device for wireless communication according to the present disclosure.

[0036] Figure 20 This is a diagram illustrating an example of a hardware implementation of a device for employing a processing system according to the present disclosure.

[0037] Figure 21 The diagram illustrates an example of the implementation of code and circuitry for a device according to this disclosure. Detailed Implementation

[0038] According to one or more examples, a user equipment (UE) such as an extended reality (XR) device may use discontinuous reception (DRX) mode to save power. A UE in DRX mode can transition between a sleep state for power saving 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 sleep mode may shut down its radio components and one or more other components or functions of the UE. Shutting down or disconnecting the radio components may include removing power from the radio components, causing the radio components to operate incompletely or not at full power. In one or more examples, a UE may wake up to an active state by turning on its radio components and one or more other components or functions of the UE. Other components may include, for example, buffers, timers, memory, and / or a processor. UE functions may include, for example, communication, application operation, and / or configuration. Turning on or off the radio components may include providing power to the radio components, causing the radio components to operate fully (e.g., all applications or functions have sufficient power to perform) and / or operate at full power. As used herein, the active state for data transmission and reception may be referred to as the DRX “on duration” (or “on-duration”). A DRX cycle can begin at the beginning of an on-duration period and end at the beginning of the next on-duration period. In some respects, a DRX cycle can be referred to as a "DRX long cycle".

[0039] In some examples, the UE can use wake-up conditions to determine which on-time of the DRX cycle to wake up for. The wake-up condition may be based at least in part on the subframe number of a subframe, which may be a subframe of a frame identified by a System Frame Number (SFN) in one or more aspects. An SFN may be part of a super SFN (H-SFN) of multiple SFNs. An H-SFN may include 1024 SFNs in a loop (the H-SFN restarts and increments after 1024 SFNs). An extended DRX (eDRX) cycle may include multiple H-SFNs. The UE may wake up in each eDRX cycle to monitor paging. eDRX cycles for the Uu interface may be introduced in a UE inactive (idle) state, with a maximum eDRX cycle of 3 hours. The UE may wake up in each eDRX cycle or at most every 3 hours to monitor paging opportunities (PO).

[0040] In some examples, a sidelink UE may support sidelink DRX (SL DRX). A direct frame number (DFN) can be used in sidelink communication. A DFN is similar to an SFN used in uplink and downlink communication. A DFN can be 10 bits and 10 ms. A super DFN (H-DFN) can comprise 1024 DFNs (10.24 seconds). The H-DFN can increment as the DFN wraps around (after 1024 DFNs). An H-DFN can be equivalent to a superframe or H-SFN used for DRX. In connected-mode sidelink DRX, the UE can maintain a sidelink connection during DRX cycles.

[0041] In some examples, two peer UEs can calculate the wake-up time for sidelink communication. The wake-up time can be a selected DFN. UEs can derive the DFN to wake up in two ways: 1) by deriving the DFN from Global Navigation Satellite System (GNSS) timing; or 2) by receiving the DFN from Sidelink Synchronization Signal (SLSS) signaling. Requiring UEs to monitor GNSS signals consumes power. In some cases, UEs can obtain the DFN from SLSS signaling. The two UEs can synchronize their times to enter sleep mode, and then each UE can rely on its internal clock to calculate the wake-up time. That is, the UE does not necessarily need to rely on monitoring GNSS timing.

[0042] In some examples, UEs can be enabled to use sidelinks in two scenarios: direct sidelink (non-relay) communication or UE-to-network (U2N) relay. Direct sidelink communication involves communication between two UEs without a relay UE to a network entity. U2N relay involves a remote UE and a relay UE, with the relay UE relaying communication between the remote UE and the network entity.

[0043] In scenarios with direct sidelink communication on the sidelink interface, the UE can be configured for sidelink DRX, where the active time can be calculated based on the DFN. If the active time is calculated using the DFN, there are 1024 DFNs in the H-DFN, and therefore the maximum sidelink DRX cycle is 10.24 seconds. As an example, for direct sidelink communication, the two UEs can be RedCap UEs or Internet of Things (IoT) devices, and both UEs can attempt to conserve power. However, the maximum 10.24 seconds of the DRX cycle may not be sufficient for the UE to maximize power savings. The UE can only conserve power during the inactive period of the DRX cycle, and therefore the UE can conserve power for up to a maximum of 5.12 seconds in the H-DFN. Without a comparable eDRX for the sidelink (where the UE can sleep for a longer duration than allowed by the connected sidelink DRX, such as up to 3 hours or more), the UE may not be able to conserve as much power using the sidelink interface as it could using the Uu interface.

[0044] In scenarios with U2N relays, the remote UE wakes up to monitor the PO (Position Target) on the Uu interface for each DRX cycle. The relay UE also monitors the remote UE's PO. In sidelink DRX, the activity time is calculated based on the DFN (Dedicated Function Number), and the maximum DRX cycle length is 10.24 seconds if the DFN is used to calculate the activity time. In the inactive (idle) state, the remote UE has a connection with the relay UE, and the relay UE forwards received paging messages to the remote UE (e.g., the remote UE cannot receive paging messages because it is outside the coverage of a network entity). As described above for the direct sidelink communication scenario, if the remote UE is inactive and there is no eDRX on the sidelink, the remote UE must monitor the sidelink for each DRX cycle. That is, in one example, the remote UE and relay UE may not be able to sleep for longer than allowed by the connected-mode sidelink DRX (e.g., up to 3 hours or more), but can wake up for each DRX cycle. The remote UE and relay UE can conserve power only during the inactive period of the DRX cycle. Each DRX cycle of wake-up consumes power from both the remote UE and the relay UE.

[0045] Based on the various aspects described herein, sidelink UEs can save more power in both direct sidelink communication scenarios and U2N scenarios by introducing eDRX for sidelink. Sidelink eDRX can include a set of H-DFNs. A set of H-DFNs can include one or more H-DFNs. The UE (e.g., a sidelink UE, a remote UE, a relay UE) can calculate the DFNs to wake up during its period, and the DFNs can be within a sidelink eDRX cycle. The DFNs can be within an Active Time Window (ATW) in the sidelink eDRX cycle. Using the Active Time Window with the sidelink eDRX cycle allows the UE to sleep for longer periods and save more power because the sidelink eDRX cycle is a large cycle (e.g., up to 3 hours or more). Therefore, the UE's sleep time is not limited to half of the 10.24ms H-DFN. Conversely, the UE's sleep time (outside the active time window in the eDRX cycle) can be longer than the sleep time in the connected-mode sidelink DRX, or multiple inactive DFNs can be included in the sidelink eDRX, whose combined sleep time is more than half that of an H-DFN. Power savings can assist battery-constrained devices, such as RedCap UEs.

[0046] In some respects, UEs can negotiate configurations for sidelink eDRX cyclics. For example, the sending UE (TXUE) can determine sidelink eDRX cyclic parameters and transmit these parameters to the receiving UE (RXUE) using sidelink messages (e.g., PC5-RRC messages or sidelink MACCE). Additionally or alternatively, the RX UE can transmit sidelink eDRX auxiliary information to the TX UE. Auxiliary information may include UE identifiers (IDs) (e.g., 5G Serving Temporary Mobile Subscriber Identity (5G-S-TMSI), Subscription Hidden Identifier (SUCI), hash of the UE ID (UE_ID_H), or UE L2 ID), indications of sidelink eDRX cyclics (optionally), and / or indications of active time windows. That is, if the TX is using the TX UE ID to calculate the active time, the TX UE can transmit the TX UE ID (5G-S-TMSI, SUCI, UE_ID_H, UE L2 ID) to the RX UE. In some respects, the TX UE can transmit eDRX parameters (eDRX cycle, active time window) to its serving gNB, and the serving gNB can provide sidelink eDRX parameters to the TX UE. In some respects, sidelink eDRX parameters can be within an existing sidelink configuration information element (IE) or outside an existing sidelink configuration IE.

[0047] By negotiating the sidelink eDRX cyclic configuration, the UE can align itself when it wakes up within the active time window of the sidelink eDRX cycle. This prevents the UE from missing communications and saves power.

[0048] In some aspects, parameters may also include indications of the start point and / or eDRX offset of the sidelink eDRX cycle (e.g., the time after the indication of entering sidelink eDRX mode, SFN-DFN offset). By providing the start point or eDRX offset, the UE can coordinate the timing of the sidelink eDRX with the timing of the Uu eDRX. Therefore, the UE can wake up simultaneously within each eDRX cycle, and thus wake up less frequently, saving power.

[0049] In some aspects, the sidelink eDRX cyclic mode may involve calculating the active time window within the sidelink eDRX cycle. The calculation may include information for the active time window, such as the UE ID or a hash of the UE ID. The UE may calculate the 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, this information may include a start offset from the start of the sidelink eDRX cycle, and the UE may use this start offset to calculate the active window. In some aspects, this information may include an offset between the active time window of the Uu eDRX cycle and the active time window of the sidelink eDRX cycle. Two UEs may share this information to align their active time windows. By aligning their active time windows, UEs can communicate with each other during active times and conserve power during inactive times.

[0050] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functions, or structures and functions other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0051] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0052] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0053] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., LTE) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that an 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, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that 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)).

[0054] In some examples, network node 110 is a network node (such as RU) that communicates with UE 120 via a radio access link, or includes network nodes (such as RU) that communicate with the UE via a radio access link. In some examples, network node 110 is a network node (such as DU) that communicates with other network nodes 110 via a fronthaul or midhaul link, or includes network nodes (such as DU) that communicate with such other network nodes via a fronthaul or midhaul link. In some examples, network node 110 is a network node (such as CU) that communicates with other network nodes 110 via a midhaul link or with the core network via a backhaul link, or includes network nodes (such as CU) that communicate with such other network nodes via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, NR base stations, LTE base stations, Node B, eNB (e.g., in 4G), gNB (e.g., in 5G), access points, transmit / receive points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 may interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0055] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context of terminology use, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0056] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed 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, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "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 can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device may include more than one base station.

[0057] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit data to downstream nodes (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions to other UE 120s. Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, repeater, etc.

[0058] Wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0059] Network controller 130 may be coupled to or communicate with a group of network nodes 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

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

[0061] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with network nodes, 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 customer premises equipment. UEs 120 may be housed within a housing containing components such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0063] 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 network node 110 as an intermediary device to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110. In some examples, UE 120a and UE 120e may communicate directly as part of direct sidelink communication. In some examples, UE 120a can act as a relay UE, UE 120e can act as a remote UE, and network node 110a can be a next-generation (NG) RAN network node as part of a UE-to-network (U2N) relay.

[0064] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0065] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, 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 the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

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

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

[0068] In some aspects, network entities (e.g., 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 associated with a configuration for activating a first UE in an active time window of a sidelink eDRX cycle that includes a set of H-DFNs. The communication manager 150 may send instructions for one or more parameters to a second UE. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0069] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0070] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in a wireless network 100 according to this disclosure. Network node 110 may be equipped with a set of antennas 234a to 234t, such as... T One antenna ( T ≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R One antenna ( R ≥1). Network node 110 of Example 200 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component that facilitates communication with UE 120 or another network node. Some network node 110 may not include radio frequency components that facilitate direct communication with UE 120, such as one or more CUs or one or more DUs.

[0071] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can select one or more modulation and decoding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 can process (e.g., encode and modulate) the data for UE 120, at least in part, based on the MCS selected for UE 120, and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., 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. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can transmit a set of output symbol streams (e.g., T Each output symbol stream is provided to a corresponding set of modems 232 (e.g., ...). T Each modem 232a to 232t may be used to process a corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t may be used via a corresponding set of antennas 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., ...). T (One downlink signal).

[0072] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can transmit a set of received signals (e.g., R The received signals are provided to a group of modems 254 (e.g., RA modem 254 (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator component to condition the received signal (e.g., filter, amplify, down-convert, and / or digitize) to obtain an input sample. Each modem 254 may use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

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

[0075] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. This transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). Figures 4 to 21 ( ) any aspect of the method described in the method.

[0076] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232 (shown as DEMOD)), detected by MIMO detector 236, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute this document (e.g., reference). Figures 4 to 21 ( ) any aspect of the method described in the method.

[0077] As described in more detail elsewhere in this document, the controller / processor of the network entity (e.g., controller / processor 240 of network node 110), the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more techniques associated with negotiating the configuration used for sidelink eDRX round-robin. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 14 Process 1400 Figure 15 The operation of process 1500 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, these one or more instructions may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation and / or interpretation). Figure 14 Process 1400 Figure 15 The operation of process 1500 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

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

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

[0080] In some respects, a single processor can perform all the functions described as being performed by that one or more processors. In other respects, the one or more processors can jointly perform a set of functions. For example, a first group(s) of the one or more processors can perform a first function described as being performed by that one or more processors, and a second group(s) of the one or more processors can perform a second function described as being performed by that one or more processors. The first group and the second group of processors may be the same group of processors or may be different groups of processors. The reference to "one or more processors" should be understood as referring to a combination of functions. Figure 2 Any one or more processors described. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in conjunction with... Figure 2 The memory described. For example, a function described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0081] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0082] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0083] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0084] Aggregated base stations (e.g., aggregated network nodes) can 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 cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the 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 across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0085] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented by two or more units across various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. The various units of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0086] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as 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). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0087] Each of these units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO frame 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to one or more communication interfaces of the respective unit, may be configured to communicate with one or more units in other units via transmission media. In some examples, each unit may include a wired interface and a wireless interface configured to receive signals via a wired transmission media or transmit signals to one or more units in other units, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission media or transmit signals to one or more units in other units, or both.

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

[0089] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 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, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0090] Each RU 340 can implement lower-layer functionality. In some deployments, the RU 340 controlled by the DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In such architectures, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0091] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with 4G RAN hardware aspects such as the Open eNB (O-eNB) 311 via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0092] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0093] 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 an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or 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 in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0094] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0095] Figure 4 This is a diagram illustrating Example 400 of the DRX according to this disclosure. For example... Figure 4 As shown, Example 400 includes a UE 120 communicating with a network entity (e.g., a network node (NN) 110). In some examples, the UE 120 may be in a connected state with the network node 110 (e.g., an RRC connected state).

[0096] In one or more examples, a UE can use DRX mode to conserve power. A UE in DRX mode can transition between a sleep state for power saving and an active state for data transmission and reception. A DRX cycle can include an active state duration and an inactive state duration. In one or more examples, a UE in sleep mode can shut down its radio components and one or more other components or functions of the UE. Shutting down or disconnecting the radio components can include removing power from the radio components, causing them to operate incompletely or not at full power. In one or more examples, a UE can wake up to an active state by turning on its radio components and one or more other components or functions of the UE. Other components can include, for example, buffers, timers, memory, and / or a processor. UE functions can include, for example, communication, application operation, and / or configuration. Turning on or off the radio components can include providing power to the radio components, causing them to operate fully (e.g., all applications or functions have sufficient power to perform) and / or operate at full power. As used herein, the active state for data transmission and reception can be referred to as a DRX “on duration” (or “on-duration”). A DRX cycle can begin at the beginning of an on-duration and end at the beginning of the next on-duration. In some respects, a DRX cycle can be called a "DRX long cycle". Each DRX cycle can correspond to a DRX on-duration timer (the length of the on-duration duration) and a DRX inactivity timer (how long after new data is received before the UE goes to sleep).

[0097] In some examples, the UE may use wake-up conditions to determine when to wake up. Wake-up conditions may be based at least in part on the subframe number of a subframe, which may be a subframe of a frame identified by an SFN in one or more respects.

[0098] As shown in Example 400, network node 110 may send DRX configuration to UE 120. This configuration may indicate an inactivity period 405 for DRX cycle 410. This configuration may indicate the start time (e.g., time offset), duration, length, and / or periodicity of the inactivity period 405. It is expected that UE 120 will not monitor or receive specific channels or signals during inactivity period 405. In this way, UE 120 may enter a sleep state during inactivity period 405. Network node 110 may refrain from transmitting during UE 120's inactivity period 405. Downlink channels or signals restricted during inactivity time 405 may include periodic and / or semi-persistent channel state information (CSI) reference signals (CSI-RS) (e.g., including tracking reference signals (TRS)), positioning reference signals (PRS), physical downlink control channel (PDCCH) communications scrambled with UE-specific radio network temporary identifiers (RNTI), PDCCHs in the type 3 common search space (CSS) (e.g., group common PDCCH), and / or semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) communications, etc. Physical channel or signal restrictions applicable to inactivity time 405 may not apply to activity time 415.

[0099] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0100] Figure 5 This is a diagram illustrating example 500 of sidelink communication according to this disclosure.

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

[0102] like Figure 5 As further shown, 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 can be used to convey control information, similar to the PDCCH and / or Physical Uplink Control Channel (PUCCH) used for cellular communication with network node 110 via an access link or access channel. The PSSCH 520 can be used to convey data, similar to the PDSCH and / or Physical Uplink Shared Channel (PUSCH) used for cellular communication with network node 110 via an access link or access channel. For example, the PSCCH 515 may carry sidelink control information (SCI) 530, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or spatial resources), wherein a transport block (TB) 535 may be carried on the PSSCH 520. The TB 535 may include data. PSFCH 525 can be used to convey sidelink feedback 540, such as Hybrid Automatic Repeat Request (HARQ) feedback (e.g., Acknowledgment or Negative Acknowledgment (ACK / NACK) information), Transmit Power Control (TPC), and / or Schedule Request (SR).

[0103] Although shown on PSCCH 515, SCI 530 may include multiple communications at different levels, such as Level 1 SCI (SCI-1) and Level 2 SCI (SCI-2) in some respects. SCI-1 may be transmitted on PSCCH 515. SCI-2 may be transmitted on PSSCH 520. SCI-1 may include, for example, indications of one or more resources on PSSCH 520 (e.g., time resources, frequency resources, and / or spatial resources), information for decoding sidelink communications on PSSCH, Quality of Service (QoS) priority values, resource reservation periods, PSSCH DMRS modes, SCI format for SCI-2, beta offset for SCI-2, number of PSSCH DMRS ports, and / or MCS. SCI-2 may include information associated with data transmission on PSSCH 520, such as HARQ process ID, New Data Indicator (NDI), source identifier, destination identifier, and / or CSI report triggering.

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

[0105] In some aspects, UE 505 may operate using a sidelink transmission mode (e.g., mode 1), where resource selection and / or scheduling is performed by network node 110 (e.g., a base station, CU, or DU). For example, UE 505 may receive permission from network node 110 (e.g., in downlink control information (DCI) or in RRC messages, such as permission for configuration) for sidelink channel access and / or scheduling (e.g., directly or via one or more network nodes). In some aspects, UE 505 may operate using a transmission mode (e.g., mode 2), where resource selection and / or scheduling is performed by UE 505 (e.g., not by network node 110). In some aspects, UE 505 may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, UE 505 can measure received RSSI parameters (e.g., sidelink-RSSI (S-RSSI) parameters) associated with various sidelink channels, can measure RSRP parameters (e.g., PSSCH-RSRP parameters) associated with various sidelink channels, and / or can measure RSRQ parameters (e.g., PSSCH-RSRQ parameters) associated with various sidelink channels, and can select the channel for transmitting sidelink communication based at least in part on the measurements.

[0106] Alternatively or additionally, UE 505 may use SCI 530 received in PSCCH 515 to perform resource selection and / or scheduling, which may indicate the occupied resources and / or channel parameters. Alternatively or additionally, UE 505 may perform resource selection and / or scheduling by determining the Channel Busy Rate (CBR) associated with various sidelink channels, which may be used for rate control (e.g., by indicating the maximum number of resource blocks available to UE 505 for a particular set of subframes).

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

[0108] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The descriptions are different.

[0109] Figure 6 This is a diagram illustrating example 600 of sidelink communication and access link communication according to this disclosure.

[0110] like Figure 6 As shown, the transmitter (Tx) / receiver (Rx) UE 605 and the Rx / Tx UE 610 can communicate with each other via a side link, as described above. Figure 5 As described herein. Further, in some sidelink modes, network node 110 may communicate with Tx / Rx UE 605, such as via a first access link (e.g., directly or via one or more network nodes). In some examples, Tx / Rx UE 605 may be a relay UE relaying communication between Rx / Tx UE 610 (remote UE). Tx / Rx UE 605 and / or Rx / Tx UE 610 may communicate with one or more UEs described elsewhere herein (such as...). Figure 1 This corresponds to UE 120. Therefore, a direct link between UEs 120 (e.g., via the PC5 interface) can be referred to as a side link, and a direct link between network 110 and UE 120 (e.g., via the Uu interface) can be referred to as an access link. Side link communication can be sent via the side link, and access link communication can be sent via the access link. Access link communication can be downlink communication (from network node 110 to UE 120) or uplink communication (from UE 120 to network node 110).

[0111] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The descriptions are different.

[0112] Figure 7 This is a diagram illustrating Example 700 of a Next Generation Radio Access Network (NG-RAN) architecture according to this disclosure.

[0113] Example 700 illustrates network nodes in NG-RAN, such as gNB 705 and NG-eNB 710. These network nodes may have Uu links to UE 715 and UE 720 within NG-RAN coverage. UE 715 and UE 720 may communicate via a sidelink (e.g., a PC5 interface). UE 720 may be outside NG-RAN coverage but may communicate with UE 715 and UE 720 via a sidelink. UE 715 and / or UE 720 may operate as a relay UE to UE 720 (a remote UE), as part of a U2N relay. The U2N relay can be single-hop or multi-hop. Transmission and reception via a PC5 interface are supported when the UE is within NG-RAN coverage, regardless of its RRC state, and when the UE is outside NG-RAN coverage.

[0114] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0115] Figure 8A and Figure 8B This is a diagram illustrating an example of a control plane protocol stack for a side link according to this disclosure.

[0116] Figure 8A The Access Layer (AS) protocol stack 802 of the control plane for the sidelink control channel of RRC in the PC5 interface is shown. The protocol stack between UE 715 and UE 720 may include the corresponding PHY layer, MAC layer, RLC layer, PDCP layer, and RRC layer. The control plane function handles the transmission of control information between the UEs. Generally, if the first layer is further away from the PHY layer than the second layer, the first layer is referred to as being higher than the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layer may be referred to as being higher than the PHY layer and lower than the RRC layer. Figure 8A The Application (APP) layer, not shown, may be higher than the RRC / PDCP / RLC / MAC layers. 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), although the description herein mentions that the layer itself handles these services and functions.

[0117] The RRC layer handles communications related to the configuration and operation of UE 120, such as establishment, maintenance, security, and detection and recovery of radio link failures. The RRC layer is often referred to as Layer 3 (L3).

[0118] The PDCP layer, RLC layer, and MAC layer can be collectively referred to as Layer 2 (L2). Therefore, in some cases, the PDCP, RLC, and MAC layers are referred to as sub-layers of Layer 2.

[0119] The PDCP layer can provide data in the form of PDCP Protocol Data Units (PDUs) to the RLC layer via the RLC channel. The RLC layer can handle the transmission of upper-layer PDUs to the MAC layer and / or PHY layer, sequence numbering independent of PDCP sequence numbering, error correction via Automatic Repeat Request (ARQ), segmentation and resegmentation, reassembly of Service Data Units (SDUs), RLC SDU discarding, and RLC reconstruction.

[0120] The RLC layer can provide the MAC layer with data mapped to logical channels. 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 MAC SDUs belonging to one or different logical channels into / from the TB delivered to / from the physical layer on the transport channel, demultiplexing the MAC SDU from the TB, scheduling information reporting, error correction via HARQ, priority handling between UEs via dynamic scheduling, priority handling between logical channels of a UE via logical channel prioritization, and padding.

[0121] The MAC layer can encapsulate data from logical channels into data blocks (TBs) and can provide TBs to the PHY layer on one or more transport channels. The PHY layer can handle various operations related to the transmission of data signals, such as combining... Figure 2 In more detail, the PHY layer is often referred to as layer 1 (L1).

[0122] On the receiving side, the operation can be similar to, but reversed, those described for the transmitting side. For example, the PHY layer can receive the transport layer (TB) and provide it to the MAC layer on one or more transport channels. The MAC layer can map transport channels to logical channels and provide data to the RLC layer via the logical channels. The RLC layer can map logical channels to RLC channels and provide data to the RRC layer via the RLC channels. The PDCP layer can map RLC channels to radio bearers and provide data to the RRC layer via the radio bearers.

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

[0124] Figure 8B The control plane protocol stack 804 is similar to the AS protocol stack 802, except that the PC5 side link (PC5-S) layer is above the PDCP layer. The UE can send and receive control signaling and data at the PC5-S layer.

[0125] As indicated above, Figure 8A and Figure 8B Provided as an example. Other examples may be found with reference to [the relevant information]. Figure 8A and Figure 8B The examples described are different.

[0126] Figure 9 These are examples 900 and 902 illustrating the control plane protocol stack for U2N relay according to this disclosure.

[0127] Example 900 illustrates a control plane protocol stack for an L2 U2N relay between a 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 termination points for Non-Access Layer (NAS) signaling and / or mobility management, etc. The remote UE 720 may establish security with the AMF 910 via one or more NAS operations. NAS-level operations may include authentication operations performed between the remote UE 720 and the AMF 910.

[0128] In some respects, the AMF 910 may, for example, at least in part, respond to a request for data services from the UE 120 by requesting the Network Slice Selection Function (NSSF) to select a network slice instance for the UE 120. The NSSF may include one or more devices for selecting a network slice instance for the UE 120. A network slice is a network architecture model in which logically distinct network slices operate using a common network infrastructure.

[0129] The remote UE 720 can communicate with the AMF 910 at the NAS Mobility Management (MM) layer. The remote UE 720 can also communicate with the Session Management Function (SMF) 915 at the 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 a wireless telecommunications system. For example, the SMF 915 can configure service bootstrapping policies at the User Plane Function (UPF) 920 and / or enforce UE Internet Protocol (IP) address allocation and policies, etc. In some aspects, the SMF 915 can provision the remote UE 720 with a network slice instance selected by the NSSF.

[0130] Example 900 illustrates protocol layers such as PC5-PHY, PC5-MAC, and PC5-RLC for a remote UE 720. A relay UE 715 can use these layers on its PC5 interface with the UE 720. The UE 715 can use Uu-RLC, Uu-MAC, Uu-PHY, and an adaptation layer on its Uu interface with the NG-RAN 905. The adaptation layer can send information (e.g., Master Information Block (MIB), System Information Block (SIB)) for an upper layer (e.g., the RRC layer) to initiate initial access. This information can be provided by the adaptation layer, or the upper layer can skip the step of checking such information (e.g., the RRC layer can always assume that the RRC layer has valid information). Both the remote UE 720 and the relay UE 715 can use the PC5 adaptation layer for similar signaling. The NG-RAN 905 can use the N2 interface stack. Components of the 5G core network can communicate through various interfaces, such as N2, N3, N4, N6, N9, and N11. Some of these interfaces can relate to Next Generation Application Protocol (NGAP), Flow Control Transmission Protocol (SCTP), Packet Forwarding Control Protocol (PFCP), and General Packet Radio System (GPRS) Tunneling Protocol User Plane (GTP-U). The AMF 910 can use both the N2 and N11 interface stacks. The SMF 915 can use the N11 interface stack.

[0131] Example 902 illustrates a user plane protocol stack for L2 U2N relay, where a remote UE 720 can use a PDU layer with a UPF 920 to communicate data. The UPF 920 may include one or more devices that act as anchors for mobility within and / or between RATs. In some aspects, the UPF 920 can apply rules to packets, such as rules relating to packet routing, traffic reporting, and / or handling user plane QoS.

[0132] Other layers in the user plane may include the SDAP layer in L2. Therefore, 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 UE 120 is transmitting uplink communication or network node 110 is transmitting downlink communication), the SDAP layer may receive data streams in the form of QoS streams. The SDAP layer or RRC / NAS layer may map QoS streams or control information to radio bearers. Therefore, it can be said that the SDAP layer handles QoS streams on the transmitting side. The SDAP layer may provide QoS streams to the PDCP layer via the corresponding radio bearer. Layers used for communication between NG-RAN 905 and UPF 920 via the N3 interface may include GTP-U, User Datagram Protocol (UDP), IP, L2, and L1.

[0133] In some examples, when both relay UE 715 and remote UE 720 are in RRC IDLE or RRC INACTIVE, relay UE 715 monitors the paging opportunities (POs) of its connected remote UE 720. When relay UE 715 needs to monitor paging of remote UE 720, relay UE 715 can monitor all POs of remote UE 720. When relay UE 715 is in RRC_CONNECTED and remote UE 720 is in RRC_IDLE or RRC_INACTIVE, there are two options for paging delivery. If the active downlink bandwidth portion (BWP) of relay UE 715 is configured using the control resource set (CORESET) and paging search space, relay UE 715 can monitor the POs of its connected remote UE 720.

[0134] The delivery of paging for remote UE 720 can be performed via a dedicated RRC message from the network node of NG-RAN 905 to relay UE 715. The dedicated RRC message used to deliver paging for a remote UE to RRC_CONNECTED relay UE 715 may contain one or more remote UE IDs. The network implementation determines which of the two options to use. If the relay UE 715 in RRC_CONNECTED configuration utilizes the paging search space, it can determine whether to monitor the PO of remote UE 720 based on indications within the PC5-RRC signaling received from remote UE 720 (e.g., 5G-S-TMSI, Inactive Radio Network Temporary Identifier (I-RNTI)).

[0135] A remote UE 720 in RRC_IDLE state can provide a 5G-S-TMSI and a UE-specific DRX cycle (configured by the upper layer) to a relay UE 715 to request PO monitoring. A remote UE 720 in RRC_INACTIVE state provides the relay UE 715 with two UE-specific DRX cycles (configured by the upper layer and NG-RAN respectively), the minimum of the 5G-S-TMSI and I-RNTI values ​​for PO monitoring. A relay UE 715 in RRC_CONNECTED state can use [the following method / method] for paging delivery purposes. SidelinkUEInformationNR The message notifies the gNB of the remote UE 720 information (i.e., 5G-S-TSMI / I-RNTI). The relay UE 715 receives the paging message to check the 5G-S-TSMI / I-RNTI and accordingly transmits the relevant paging record to the remote UE 720. The relay UE 720 can transmit the paging to the remote UE 720 via PC5 using unicast signaling.

[0136] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0137] In some examples, the sidelink can support sidelink DRX (SL DRX) for unicast, multicast, and broadcast. For unicast, SL DRX is configured for each pair of source L2 IDs and destination L2 IDs. The UE maintains a set of SL DRX timers for each direction of each pair of source L2 IDs and destination L2 IDs. The SL DRX configuration for a pair of source / destination L2 IDs for a direction can be negotiated between UEs in the AS layer. For the SL DRX configuration in each direction, where one UE is a TX UE and the other is a receive (RX) UE, the RX UE can transmit auxiliary information to the TX UE, including its desired SL on duration timer, SL DRX start offset, and SL DRX cycle. The mode 2 TX UE can use the auxiliary information to determine the SL DRX configuration for the RX UE. The SL DRX configuration for the RX UE is determined by the TX UE in RRC_IDLE / RRC_INACTIVE / Out of Coverage (OOC) or in RRC_CONNECTED and using mode 2 resource allocation. For TX UEs in RRC_CONNECTED mode 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 transmits the SL DRX configuration to be used by the RX UE. The RX UE can accept or reject the SL DRX configuration. The default SL DRX configuration for multicast / broadcast can be used in Direct Communication Request (DCR) messages.

[0138] When the TX UE is in RRC_CONNECTED, the TX UE can report the received auxiliary information to its serving gNB, and transmit the SL DRX configuration to the RX UE when it receives the SL DRX configuration from the dedicated RRC signaling 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 Uu and SLDRX configurations).

[0139] In unicast, support is provided for the SL Enable Duration Timer, SL Inactivity Timer, SL HARQ Round Trip Time (RTT) Timer, and SL HARQ Retransmission Timer. Each SL procedure at the RX UE maintains an SL HARQ RTT timer and an SL HARQ Retransmission Timer. In addition to the (pre)configured values ​​for each of these timers, the SL HARQ RTT timer value can be derived from the retransmission resource timing when the SCI indicates more than one transmit resource. The SL DRX MAC CE is introduced only for SL DRX operations in unicast.

[0140] In some examples, DFNs are used for sidelink communication. A DFN is similar to an SFN used in uplink and downlink communication. A DFN can be 10 bits and 10 ms. An H-DFN can comprise 1024 subframes or 10.24 seconds. An H-DFN can increment as it wraps around (after 1024 DFNs). Extended DRX (eDRX) can comprise multiple H-SFNs. An H-DFN can be equivalent to a superframe or super SFN (H-SFN) used for DRX.

[0141] In some examples, two peer UEs can use the DFN to calculate the activity time on the sidelink. Currently, UEs can derive the DFN in two ways: 1) from GNSS timing; or 2) from SLSS signaling. Requiring the UE to monitor GNSS signals consumes power. In some aspects, if the UE can obtain the DFN from SLSS signaling, the two UEs can first synchronize their sleep times, and then each UE can rely on its internal clock to calculate the wake-up time. That is, the UE does not need to rely on monitoring GNSS timing.

[0142] The UE can be configured to monitor paging messages using eDRX cycles in an inactive (idle) state. eDRX cycles extend the DRX cycle to approximately 3 hours by including multiple H-SFNs (10 bits). One H-SFN can include 1024 SFNs. The UE can wake up during the paging time window (PTW) of each extended DRX cycle. A paging superframe (PH) refers to the H-SFN during the PTW used by the UE in RRC_IDLE that begins monitoring paging DRX. PH and PTW are determined based on formulas known to the AMF, UE, and NG-RAN. If the eDRX cycle is longer than 10.24 seconds, H-SFN, PH, and PTW are used.

[0143] Figure 10 This is a diagram illustrating an example 1000 of a sidelink eDRX according to this disclosure.

[0144] In scenarios with direct sidelink communication on the sidelink interface, the UE can be configured for sidelink DRX, where the active time can be calculated based on the DFN. If the active time is calculated using the DFN, there are 1024 DFNs in the H-DFN, and therefore the maximum sidelink DRX cycle is 10.24 seconds. As an example, for direct sidelink communication, two UEs can be RedCap UEs or Internet of Things (IoT) devices, and both UEs can attempt to conserve power. However, the maximum 10.24 seconds of the DRX cycle may not be sufficient for the UE to maximize power savings. The UE can only conserve power during the inactive period of the DRX cycle, and therefore the UE can conserve power for up to a maximum of 5.12 seconds in the H-DFN. Without a comparable eDRX for the sidelink (where the UE can sleep and not wake up for a longer period than the connected-mode sidelink DRX), the UE may not be able to conserve as much power using the sidelink interface as it could using the Uu interface.

[0145] In scenarios with U2N relays, the remote UE wakes up to monitor the PO (Position Target) on the Uu interface for each DRX cycle. The relay UE also monitors the remote UE's PO. In existing sidelink DRXs, the activity time is calculated based on the DFN (Dedicated Node Number). If the DFN is used to calculate the activity time, the maximum DRX cycle length is 10.24 seconds. In an inactive (idle) state, the remote UE has a connection with the relay UE, and the relay UE forwards received paging messages to the remote UE (e.g., the remote UE cannot receive paging messages). As described above for direct sidelink communication scenarios, if the remote UE is inactive and there is no eDRX on the sidelink, the remote UE must monitor the sidelink for each DRX cycle. The remote UE and relay UE may not sleep for longer than the connected mode sidelink DRX, but may have to wake up for each DRX cycle. The remote UE and relay UE can conserve power only during the inactive period of the DRX cycle. Waking up for each DRX cycle consumes power for both the remote UE and the relay UE.

[0146] Based on the various aspects described herein, side-link UEs can save more power. The UE can calculate the DFNs to wake up during its period, and these DFNs can be within a side-link eDRX cycle. The DFNs can be within an active time window in the side-link eDRX cycle. Using the active time window in conjunction with the side-link eDRX cycle allows the UE to sleep for longer periods and save more power because the side-link eDRX cycle is a large cycle (e.g., up to 3 hours or more). Therefore, the UE's sleep time is not limited to half of the 10.24ms H-DFN. Instead, the UE's sleep time (outside the active time window in the eDRX cycle) can be longer than the sleep time in connected-mode side-link DRX (e.g., up to 3 hours or more), and / or may include multiple inactive DFNs in the side-link eDRX, whose combined sleep time is more than half of the HDFN. Power savings can assist battery-constrained devices, such as RedCap UEs.

[0147] In a direct sidelink scenario, two UEs can wake up simultaneously to communicate with each other using sidelink eDRX cyclically. In a U2N trunk scenario, a remote UE and a trunk UE can wake up simultaneously to communicate with each other using sidelink eDRX cyclically. Using sidelink eDRX cyclically, the UE can calculate the active time window for waking up.

[0148] The active time window in the side-link eDRX can be aligned with the active time window in the Uu eDRX cycle. In H-DFN settings for direct communication, if an H-SFN is received, the UE can set the H-DFN to the same number as the H-SFN. If no H-SFN is received, the UE can set the H-DFN either by implementing it or based on H-DFNs received from other UEs. During H-DFN synchronization, the UE can... RRCReconfigurationSidelink The current H-DFN is indicated to the peer UE in the message, or in the SCI or side-link MAC CE. Alternatively, the UE may indicate the H-SFN in the SLSS message.

[0149] Example 1000 illustrates a sidelink eDRX cycle 1002 comprising multiple H-DFNs 1004. The UE can wake up within an H-DFN 1004 consisting of 1024 DFNs. In some aspects, the UE can calculate an active time window 1008 within the H-DFN 1004 that includes an active DRX cycle. The UE can calculate to wake up within DFN 1010. DFN 1010 can be the on-time duration of DRX cycle 1012 (a short DRX cycle). The active time window 1008 can begin after an offset (Start_Offset) 1014 within the eDRX cycle 1002. The start (ATW_start) 1008 of the active time window 1008 can be a PO that begins within the eDRX cycle 1002. The end (ATW_end) of the active time window 1008 can end within the eDRX cycle 1002. In some respects, ATW_start can be calculated as (Tcurrent - Tref) mod eDRX cycle = Start_Offset, where Tcurrent is the current Coordinated Universal Time (UTC) obtained from the GNSS, and Tref is the reference UTC time 00:00:00 for January 1, 1900, in milliseconds. ATW_end can be calculated as ATW_end = ATW_start + On_Duration. For U2N relays, the core network and gNB can calculate the PO as described above to align the Uu PO and SL PO.

[0150] In some respects, UEs can negotiate sidelink eDRX configurations between them. For example, the TX UE can determine the sidelink eDRX parameters and use sidelink messages (such as PC5-RRC messages, e.g., RRCReconfigurationSidelinkThe TX UE transmits parameters to the RX UE via either a sidelink MAC CE or a sidelink eDRX UE. Optionally, the RX UE may transmit sidelink eDRX auxiliary information to the TX UE. Auxiliary information may include the UE ID (e.g., 5G-S-TMSI, SUCI, a hash of the UE ID (UE_ID_H), or the UE L2 ID), an indication of sidelink eDRX cycling (optionally), and / or an indication of the active time window. That is, if the TX is using the TX UE ID to calculate the active time, the TX UE may transmit the UE ID (5G-S-TMSI, SUCI, UE_ID_H, UE L2 ID) to the RX UE. In some aspects, the TX UE may transmit eDRX parameters (eDRX cycling, 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 or outside the existing sidelink configuration IE.

[0151] In some aspects related to direct sidelink communication, the UE can calculate the activity time in the H-DFN used for direct sidelink communication. For example, the activity time can be calculated as H-DFN mod T. eDRX_SL =(UE_ID_H mod T eDRX_SL ), where UE_ID_H is the hashed ID UE_ID_H with 13 most significant bits, T eDRX_SL It is the RX UE-specific sidelink eDRX loop (T) in H-DFN eDRX_SL =2…1024 super DFNs). ATW_start represents the first DFN of the H-DFN, which is part of the active time window and has a DFN that satisfies 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 ATW and has a DFN that satisfies 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 can be the same as the Uu hash ID of the 5G-S-TMSI. If 5G-S-TMSI does not exist, SUCI can be used to derive the hashed ID. UE_ID_H can also be the UE L2 ID.

[0152] In some aspects associated with U2N relays, the remote UE can calculate the active time window in each sidelink eDRX cycle and wake up within the active time window to monitor paging. The calculated sidelink active time window can be aligned with the Uu active time window used for paging monitoring. The relay UE can 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 sidelink eDRX configuration negotiation, the remote UE can use PC5 RRC messages (e.g., RRCReconfigurationSidelink The PC5-S message or sidelink MAC CE transmits sidelink eDRX parameters to the relay UE. Sidelink eDRX parameters may include the remote UE ID (e.g., 5G-S-TMSI, UE_ID_H, eDRX cycle count, active time window). The sidelink eDRX cycle count and active time window for the remote UE can be provided at the NAS layer.

[0153] In some aspects related to U2N relay, the remote UE can calculate the activity time as H-DFN' mod T. eDRX_SL =(UE_ID_H mod T eDRX_SL ATW_start can represent the first DFN of H-DFN, which is part of the active time window and has a DFN that satisfies the following equation: DFN'=128 i eDRX_SL , where i eDRX_SL =floor(UE_ID_H / T eDRX_SL )mod 8.

[0154] By negotiating the sidelink eDRX configuration, the UE can align itself when it wakes up during the active time window of the sidelink eDRX cycle. This prevents the UE from missing communications and saves power.

[0155] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0156] Figures 11A to 11C These are illustrations of examples 1100, 1102, and 1104 of SFN-DFN offsets according to this disclosure.

[0157] If the SFN-DFN offset is indicated and if the SFN-DFN offset > 0, then ATW_start can be the first DFN' before DFN'. n One direct radio frame, of which n yes Figure 11AExample 1100 shows an SFN-DFN offset of 1106. If the SFN-DFN offset is less than 0, then ATW_start can be the first SFN after DFN'. n One direct radio frame, of which n yes Figure 11B Example 1102 shows an SFN-DFN offset of 1106. If the SFN-DFN offset = 0, then ATW_start can be at DFN'.

[0158] Additionally, if a subframe offset or slot offset of 1108 is indicated, then ATW_start can be an earlier direct radio frame than the ATW_start calculated above, such as... Figure 11C As shown in Example 1104. ATW_end can be the last DFN of ATW and has a DFN that satisfies the following equation: DFN = (ATW_start + ... L ×100-1) mod 1024.

[0159] As indicated above, Figures 11A to 11C Some examples are provided. Other examples can be found in the section about... Figures 11A to 11C The examples described are different.

[0160] Figure 12 This is a diagram illustrating example 1200 of an active time window in a sidelink eDRX loop according to this disclosure. Example 1200 shows a sidelink eDRX loop 1202, which includes an active time window 1204 with ATW_start 1206 and ATW_end 1208. An eDRX offset 1210 may exist between time eDRX 1212 and eDRX start 1214.

[0161] In some aspects associated with direct sidelink communication, the two sidelink UEs can calculate the active time based on the coordinated activation of sidelink eDRX. The two UEs can coordinate the eDRX start point and calculate the active time window in each sidelink eDRX cycle. Each UE can wake up in the active time window 1204 of each sidelink eDRX cycle 1202 to send or receive sidelink data. In some aspects, legacy SL DRX can be used during the active time window 1204.

[0162] In some aspects, the UE can negotiate the sidelink eDRX configuration. For example, the TX UE can determine sidelink eDRX parameters (e.g., indicating sidelink eDRX cycles and / or active time windows) and transmit these parameters to the RX UE using sidelink messages (e.g., PC5-RRC messages or sidelink MAC CE). Optionally, the RX UE can transmit eDRX auxiliary information to the TX UE. The auxiliary information may include eDRX cycles and / or active time windows. Optionally, the TX UE can transmit sidelink eDRX parameters (e.g., indicating sidelink eDRX cycles, ATW) to its serving gNB, and the serving gNB can provide the TX UE with modified sidelink eDRX parameters. The TX UE can determine the starting point for entering eDRX mode (eDRX start 1214) and transmit the relevant configuration to the RX UE. The eDRX offset 1210 can be compared with the time when the UE receives the indication to enter sidelink eDRX mode (time eDRX 1212). The TX UE can transmit a PC5-RRC message to the RX UE indicating entry into sidelink eDRX mode. If a start point (eDRX_offset 1210) is indicated, the TX and RX UEs can enter sidelink eDRX mode after eDRX_offset 1210 time. eDRX_offset 1210 can be in seconds, milliseconds, or direct radio frames. If no start point (eDRX_offset 1210) is indicated, the TX and RX UEs can directly enter eDRX mode. Optionally, the TX UE can transmit an indication to its serving gNB requesting entry into sidelink eDRX mode. The gNB can transmit an indication of eDRX_offset 1210 to the TX UE.

[0163] In some respects, two UEs can use eDRX_start 1214 to calculate ATW_start 1206 and ATW_end 1208: Time_eDRX + eDRX_offset as the timing for entering eDRX mode. ATW_start can be eDRX_start + Start_offset + ( n -1) × eDRX loop, where n This is the [number]th [number] after entering sidelink eDRX mode. n One loop. ATW_end can be ATW_start + ATW.

[0164] In some aspects associated with U2N relays, network entities can utilize sidelink eDRX start point parameters to configure remote UEs and / or relay UEs. Remote and relay UEs can transmit modified eDRX start point parameters to either the relay or remote UE. Remote UEs can calculate the active time window for each sidelink eDRX cycle and wake up within that active time window to monitor paging. In some aspects, legacy SL DRX can be used during the active time window.

[0165] In some aspects, two UEs can negotiate sidelink eDRX configuration. Network entities can use RRC messages or SL MACCE to configure the sidelink eDRX start point parameter (eDRX_offset) for the remote and relay UEs. The remote and relay UEs can transmit a modified eDRX_offset to the relay and / or remote UE using PC5-RRC messages or sidelink MACCE. The modified eDRX_offset may take into account the processing time for receiving or sending messages in the remote or relay UE. The remote or relay UE can transmit a PC5-RRC message to the relay or remote UE indicating entry into sidelink eDRX mode. The relay or remote UE may enter eDRX mode after the eDRX_offset time. If no start point (eDRX_offset) is indicated, the remote and relay UEs may directly enter sidelink eDRX mode. The remote UE can transmit sidelink eDRX parameters to the relay UE. Sidelink eDRX parameters may include indications of eDRX cycles and / or indications of active time windows. The UE can calculate ATW_start and ATW_end as described above for the directional communication scenario.

[0166] In some respects, whenever a UE wakes up, both UEs check the availability of a sidelink (e.g., PC5) connection by sending a keep-alive message to their peer UE. If the PC5 connection is unavailable, the UE can release the PC5 connection locally.

[0167] As indicated above, Figure 12 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 12 The examples described are different.

[0168] Figure 13 This is a diagram illustrating an example 1300 associated with a side-link eDRX configuration according to this disclosure. For example... Figure 13As shown, network entity 1310 (e.g., network node 110) and UE 1320 (e.g., UE 120, UE 715) can communicate with each other on a wireless network (e.g., wireless network 100). UE 1320 can communicate with UE 1330 (e.g., UE 120, UE 720) on a side link (e.g., a PC5 link). In one scenario, UE 1320 and UE 1330 communicate directly. In another scenario, UE 1320 operates as a relay UE for UE 1330, which can be a remote UE outside the coverage of network entity 1310. Example 1330 is applicable to both scenarios.

[0169] As shown by reference numeral 1335, network entity 1310 may send sidelink eDRX cycle parameters (e.g., the length of the sidelink eDRX cycle as the number of H-DFNs) for sidelink eDRX cycle configuration 1336. As shown by reference numeral 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.

[0170] In some aspects, negotiation may include UE 1320 transmitting parameters. Parameters may also include indications of the start point and / or eDRX offset of the sidelink eDRX loop (e.g., time after the indication to enter sidelink eDRX mode, SFN-DFN offset). As shown by reference numeral 1342, UE 1320 may select parameters. As shown by reference numeral 1344, UE 1320 may transmit and UE 1330 may receive parameters. As shown by reference numeral 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 a sidelink eDRX loop mode, which uses sidelink eDRX looping (e.g., as...). Figure 12 Example 1200 shows the side-link eDRX loop 1202 in DRX mode.

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

[0172] In some aspects, negotiation may alternatively involve parameters in the auxiliary information transmitted by UE 1330 and received by UE 1320, as indicated by reference numeral 1348. The auxiliary information may include the length of the sidelink eDRX loop, the UE ID, and / or a hash of the UE ID. As indicated by reference numeral 1350, UE 1320 may transmit and UE 1330 may respond. The response may indicate acceptance, rejection, or modification of the parameters in the auxiliary information.

[0173] As shown by reference numeral 1355 in the attached figure, UE 1330 can calculate the DFN to be woken up in. This may involve calculating the H-DFN within the sidelink eDRX cycle and / or the active time window. The calculated DFN can be the active duration of a short DRX cycle within the active time window.

[0174] As shown by reference numeral 1360, UE 1330 can wake up at the DFN to receive communication during the active duration of a short DRX cycle. As shown by reference numeral 1365, UE 1320 can also calculate the DFN to wake up simultaneously. As shown by reference numeral 1370, UE 1320 can wake up at the calculated DFN. As shown by reference numeral 1375, UE 1320 can transmit communication during the active duration.

[0175] By negotiating and using side-link eDRX cycles, UEs can coordinate to communicate and save more power compared to not using side-link eDRX cycles and their active time windows.

[0176] As indicated above, Figure 13 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 13 The examples described are different.

[0177] Figure 14 This is a diagram illustrating an example process 1400 performed, for example, at a first UE or a device of the first UE, according to this disclosure. Example process 1400 is an example in which a device or a first UE (e.g., UE 120, UE 715, UE 720, UE 1320, UE 1330) performs operations associated with negotiating configurations for sidelink eDRX.

[0178] like Figure 14 As shown, in some aspects, process 1400 may include negotiating with the second UE a configuration associated with wake-up in a DFN within an active time window comprising a set of H-DFNs in a sidelink eDRX cycle (box 1410). For example, the first UE (e.g., using...) Figure 16The communication manager 140 and / or configuration component 1608 depicted herein can negotiate with the second UE the configuration associated with wake-up in a DFN within an active time window that includes a set of H-DFNs in the side-link eDRX cycle, as described above.

[0179] like Figure 14 As further shown, in some aspects, process 1400 may include calculating the DFN (block 1420) at least in part based on this configuration. For example, the first UE (e.g., using...) Figure 16 The communication manager 140 and / or computing component 1610 depicted herein may compute the DFN at least in part based on this configuration, as described above.

[0180] like Figure 14 As further shown, in some aspects, process 1400 may include wake-up in a DFN, where DFN is the duration of activity within an activity time window (box 1430). For example, the first UE (e.g., using...) Figure 16 The communication manager 140 and / or receiving component 1602 depicted can be awakened in DFN, where DFN is the activity duration within the activity time window, as described above.

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

[0182] In the first aspect, the configuration includes the length of the sidelink eDRX loop.

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

[0184] In the third aspect, either alone or in combination with one or more of the first and second aspects, the configuration includes information for determining the activity time window.

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

[0186] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the negotiated configuration includes: selecting one or more parameters for sidelink eDRX cyclic; sending an indication of the one or more parameters; and receiving a response to the indication.

[0187] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the negotiated configuration includes receiving auxiliary information, and the selection of one or more parameters includes selecting one or more parameters at least in part based on the auxiliary information.

[0188] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the auxiliary information includes one or more of the following: UE ID, hash of the UE ID, length of the side-link eDRX cycle, or information for the active time window.

[0189] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the negotiated configuration includes: receiving an indication of one or more parameters for a sidelink eDRX cycle; and sending a response to the indication.

[0190] In the ninth aspect, the negotiated configuration includes sending auxiliary information, either alone or in combination with one or more of the first to eighth aspects, including one or more of the following: UE ID, hash of the UE ID, length of the side-link eDRX cycle, or information for the active time window.

[0191] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the activity time window is based at least in part on the offset from the Uu activity time window.

[0192] In the eleventh aspect, the starting point of the side-link eDRX cycle is configured, either alone or in combination with one or more of the first to tenth aspects.

[0193] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the starting point is the eDRX offset following the start indication for initiating the side-link eDRX mode.

[0194] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 1400 includes receiving information about the eDRX offset.

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

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

[0197] although Figure 14 An example box for process 1400 is shown, but in some respects, it differs from... Figure 14Compared to the boxes depicted, process 1400 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1400 may be executed in parallel.

[0198] Figure 15 This is a diagram illustrating an example process 1500 performed, for example, at a network entity or a device of a network entity, according to this disclosure. Example process 1500 is an example in which a device or network entity (e.g., network node 110, network entity 1310) performs operations associated with the configuration for sidelink eDRX.

[0199] like Figure 15 As shown, in some aspects, process 1500 may include obtaining one or more parameters (box 1510) of a configuration associated with waking up in a DFN within an active time window of a sidelink eDRX cycle that includes a set of H-DFNs. For example, network entities (e.g., using...) Figure 19 The communication manager 150 and / or configuration component 1908 depicted herein may obtain one or more parameters associated with configuring the first UE to wake up in an active time window of a DFN that includes a set of H-DFNs in a side-link eDRX cycle, as described above.

[0200] like Figure 15 As further shown, in some aspects, process 1500 may include sending an indication to a second UE for one or more parameters (box 1520). For example, a network entity (e.g., using...) Figure 19 The communication manager 150 and / or the transmitting component 1904 depicted herein can transmit instructions for one or more parameters to the second UE, as described above.

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

[0202] In a first aspect, process 1500 includes sending information for an eDRX offset associated with the start-up sidelink eDRX mode after a start instruction for starting the sidelink eDRX mode.

[0203] In the second aspect, either alone or in combination with the first aspect, process 1500 includes sending information for the start point of the sidelink eDRX mode.

[0204] although Figure 15 An example box for process 1500 is shown, but in some respects, it differs from... Figure 15Compared to the boxes depicted, process 1500 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1500 may be executed in parallel.

[0205] Figure 16 This is a diagram of an example device 1600 for wireless communication according to the present disclosure. Device 1600 may be a first UE, or a first UE may include device 1600. In some aspects, device 1600 includes a receiving component 1602 and a transmitting component 1604, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1600 may use the receiving component 1602 and the transmitting component 1604 to communicate with another device 1606 (such as a UE, a base station, or another wireless communication device). As further shown, device 1600 may include a communication manager 140. Communication manager 140 may include a configuration component 1608 and / or a computing component 1610, etc.

[0206] In some respects, device 1600 can be configured to perform the functions described herein. Figures 1 to 13 One or more operations described herein. Additionally or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as Figure 14 The process is 1400. In some respects, Figure 16 The illustrated device 1600 and / or one or more components may include a combination Figure 2 One or more components of the first UE described. Additionally or alternatively, Figure 16 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more of the components in the group may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) 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 function or operation of the component.

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

[0208] Transmitting component 1604 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1606. In some aspects, one or more other components of device 1600 may generate communications and provide the generated communications to transmitting component 1604 for transmission to device 1606. In some aspects, transmitting component 1604 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1606. In some aspects, transmitting component 1604 may include combinations of... Figure 2 The described first UE includes 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 combinations thereof. In some aspects, the transmit component 1604 may co-located with the receive component 1602 in one or more transceivers.

[0209] Configuration component 1608 can negotiate with the second UE a configuration associated with wake-up in a DFN within an active time window that includes a set of H-DFNs in a sidelink eDRX cycle. Calculation component 1610 can calculate the DFN based at least in part on this configuration. Reception component 1602 can wake up in a DFN, where the DFN is the activity duration within the active time window.

[0210] The calculation component 1610 can calculate the active time window based at least in part on the length of the sidelink eDRX cycle. The receiving component 1602 can receive information for the eDRX offset.

[0211] Figure 16 The number and arrangement of components shown are provided as an example. In reality, with... Figure 16 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 16 The two or more components shown can be implemented within a single component, or Figure 16 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 16 The set (one or more) components shown are executable and described as being composed of Figure 16 The other set of components shown performs one or more functions.

[0212] Figure 17This is an illustration of an example 1700 of a hardware implementation of an apparatus 1705 employing a processing system 1710 according to the present disclosure. The apparatus 1705 may be a first UE or may be located at the first UE (e.g., included in the first UE).

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

[0214] Processing system 1710 may be coupled to one or more transceivers 1730. Transceiver 1730 is coupled to one or more antennas 1735. Transceiver 1730 provides components for communicating with various other devices via a transmission medium. Transceiver 1730 receives signals from one or more antennas 1735, extracts information from the received signals, and provides the extracted information to processing system 1710 (specifically, receiving component 1602). Furthermore, transceiver 1730 receives information from processing system 1710 (specifically, transmitting component 1604) and generates signals to be applied to one or more antennas 1735 based at least in part on the received information.

[0215] Processing system 1710 includes one or more processors 1720 coupled to computer-readable medium / memory 1725. Processor 1720 is responsible for general processing, including executing software stored on computer-readable medium / memory 1725. When executed by processor 1720, the software causes processing system 1710 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1725 can also be used to store data manipulated by processor 1720 during software execution. The processing system also includes at least one of the illustrated components. These components may be software modules running in processor 1720, residing in / stored on computer-readable medium / memory 1725, one or more hardware modules coupled to processor 1720, or some combination thereof.

[0216] In some aspects, processing system 1710 may be a component of UE 120 and may include one or more memories such as memory 282, and / or may include at least one of one or more processors such as TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In some aspects, apparatus 1705 for wireless communication includes: components for negotiating with a second UE a configuration associated with wake-up in a DFN within an active time window comprising a set of H-DFNs; components for calculating the DFN at least in part based on the configuration; and components for wake-up in a DFN, where DFN is the duration of activity within the active time window. The aforementioned components may be one or more of the aforementioned components of processing system 1710 of apparatus 1600 and / or apparatus 1705 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 1710 may include TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In one configuration, the aforementioned components may be a TXMIMO processor 266, an RX processor 258, and / or a controller / processor 280 configured to perform the functions and / or operations set forth herein.

[0217] Figure 17 This is provided as an example. Other examples can be combined with it. Figure 17 The examples described are different.

[0218] Figure 18 This is an illustration of an example 1800 of a specific implementation of code and circuitry for device 1805 according to the present disclosure. The circuitry may include processing circuitry and memory circuitry. Device 1805 may be a first UE, or a first UE may include device 1805.

[0219] like Figure 18 As shown, device 1805 may include circuitry (circuit 1820) for negotiating with the second UE a configuration associated with wake-up in a DFN within an active time window of a sidelink eDRX cycle that includes a set of H-DFNs. For example, circuitry 1820 may enable device 1805 to negotiate with the second UE a configuration associated with wake-up in a DFN within an active time window of a sidelink eDRX cycle that includes a set of H-DFNs.

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

[0221] like Figure 18 As shown, device 1805 may include circuitry (circuit 1830) for calculating the DFN based at least in part on the configuration. For example, circuitry 1830 may enable device 1805 to calculate the DFN based at least in part on the configuration.

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

[0223] like Figure 18 As shown, device 1805 may include circuitry for waking up in a DFN, which is the duration of activity within an activity time window (circuit 1840). For example, circuitry 1840 may enable device 1805 to wake up in a DFN, which is the duration of activity within an activity time window.

[0224] like Figure 18 As shown, device 1805 may include code stored in computer-readable medium 1725 for waking up in a DFN, where DFN is the duration of activity within an active time window (code 1845). For example, when executed by processor 1720, code 1845 may cause processor 1720 to wake up transceiver 1730 in a DFN, where DFN is the duration of activity within an active time window.

[0225] Figure 18 This is provided as an example. Other examples can be combined with it. Figure 18 The examples described are different.

[0226] Figure 19This is a diagram of an example device 1900 for wireless communication according to the present disclosure. Device 1900 may be a network entity, or a network entity may include device 1900. In some aspects, device 1900 includes a receiving component 1902 and a transmitting component 1904, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1900 can use the receiving component 1902 and the transmitting component 1904 to communicate with another device 1906 (such as a UE, a base station, or another wireless communication device). As further shown, device 1900 may include a communication manager 150. Communication manager 150 may include a configuration component 1908, etc.

[0227] In some respects, device 1900 can be configured to perform the functions described herein. Figures 1 to 13 One or more operations described herein. Additionally or alternatively, the apparatus 1900 may be configured to perform one or more processes described herein, such as Figure 15 The process is 1500. In some respects, Figure 19 The illustrated device 1900 and / or one or more components may include a combination Figure 2 One or more components of the described network entity. Additionally or alternatively, Figure 19 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more of the components in the group may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) 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 function or operation of the component.

[0228] Receiver 1902 may receive communications from device 1906, such as reference signals, control information, data communications, or combinations thereof. Receiver 1902 may provide the received communications to one or more other components of device 1900. In some aspects, receiver 1902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1900. In some aspects, receiver 1902 may include combinations of... Figure 2 The described network entity includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0229] Transmitting component 1904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1906. In some aspects, one or more other components of device 1900 can generate communications and provide the generated communications to transmitting component 1904 for transmission to device 1906. In some aspects, transmitting component 1904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 1906. In some aspects, transmitting component 1904 may include combinations of... Figure 2 The described network entity includes 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 combinations thereof. In some aspects, the transmit component 1904 may co-located with the receive component 1902 in one or more transceivers.

[0230] Configuration component 1908 can obtain one or more parameters associated with configuring the first UE to wake up in an active time window of a sidelink eDRX cycle that includes a set of H-DFNs. Transmission component 1904 can send indications of one or more parameters to the second UE.

[0231] The transmitting component 1904 may transmit information for the eDRX offset associated with initiating the sidelink eDRX mode after a start indication for initiating the sidelink eDRX mode. The transmitting component 1904 may also transmit information for the start point of the sidelink eDRX mode.

[0232] Figure 19 The number and arrangement of components shown are provided as an example. In reality, with... Figure 19 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 19 The two or more components shown can be implemented within a single component, or Figure 19 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 19 The set (one or more) components shown are executable and described as being composed of Figure 19 The other set of components shown performs one or more functions.

[0233] Figure 20 This is an illustration of an example 2000 of a hardware implementation of an apparatus 2005 for employing a processing system 2010 according to the present disclosure. The apparatus 2005 may be a network entity or may be located at a network entity (e.g., included in a network entity).

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

[0235] The processing system 2010 may be coupled to one or more transceivers 2030. The transceivers 2030 are coupled to one or more antennas 2035. The transceivers 2030 provide components for communicating with various other devices via a transmission medium. The transceivers 2030 receive signals from the one or more antennas 2035, extract information from the received signals, and provide the extracted information to the processing system 2010 (specifically, the receiving component 1902). Furthermore, the transceivers 2030 receive information from the processing system 2010 (specifically, the transmitting component 1904) and generate signals to be applied to the one or more antennas 2035, at least in part, based on the received information.

[0236] The processing system 2010 includes one or more processors 2020 coupled to a computer-readable medium / memory 2025. The processors 2020 are responsible for general processing, including executing software stored on the computer-readable medium / memory 2025. When executed by the processors 2020, the software causes the processing system 2010 to perform the various functions described herein with respect to any particular device. The computer-readable medium / memory 2025 can also be used to store data manipulated by the processors 2020 during software execution. The processing system also includes at least one of the illustrated components. A component may be a software module running in the processor 2020, residing in / stored in the computer-readable medium / memory 2025, one or more hardware modules coupled to the processor 2020, or some combination thereof.

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

[0238] Figure 20 This is provided as an example. Other examples can be combined with it. Figure 20 The examples described are different.

[0239] Figure 21 This is an illustration of example 2100 of the code and circuitry implementation for device 2105 according to the present disclosure. Device 2105 may be a network entity, or a network entity may include device 2105.

[0240] like Figure 21 As shown, apparatus 2105 may include circuitry (circuit 2120) for obtaining one or more parameters of a configuration associated with waking up in a DFN within an active time window of a sidelink eDRX cycle that includes a set of H-DFNs. For example, circuitry 2120 may enable apparatus 2105 to obtain one or more parameters of a configuration associated with waking up in a DFN within an active time window of a sidelink eDRX cycle that includes a set of H-DFNs.

[0241] like Figure 21As shown, apparatus 2105 may include code (code 2125) stored in computer-readable medium 2025 for obtaining one or more parameters of a configuration associated with waking up in a DFN within an active time window of a sidelink eDRX cycle that includes a set of H-DFNs. For example, when executed by processor 2020, code 2125 may cause processor 2020 to cause transceiver 2030 to obtain one or more parameters of a configuration associated with waking up in a DFN within an active time window of a sidelink eDRX cycle that includes a set of H-DFNs.

[0242] like Figure 21 As shown, device 2105 may include circuitry (circuit 2130) for sending an indication of one or more parameters to a second UE. For example, circuitry 2130 may enable device 2105 to send an indication of one or more parameters to the second UE.

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

[0244] Figure 21 This is provided as an example. Other examples can be combined with it. Figure 21 The examples described are different.

[0245] The following provides an overview of some aspects of this disclosure: Aspect 1: A method of wireless communication performed at a first user equipment (UE), the method comprising: negotiating with a second UE a configuration associated with wake-up in a DFN within an active time window of an active time window comprising a set of super direct frame numbers (DFNs) (H-DFNs); calculating the DFN based at least in part on the configuration; and wake-up in the DFN, wherein the DFN is the duration of activity within the active time window.

[0246] Aspect 2: According to the method of aspect 1, the configuration includes the length of the side link eDRX loop.

[0247] Aspect 3: According to the method of aspect 2, the method further includes calculating the activity time window based at least in part on the length of the side link eDRX cycle.

[0248] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the configuration includes information for determining the activity time window.

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

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

[0251] Aspect 7: The method according to any one of Aspects 1 to 6, wherein negotiating the configuration includes: selecting one or more parameters for the side link eDRX loop; sending an indication of the one or more parameters; and receiving a response to the indication.

[0252] Aspect 8: According to the method of aspect 7, negotiating the configuration includes receiving auxiliary information, and selecting the one or more parameters includes selecting the one or more parameters at least in part based on the auxiliary information.

[0253] Aspect 9: According to the method of aspect 8, the auxiliary information includes a UE identifier (ID).

[0254] Aspect 10: According to the method of aspect 8, the auxiliary information includes a hash of the UE identifier (ID).

[0255] Aspect 11: According to the method of aspect 8, wherein the auxiliary information includes the length of the side link eDRX loop.

[0256] Aspect 12: According to the method of aspect 8, the auxiliary information includes information for the activity time window.

[0257] Aspect 13: The method according to any one of Aspects 1 to 12, wherein negotiating the configuration includes: receiving an indication for one or more parameters for the side link eDRX cycle; and sending a response to the indication.

[0258] Aspect 14: The method according to any one of Aspects 1 to 13, wherein negotiating the configuration includes sending auxiliary information, the auxiliary information including one or more of the following: UE identifier (ID), hash of the UE ID, length of the sidelink eDRX cycle, or information for the active time window.

[0259] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the active time window is at least partially based on an offset from the active time window of Uu.

[0260] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the configuration indicates the starting point of the side link eDRX loop.

[0261] Aspect 17: According to the method of aspect 16, the starting point is an eDRX offset following the start indication for initiating the side-link eDRX mode.

[0262] Aspect 18: According to the method of aspect 17, the method further includes receiving information for the eDRX offset.

[0263] Aspect 19: The method according to aspect 16, wherein the first UE is a remote UE configured to communicate with a network entity via the second UE.

[0264] Aspect 20: According to the method of aspect 16, wherein the first UE is a relay UE configured to relay communication between the second UE and a network entity.

[0265] Aspect 21: A method of wireless communication performed at a network entity, the method comprising: obtaining one or more parameters associated with a configuration for waking up in an active time window of a first user equipment (UE) in a sidelink extended discontinuous reception (DRX) (eDRX) cycle comprising a set of super direct frame numbers (DFN) (H-DFN); and sending an indication of the one or more parameters to a second UE.

[0266] Aspect 22: According to the method of aspect 21, the method further includes sending information for an eDRX offset associated with the start-up sidelink eDRX mode after a start indication for starting the sidelink eDRX mode.

[0267] Aspect 23: The method according to any one of aspects 21 to 22, the method further comprising sending information for the start point of the sidelink eDRX mode.

[0268] Aspect 24: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to 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 according to one or more of aspects 1 to 23.

[0269] 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 being configured to cause the device to perform the method according to one or more of aspects 1 to 23.

[0270] Aspect 26: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 23.

[0271] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 23.

[0272] Aspect 28: A non-transitory computer-readable medium storing a set of instructions for wireless communication, said instruction comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 23.

[0273] Aspect 29: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 23.

[0274] 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 being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 23.

[0275] Aspect 31: An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: a processing system including processor circuitry and memory circuitry storing code and coupled thereto, the processing system being configured to cause the network entity to perform the method according to one or more of aspects 1 to 20.

[0276] Aspect 32: An apparatus for wireless communication at a network entity, the apparatus comprising: a processing system including processor circuitry and memory circuitry storing code and coupled thereto, the processing system being configured to cause the network entity to perform one or more of the methods described in aspects 21 to 23.

[0277] Aspect 33: An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the first UE to: negotiate with a second UE a configuration associated with wake-up in a DFN within an active time window of an active time window comprising a set of super direct frame numbers (DFNs) (H-DFNs); calculate the DFN at least in part based on the configuration; and wake up in the DFN, the DFN being the duration of activity within the active time window.

[0278] Aspect 34: The apparatus according to aspect 33, wherein the one or more processors are individually or jointly configured to cause the first UE to: negotiate with the second UE a configuration associated with wake-up in a DFN within an active time window of an active time window comprising a set of super direct frame numbers (DFNs) (H-DFNs); calculate the DFN at least in part based on the configuration; and wake up in the DFN, the DFN being the duration of activity within the active time window.

[0279] Aspect 35: An apparatus for wireless communication at a network entity, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the network entity to: obtain one or more parameters associated with a configuration for waking up in an active time window of a sidelink extended discontinuous reception (DRX) (eDRX) cycle comprising a set of super direct frame numbers (DFNs) (H-DFNs); and send an indication of the one or more parameters to a second UE.

[0280] Aspect 36: The apparatus according to aspect 35, wherein the one or more processors are individually or jointly configured to cause the network entity to: obtain one or more parameters associated with a configuration for waking up in an active time window of a sidelink extended discontinuous reception (DRX) (eDRX) cycle that includes a set of super direct frame numbers (DFNs) (H-DFNs); and send an indication of the one or more parameters to a second UE.

[0281] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various forms of practice.

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

[0283] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

[0284] As used in this article, depending on the context, "meeting the threshold" can mean a value 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, etc.

[0285] Although specific combinations of features are set forth 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 set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase referring to “at least one of” the list of items means any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0286] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in the case of its use in conjunction with “any” or “only one”).

Claims

1. An apparatus for wireless communication at a first user equipment (UE), 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 first UE to: negotiate, with a second UE, a configuration associated with waking up in a super-direct frame number (DFN) (H-DFN) of an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle that includes a set of 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 time within the active time window.

2. The apparatus of claim 1, wherein the configuration includes a length of the sidelink eDRX cycle.

3. 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 the length of the sidelink eDRX cycle.

4. The apparatus of claim 1, wherein the configuration includes information for determining the active time window.

5. 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 the UE ID.

6. 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; send an indication of the one or more parameters; and receive a response to the indication.

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

8. 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.

9. 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 send a response to the indication. ​ 10. 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, the assistance information comprising 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.

11. 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.

12. The apparatus of claim 1, wherein the configuration indicates a starting point of the sidelink eDRX cycle.

13. The apparatus of claim 12, wherein the starting point is an eDRX offset after a start indication to start a sidelink eDRX mode.

14. 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.

15. The apparatus of claim 12, wherein the first UE is a remote UE configured to communicate with a network entity via the second UE.

16. The apparatus of claim 12, wherein the first UE is a relay UE configured to relay communications between the second UE and a network entity.

17. An apparatus for wireless communication at a network entity, 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 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) of an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle comprising a set of hyper-DFNs (H-DFNs); and transmit, to a second UE, an indication of the one or more parameters.

18. The apparatus of claim 17, wherein the one or more processors are further configured to cause the network entity to transmit, after a start indication to start a sidelink eDRX mode, information for an eDRX offset associated with starting a sidelink eDRX mode.

19. 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.

20. A method of wireless communication performed at a first user equipment (UE), the method comprising: negotiating, with a second UE, a configuration associated with waking up in a direct frame number (DFN) of an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle comprising 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 time within the active time window.

21. The method of claim 20, wherein the configuration comprises a length of the sidelink eDRX cycle.

22. 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.

23. The method of claim 20, wherein the configuration comprises information for determining the active time window.

24. The method of claim 23, wherein the information for the active time window comprises a UE identifier (ID) or a hash of the UE ID, and wherein the method comprises calculating a start of the active time window based at least in part on the UE ID or the hash of the UE ID.

25. The method of claim 20, wherein negotiating the configuration comprises: selecting one or more parameters for the sidelink eDRX cycle; sending an indication of the one or more parameters; and receiving a response to the indication.

26. The method of claim 25, wherein negotiating the configuration comprises receiving assistance information, and wherein selecting the one or more parameters comprises selecting the one or more parameters based at least in part on the assistance information.

27. The method of claim 26, wherein the assistance information comprises 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.

28. The method of claim 20, wherein negotiating the configuration comprises: receiving an indication of one or more parameters for the sidelink eDRX cycle; and sending a response to the indication.

29. The method of claim 20, wherein negotiating the configuration comprises sending assistance information comprising 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.

30. A method of wireless communication performed at a network entity, the method 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) of an active time window in a sidelink extended discontinuous reception (DRX) (eDRX) cycle comprising a set of H-DFNs; and sending, to a second UE, an indication of the one or more parameters. ​ ​

Images