Using uwb sidelink and wake-up mechanism of companion device

Abstract

A method and related apparatus for wireless communication at a user equipment (UE) are provided. In the method, the UE transmits, on a sidelink, wake-up monitoring information to a second device for monitoring a first wake-up signal that is based on a physical downlink control channel (PDCCH) to wake up the UE. The UE then receives, on the sidelink, a second wake-up signal from the second device, where the second wake-up signal is based on reception of the first wake-up signal at the second device; and performs a wake-up procedure based on the second wake-up signal.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. nonprovisional patent application serial number 18 / 608,429, filed March 18, 2024, entitled “WAKE UP MECHANISM USING UWBSIDELINK AND COMPANION DEVICES”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates in general to communication systems, and more specifically to wake-up mechanisms using sidelinks and accompanying devices in wireless communications. Background Technology

[0004] 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 may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR are based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a first device are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based on information at least partially stored in the at least one memory, the at least one processor may be configured individually or in any combination to cause the first device to: transmit wake-up monitoring information on a sidelink for a second device to monitor a first wake-up signal for waking up the first device based on a physical downlink control channel (PDCCH); receive a second wake-up signal on the sidelink from the second device, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and perform a wake-up process based on the second wake-up signal.

[0008] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0011] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0012] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0013] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0014] Figure 3 An example aspect of the side link time slot structure is illustrated.

[0015] Figure 4This is a diagram illustrating examples of a first device and a second device that support side-link-based wireless communication.

[0016] Figure 5 An example aspect of sidelink communication between devices is illustrated according to the aspects presented herein.

[0017] Figure 6 An example of an extended reality (XR) business flow is shown.

[0018] Figure 7 This is a diagram illustrating an example sidelink communication between a UE and its accompanying device.

[0019] Figure 8A This is a call flowchart illustrating various aspects of wireless communication methods according to this disclosure.

[0020] Figure 8B This is a call flowchart illustrating various aspects of wireless communication methods according to this disclosure.

[0021] Figure 9 This is a flowchart illustrating a method for wireless communication at a first device according to various aspects of this disclosure.

[0022] Figure 10 This is an illustration illustrating an example of a hardware implementation used in an example device and / or UE.

[0023] Figure 11 This is a diagram illustrating an example of the hardware implementation of a sample network entity. Detailed Implementation

[0024] User equipment (UE) can be woken up by a wake-up signal transmitted by the network via the physical downlink control channel (PDCCH) (e.g., transitioning from a low-power state to an active state, allowing it to receive and transmit data). However, continuously monitoring the PDCCH for a wake-up signal consumes significant power and time, impacting UE battery life and overall user experience. Sidelinks (such as ultra-wideband (UWB) sidelinks) allow UEs to communicate with their companion devices (such as smartwatches or extended reality (XR) glasses) in low-power mode. The example aspects presented herein provide a wake-up mechanism based on sidelink communication that significantly reduces power consumption while providing reliable and low-latency communication.

[0025] Various aspects are involved in wireless communication as a whole. Some aspects involve more specifically wake-up mechanisms using sidelinks and accompanying devices. In some examples, a first device may send wake-up monitoring information to a second device on a sidelink to monitor a first wake-up signal that wakes up the first device based on the Physical Downlink Control Channel (PDCCH). The first device may also receive a second wake-up signal from the second device on the sidelink. The second wake-up signal may be based on the reception of the first wake-up signal on the second device. The first device may then perform a wake-up process based on the second wake-up signal. In some examples, the first device may be a User Equipment (UE), and the second device is an accompanying device of the UE. In some examples, the second device may be a UE, and the first device may be an accompanying device of the UE. In some examples, the first device may be a first accompanying device of the UE, and the second device may be a second accompanying device of the UE. In some examples, the first device may select the second device from a plurality of candidate devices to monitor the first wake-up signal based on the battery status of each candidate device.

[0026] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques enable the power consumption of the wake-up process to be minimized by offloading the task of PDCCH monitoring to a single device within a tightly located group (or cluster) of devices and using a side link (e.g., a UWB side link) for low-power, low-latency communication of the wake-up signal. In some examples, the described techniques ensure reliable wake-up signal detection and transmission, as well as optimal power usage across all devices, by allowing the selection of the most suitable device from the group (or cluster) for wake-up signal monitoring based on current conditions such as battery life.

[0027] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0028] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any 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.

[0029] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0030] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0031] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0032] 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, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0033] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0034] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (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)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0035] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0036] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) 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 the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0037] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 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 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0038] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0039] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration allows the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0040] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 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, SMO framework 105 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 190) via a cloud computing platform interface (such as the O2 interface) to perform network element lifecycle management (such as instantiating virtualized network elements). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0041] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling 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 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0042] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and use AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0043] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each direction, the total number of carriers used for transmission can be up to [number missing]. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number] carriers. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0044] Some UEs 104 can communicate directly with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 can use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™(Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0045] Examples of sidelink communication may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU), vehicle-to-network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), vehicle-to-pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof, and / or vehicle-based communication devices communicating with other devices; these communications can be collectively referred to as vehicle-to-everything (V2X) communication. Sidelink communication may be based on V2X or other D2D communication, such as Proximity Services (ProSe). In addition to the UE, sidelink communication may also be transmitted and received by other transmitting and receiving devices (such as roadside unit (RSU) 107). In some aspects, the PC5 interface can be used to exchange sidelink communication, such as in combination with... Figure 3 The examples described in [the document] are as follows. Although including [other examples] Figure 3 The following description of an example time slot structure can provide an example of sidelink communication combined with 5G NR, but the concepts described herein are applicable to other similar fields such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0046] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0047] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0048] 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 FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0049] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0050] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0051] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0052] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that processes signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0053] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more accompanying devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0054] Refer again Figure 1 In some aspects, UE 104 may include a sidelink wake-up component 198. The sidelink wake-up component 198 may be configured to: transmit wake-up monitoring information on a sidelink to a second device for monitoring a first wake-up signal to wake up UE 104 based on a PDCCH; receive a second wake-up signal on the sidelink from the second device, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and perform a wake-up procedure based on the second wake-up signal. While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0055] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured using slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured using slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured using any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0056] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0057]

[0058] Table 1: Parameter Set, SCS, and CP

[0059] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For the extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols per slot and 2 slots per subframe. µ One time slot. The subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0060] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0061] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0062] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 coherent REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0063] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0064] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0065] Figure 3 Figures 300 and 310 illustrate example aspects of time slot structures that can be used for sidelink communication (e.g., between UE 104, RSU, etc.). In some examples, the time slot structure may be within a 5G / NR frame structure, or may use aspects of a 5G / NR frame structure. In other examples, the time slot structure may be within an LTE frame structure. For example, in some aspects, CV2X communication may use an LTE frame structure. While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar domains such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. Figure 3 The example time slot structure in the diagram is merely an example, and other sidelink communications may have different frame structures and / or different channels for sidelink communication. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Figure 300 illustrates, for example, a single resource block transmitted in a single time slot corresponding to a transmission time interval (TTI) of 0.5 ms. The physical sidelink control channel may be configured to occupy multiple physical resource blocks (PRBs), for example, 10, 12, 15, 20, or 25 PRBs. The PSCCH may be limited to a single subchannel. The PSCCH duration may be configured, for example, 2 or 3 symbols. Subchannels may include, for example, 10, 15, 20, 25, 50, 75, or 100 PRBs. Resources used for sidelink transmissions may be selected from a resource pool comprising one or more subchannels. As a non-limiting example, a resource pool may include between 1 and 27 subchannels. A PSCCH size may be established for the resource pool, for example, to occupy 10% to 100% of a subchannel for a duration of 2 or 3 symbols. Figure 3Figure 310 illustrates an example where the PSCCH occupies approximately 50% of a subchannel, serving as an example to illustrate the concept of the PSCCH occupying a portion of a subchannel. The Physical Sidelink Shared Channel (PSSCH) occupies at least one subchannel. In some aspects, the PSCCH may include a first portion of Sidelink Control Information (SCI), which may be referred to as SCI-1, and the PSCCH may include a second portion of the SCI, which may be referred to as SCI-2. The SCI may indicate information for the receiver to receive data transmissions in the PSCCH. In some aspects, the SCI may indicate the resources on which the PSCCH will be transmitted. In such aspects, the SCI may be referred to as including resource reservation.

[0066] A resource grid can be used to represent frame structure. Each time slot may include a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. Figure 3 As illustrated, some REs in the REs may include control information from the PSCCH, and some REs may include demodulation RS (DMRS). At least one symbol may be used for feedback. Figure 3 An example of two symbols with adjacent gap symbols in a Physical Side Link Feedback Channel (PSFCH) is illustrated. Symbols before and / or after the feedback can be used for the transition between data reception and feedback transmission. This gap allows a device to switch from operating as a transmitting device to preparing to operate as a receiving device, for example, in a subsequent time slot. As illustrated, data can be transmitted in the remaining RE. This data may include the data messages described herein. The positioning of any of the data, DMRS, SCI, feedback, gap symbols, and / or LBT symbols may differ. Figure 3 The example shown illustrates this. In some respects, multiple time slots can be aggregated together. Figure 4 This is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. Figure 4 In the illustrated example, the first wireless device may include a network node such as base station 410, one or more components of a disassembled base station, or an NTN node such as a satellite-based node. The second wireless device may include UE 450. In the example where the second wireless device is a base station, base station 410 may communicate with UE 450 in the access network. Figure 4As shown, base station 410 includes a transmit processor (TX processor 416), a transmitter 418Tx, a receiver 418Rx, an antenna 420, a receive processor (RX processor 470), a channel estimator 474, a controller / processor 475, and at least one memory 476 (e.g., one or more memories). Example UE 450 includes an antenna 452, a transmitter 454Tx, a receiver 454Rx, an RX processor 456, a channel estimator 458, a controller / processor 459, at least one memory 460 (e.g., one or more memories), and a TX processor 468. In other examples, base station 410 and / or UE 450 may include additional or alternative components.

[0067] In the DL, Internet Protocol (IP) packets can be provided to the controller / processor 475. The controller / processor 475 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 475 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0068] TX processor 416 and RX processor 470 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 416 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially pre-decoded to generate multiple spatial streams. The channel estimate from channel estimator 474 can be used to determine the decoding and modulation scheme and for spatial processing. The channel estimate can be derived from a reference signal transmitted by UE 450 and / or channel condition feedback. Each spatial stream can then be provided to different antennas in antenna 420 via a separate transmitter (e.g., transmitter 418Tx). Each transmitter 418Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0069] At UE 450, each receiver 454Rx receives signals via its corresponding antenna in antenna 452. Each receiver 454Rx recovers the information modulated onto the RF carrier and provides this information to RX processor 456. TX processor 468 and RX processor 456 implement Layer 1 functionality associated with various signal processing functions. RX processor 456 can perform spatial processing on the information to recover any spatial stream destined for UE 450. In cases where multiple spatial streams are destined for UE 450, RX processor 456 can combine two or more of these spatial streams into a single OFDM symbol stream. RX processor 456 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 410. These soft decisions can be based on a channel estimate calculated by channel estimator 458. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 410 on the physical channel. The data and control signals are then provided to controller / processor 459, which implements layer 3 and layer 2 functionality.

[0070] The controller / processor 459 may be associated with at least one memory 460 storing program code and data. The at least one memory 460 may be referred to as a computer-readable medium. In the UL, the controller / processor 459 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 459 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0071] Similar to the functionality described in conjunction with DL transmission performed by base station 410, controller / processor 459 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0072] The channel estimate derived by channel estimator 458 from the reference signal or feedback transmitted by base station 410 can be used by TX processor 468 to select appropriate decoding and modulation schemes and facilitate spatial processing. The spatial stream generated by TX processor 468 can be provided to different antennas in antenna 452 via individual transmitters (e.g., transmitter 454Tx). Each transmitter 454Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0073] UL transmission is processed at base station 410 in a manner similar to that described in conjunction with the receiver function at UE 450. Each receiver 418Rx receives the signal via its corresponding antenna in antenna 420. Each receiver 418Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 470.

[0074] The controller / processor 475 may be associated with at least one memory 476 storing program code and data. The at least one memory 476 may be referred to as a computer-readable medium. In the UL, the controller / processor 475 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 475 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0075] At least one of the TX processor 468, RX processor 456, and controller / processor 459 can be configured to combine Figure 1 The sidelink wake-up component 198 is used to perform various aspects.

[0076] At least one of the TX processor 416, RX processor 470, and controller / processor 475 can be configured to combine Figure 1 The sidelink wake-up component 199 is used to perform various aspects.

[0077] Figure 5 Example 500 illustrates sidelink communication between UE 502, UE 504, and UE 506. Communication may be based on, including, combining... Figure 3 The time slot structure of the described aspects. For example, UE 502 may transmit sidelink transmissions that can be received by UE 504 and / or UE 506, such sidelink transmissions including, for example, a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH). The control channel may include information (e.g., SCI) for decoding the data transmission (e.g., PSSCH), including reservation information such as information about time and / or frequency resources reserved for data channel transmissions. For example, the SCI may indicate the number of TTIs and RBs to be occupied by the data transmission. The SCI may also be used by the receiving device to avoid interference by avoiding transmissions on reserved resources. In addition to sidelink reception, UE 502, UE 504, and UE 506 may each be able to perform sidelink transmissions. Such sidelink transmissions may be unicast, broadcast, or multicast to nearby devices. For example, UE 502 may transmit communications intended to be received by other UEs within a range 501 of UE 502. Additionally or alternatively, UE 504 or UE 506 may transmit via sidelink. Sidelink transmission, along with other types of radio transmission, may be transmitted as directional beams, for example, as in combination with... Figure 1 As described in 182 and 184. For example. Figure 5 An example is illustrated where UE 502 transmits using beams 510 and 522 and receives via beam 512. UE 504 transmits using beam 514 and receives using beams 516 and 524. UE 506 transmits using beam 518 and receives using beam 512. One or more of UE 502, UE 504, and UE 506 may include combinations of... Figure 1 The sidelink wake-up component 198 is described. In some aspects, the UE exchanging sidelink communications may be associated with, included in, or located on a vehicle.

[0078] In some aspects, sidelink communication may be based on half-duplex communication, where UE 502, UE 504, and UE 506 transmit and receive at different times, for example, not simultaneously. In other aspects, one or more of UE 502, UE 504, and UE 506 may support full-duplex communication, for example, where the UEs transmit and receive simultaneously (e.g., with at least partial overlap in time) within the same frequency range. Full-duplex communication enables more efficient resource utilization and reduces communication latency. In such an example, link 526 may be a full-duplex link between UE 502 and UE 504. Link 528 may be a full-duplex link for UE 506.

[0079] Sidelink communication can be based on different types or modes of resource allocation mechanisms. In a first resource allocation mode (which may be referred to herein as "Mode 1"), centralized resource allocation can be provided by a network entity. For example, base station 102 can determine resources for sidelink communication and allocate resources to different UEs 104 (e.g., UE 502, UE 504, or UE 506) for sidelink transmission. In this first mode, the UE receives the sidelink resource allocation from base station 102. In a second resource allocation mode (which may be referred to herein as "Mode 2"), distributed resource allocation can be provided. In Mode 2, each UE can autonomously determine the resources for sidelink transmission. To coordinate the selection of sidelink resources by each UE, each UE can use sensing technology to monitor the resource reservations of other sidelink UEs and can select resources for sidelink transmission from unreserved resources. Devices communicating based on sidelinks can determine one or more radio resources used by other devices in the time and frequency domains in order to select transmission resources that avoid conflict with other devices. Sidelink transmission and / or resource reservation can be periodic or aperiodic, whereby the UE can reserve resources for transmission in the current time slot and up to two future time slots (as discussed below).

[0080] Therefore, in this second mode (e.g., mode 2), each UE can autonomously select resources for sidelink transmission, for example, in the absence of a central entity (such as a base station indicating resources for a device). The first UE can reserve the selected resources to notify other UEs about the resources that the first UE intends to use for sidelink transmission.

[0081] In some examples, resource selection for sidelink communication can be based on sensing mechanisms. For instance, before selecting resources for data transmission, the UE can first determine whether the resources have already been reserved by other UEs.

[0082] For example, as part of the sensing mechanism for resource allocation mode 2, the UE can determine (e.g., sense) whether the selected sidelink resource has been reserved by another UE before selecting it for data transmission. If the UE determines that the sidelink resource has not been reserved by another UE, the UE can use the selected sidelink resource for data transmission, for example, in PSSCH transmission. The UE can estimate or determine which radio resources (e.g., sidelink resources) are in use and / or reserved by other UEs by detecting and decoding sidelink control information (SCI) transmitted by other UEs. The UE can use a sensing-based resource selection algorithm to estimate or determine which radio resources are in use and / or reserved by other UEs. The UE can receive an SCI from another UE, which includes reservation information based on a resource reservation field included in the SCI. The UE continuously monitors (e.g., senses) and decodes SCIs from peer UEs. The SCI may include reservation information, for example, indicating the time slot and RB that a particular UE has selected for future transmission. The UE can exclude resources used and / or reserved by other UEs from a candidate resource set used by the UE for sidelink transmission, and the UE can select / reserve resources from unused resources that thus form the candidate resource set for sidelink transmission. The UE can continuously sense SCIs with resource reservations to maintain a candidate resource set from which it can select one or more resources for sidelink transmission. Once the UE selects candidate resources, it can transmit an SCI indicating its own reservation of resources for sidelink transmission. The amount of resources reserved by the UE (e.g., sub-channels per subframe) can depend on the size of the data to be transmitted by the UE. Although this example is described with respect to the UE receiving reservation information from another UE, reservation information can also be received from the RSU or other devices communicating via the sidelink.

[0083] For example, for sidelink transmissions, these resources can be included in a sidelink resource pool. Resource allocation for each UE can be in units of one or more sub-channels in the frequency domain (e.g., sub-channels SC1 to SC4) and can be based on a timeslot in the time domain. UEs can also use resources in the current timeslot to perform initial transmissions and can reserve resources in future timeslots for retransmissions. In this example, UE1 and UE2 are reserving two different future timeslots for retransmissions. Resource reservations can be restricted to a window of predefined timeslots and sub-channels, such as a window of 8 timeslots multiplied by 4 sub-channels as a non-limiting example 500, which provides a total of 32 available resource blocks. This window can also be referred to as a resource selection window.

[0084] Wireless communication systems can support various types of services. As an example of the types of services a wireless network can support, XR services can refer to wireless communications used for technologies such as Virtual Reality (VR), Mixed Reality (MR), and Augmented Reality (AR). VR can refer to technology that immerses users in a simulated experience similar to or different from the real world. Users can interact with VR systems through VR headsets or multi-projection environments that generate realistic images, sounds, and other sensations that simulate the user's physical presence in the virtual environment. MR can refer to technology that blends aspects of virtual and real environments. AR can refer to technology that uses computer-generated perceptual information to enhance objects residing in the real world (sometimes across multiple sensory modalities such as vision, hearing, touch, somatosensory, and / or olfaction). AR systems can combine real and virtual worlds, real-time interaction, and accurate 3D registration of virtual and real objects. In some examples, AR systems can overlay sensory information (e.g., images) onto a natural environment and / or occlude real objects from the natural environment. XR services may include video and / or audio data. XR services can be sent by the base station and received by the UE, or XR services can be sent by the UE and received by the base station.

[0085] XR services can arrive in the form of periodic service bursts (“XR service bursts” or “XR bursts”). XR service bursts can vary in terms of the number of packets in each burst and / or the size of each packet in a burst. Figure 6 Figure 600 illustrates a first XR stream 602 including a first XR service burst 604 and a second XR service burst 606. As illustrated in Figure 600, these service bursts may include different numbers of packets. For example, the first XR service burst 604 is shown with three packets (represented as rectangles in Figure 600), and the second XR service burst 606 is shown with two packets. Furthermore, as illustrated in Figure 600, the three packets in the first XR service burst 604 and the two packets in the second XR service burst 606 may differ in size. That is, the packets within the first XR service burst 604 and the second XR service burst 606 may include different amounts of data.

[0086] XR bursts can arrive in non-integer periods (i.e., in non-integer cycles). These periods can differ from integers for symbols, time slots, etc. In one example, for video data at 60 frames per second (FPS), an XR burst can arrive in a period of 1 / 60 = 16.67 ms. In another example, for video data at 120 FPS, an XR burst can arrive in a period of 1 / 120 = 8.33 ms.

[0087] The arrival time of XR services can vary. For example, an XR service burst may arrive earlier or later than the time the UE (or base station) expects the XR service burst to arrive and be available for transmission. The variability of packet arrival relative to the period (e.g., a 16.76ms period, an 8.33ms period, etc.) can be referred to as "jitter". In one example, the jitter of an XR service can range from -4ms (arriving earlier than expected) to +4ms (arriving later than expected). For example, referring to the first XR stream 602, the UE can expect the first packet of the first XR service burst 604 to arrive at time t0, but the first packet of the first XR service burst 604 arrives at time t1.

[0088] XR services may include multiple streams arriving at the UE (or base station) concurrently with each other (or within a threshold time period). For example, Figure 600 includes a second XR stream 608. The second XR stream 608 may have different characteristics from the first XR stream 602. For example, the second XR stream 608 may have XR service bursts with different numbers of packets, different packet sizes, etc. In one example, the first XR stream 602 may include video data, and the second XR stream 608 may include audio data for the video data. In another example, the first XR stream 602 may include intra-coded image frames (I-frames) containing the complete image, and the second XR stream 608 may include predicted image frames (P-frames) containing changes relative to the previous image.

[0089] The example aspect presented herein provides a wake-up mechanism based on communication between a UE and its surrounding accompanying devices (e.g., smartwatches or XR glasses) via a side link (e.g., a UWB side link). By sharing PDCCH monitoring parameters between the UE and its accompanying devices, this wake-up mechanism allows one device to monitor its interface with the network (e.g., the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN)-UE interface, or the Uu interface) to obtain a wake-up signal (WUS), and upon receiving a WUS for the corresponding device, wakes up the other device on a side link (e.g., a UWB side link).

[0090] XR technology may face the challenge of balancing the computational demands of XR applications with the physical limitations of XR devices, such as weight, power consumption, and head dissipation. XR applications may involve significant processing power to deliver the best user experience, such as high frame rates (e.g., fps). (e.g., 120Hz) and high-quality video formats (e.g., 8K). However, the portability and compactness of XR devices may make lower weight, lower power consumption, and / or heat dissipation a greater priority. Balancing such computing power while reducing weight, power consumption, and heat dissipation can be challenging. In some respects, a method could be used to offload some processing (e.g., some of the XR-related processing tasks) to an accompanying device to reduce the processing load on the XR device.

[0091] In some examples, sidelink communication may include an unlicensed ultra-wideband (UWB) compatible sidelink for communication between the UE and its accompanying equipment. Figure 7 Figure 700 illustrates example sidelink communication between the UE and, as examples, XR glasses 712 and smartwatch 714, which are accompanying devices. Figure 7 In this configuration, UE 702 can communicate with its accompanying devices (such as XR glasses 712 and smartwatch 714) via sidelinks (such as sidelinks 740 and 742). In some examples, this sidelink communication can be UWB sidelink communication. UE 702 can communicate with base station 704 via Uu link 730. In some examples, the accompanying devices can communicate with base station 704 via Uu link. For example, XR glasses 712 can communicate with base station 704 via Uu link 734, and smartwatch 714 can communicate with base station 704 via Uu link 732. In some aspects, the accompanying devices can use UWB sidelink communication to communicate with base station 704 via the UE. UWB sidelinks can be beneficial for XR applications because the accompanying devices (e.g., XR glasses 712, smartwatch 714) can offload some computing tasks and Uu communication with the network (e.g., base station 704) to a nearby UE (e.g., UE 702) via UWB sidelinks. Due to task offloading and the low power consumption of the UWB side link, this offloading mechanism can significantly reduce the power consumption of accompanying devices (e.g., XR glasses 712, smartwatch 714).

[0092] Sidelinks (e.g., sidelinks 740, 742) between a UE (e.g., UE 702) and its accompanying devices (e.g., XR glasses 712, smartwatch 714) can be used to improve the efficiency of the UE's wake-up process. An example aspect provides a wake-up mechanism based on sidelinks (e.g., UWB sidelinks) and accompanying devices. In wireless communication, the UE's accompanying devices (e.g., XR glasses 712 and smartwatch 714) can be equipped with radio frequency (RF) chains, enabling them to communicate directly with a network (e.g., base station 704) on the Uu frequency (e.g., via Uu links 732, 734). Given the close proximity between them and the UE, and between them and each other (e.g., typically only a few meters apart), communication between these devices via sidelinks (e.g., UWB sidelinks) can be performed with lower power consumption and latency. Therefore, the wake-up mechanism of the UE (e.g., UE 702) or accompanying devices (e.g., XR glasses 712 and smartwatch 714) can be improved by utilizing sidelink communication with other accompanying devices. For example, a wake-up mechanism can centralize the task of PDCCH monitoring for a group (or cluster) of devices into a single device within that group (or cluster). This single device can be a UE (e.g., UE 702) or an accompanying device (e.g., XR glasses 712). Upon detecting a relevant PDCCH, the device can initiate a low-power wake-up process via a side link (e.g., a UWB side link). This wake-up mechanism not only simplifies the wake-up process but also significantly reduces the associated power consumption.

[0093] In some examples, the wake-up signal (WUS) transmitted by the network (e.g., base station 704) may be based on the PDCCH. To detect this WUS, the UE's PDCCH monitoring process can be performed exhaustively, covering a wide search space at low signal-to-noise ratios (SNR), and the PDCCH can carry a large payload (e.g., DCI) of up to hundreds of bits. The PDCCH waveform is designed to accommodate these conditions, and its detection at the receiver (e.g., at the UE) can consume significant processing power due to the complex processing involved, including Fast Fourier Transform (FFT), Time Tracking Loop (TTL), channel estimation, demodulation, and polarized channel decoding.

[0094] To improve efficiency and reduce power consumption, PDCCH monitoring tasks for a group of devices can be assigned to individual devices within that group, and a sidelink mechanism can be provided to wake up the appropriate device as needed. For example, refer to... Figure 7For a device group 750 including UE 702, XR glasses 712, and smartwatch 714, the PDCCH monitoring task for the device group 750 can be assigned to a single device within the group 750 (e.g., UE 702 or smartwatch 714), and this single device can send a wake-up signal via a sidelink (e.g., sidelink 740 or 742) to wake up the appropriate device in the group 750. The advantage of using a sidelink wake-up signal lies in its simplicity and robustness. Since a small payload (e.g., a few bits) is sufficient for the sidelink wake-up signal to indicate which device should be woken up, the sidelink WUS waveform can be designed to be more robust to frequency and time deviations or offsets. This simplicity enables a simple, low-power reception process that does not require complex channel estimation or decoding. For example, for sidelink wake-up purposes, a basic correlation with a predefined sequence may be sufficient.

[0095] In some respects, a companion device (e.g., a smartwatch 714 or XR glasses 712) can wake up a UE (e.g., UE 702) or another companion device, and in other respects, a UE (e.g., UE 702) can wake up a companion device (e.g., smartwatch 714 or XR glasses 712). The choice between these methods depends on specific implementation factors, such as the battery capacity of the devices involved. In some examples, given the smaller battery size of the companion device, it may be more practical for the UE (e.g., UE 702) to wake up the companion device (e.g., smartwatch 714 or XR glasses 712). On the other hand, in some examples, the overhead of waking up the UE (e.g., UE 702) may be greater due to the longer wake-up time (compared to the wake-up time of the companion device). Therefore, when a shorter overall wake-up time is desired, it may be preferred for the companion device to initiate the wake-up process. Both of these methods offer a substantial improvement over a wake-up mechanism where each device independently monitors the WUS. Additionally, the wake-up mechanism is scalable and can be extended to more than two devices to allow a single device to monitor the WUS and wake up all other devices within a device group (or cluster), thereby optimizing power consumption and the wake-up process across multiple devices. For example, in group 750, one device (e.g., UE 702) can monitor the WUS for all other devices (e.g., smartwatch 714 or XR glasses 712) and wake up the appropriate device upon receiving the corresponding wake-up signal.

[0096] In some respects, companion devices for the UE can be used to monitor wake-up signals for the UE. This approach avoids the complexity and significant time required for the UE's modem wake-up process. These companion devices can be connected to the UE via a side link (e.g., a UWB side link) and can include, for example, smartwatches and XR glasses. Compared to the UE's modem and wake-up process, the modem and wake-up process of these companion devices may be faster and consume less power.

[0097] Figure 8A This is a call flow diagram 800 illustrating a method of wireless communication according to various aspects of this disclosure. Various aspects are described in conjunction with UE 802, accompanying device 806 of UE 802, and base station 804. In some examples, accompanying device 806 may be a smartwatch 714 or XR glasses 712. These aspects may be performed aggregatedly by UE 802, accompanying device 806, or base station 804, and / or by one or more components of base station 804 (e.g., CU 110, DU 130, and / or RU 140). Accompanying device 806 may communicate with base station 804 via Uu link 842, and accompanying device 806 may communicate with UE 802 via side link 840.

[0098] like Figure 8A As shown, in some examples, UE 802 may use a sidelink 840 (e.g., a UWB sidelink) to signal information related to the wake-up process to accompanying device 806. This information may include, for example, wake-up signal (WUS) PDCCH search space parameters (e.g., at 810), and monitoring timing for monitoring the WUS PDCCH (e.g., at 812). Additionally, UE 802 may report a wake-up indication at 814 via a Uu control message (e.g., a PUCCH) instructing the UE to rely on accompanying device 806 to obtain the wake-up signal, which may potentially result in a longer wake-up time. In some examples, the UE may also publish the minimum time interval between WUS and PDSCH downlink / uplink allocation. In some examples, the minimum time interval between WUS and PDSCH downlink / uplink allocation may be included in the wake-up indication.

[0099] In some examples, at 816, UE 802 and accompanying device 806 may communicate sidelink WUS parameters to each other. Sidelink WUS parameters may include, for example, sequence generation parameters, frequency domain positioning, and time domain positioning of the WUS. Accompanying device 806 is responsible for monitoring the PDCCH at 818 to obtain wake-up signaling (e.g., PDCCH WUS), while UE 802 is responsible for monitoring the sidelink WUS at 820. Upon detecting a PDCCH wake-up signal dedicated to UE 802 (at 828), accompanying device 806 may send the WUS to UE 802 at 830 on sidelink 840 (e.g., a UWB sidelink). Accompanying device 806 may also send downlink control information (DCI) parameters to UE 802 at 832 after sending the WUS (at 830). At 834, UE 802 may perform a wake-up procedure based on the WUS received at 830.

[0100] In some aspects, to facilitate continuous and reliable communication, UE 802 may periodically verify the normal operating condition of companion device 806. For example, UE 802 may send a verification signal (or "keep-alive" signal) at 822 via sidelink 840 (e.g., a UWB sidelink) to ensure that companion device 806 maintains a continuous connection with other devices (e.g., UE 802) and can be used as a wake-up source for other devices (e.g., UE 802) in the vicinity. In some examples, the verification signal may be sent periodically following a periodic pattern. In some examples, each device with a neighboring device serving as its wake-up signal source may send a periodic verification signal (or "keep-alive" signal) to that neighboring device and monitor the response from that neighboring device. At 824, companion device 806 may send a response to the verification signal to UE 802, indicating the normal operating condition of companion device 806. In some examples, when the accompanying device 806 fails to respond to the authentication signal (transmitted at 822), indicating a potential connection loss or battery depletion, UE 802 can revert to independent WUS monitoring mode. For example, when UE 802 fails to receive a suitable response from the accompanying device 806, the UE can begin monitoring PDCCH WUS from the network (e.g., base station 804) at 826 instead of relying on the accompanying device 806 to monitor the wake-up signal.

[0101] In some examples, the device responsible for waking up other devices can dynamically select from multiple candidate devices based on the current status of the involved devices (such as battery status). For example, at 807, UE 802 can exchange control information about its status (such as battery status) with its multiple companion devices (including companion device 806). Through this cooperative communication, UE 802 can select the device in the best state to monitor the wake-up signal at 808, thereby ensuring the most energy-efficient operation possible.

[0102] In some respects, the UE can be responsible for waking up the accompanying device, because the accompanying device may have a smaller battery size and more limited power resources compared to the UE.

[0103] Figure 8B This is a call flowchart 850 illustrating a method of wireless communication according to various aspects of this disclosure. Various aspects are described in conjunction with UE 852, accompanying device 856 of UE 852, and base station 854. In some examples, accompanying device 856 may be a smartwatch 714 or XR glasses 712. These aspects may be performed aggregately by UE 852, accompanying device 856, or base station 854, and / or by one or more components of base station 854 (e.g., CU 110, DU 130, and / or RU 140). UE 852 may communicate with base station 854 via Uu link 892, and UE 852 may communicate with accompanying device 856 via side link 890.

[0104] like Figure 8B As shown, in some examples, the accompanying device 856 may use a side link 890 (e.g., a UWB side link) to signal information related to the wake-up process to the UE 852. This information may include, for example, wake-up signal (WUS) PDCCH search space parameters (e.g., at 862), and monitoring timing for monitoring the WUS PDCCH (e.g., at 864).

[0105] In some examples, at 866, UE 852 and accompanying device 856 can communicate sidelink WUS parameters to each other. Sidelink WUS parameters may include, for example, sequence generation parameters, frequency domain positioning, and time domain positioning of the WUS. UE 852 is responsible for monitoring the PDCCH at 868 to obtain wake-up signaling, while accompanying device 856 is responsible for monitoring the sidelink WUS at 870. Upon detecting a PDCCH wake-up signal dedicated to accompanying device 856 (at 878), UE 852 may send the WUS to accompanying device 856 at 880 on sidelink 890 (e.g., a UWB sidelink). UE 852 may also send DCI parameters to accompanying device 856 at 882 after sending the WUS (at 880). At 884, accompanying device 856 may perform a wake-up procedure based on the WUS signal received at 880.

[0106] In some aspects, the accompanying device 856 can periodically verify the normal operating status of the UE 852. For example, the accompanying device 856 can send an verification signal (or "keep active" signal) at 872 via a side link 890 (e.g., a UWB side link) to ensure that the UE 852 maintains a continuous connection with other devices (e.g., the accompanying device 856) and can be used as a wake-up source for other devices (e.g., the accompanying device 856) in the vicinity. In some examples, the verification signal can be sent periodically. At 874, the UE 852 can transmit a response to the verification signal to the accompanying device 856, indicating the normal operating status of the UE 852. In some examples, when the UE 852 fails to respond to the verification signal (transmitted at 872), indicating a potential connection loss or battery depletion, the accompanying device 856 can begin monitoring PDCCH WUS from the network (e.g., base station 854) at 876, instead of relying on the UE 852 to monitor the wake-up signal.

[0107] Figure 9 This is a flowchart 900 illustrating a method for wireless communication at a first device according to various aspects of the present disclosure. The method can be performed by the first device. The first device can be a UE. The UE can be UE 104, UE 450, UE 702, UE 802, UE 852, or... Figure 10 The hardware implementation of device 1004. By offloading the task of PDCCH monitoring to individual devices within a closely located group (or cluster) of devices, and using side links (e.g., UWB side links) for low-power, low-latency communication of wake-up signals, these methods minimize the power consumption of the wake-up process. Additionally, by allowing the selection of the most suitable device from the group (or cluster) based on current conditions (such as battery life) for wake-up signal monitoring, these methods ensure reliable wake-up signal detection and transmission, as well as optimal power usage across all devices.

[0108] like Figure 9 As shown, at 902, the first device can send wake-up monitoring information to the second device on the side link to monitor the first wake-up signal that wakes up the first device based on the physical downlink control channel (PDCCH). Figure 7 , Figure 8A and Figure 8B This illustrates various aspects of combining the steps of flowchart 900. For example, refer to... Figure 8AThe first device (e.g., UE 802) may send wake-up monitoring information to the second device (e.g., companion device 806) on the side link 840 at 810 and 812 for monitoring the first wake-up signal (e.g., PDCCH WUS at 828) that wakes up the first device (e.g., UE 802) based on the physical downlink control channel (PDCCH). In some aspects, 902 may be performed by the side link wake-up component 198.

[0109] At point 904, the first device can receive a second wake-up signal from the second device on the side link. The second wake-up signal may be based on the reception of the first wake-up signal on the second device. For example, refer to... Figure 8A The first device (e.g., UE 802) may receive a second wake-up signal (e.g., a sidelink WUS at 830) on a sidelink 840 from the second device (e.g., companion device 806) at 830. The second wake-up signal may be based on the reception of a first wake-up signal (e.g., a PDCCH WUS at 828) on the second device (e.g., companion device 806). In some aspects, 904 may be performed by the sidelink wake-up component 198.

[0110] At point 906, the first device can perform a wake-up process based on the second wake-up signal. For example, refer to... Figure 8A The first device (e.g., UE 802) may perform the wake-up procedure at 834 based on a second wake-up signal (e.g., the sidelink WUS at 830). In some aspects, 906 may be performed by the sidelink wake-up component 198.

[0111] In some respects, the first device can be a UE, and the second device can be an accompanying device of the UE. The UE can be UE 104, UE 450, UE 702, or... Figure 10 The hardware implementation of device 1004. For example, refer to Figure 8A The first device can be UE 802, and the second device can be UE 802's accompanying device 806.

[0112] In some respects, the second device can be a UE, and the second device can be an accompanying device of the UE. For example, refer to Figure 8B The second device can be UE 852, and the first device can be UE 852's companion device 856.

[0113] In some respects, the first device may be a first accompanying device of the UE, and the second device may be a second accompanying device of the UE. For example, refer to Figure 7The first device can be a first accompanying device of UE 702 (e.g., XR glasses 712), and the second device can be a second accompanying device of UE 802 (e.g., smartwatch 714).

[0114] In some respects, a sidelink can be an ultra-wideband sidelink. For example, see reference... Figure 7 , Figure 8A and Figure 8B Side links 740, 742, 840, and 890 can be ultra-wideband side links.

[0115] In some aspects, wake-up monitoring information may include one or more of the following: search space parameters for monitoring the first wake-up signal, or monitoring timing for monitoring the first wake-up signal. For example, refer to Figure 8A The wake-up monitoring information may include one or more of the following: search space parameters (at 810) for monitoring the first wake-up signal (e.g., PDCCH WUS at 828), or monitoring timing (at 812) for monitoring the first wake-up signal (e.g., PDCCH WUS at 828).

[0116] In some respects, the first device may send a wake-up instruction to a network entity based on a second wake-up signal, instructing on a wake-up process. The network entity may be... Figure 1 The base station or base station component in the access network, or a core network component (e.g., base station 102, 804; or Figure 10 (Network entity 1002 in the hardware implementation). In some aspects, the first device may send a wake-up indication via the Physical Uplink Control Channel (PUCCH). For example, refer to... Figure 8A A first device (e.g., UE 802) may send a wake-up indication at 814 to a network entity (base station 804). This wake-up indication may indicate a wake-up process based on a second wake-up signal (e.g., the sidelink WUS at 830). In some examples, this wake-up indication may be sent (at 814) via the PUCCH.

[0117] In some aspects, the wake-up indication may also include: a minimum time interval between the first wake-up signal and the downlink or uplink allocation for communicating with the network entity. For example, refer to Figure 8A The wake-up indication (at 814) may include the minimum time interval between the first wake-up signal and the downlink or uplink allocation for communication with the network entity (base station 804).

[0118] In some respects, the first device may communicate side-link wake-up signal (WUS) parameters for the second wake-up signal to the second device. For example, refer to Figure 8AThe first device (e.g., UE 802) may communicate sidelink WUS parameters for the second wake-up signal to the second device (e.g., companion device 806) at 816.

[0119] In some aspects, sidelink WUS parameters may include one or more of the following: sequence generation parameters for the second wake-up signal, frequency domain positioning for the second wake-up signal, or time domain positioning for the second wake-up signal. For example, refer to Figure 8A The sidelink WUS parameters (at 816) may include one or more of the following: sequence generation parameters for the second wake-up signal (e.g., the sidelink WUS at 830), frequency domain positioning for the second wake-up signal (e.g., the sidelink WUS at 830), or time domain positioning for the second wake-up signal (e.g., the sidelink WUS at 830).

[0120] In some respects, after receiving the second wake-up signal, the first device may receive downlink control information (DCI) parameters from the second device. For example, refer to Figure 8A After receiving the sidelink WUS (at 830), the first device (e.g., UE 802) can receive DCI parameters from the second device (e.g., companion device 806) at 832.

[0121] In some aspects, the second device may be one of a plurality of candidate devices, and the first device may select the second device from the plurality of candidate devices to monitor the first wake-up signal. For example, refer to Figure 8A The second device (e.g., accompanying device 806) can be one of a plurality of candidate devices, and the first device (e.g., UE 802) can select the second device (e.g., accompanying device 806) from the plurality of candidate devices at 808 to monitor the first wake-up signal (e.g., PDCCH WUS at 828).

[0122] In some aspects, the first device may select a second device from the plurality of candidate devices to monitor the first wake-up signal based on the battery status of each candidate device. For example, refer to Figure 8A The first device (e.g., UE802) may select a second device (e.g., companion device 806) from the plurality of candidate devices at 808 based on the battery status of each candidate device to monitor the first wake-up signal (e.g., PDCCH WUS at 828).

[0123] In some aspects, the first device can receive control information regarding the battery status of each of the plurality of candidate devices. For example, refer to Figure 8AThe first device (e.g., UE 802) may receive control information for the battery status of each of the plurality of candidate devices from the plurality of candidate devices at 807.

[0124] In some respects, the first device can send an authentication signal to the second device on a side link; and monitor a response signal from the second device in response to the authentication signal. For example, refer to Figure 8A The first device (e.g., UE 802) may send an authentication signal to the second device (e.g., companion device 806) on the side link 840; and monitor the response signal from the second device (e.g., companion device 806) to the authentication signal (e.g., at 824).

[0125] In some respects, the first device can periodically send verification signals to the second device based on periodicity. For example, refer to Figure 8A The first device (e.g., UE 802) may periodically send an authentication signal to the second device (e.g., companion device 806) at 822 based on periodicity.

[0126] In some respects, the first device may monitor the first wake-up signal in response to the absence of a response signal from the second device in response to the verification signal. For example, refer to Figure 8A The first device (e.g., UE 802) may monitor the first wake-up signal (e.g., PDCCHWUS) at 826 in response to the absence of a response signal for the authentication signal from the second device (e.g., companion device 806).

[0127] Figure 10Figure 1000 illustrates an example of a hardware implementation of device 1004. Device 1004 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1004 may include at least one cellular baseband processor (or processing circuitry) 1024 (also referred to as a modem) coupled to one or more transceivers 1022 (e.g., cellular RF transceivers). Cellular baseband processor (or processing circuitry) 1024 may include at least one on-chip memory (or storage circuitry) 1024'. In some aspects, device 1004 may also include one or more Subscriber Identity Module (SIM) cards 1020, and at least one application processor (or processing circuitry) 1006 coupled to a Secure Digital (SD) card 1008 and a screen 1010. Application processor (or processing circuitry) 1006 may include on-chip memory (or memory circuitry) 1006'. In some aspects, device 1004 may also include a Bluetooth module 1012, a WLAN module 1014, an SPS module 1016 (e.g., a GNSS module), one or more sensor modules 1018 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), an additional memory module 1026, a power supply 1030, and / or a camera 1032. Bluetooth module 1012, WLAN module 1014, and SPS module 1016 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1012, WLAN module 1014, and SPS module 1016 may include their own dedicated antennas and / or communicate using antenna 1080. Cellular baseband processor (or processing circuitry) 1024 communicates with UE 104 and / or RU associated with network entity 1002 via transceiver 1022 and one or more antennas 1080. Cellular baseband processor (or processing circuitry) 1024 and application processor (or processing circuitry) 1006 may each include computer-readable medium / memory (or memory circuitry) 1024', 1006'. An additional memory module 1026 may also be considered as computer-readable medium / memory (or memory circuitry). Each computer-readable medium / memory (or memory circuitry) 1024', 1006', 1026 may be non-transitory. Cellular baseband processor (or processing circuitry) 1024 and application processor (or processing circuitry) 1006 are each responsible for general processing, including executing software stored on the computer-readable medium / memory (or memory circuitry).When executed by the cellular baseband processor (or processing circuit) 1024 / application processor (or processing circuit) 1006, the software causes the cellular baseband processor (or processing circuit) 1024 / application processor (or processing circuit) 1006 to perform the various functions described above. The cellular baseband processor (or processing circuit) 1024 and the application processor (or processing circuit) 1006 are configured to perform the various functions described above based at least in part on information stored in a memory (or memory circuit). That is, the cellular baseband processor (or processing circuit) 1024 and the application processor (or processing circuit) 1006 can be configured to perform a first subset of the various functions described above without information stored in the memory, and can be configured to perform a second subset of the various functions described above based on information stored in the memory. The computer-readable medium / memory (or memory circuit) can also be used to store data manipulated by the cellular baseband processor (or processing circuit) 1024 / application processor (or processing circuit) 1006 during software execution. The cellular baseband processor (or processing circuitry) 1024 / application processor (or processing circuitry) 1006 may be a component of the UE 450 and may include at least one of a memory 460 and / or a TX processor 468, an RX processor 456, and a controller / processor 459. In one configuration, the device 1004 may be at least one processor chip (modem and / or application) and may only include the cellular baseband processor (or processing circuitry) 1024 and / or the application processor (or processing circuitry) 1006, and in another configuration, the device 1004 may be the entire UE (see, for example, see below). Figure 4 The UE450 includes an additional module of the device 1004.

[0128] As discussed above, component 198 can be configured to: send wake-up monitoring information to a second device on a side link for monitoring a first wake-up signal that wakes up the UE based on a PDCCH; receive a second wake-up signal from the second device on the side link, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and perform a wake-up procedure based on the second wake-up signal. Component 198 can be further configured to perform a combination Figure 9 Any aspect described in the flowchart and / or by Figure 8AComponent 198 may be any aspect of the UE 802's execution. Component 198 may be within the cellular baseband processor (or processing circuitry) 1024, the application processor (or processing circuitry) 1006, or both. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, apparatus 1004 may include a variety of components configured for various functions. In one configuration, device 1004, particularly cellular baseband processor (or processing circuit) 1024 and / or application processor (or processing circuit) 1006, includes: components for transmitting wake-up monitoring information to a second device on a side link for monitoring a first wake-up signal for waking up the UE based on a PDCCH; components for receiving a second wake-up signal from the second device on the side link, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and components for performing a wake-up process based on the second wake-up signal. Device 1004 may also include components for performing a combination Figure 9 Any aspect described in the flowchart and / or by Figure 8A The components of UE 802 in the device can be any of the aspects of the device. These components can be components 198 of the device 1004 configured to perform the functions described thereby. As described above, the device 1004 may include a TX processor 468, an RX processor 456, and a controller / processor 459. Thus, in one configuration, these components can be the TX processor 468, the RX processor 456, and / or the controller / processor 459 configured to perform the functions described thereby.

[0129] Figure 11Figure 1100 illustrates an example of a hardware implementation of network entity 1102. Network entity 1102 may be a BS, a component of a BS, or implement BS functionality. Network entity 1102 may include at least one of CU 1110, DU 1130, or RU 1140. For example, depending on the layer functionality handled by component 199, network entity 1102 may include: CU 1110; both CU 1110 and DU 1130; each of CU 1110, DU 1130, and RU 1140; DU 1130; both DU 1130 and RU 1140; or RU 1140. CU 1110 may include at least one CU processor (or processing circuitry) 1112. CU processor (or processing circuitry) 1112 may include on-chip memory (or memory circuitry) 1112'. In some aspects, CU 1110 may also include an additional memory module 1114 and a communication interface 1118. CU 1110 communicates with DU 1130 via a midhaul link (such as an F1 interface). DU 1130 may include at least one DU processor (or processing circuitry) 1132. DU processor (or processing circuitry) 1132 may include on-chip memory (or memory circuitry) 1132'. In some aspects, DU 1130 may also include an additional memory module 1134 and a communication interface 1138. DU 1130 communicates with RU 1140 via a fronthaul link. RU 1140 may include at least one RU processor (or processing circuitry) 1142. RU processor (or processing circuitry) 1142 may include on-chip memory (or memory circuitry) 1142'. In some aspects, RU 1140 may also include an additional memory module 1144, one or more transceivers 1146, an antenna 1180, and a communication interface 1148. RU 1140 communicates with UE 104. On-chip memories (or memory circuits) 1112', 1132', 1142' and additional memory modules 1114, 1134, 1144 can each be considered as computer-readable media / memory (or memory circuit). Each computer-readable medium / memory (or memory circuit) can be non-transitory. Each of the processors (or processing circuits) 1112, 1132, 1142 is responsible for general processing, including executing software stored on the computer-readable medium / memory (or memory circuit). When executed by the corresponding processor (or processing circuit), the software causes that processor (or processing circuit) to perform the various functions described above. The computer-readable medium / memory (or memory circuit) can also be used to store data manipulated by the processor (or processing circuit) during software execution.

[0130] As discussed above, component 199 can be configured to perform actions by... Figure 8AThe base station 804 in the system performs any aspect of the process / algorithm. Component 199 may be located within one or more processors (or processing circuitry) of one or more of CU 1110, DU 1130, and RU 1140. Component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1102 may include a variety of components configured for various functions. In one configuration, network entity 1102 includes components for performing the process / algorithm by... Figure 8A The components of the base station 804 in the network can be any of the components in various aspects. These components can be components 199 of the network entity 1102 configured to perform the functions described therein. As described above, the network entity 1102 may include a TX processor 416, an RX processor 470, and a controller / processor 475. Therefore, in one configuration, these components can be the TX processor 416, the RX processor 470, and / or the controller / processor 475 configured to perform the functions described therein.

[0131] This disclosure provides a method for wireless communication at a first device. The method may include: transmitting wake-up monitoring information to a second device on a sidelink for monitoring a first wake-up signal based on a PDCCH to wake up the first device; receiving a second wake-up signal from the second device on the sidelink, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and performing a wake-up process based on the second wake-up signal. By offloading the task of PDCCH monitoring to individual devices within a closely located group (or cluster) of devices, and using a sidelink (e.g., a UWB sidelink) for low-power, low-latency communication of the wake-up signal, these methods minimize the power consumption of the wake-up process. Additionally, by allowing the selection of the most suitable device from the group (or cluster) based on current conditions (such as battery life) for wake-up signal monitoring, these methods ensure reliable wake-up signal detection and transmission, as well as optimal power usage across all devices.

[0132] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of an exemplary approach. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts can be rearranged based on design preferences. Furthermore, some boxes can be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0133] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to execute a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. A processor may be referred to as a processor circuit. A memory / memory module may be referred to as a memory circuit. If a first device receives data from or sends data to a second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices through a set of devices. A device configured to "output" or "provide" data (such as transmission, signaling, or messaging) may, for example, transmit data using a transceiver, or may transmit the data to the device that sent the data.A device configured to "acquire" data (such as, transmit, signal, or message) may receive the data, for example, using a transceiver, or may obtain the data from a device that receives the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," etc., cannot replace the word "component." Therefore, no claim element will be construed as a functional component unless the element is expressly recited using the phrase "component for..."

[0134] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise stated otherwise.

[0135] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0136] Aspect 1 is a method for wireless communication at a first device. The method includes: transmitting wake-up monitoring information for a second device on a side link for monitoring a first wake-up signal that wakes up the first device based on a physical downlink control channel (PDCCH); receiving a second wake-up signal from the second device on the side link, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and performing a wake-up process based on the second wake-up signal.

[0137] Aspect 2 is the method according to aspect 1, wherein the first device is a user equipment (UE) and the second device is an accompanying device of the UE.

[0138] Aspect 3 is the method according to aspect 1, wherein the second device is a user equipment (UE) and the first device is an accompanying device of the UE.

[0139] Aspect 4 is the method according to aspect 1, wherein the first device is a first accompanying device of a user equipment (UE), and the second device is a second accompanying device of the UE.

[0140] Aspect 5 is the method according to any one of Aspects 1 to 4, wherein the side link is an ultra-wideband side link.

[0141] Aspect 6 is the method according to any one of Aspects 1 to 5, wherein the wake-up monitoring information includes one or more of the following: search space parameters for monitoring the first wake-up signal, or monitoring timing for monitoring the first wake-up signal.

[0142] Aspect 7 is the method according to any one of aspects 1 to 6, wherein the method further comprises: sending a wake-up instruction for the wake-up process based on the second wake-up signal to the network entity.

[0143] Aspect 8 is the method according to aspect 7, wherein sending the wake-up indication includes: sending the wake-up indication via the physical uplink control channel (PUCCH).

[0144] Aspect 9 is the method according to aspect 7, wherein the wake-up indication further includes: a minimum time interval between the first wake-up signal and a downlink or uplink allocation for communicating with the network entity.

[0145] Aspect 10 is a method according to any one of aspects 1 to 9, wherein the method further comprises: communicating sidelink wake-up signal (WUS) parameters for the second wake-up signal to the second device.

[0146] Aspect 11 is the method according to aspect 10, wherein the side link WUS parameters include one or more of the following: sequence generation parameters for the second wake-up signal, frequency domain positioning for the second wake-up signal, or time domain positioning for the second wake-up signal.

[0147] Aspect 12 is a method according to any one of aspects 1 to 11, wherein the method further comprises: after receiving the second wake-up signal: receiving downlink control information (DCI) parameters from the second device.

[0148] Aspect 13 is the method according to aspect 1, wherein the second device is one of a plurality of candidate devices, and wherein the method further comprises: selecting the second device from the plurality of candidate devices to monitor the first wake-up signal.

[0149] Aspect 14 is the method according to aspect 13, wherein selecting the second device includes: selecting the second device from the plurality of candidate devices to monitor the first wake-up signal based on the battery status of each candidate device among the plurality of candidate devices.

[0150] Aspect 15 is the method according to aspect 14, wherein the method further includes: receiving control information from the plurality of candidate devices regarding the battery status of each of the plurality of candidate devices.

[0151] Aspect 16 is a method according to any one of aspects 1 to 15, wherein the method further comprises: sending an authentication signal to the second device on the side link for the second device; and monitoring a response signal from the second device for the authentication signal.

[0152] Aspect 17 is the method according to aspect 16, wherein sending the verification signal to the second device includes: periodically sending the verification signal to the second device based on periodicity.

[0153] Aspect 18 is the method according to aspect 16, wherein the method further includes: monitoring the first wake-up signal in response to the absence of the response signal from the second device for the verification signal.

[0154] Aspect 19 is an apparatus for wireless communication at a first device, the apparatus comprising: a processing system including processor circuitry and memory circuitry, the memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the first device to perform the method according to one or more of aspects 1 to 18.

[0155] Aspect 20 is an apparatus for wireless communication at a first device, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured individually or in any combination to perform the method according to any one of aspects 1 to 18.

[0156] Aspect 21 is an apparatus for wireless communication at a first device, the apparatus comprising components for performing each step of the method according to any one of aspects 1 to 18.

[0157] Aspect 22 is an apparatus according to any one of aspects 19 to 21, the apparatus further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 1 to 18.

[0158] Aspect 23 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code at a first device, said code, when executed by at least one processor, causing said at least one processor to perform the method according to any one of aspects 1 to 18, either alone or in any combination.

Claims

1. An apparatus for wireless communication at a first device, the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the first device to: On the side link, wake-up monitoring information is sent to the second device to monitor the first wake-up signal that wakes up the first device based on the physical downlink control channel (PDCCH); Receive a second wake-up signal from the second device on the side link, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and The wake-up process is executed based on the second wake-up signal.

2. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, wherein, in order to transmit the wake-up monitoring information, the at least one processor is configured individually or in any combination to cause the first device to transmit the wake-up monitoring information via the transceiver, and wherein the first device is a user equipment (UE), and the second device is an accompanying device of the UE.

3. The apparatus of claim 1, wherein the second device is a user equipment (UE), and the first device is an accompanying device of the UE.

4. The apparatus of claim 1, wherein the first device is a first accompanying device of a user equipment (UE), and the second device is a second accompanying device of the UE.

5. The apparatus of claim 1, wherein the side link is an ultra-wideband side link.

6. The apparatus of claim 1, wherein the wake-up monitoring information includes one or more of the following: Search space parameters used to monitor the first wake-up signal, or Monitoring timing for monitoring the first wake-up signal.

7. The apparatus of claim 1, wherein the at least one processor is further configured, individually or in any combination, to cause the first device to: Send a wake-up instruction to the network entity based on the wake-up process using the second wake-up signal.

8. The apparatus of claim 7, wherein, in order to send the wake-up instruction, the at least one processor is configured individually or in any combination to cause the first device to: The wake-up indication is sent via the Physical Uplink Control Channel (PUCCH).

9. The apparatus of claim 7, wherein the wake-up indication further comprises: The minimum time interval between the first wake-up signal and the downlink or uplink allocation for communicating with the network entity.

10. The apparatus of claim 1, wherein the at least one processor is further configured, individually or in any combination, to cause the first device to: The second device communicates the sidelink wake-up signal (WUS) parameters used for the second wake-up signal.

11. The apparatus of claim 10, wherein the sidelink WUS parameters include one or more of the following: Sequence generation parameters used for the second wake-up signal, Used for frequency domain positioning of the second wake-up signal, or Used for time-domain positioning of the second wake-up signal.

12. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to cause the first device, after being configured to receive the second wake-up signal: Receive downlink control information (DCI) parameters from the second device.

13. The apparatus of claim 1, wherein the second device is one of a plurality of candidate devices, and wherein the at least one processor is further configured, individually or in any combination, to cause the first device to: The second device is selected from the plurality of candidate devices to monitor the first wake-up signal.

14. The apparatus of claim 13, wherein, in order to select the second device, the at least one processor is further configured, individually or in any combination, to cause the first device to: Based on the battery status of each of the plurality of candidate devices, the second device is selected from the plurality of candidate devices to monitor the first wake-up signal.

15. The apparatus of claim 14, wherein the at least one processor is further configured, individually or in any combination, to cause the first device to: Receive control information regarding the battery status of each of the plurality of candidate devices.

16. The apparatus of claim 1, wherein the at least one processor is further configured, individually or in any combination, to cause the first device to: On the side link, an authentication signal is sent to the second device for the second device; and Monitor the response signal from the second device in response to the verification signal.

17. The apparatus of claim 16, wherein, in order to send the verification signal to the second device, the at least one processor is configured individually or in any combination to cause the first device to: The verification signal is periodically sent to the second device based on a periodicity.

18. The apparatus of claim 16, wherein the at least one processor is further configured, individually or in any combination, to cause the first device to: In response to the absence of a response signal from the second device for the verification signal, the first wake-up signal is monitored.

19. A method for wireless communication at a first device, the method comprising: On the side link, wake-up monitoring information is sent to the second device to monitor the first wake-up signal that wakes up the first device based on the physical downlink control channel (PDCCH); Receive a second wake-up signal from the second device on the side link, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and The wake-up process is executed based on the second wake-up signal.

20. A computer-readable medium storing computer-executable code at a first device, said code, when executed by at least one processor, causing the at least one processor, individually or in any combination, to cause the first device to: On the side link, wake-up monitoring information is sent to the second device to monitor the first wake-up signal that wakes up the first device based on the physical downlink control channel (PDCCH); Receive a second wake-up signal from the second device on the side link, wherein the second wake-up signal is based on the reception of the first wake-up signal on the second device; and The wake-up process is executed based on the second wake-up signal.

Images