Joint design for user equipment cooperation
Patent Information
- Application Number
- PCT/CN2025/084643
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-25
- Publication Date
- 2026-10-01
Smart Images

Figure CN2025084643_01102026_PF_FP_ABST
Abstract
Description
JOINT DESIGN FOR USER EQUIPMENT COOPERATIONTECHNICAL FIELD
[0001] This disclosure relates generally to wireless communication, and more specifically to systems, devices, methods, and techniques associated with joint design for user equipment cooperation. DESCRIPTION OF THE RELATED TECHNOLOGY
[0002] Communication systems are deployed to provide communication services such as voice, video, packet data, messaging, or broadcast, among others. A communication system may include a wireless communication network (such as a radio access network (RAN) ) that supports communication between wireless communication devices such as network entities (such as base stations) , client devices (such as one or more user equipments (UEs) ) , and others. Such devices may communicate with one another using a variety of protocols (such as radio access technologies (RATs) ) , including those of cellular-based systems such as fourth generation (4G) systems (such as Long Term Evolution (LTE) systems) , fifth generation (5G) systems (such as 5G New Radio (5G-NR) systems) , and sixth generation (6G) systems. A wireless communication network may support communication by implementing system resources (such as frequency resources, time resources, spatial resources) in accordance with a wireless communication protocol.SUMMARY
[0003] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein. The following is a summary of some non-limiting aspects of the disclosure:
[0004] A method for wireless communications by a user equipment (UE) is described. The method may include receiving a signal that identifies a target wake time (TWT) configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications, coordinating with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration, and performing the inter-UE communications with the associated UE based on the first wakeup time, on the second wakeup time, or both.
[0005] A UE for wireless communications is described. The UE may include a processing system that includes processor circuitry and memory circuitry that stores code. The processing system may be configured to cause the UE to receive a signal that identifies a TWT configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications, coordinate with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration, and perform the inter-UE communications with the associated UE based on the first wakeup time, on the second wakeup time, or both.
[0006] Another UE for wireless communications is described. The UE may include means for receiving a signal that identifies a TWT configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications, means for coordinating with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration, and means for performing the inter-UE communications with the associated UE based on the first wakeup time, on the second wakeup time, or both.
[0007] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive a signal that identifies a TWT configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications, coordinate with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration, and perform the inter-UE communications with the associated UE based on the first wakeup time, on the second wakeup time, or both.
[0008] Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for selecting, based on the coordinating with the associated UE, a TWT pattern from the set of TWT patterns, where the first wakeup time and the second wakeup time may be based on the TWT pattern.
[0009] In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the TWT configuration identifies a TWT pattern for use by the UE and the associated UE and the first wakeup time and the second wakeup time may be based on the TWT pattern.
[0010] Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for coordinating with the associated UE may be based on uplink communications from the UE, from the associated UE, or both.
[0011] In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the TWT configuration may be based at least in part on the uplink communications from the UE, from the associated UE, or both.BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1 shows an example of a wireless communication system.
[0013] Figure 2 shows an example of a signaling diagram that supports joint design for user equipment (UE) cooperation.
[0014] Figure 3 shows an example of a TWT configuration that supports joint design for UE cooperation.
[0015] Figure 4 shows an example of a TWT configuration that supports joint design for UE cooperation.
[0016] Figure 5 shows an example of a TWT configuration that supports joint design for UE cooperation.
[0017] Figure 6 shows a block diagram of a processing system that supports joint design for UE cooperation.
[0018] Figure 7 shows a diagram of a system including a device that supports joint design for UE cooperation.
[0019] Figures 8 through 10 show flowcharts illustrating methods that support joint design for UE cooperation.
[0020] Details of aspects and advantages of the subject matter in this disclosure are set forth in the drawings and accompanying descriptions. Like reference numbers and designations in the various drawings indicate like elements.DETAILED DESCRIPTION
[0021] A communication system may include a radio access network (RAN) that supports wireless communication. Communication of a RAN may be performed in accordance with one or more radio access technologies (RATs) , including 4G, 5G, or 6G, among others, including technologies not explicitly mentioned herein. A RAT may employ access technologies (such as multiplexing technologies) including code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , single-carrier FDMA (SC-FDMA) , time division synchronous code division multiple access (TD-SCDMA) , or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) , among others. A RAT may support one or more service types, including machine type communication (MTC) , massive MTC (mMTC) , Internet of Things (IoT) , narrowband IoT (NB-IoT) , reduced capability (RedCap) , enhanced mobile broadband (eMBB) , ultra-reliable low-latency communication (URLLC) , or public safety, among others.
[0022] To support these and other target verticals, a communication system (such as a RAN) may be designed to implement one or more of a modularized functional infrastructure, a disaggregated and service-based network architecture, network function virtualization, network slicing, multi-access edge computing, spatial processing or multipath techniques, IoT or RedCap device connectivity and management, industrial connectivity, licensed and unlicensed spectrum access, sidelink or other device-to-device (D2D) direct communication (such as vehicle-to-everything (V2X) ) , frequency spectrum expansion, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, device aggregation, advanced duplex communication (such as sub-band full-duplex (SBFD) ) , multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, network energy savings (NES) , low-power signaling and radios, or artificial intelligence or machine learning (AI / ML) , among other examples.
[0023] The foregoing and other technological improvements may support use cases such as voice calls, messaging, data transfer, streaming, wireless data centers, extended reality (XR) and metaverse applications, vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage using non-terrestrial or aerial platforms, among other examples. As the demand for connectivity continues to increase, further improvements may be implemented, and other RATs, including 6G and beyond, may be introduced to enable new applications and use cases. The systems, methods, and devices described herein may enable one or more of the foregoing technologies or new technologies or support one or more of the foregoing use cases or new use cases.
[0024] In some wireless communication systems, user equipment (UE) may be associated with each other, such as being in a cooperating scenario. A UE may assist an anchor UE for data transmissions or other functions when operating in a cooperating mode. In some cases, the cooperating UE (the UEs that are collectively cooperating with each other) may perform inter-UE communications using various cellular or non-cellular wireless technologies (e.g., inter-UE communications using Wi-Fi, Bluetooth, sidelink, or other technology) . As one example, the cooperating UE may perform the inter-UE communications via a Wi-Fi technology where separate target wake time (TWT) configurations are configured for each of the cooperating UE. This may result in a communication loss between the cooperating UE, such as when one UE is in the TWT sleep mode while the other UE is in the TWT wake state.
[0025] Aspects of the subject matter described in this disclosure relate to improved TWT configuration coordination between cooperating UE. For example, a TWT configuration that is common, shared, or otherwise coordinated between the cooperating UE may be used to align or otherwise configure the TWT wake and sleep periods of the cooperating UE. The TWT configuration may provide for time alignment (e.g., at least to some degree) between the wake state and sleep states of the cooperating UE. For example, one UE may receive or otherwise obtain a signal (e.g., from a network entity of the cellular network) that identifies a TWT configuration for application between the UE and an associated UE. In some cases, the TWT configuration may identify a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications. The first wakeup time and the second wakeup time may be overlapping in a time domain or may be non-overlapping in the time domain (e.g., the second wakeup time may be offset from the first wakeup time according to an offset or time gap) . The cooperating UE may coordinate (e.g., with the associated UE) to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration. Accordingly, the cooperating UE may perform the inter-UE communications based at least in part on the first wakeup time, on the second wakeup time, or both.
[0026] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by coordinating the TWT wake and sleep periods of the cooperating UE, the described techniques can be used to improve the inter-UE communications between the cooperating UE. The coordinated TWT wake and sleep periods may allow for one UE to provide improved services and / or functions to a cooperating UE, such as when the cooperating UE is a reduced capability (RedCap) UE, is located at a cell edge, or is otherwise unable to support ongoing and substantive wireless communications with the cellular network.
[0027] Figure 1 shows an example of a wireless communication system 100. The wireless communication system 100 includes a core network 150 and a RAN 120 that support communication with one or more devices, such as UEs 115. A RAN 120 may include one or more network entities 105 configured to support wireless communication with the UEs 115.
[0028] The wireless communication system 100 may support communication among network entities 105 and UEs 115 in accordance with a layered protocol stack. For example, in a user plane, communication at a bearer layer, a Packet Data Convergence Protocol (PDCP) layer, or Service Data Adaption Protocol (SDAP) layer may be Internet Protocol (IP) -based. A Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate via logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. A MAC layer also may implement error detection techniques, error correction techniques, or retransmissions. In a control plane, a Radio Resource Control (RRC) layer may provide establishment, configuration, and maintenance of an RRC connection between UEs 115 and a network entity 105 or a core network 150, supporting radio bearers for user plane data. A Physical (PHY) layer may map transport channels to physical channels.
[0029] A core network 150 may support user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions (such as via network entities 105) . A core network 150 may be a 5G core (5GC) or 6G core (6GC) , and may include at least one control plane entity that manages access and mobility and at least one user plane entity that routes packets or interconnects to external networks (such as a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , a user plane function (UPF) ) .
[0030] A network entity 105 may support wireless communication in accordance with one or more coverage areas 110, and may be referred to as a network element, a network node, a RAN node, or network equipment, among other nomenclature. One or more of the network entities 105 may include or may be referred to as a base station. Depending on its capabilities, a base station may be referred to as a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a 6G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology. The wireless communication system 100 may include a heterogeneous network in which different types of network entities 105 support communication for one or more coverage areas 110 using the same or different RATs.
[0031] In some examples, a network entity 105 may be implemented in an aggregated (such as monolithic, standalone) architecture, which may utilize a protocol stack that is physically or logically integrated within one network entity 105 (such as a single physical RAN node) . In some other examples, a network entity 105 may be implemented in a disaggregated architecture, which may utilize a protocol stack that is physically or logically distributed among multiple network entities 105, including in an integrated access and backhaul (IAB) network, an open RAN (O-RAN) , or a virtualized RAN (vRAN) . In a disaggregated architecture, a network entity 105 may include or be referred to as one or more of a central unit (CU) (such as CU 160) , a distributed unit (DU) (such as DU 165) , a radio unit (RU) (such as RU 170) , or a combination thereof. The wireless communication system 100 may also implement a service-based architecture that provides a modular framework in which control plane functionality and common data repositories may be delivered through a set of interconnected network functions (NFs) that may access services of other NFs.
[0032] UEs 115 may be located in a coverage area 110 of one or more network entities 105 and may include or be referred to as an access terminal, a mobile station, a client device, or a subscriber unit. A UE 115 may be, include, or be coupled with a cellular phone, a wireless modem, a tablet device, a laptop computer, a wireless local loop (WLL) station, a camera, a medical or biometric device, a wearable device, a gaming device, an entertainment device, an XR device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Positioning System (GPS) or other positioning device, a robot or other device implementing artificial intelligence, a UE function of a network node, or any other wireless communication device or function that may communicate using a wireless medium.
[0033] The wireless communication system 100 may support various types of communication links among devices. For example, wireless communication between a network entity 105 and a UE 115 may be supported using one or more of a communication link 125 (such as a Uu interface) , which may include downlink communication from a network entity 105 to a UE 115, uplink communication from a UE 115 to a network entity 105, or both. Direct wireless communication between UEs 115 may be supported using a communication link 135 (such as a device-to-device (D2D) communication link, a sidelink, a PC5 interface) .
[0034] Communication between a network entity 105 and a core network 150 may be supported using a backhaul link 132 (such as an S1, N2, N3, NG, or other interface) . In some implementations, communication between network entities 105 may be supported using a backhaul link 132 (such as an X2, Xn, or other interface) either directly (such as directly between network entities 105) or indirectly (such as via a core network 150) . In some implementations (such as in a disaggregated architecture) , communication between a CU 160 and a DU 165 may be supported using a midhaul link 162, and communication between a DU 165 and an RU may be supported using a fronthaul link 168. A backhaul link 132, a midhaul link 162, a fronthaul link 168, or any combination thereof may be or include one or more wired links (such as an electrical link, an optical fiber link) or one or more wireless links (such as a radio link, a wireless optical link) , among other examples or combinations thereof. Wireless backhaul, midhaul, or fronthaul may be implemented via one or more IAB nodes 104, which may act as a relay using resources of an IAB donor network entity 105 (such as via a wireless link 130) .
[0035] The wireless communication system 100 may include one or more of a relay 172 that may steer or reflect signals transmitted by other entities, which may support any of the described communication links. A relay 172 may include active elements or passive elements and may be in the form of a reconfigurable intelligent surface (RIS) . An RIS may include tunable reflecting antenna arrays or metasurfaces, which may be used to enhance coverage or efficiency in multipath environments.
[0036] Network entities 105 and UEs 115 each may include one or multiple antennas. Multiple antennas of such devices may be used to employ techniques such as transmit diversity, receive diversity, MIMO communication, or beamforming, and may be organized or structured as one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. As used herein, the term “antenna” may refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. The term “antenna panel” may refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters associated with the group of antennas. In some implementations, an antenna panel may support RF beamforming for a signal transmitted or received via an antenna port. The term “antenna module” may refer to circuitry including one or more antennas as well as one or more other components (such as filters, amplifiers, processors, beamformers) associated with integrating the antenna module into a device such as a network entity 105 or a UE 115.
[0037] Beamforming, such as directional transmission or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (such as at a network entity 105, at a UE 115) to shape or steer a beam 175 (such as an antenna beam, a transmit beam, a receive beam) along a spatial path (such as along a direction) , which may include one or more paths between a transmitting device and a receiving device. Beamforming may be achieved by combining signals communicated via multiple antenna elements of an antenna array such that signals propagating along some orientations (such as relative to the antenna array) experience constructive interference while others may experience destructive interference. Adjustments of signals communicated via the antenna elements may include a transmitting device or a receiving device applying phase offsets, amplitude offsets, or both to signals carried via (such as transmitted by, received by) antenna elements of the device, which may be defined by a beamforming weight set associated with a particular orientation (such as relative to the antenna array of the device) .
[0038] Communication resources of the wireless communication system 100 (such as of a RAN 120) may refer to a resource in the frequency domain (such as a frequency resource, an RF resource) , a resource in the time domain (such as a time resource) , a resource in the spatial domain (such as a spatial resource, a spatial layer) , or a combination thereof. The wireless communication system 100 may leverage orthogonality of such resources to convey different communications to or from different devices (such as for a communication link 125, for a communication link 135, for unicast communication, for multicast communication, for broadcast communication) .
[0039] A frequency resource may refer to a frequency or range of frequencies (such as a bandwidth, a frequency channel) of a frequency band implemented for wireless communication. For example, a frequency resource may refer to a resource of a lower frequency band (such as Frequency Range 1 (FR1) , between 425 MHz and 7.125 GHz) , a mid-band (such as Frequency Range 3 (FR3) , between 7.125 GHz and 24.25 GHz) , or an upper frequency band (such as Frequency Range 2 (FR2) , between 24.25 GHz and 71 GHz) . Communication in the upper frequency band may be referred to as millimeter wave (mmW) communication, and communication above an upper frequency band (such as between mmW and THz frequencies, between 100 GHz and 1 THz) may be referred to as sub-Terahertz (sub-THz) communication.
[0040] A frequency resource may refer to a “carrier” (such as a frequency channel) , or portion thereof, and a carrier bandwidth may be referred to as a “system bandwidth. ” A carrier may be subdivided in the frequency domain, including into subcarriers, bandwidth parts (BWPs) , or both. For example, a resource block (RB) , such as a physical resource block (PRB) , may be defined in accordance with a set of subcarriers (such as twelve consecutive subcarriers in the frequency domain) , and a BWP may be configured in accordance with a set of RBs (such as a set of contiguous RBs) .
[0041] A frequency resource may be configured to carry either downlink communication or uplink communication (such as in a frequency division duplexing (FDD) configuration) or may be configured to carry both downlink and uplink communication (such as in a time division duplexing (TDD) configuration, in a sub-band full duplex (SBFD) configuration) . One or more numerologies for a carrier may be supported, each associated with a subcarrier spacing (SCS) and a cyclic prefix (CP) . Supported numerologies may vary by frequency range (such as FR1, FR2, FR3) , and a carrier may be divided into portions (such as BWPs) having the same or different numerologies. BWPs may be configured as uplink BWPs or downlink BWPs (such as by a network entity 105) , including in response to network conditions (such as to allocate uplink and downlink BWPs in response to traffic conditions) , device capability (such as allocating BWPs with a greater quantity of RBs to UEs 115 with relatively higher capabilities) , or both. A UE 115 may be configured with a set of multiple BWPs (such as a set of uplink BWPs, a set of downlink BWPs, or both) , and a single BWP of a set (such as an active UL BWP, an active DL BWP, or both) may be active at a given time, such that communication of a UE 115 is supported by active BWP (s) .
[0042] A time resource may refer to a duration of a frame (such as a radio frame, a frame structure) , or portion thereof. For example, a frame may span a duration of 10 ms, and each frame may be identified by a system frame number (SFN) . A frame may be subdivided in the time domain, including into subframes, slots, mini-slots, or a combination thereof. Slots or mini-slots may each include a respective quantity of symbols (such as symbol durations, symbol periods, OFDM symbols) , which may be a function of a configured CP. A duration of a symbol is a function of the SCS or frequency band of operation.
[0043] A spatial resource may refer to an antenna, an antenna direction, an antenna port, a signal direction (such as a beamforming direction) , or other resource that supports spatial orthogonality. A device (such as a network entity 105, a UE 115) may perform communications of a given frequency resource and time resource with a single spatial resource (such as communication without regard to spatial orthogonality) . Additionally, or alternatively, a device may implement multiple spatial resources to support multiple signal streams using resources that are overlapping in the time and frequency domains (such as to support MIMO techniques) .
[0044] Signals of the wireless communication system 100 (such as of a RAN 120) may be communicated using one or more resource elements (REs) , and an RE may refer to a resource that corresponds to one subcarrier in the frequency domain and one symbol in the time domain. An RE may be used to convey a modulation symbol corresponding to one or more bits of information (such as of a physical channel, of a reference signal) in accordance with a modulation scheme. For example, a quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM) technique may be implemented to communicate one or more bits that are distinguished in accordance with phase components, amplitude components, or both of a signal conveyed using a RE. A quantity of bits carried by an RE may depend on an order of the modulation scheme, and a relatively higher order may correspond to a relatively higher rate of communication. A device may support communication of REs using multiple subcarriers concurrently by implementing multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) , among others.
[0045] Physical channels may carry information using modulation symbols conveyed by corresponding REs. Physical shared channels (such as for communicating user data) may include a physical downlink shared channel (PDSCH) for communicating user data in a downlink direction and a physical uplink shared channel (PUSCH) for communicating user data in an uplink direction. Physical control channels (such as for managing communication via physical channels) may include a physical downlink control channel (PDCCH) for communicating downlink control information (DCI) and a physical uplink control channel (PUCCH) for communicating uplink control information (UCI) . A network entity 105 may indicate (such as schedule, allocate) communication resources for a UE 115 using DCI, including indicating downlink resources of a PDSCH (such as in accordance with a downlink grant) , uplink resources of a PUSCH (such as in accordance with an uplink grant) , or a combination thereof. A control region (such as a control resource set (CORESET) ) for a physical control channel may be configured in accordance with a pattern of REs in the time and frequency domains, and one or more control regions may be configured for a set of UEs. A UE 115 may monitor control regions for control information according to one or more search space sets, which may include a common search space set (such as for sending control information to one or more UEs 115) , UE-specific search space sets (such as for sending control information to a UE 115) , or a combination thereof. A physical broadcast channel (PBCH) may be used to broadcast parameters to UEs 115 to synchronize with a network entity 105 and establish communications (such as to establish a communication link 125) .
[0046] Reference signals may be communicated to establish reference characteristics (such as a frequency reference, a temporal reference, a spatial reference, a signal quality reference) between devices of a RAN 120, which may support communication using physical channels. Reference signals communicated between network entities 105 and UEs 115 may include synchronization signals (such as a primary synchronization signal (PSS) , a secondary synchronization signal (SSS) ) that support temporal synchronization, channel state information-reference signals (CSI-RSs) that support evaluating downlink channel characteristics, sounding reference signals (SRSs) that support evaluating uplink channel characteristics, demodulation reference signals (DMRSs) that support demodulation, or phase tracking reference signals (PTRSs) for evaluating oscillator characteristics, among others. Network entities 105 and UEs 115 may receive and measure transmitted reference signals to support one or more of these and other functions.
[0047] Devices of the wireless communication system 100 may be configured to support one or more aspects of the described techniques for joint design for UE cooperation. For example, a UE 115 may include a processing system 140, and a network entity 105 may include a processing system 145, each of which may be configured to cause the respective device to perform (such as being configured as means for performing) one or more of the described operations. By configuring a processing system 140, a processing system 145, or a combination thereof in accordance with the described techniques, the communication system 100 (such as the RAN 120) may support UE level coordination regarding a TWT configuration to be applied by cooperating UE.
[0048] Figure 2 shows an example of a signaling diagram 200 that supports joint design for UE cooperation. Aspects of the signaling diagram 200 may implement aspects of or be implemented by aspects of the wireless communication system 100. Aspects of the signaling diagram 200 may be implemented at or implemented by a UE 205, a UE 210, and a network entity 215, which may be examples of the corresponding devices described herein.
[0049] Some wireless networks may support a low power wakeup signal (LP-WUS) where the UE monitors the LP-WUS to determine whether to monitor PDCCH (e.g., a paging PDCCH for idle or inactive mode and / or data scheduling PDCCH for connected mode UE) . The LP-WUS may save UE power because PDCCH monitoring is generally the power bottleneck in legacy UE operations. The LP-WUS can be generated by on-off keying (OOK) modulation and detected by a simple envelope detector at the UE. Decoding a result of the PDCCH monitoring may consume more power than the detection of the LP-WUS. Using the LP-WUS to trigger PDCCH monitoring saves more UE power, especially for sporadic data scheduling. In some cases, the UE may include a LP wakeup receiver (LP-WUR) and a main radio (MR) (which is just the current wireless transceiver) . When the LP-WUR is enabled to monitor the LP-WUS, the MR may be put into a sleep mode for power savings. Once the LP-WUS is received that triggers PDCCH monitoring for the UE, the MR may be switched to a wake state (e.g., an active state) for the UE to monitor PDCCH (s) .
[0050] Moreover, some UE may be configured or otherwise support UE cooperation. For example, the cooperating UE may be UE that are associated with each other or are otherwise cooperating to support wireless communications. For example, a companion UE may assist an anchor UE for data transmission in the uplink and / or downlink in a cooperation mode. This cooperation may save power for the anchor UE because partial data communications are performed by the companion UE. This cooperation may also speed up the data rate transmission on two legs.
[0051] In some cases, the cooperating UE may be performing wireless communications with a network entity (e.g., using a cellular link, such as a Uu or PC5 interface) and be performing inter-UE communications using a cellular link or a non-cellular link (e.g., a Wi-Fi link) . Such Wi-Fi inter-UE communications may generally include various Wi-Fi related operations and / or configurations that are generally blind from the perspective of the network entity. For example, data exchanges between the anchor UE and the companion UE may include Wi-Fi based communications. Such Wi-Fi based communications may include a TWT as an important feature for power saving operations within a Wi-Fi network. The TWT mechanism configures a UE stay in a sleep state or mode when there is no data to transmit or receive so that the power consumption of the UE can be reduced by TWT configuration operations. However, the network entity associated with the cooperating UE generally does not generally manage the Wi-Fi configuration or operations for the inter-UE communications.
[0052] Thus, in some cases the cooperating UE may include an anchor UE that has two connections. One connection may include a direct connection to the network entity 215 as well as an indirect connection to the network entity 215 through the companion UE. A cellular interface (e.g., a Uu interface) full stack may be established at the anchor UE. The inter-UE communication link between the companion UE and the anchor UE may be a 3GPP based link or a non-3GPP link. In some cases, the companion UE may have a split architecture (e.g., layer two (L2) , layer three (L3) , a high physical (PHY) layer, and a low PHY layer) . The cooperation between the UEs may be performed via the uplink and / or via the downlink. As one example, the anchor UE may include a smart watch, alternative reality (AR) glasses, etc. ) where the companion UE may include a smartphone, AR glasses, etc. ) .
[0053] Moreover, in a downlink scenario the network entity, a user plane function (UPF) , or a server application may split the downlink traffic for the companion UE and the anchor UE. In some cases, the traffic may be expected to be decoded at UE side by the anchor UE (e.g., extended reality (XR) -like traffic may be associated with a tight latency, such as 10 ms) . In the uplink, the anchor UE may split the uplink traffic and expect to transmit to the companion UE first and then the companion UE helps to transmit to the network entity for the anchor UE. However, in some cases there may be a TWT wake interval mismatch with the downlink traffic, which may lead to traffic that has arrived that cannot be transmitted to the anchor UE, which may violate the required latency by the additional latency of TWT. Another issue may include the TWT wake interval mismatch with the uplink traffic. After the traffic split at the anchor UE, the companion UE may stay in a sleep state. In this case, the anchor UE cannot transmit the split traffic to the companion UE with a short latency.
[0054] Thus, the mismatch between the uplink and / or downlink traffic (such as XR traffic) and the TWT wake interval may result in some transmission failures between the cooperating UE. For example, only the traffic that overlaps with wake-up state of TWT configuration can be transmitted successfully to the cooperative UE.
[0055] Accordingly, aspects of the techniques described herein may provide for the network entity (e.g., the network entity 215) to instruct the anchor UE and the companion UE to coordinate TWT wake interval (e.g., based on cadence of XR traffic or other traffic) . In some cases, the network entity 215 may be aware of the cadence of the downlink XR traffic so the network entity 215 may indicate to the anchor UE and the companion UE to coordinate suitable TWT wake interval (s) based on the downlink traffic cadence.
[0056] For example, at 220 the network entity 215 may transmit or otherwise output (and the UE 205, the UE 210, or both UEs may receive or otherwise obtain) a signal that carries or otherwise conveys information that identifies a TWT configuration for application between the UE 205 and the UE 210. The UE 210, in this example, may be considered an associated UE from the perspective of the UE 205. That is, the UE 205 and the UE 210 may be cooperating UEs according to the techniques described herein. The signal identifying the TWT configuration may be a radio resource control (RRC) signal, a medium access control-control element (MAC-CE) signal, a downlink control information (DCI) signal, or other signaling means.
[0057] The TWT configuration may generally identify a first wakeup time for the UE 205 and a second wakeup time for the UE 210. The first wakeup time and the second wakeup time may be used for inter-UE communications between the UE 205 and the UE 210. For example, the first wakeup time and the second wakeup time may be used for inter-UE communications according to a cellular radio access technology (RAT) (e.g., a Uu interface RAT and / or a PC5 interface RAT) and / or according to a non-cellular RAT (e.g., a Wi-Fi RAT, a Bluetooth RAT, or any other non-cellular RAT) .
[0058] In some cases, the signal carrying the information identifying the TWT configuration may identify a set of TWT patterns. For example, the network entity 215 may configure several TWT wake interval patterns (e.g., a plurality of TWT patterns or more than one TWT pattern) to the cooperating UE (s) . In some cases, the network entity 215 may request that the anchor UE and the companion UE use a specific TWT pattern on a dynamic basis. For example, the signal identifying the TWT configuration may be an RRC signal where the network entity 215 transmits or otherwise outputs (and the UE 205, the UE 210, or both, receive or otherwise obtain) a MAC-CE and / or a DCI signal that dynamically requests the cooperating UEs to use one of the specific TWT patterns from the set of TWT patterns. In some cases, the UEs may select (e.g., via coordination between the UEs) the TWT pattern from the set of TWT patterns without being requested by the network entity 215 to use a specific TWT pattern. Accordingly, and in either scenario, the UE (s) may select a TWT pattern from the set of TWT patterns. The selected TWT pattern may generally identify or otherwise define the TWT wake times (e.g., the first wakeup time and / or the second wakeup time) . As discussed, in some cases the UEs may select the TWT pattern based on or using inter-UE coordination.
[0059] In some cases, the network entity 215 may update the TWT patterns (e.g., based on evolving or changing traffic conditions or patterns) . For example, the network entity 215 may transmit or otherwise output (and the UE 205, the UE 210, or both UEs may receive or otherwise obtain) a second signal that includes one or more updates to the TWT configuration. The update (s) , in this example, may include changes to one or more of the TWT patterns in the set of TWT patterns and / or to a specific TWT pattern identified in the TWT configuration.
[0060] In some cases, the signal identifying the TWT configuration may indicate a specific TWT pattern to be used for defining or otherwise identifying the first wakeup time and the second wakeup time. That is, the network entity 215 may indicate to the cooperating UEs a specific TWT wake interval (e.g., in each downlink transmission) . The indication may be signaled to the cooperating UEs via a scheduling DCI and / or via a non-scheduling DCI, a downlink MAC-CE, and / or a PDSCH transmission from the network entity 215. Accordingly, in this example the TWT configuration may carry or otherwise convey information that identifies a TWT pattern for use by the UE (e.g., the UE 205, in this example) and the associated UE (e.g., the UE 210, in this example) . Again, the first wakeup time and the second wakeup time may be based on the TWT pattern indicated in the TWT configuration.
[0061] Accordingly, at 225 the UE 205 and the UE 210 may coordinate to establish the first wakeup time for the UE 205 and the second wakeup time for the UE 210 according to the TWT configuration. As discussed, the TWT configuration may identify the TWT pattern (e.g., the wake up times) or the network entity 215 may dynamically indicate the TWT pattern to be used by the cooperating UEs. The UE 205 and the UE 210 may perform inter-UE communications based at least in part on the first wakeup time and / or the second wakeup time. In some cases, the first wakeup time and the second wakeup time are fully overlapping or at least partially overlapping in the time domain such that both UEs are in a wake or active state to support the inter-UE communications. In some cases, the first wakeup time and the second wakeup time are non-overlapping in the time domain, which may support assisted communications and / or paging operations for the cooperating UEs. For example, a time gap may be defined between the wakeup times that allows the UE 205 to decode, process, etc., communications associated with the UE 210 and then communicate information based on the result of the decoding, processing, etc., to the UE 210 during its wake time.
[0062] Accordingly, the techniques described herein provide for the network entity 215 to manage at least some aspects of the TWT configuration used for inter-UE communications between cooperating UEs. The managed TWT configuration may ensure that each cooperating UE is in a wake state to support the inter-UE communications and cooperation. This may support an indirect communication link between the UE 210 and the network entity 215 via the UE 205 as well as a direct link between the UE 210 and the network entity 215. The UE 205 (e.g., the companion UE in this example) may have a direct link with the network entity 215. The UE 205 and the UE 210 (e.g., the cooperating UEs) may have a direct communication link, such as a 3GPP link and / or a non-3GPP link.
[0063] Figure 3 shows an example of a TWT configuration 300 that supports joint design for UE cooperation. Aspects of the TWT configuration 300 may be implemented by or may implement aspects of the wireless communications system 100 and / or aspects of the signaling diagram 200. Aspects of the TWT configuration 300 may be implemented at or implemented by a UE and / or a network entity, which may be examples of the corresponding devices described herein.
[0064] The techniques described herein provide for a network entity to manage aspects of a TWT configuration to be applied between cooperating UEs. For example, the network entity may transmit a signal (e.g., an RRC signal) to one or both of the cooperating UEs that identifies a TWT configuration to be applied by the UEs. The TWT configuration may identify a first wakeup time for the companion UE and a second wakeup time for the anchor UE (e.g., a UE that is associated with the companion UE) . The first wakeup time and the second wakeup time may be configured such as to support the inter-UE communications between the cooperating UEs. The cooperating UEs may coordinate with each other to establish the first wakeup time and / or the second wakeup time according to the TWT configuration. The cooperating UEs may perform inter-UE communications based on the first wakeup time and / or the second wakeup time.
[0065] TWT configuration 300 illustrates an example where the TWT configuration identifies a set of TWT patterns and the cooperating UEs select a TWT pattern from the set of TWT patterns to define the first wakeup time and / or the second wakeup time. That is, in this example the TWT configuration identifies a first TWT pattern (e.g., TWT pattern 1) that includes periodic wake time (s) 305 that are separated in the time domain by sleep times having a duration of T1. That is, the duration of the interval may define the periodicity of the wake time (s) 305. In this example, the first TWT pattern may include a wake time (s) 305-a, a wake time (s) 305-b, a wake time (s) 305-c, and a wake time (s) 305-d. However, it is to be understood that the wake time (s) 305 may extend beyond the four wake time (s) 305 shown in Figure 3. The anchor UE, the companion UE, or both UEs may be in the wake or active state during the wake time (s) 305 and be in a sleep or idle state during the sleep times (e.g., between the wake time (s) 305) .
[0066] In this example, the TWT configuration also identifies a second TWT pattern (e.g., TWT pattern 2) that includes periodic wake time (s) 310 that are separated in the time domain by sleep times having a duration of T2. In this example, the duration of the sleep times (e.g., T2) of the second TWT pattern is shorter than the duration of the sleep times (e.g., T1) of the first TWT pattern. Thus, the duration of the interval T2 may define the periodicity of the wake time (s) 310. In this example, the second TWT pattern may include a wake time (s) 310-a, a wake time (s) 310-b, a wake time (s) 310-c, a wake time (s) 310-d, and a wake time (s) 310-e. However, it is to be understood that the wake time (s) 310 may extend beyond the five wake time (s) 310 shown in Figure 3. The anchor UE, the companion UE, or both UEs may be in the wake or active state during the wake time (s) 310 and be in a sleep or idle state during the sleep times (e.g., between the wake time (s) 310) .
[0067] In some cases, in the uplink example the anchor UE and the companion UE may coordinate the TWT wake intervals based on an uplink XR traffic cadence and / or latency requirement. For example, the coordination between the UE and the associated UE may be based on uplink communications from the UE and / or from the associated UE.
[0068] As one example, in some cases the split between the uplink traffic may be managed by the network entity (e.g., based on CSI, the available resources of the anchor UE and / or the companion UE, etc. ) where the network entity provides instructions about the TWT wake intervals according to the expected split between the cooperating UEs. That is, the TWT configuration in this example may be based on the uplink communications from the UE and / or from the associated UE. As one example, if the uplink packets requiring a tight latency are expected to split towards the companion UE, a small interval (e.g., T2, in this example) may be configured so that anchor UE can deliver the split traffic to the companion UE in a timely manner. Otherwise, a large interval (e.g., T1) may be adopted to support power saving operations for the cooperating UEs. In some cases, the network entity may indicate the information about the TWT wake intervals to the anchor UE and / or the companion UE via DCI signaling and / or via MAC-CE signaling.
[0069] However, in some scenarios the uplink traffic split may be performed autonomously by the cooperating UEs. For example, the anchor UE may be aware of the cadence and / or latency that it needs to deliver the split traffic to the companion UE. In this case the anchor UE may coordinate directly with the companion UE to establish the first wakeup time and / or the second wakeup time. That is, in this example the network entity may not provide the TWT configuration to the cooperating UEs. Instead, the UE (e.g., the companion UE) may transmit or otherwise output (and the associated UE, which is the anchor UE in this example, may receive or otherwise obtain) the signal that identifies the TWT configuration to be applied between the cooperating UEs. The UEs may coordinate to establish the first wakeup time and / or the second wakeup time according to the TWT configuration identified and signaled by the companion UE. The cooperating UEs may perform inter-UE communications according to the first wakeup time and / or the second wakeup time. In some cases, the cooperating UEs may exchange the TWT configuration information via UE-to-UE link, such as via a sidelink MAC-CE, a physical sidelink shared channel (PSSCH) , and / or via a physical sidelink control channel (PSCCH) . Thus, in this example the cooperating UEs may autonomously coordinate the TWT configuration information without assistance from the network entity.
[0070] Figure 4 shows an example of a TWT configuration 400 that supports joint design for UE cooperation. Aspects of the TWT configuration 400 may be implemented by or may implement aspects of the wireless communications system 100 and / or aspects of the signaling diagram 200. Aspects of the TWT configuration 400 may be implemented at or implemented by a UE and / or a network entity, which may be examples of the corresponding devices described herein.
[0071] The techniques described herein provide for a network entity to manage aspects of a TWT configuration to be applied between cooperating UEs. For example, the network entity may transmit a signal (e.g., an RRC signal) to one or both of the cooperating UEs that identifies a TWT configuration to be applied by the UEs. The TWT configuration may identify a first wakeup time for the companion UE and a second wakeup time for the anchor UE (e.g., a UE that is associated with the companion UE) . The first wakeup time and the second wakeup time may be configured such as to support the inter-UE communications between the cooperating UEs. The cooperating UEs may coordinate with each other to establish the first wakeup time and / or the second wakeup time according to the TWT configuration. The cooperating UEs may perform inter-UE communications based on the first wakeup time and / or the second wakeup time.
[0072] TWT configuration 400 illustrates an example where the coordination between the cooperating UEs includes identifying or otherwise selecting a time gap between the first wakeup time and the second wakeup time based on the companion UE providing paging operations to the anchor UE. The time gap may correspond to or otherwise be based on a paging occasion at the associated UE (e.g., at the companion UE and / or at the anchor UE) .
[0073] For example, aspects of the techniques described herein may include one UE assisting another UE (e.g., a cooperating UE) to monitor paging from the network entity to support power saving operations for the anchor UE (e.g., a small form factor UE that does not monitor for paging signals) . To improve such power saving operations, the UE without paging monitoring (e.g., the anchor UE) may be configured with a reasonable TWT wake interval to align with the paging occasions (POs) of another cooperating UE. The TWT wake interval may be one or a multiple of the PO cycles.
[0074] As one example, a first UE (e.g., UE1) may be a small form factor UE that does not monitor paging signals from the network entity. A second UE (e.g., UE2) may be the cooperating UE with or for UE1 and UE2 may monitor for paging signals from the network entity. In this case, the first UE may not always try to fetch paging information from the second UE and may, instead, the first UE may maintain a sleep state for power saving operations. TWT configuration 400 illustrates an example where the TWT wake interval is matched to the PO cycle, which may also reduce paging latency. As shown, the paging cycle for the second UE to monitor may include a PO 405-a, a PO 405-b, and a PO 405-c, although it is to be understood that more than three POs may be included in the paging cycle. The PO 405 in this example may generally correspond to the first wakeup time while the wake time (s) 410 of the first UE may correspond to the second wakeup time.
[0075] The UE (e.g., the second UE in this example) may receive a paging signal for the associated UE (e.g., the first UE in this example) during the first wakeup time (e.g., during one or more instances of the PO 405) . The second UE may then transmit paging information according to the paging signal to the first UE during the second wakeup time (e.g., during a wake time (s) 410) . For example, the second UE may receive the paging signal during the PO 405-a and then transmit the paging information to the first UE during the wake time 410-a, may receive the paging signal during the PO 405-b and transmit the paging information to the first UE during the wake time 410-b, and / or may receive the paging signal during the PO 405-c and transmit the paging information to the first UE during the wake time 410-c. Accordingly, the TWT configuration may allow the first UE to be triggered to wake up just after (e.g., according to the time gap) a PO 405 so that the second UE may convey the paging information to the first UE during the corresponding or next wake time (s) 410. In some cases, the cooperating UEs may coordinate the TWT wake intervals based on the paging cycle configured by the network entity.
[0076] Figure 5 shows an example of a TWT configuration 500 that supports joint design for UE cooperation. Aspects of the TWT configuration 500 may be implemented by or may implement aspects of the wireless communications system 100 and / or aspects of the signaling diagram 200. Aspects of the TWT configuration 500 may be implemented at or implemented by a UE and / or a network entity, which may be examples of the corresponding devices described herein.
[0077] The techniques described herein provide for a network entity to manage aspects of a TWT configuration to be applied between cooperating UEs. For example, the network entity may transmit a signal (e.g., an RRC signal) to one or both of the cooperating UEs that identifies a TWT configuration to be applied by the UEs. The TWT configuration may identify a first wakeup time for the companion UE and a second wakeup time for the anchor UE (e.g., a UE that is associated with the companion UE) . The first wakeup time and the second wakeup time may be configured such as to support the inter-UE communications between the cooperating UEs. The cooperating UEs may coordinate with each other to establish the first wakeup time and / or the second wakeup time according to the TWT configuration. The cooperating UEs may perform inter-UE communications based on the first wakeup time and / or the second wakeup time.
[0078] TWT configuration 500 illustrates an example where the coordination between the cooperating UEs includes identifying or otherwise selecting a time gap between the first wakeup time and the second wakeup time based on the companion UE providing paging operations to the anchor UE. The time gap may correspond to or otherwise be based on a paging occasion at the associated UE (e.g., at the companion UE and / or at the anchor UE) .
[0079] The techniques described herein may include one UE assisting another UE (e.g., a cooperating UE) to monitor paging from the network entity to support power saving operations for the anchor UE (e.g., a small form factor UE that does not monitor for paging signals) . To improve such power saving operations, the UE without paging monitoring (e.g., the anchor UE) may be configured with a reasonable TWT wake interval to align with the paging occasions (POs) of another cooperating UE. The TWT wake interval may be one or a multiple of the PO cycles.
[0080] A first UE (e.g., UE1) may be a small form factor UE that does not monitor paging signals from the network entity. A second UE (e.g., UE2) may be the cooperating UE with or for UE1 and UE2 may monitor for paging signals from the network entity. TWT configuration 500 illustrates an example where the TWT wake interval is matched to the PO cycle, which may also reduce paging latency. As shown, the paging cycle for the second UE to monitor may include a PO 505-a and a PO 505-b, although it is to be understood that more than two POs may be included in the paging cycle. The PO 505 in this example may generally correspond to the first wakeup time while the wake time (s) 510 of the first UE may correspond to the second wakeup time.
[0081] The UE (e.g., the second UE in this example) may receive a paging signal for the associated UE (e.g., the first UE in this example) during the first wakeup time (e.g., during one or more instances of the PO 505) . The second UE may then transmit paging information according to the paging signal to the first UE during the second wakeup time (e.g., during a wake time (s) 510) . For example, the second UE may receive the paging signal during the PO 505-a and then transmit the paging information to the first UE during the wake time 510-a and / or may receive the paging signal during the PO 505-b and transmit the paging information to the first UE during the wake time 510-b. Accordingly, the TWT configuration may allow the first UE to be triggered to wake up just after (e.g., according to the time gap, T2) a PO 505 so that the second UE may convey the paging information to the first UE during the corresponding or next wake time (s) 510.
[0082] TWT configuration 500 illustrates an example where the timeline between the PO 505 and the wake time (s) 510 are configured so that the second UE has sufficient time to convey the paging information to the first UE during the TWT wake duration (e.g., during the wake time (s) 510) . In particular, in the procedure where the second UE assists the first UE to monitor paging, the second UE needs to process and redeliver the paging information to the first UE after the second UE detects the target paging of the first UE. The first UE needs time to ramp up from a sleep state or mode to the wake interval in the TWT mechanism (e.g., during the wake time (s) 510 according to the TWT configuration) . Accordingly, there may be a time gap (e.g., T2) that is configured between the PO 505 and the wake time (s) 510. The time gap (e.g., T2) may be a paging processing time gap that is based on the paging processing and communicating time associated with the UE (e.g., the second UE, in this example) . In some cases, the network entity may configure a reasonable time gap (e.g., T2) based on the UE reported capabilities to the cooperating UEs. In some cases, the network entity may indicate the required time gap to the cooperating UEs via RRC, DCI, and / or MAC-CE signaling.
[0083] In some cases, the first wakeup time of the UE (e.g., the second UE in this example) may at least partially overlap with the PO 505 of the UE and / or of the associated UE (e.g., the first UE in this example) . In some case, the time gap (e.g., T2) may be measured in microseconds or in milliseconds, in symbols, or in some other units.
[0084] Figure 6 shows an example of a processing system 620 that supports joint design for UE cooperation. A processing system 620 may be an example of a processing system 140 (such as of a UE 115) and may include a TWT configuration manager 625, a coordination manager 630, an inter-UE communication manager 635, a TWT pattern manager 640, a time gap manager 645, or any combination thereof. A processing system 620, or various component thereof, may be an example of means for performing (such as a means for causing a UE 115 to perform) various techniques described herein.
[0085] The TWT configuration manager 625 may be configured to cause the UE 115 to receive a signal that identifies a TWT configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications. The coordination manager 630 may be configured to cause the UE 115 to coordinate with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration. The inter-UE communication manager 635 may be configured to cause the UE 115 to perform the inter-UE communications with the associated UE based on the first wakeup time, on the second wakeup time, or both.
[0086] In some examples, the TWT pattern manager 640 may be configured to cause the UE 115 to select, based on the coordinating with the associated UE, a TWT pattern from the set of TWT patterns, where the first wakeup time and the second wakeup time are based on the TWT pattern. In some examples, the TWT configuration identifies a TWT pattern for use by the UE and the associated UE. In some examples, the first wakeup time and the second wakeup time are based on the TWT pattern. In some examples, coordinating with the associated UE is based on uplink communications from the UE, from the associated UE, or both. In some examples, the TWT configuration is based at least in part on the uplink communications from the UE, from the associated UE, or both.
[0087] In some examples, to support coordinating with the associated UE, the time gap manager 645 may be configured to cause the UE 115 to identify a time gap between the first wakeup time and the second wakeup time, where the time gap is based on the UE providing paging operations to the associated UE. In some examples, the time gap corresponds to a timing of paging occasions at the associated UE.
[0088] In some examples, the time gap manager 645 may be configured to cause the UE 115 to receive, during the first wakeup time, a paging signal for the associated UE. In some examples, the time gap manager 645 may be configured to cause the UE 115 to transmit, during the second wakeup time and according to the time gap, paging information to the associated UE according to the paging signal. In some examples, the time gap includes a paging processing time gap. In some examples, the paging processing time gap is based on a paging processing and communicating time associated with the UE. In some examples, the first wakeup time at least partially overlaps in a time domain with a paging occasion of the UE, of the associated UE, or both. In some examples, the first wakeup time and the second wakeup time include at least partially overlapping time periods. In some examples, the signal that identifies the TWT configuration is received from a network entity.
[0089] A processing system 620 may include or be a component of one or more chips, systems-on-chips (SoCs) , chipsets, packages, components, or devices that individually or collectively constitute or include a processing system. A processing system 620 may interface with other components of a processing system 620. For example, operations described with reference to a processing system 620, or various components thereof, may be performed by or with other such components, including a receiver, a transmitter, a transceiver, a modem, a user interface, a modulator / demodulator, an encoder / decoder, or any combination thereof (such as of the processing system 620, coupled with the processing system 620, of a processing system 620) .
[0090] By including or configuring a processing system 620 for operation in a processing system 620 as described herein, the processing system 620 may support techniques for improved inter-UE communications between cooperating UE by aligning, at least to some degree, the TWT wake periods and sleep periods between the cooperating UE. The at least partially aligned wake and sleep periods may improve the inter-UE communications as well as support paging operations for the cooperating UE.
[0091] Figure 7 shows an example of a system 700 including a device 705 that supports joint design for UE cooperation. The device 705 may be an example of or include components of UE 115. The device 705 may communicate (such as wirelessly) with one or more other devices (such as network entities 105, UEs 115) . The device 705 may include components for transmitting and receiving communication, which may include a processing system 720, an input / output (I / O) controller, such as an I / O controller 710, a transceiver 715, antenna (s) 725, a memory 730, and a processor 740. Components of the device 705 may be coupled (such as operatively, communicatively, functionally, electronically, electrically, in electronic communication) a bus 755.
[0092] The transceiver 715 may support bi-directional communication via antenna (s) 725, and may support transmission operations, reception operations, or both, as described herein. The transceiver 715 may implement functionality of a modem (such as a wireless modem) and may include one or more RF chains. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs) , and other components that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for digital processing at the device 705) . The transceiver 715 may modulate symbols and provide the modulated symbols to antenna (s) 725 for transmission, and demodulate symbols from signals received using antenna (s) 725.
[0093] The processor 740 may be a general-purpose processing component that supports various operations (such as applications) of the device 705. The memory 730 may be a general-purpose storage component that stores code executable by the processor 740. Such code may include instructions that, when executed by the processor 740, cause the device 705 to perform various functions (such as to support an application of the device 705) . The I / O controller 710 may manage inputs and outputs for the device 705, may manage peripherals not integrated into the device 705, or may represent a physical connection (such as port) to an external peripheral. The processor 740 may interact with a modem, a keyboard, a mouse, a touchscreen, or other device (such as via I / O controller 710) . In some implementations, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.
[0094] The processing system 720 may be an example of a processing system 140 or a processing system 600. For example, the processing system 720 may include processor circuitry 745 and memory circuitry 750 that stores code, and may be configured to cause the device 705 to perform operations that support joint design for UE cooperation. Although the processing system 720 is illustrated as a separate component, which may involve a separate chip, chipset, or other module, in some implementations, one or more functions described with reference to the processing system 720 may be supported by or performed by a transceiver 715, antenna (s) 725, a processor 740, memory 730, or any combination thereof, such that a processing system 720 may include one or more of a transceiver 715, antenna (s) 725, a processor 740, memory 730, or any combination thereof.
[0095] By including or configuring the processing system 720 for operation in the device 705 as described herein, may support techniques for improved inter-UE communications between cooperating UE by aligning, at least to some degree, the TWT wake periods and sleep periods between the cooperating UE. The at least partially aligned wake and sleep periods may improve the inter-UE communications as well as support paging operations for the cooperating UE.
[0096] Figure 8 shows an example of a method 800 that supports joint design for UE cooperation. Operations of the method 800 may be performed by a UE or its components (such as using a processing system configured to cause the UE 115 to perform one or more of the operations) as described herein.
[0097] At 805, the method may include receiving a signal that identifies a TWT configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications. In some examples, aspects of the operations of 805 may be performed by a TWT configuration manager 625.
[0098] At 810, the method may include coordinating with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration. In some examples, aspects of the operations of 810 may be performed by a coordination manager 630.
[0099] At 815, the method may include performing the inter-UE communications with the associated UE based on the first wakeup time, on the second wakeup time, or both. In some examples, aspects of the operations of 815 may be performed by an inter-UE communication manager 635.
[0100] Figure 9 shows an example of a method 900 that supports joint design for UE cooperation. Operations of the method 900 may be performed by a UE or its components (such as using a processing system configured to cause the UE 115 to perform one or more of the operations) as described herein.
[0101] At 905, the method may include receiving a signal that identifies a TWT configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications. In some examples, aspects of the operations of 905 may be performed by a TWT configuration manager 625.
[0102] At 910, the method may include selecting, based on the coordinating with the associated UE, a TWT pattern from the set of TWT patterns, where the first wakeup time and the second wakeup time are based on the TWT pattern. In some examples, aspects of the operations of 910 may be performed by a TWT pattern manager 640.
[0103] At 915, the method may include coordinating with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration. In some examples, aspects of the operations of 915 may be performed by a coordination manager 630.
[0104] At 920, the method may include performing the inter-UE communications with the associated UE based on the first wakeup time, on the second wakeup time, or both. In some examples, aspects of the operations of 920 may be performed by an inter-UE communication manager 635.
[0105] Figure 10 shows an example of a method 1000 that supports joint design for UE cooperation. Operations of the method 1000 may be performed by a UE or its components (such as using a processing system configured to cause the UE 115 to perform one or more of the operations) as described herein.
[0106] At 1005, the method may include receiving a signal that identifies a TWT configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications. In some examples, aspects of the operations of 1005 may be performed by a TWT configuration manager 625.
[0107] At 1010, the method may include identifying a time gap between the first wakeup time and the second wakeup time, where the time gap is based on the UE providing paging operations to the associated UE. In some examples, aspects of the operations of 1010 may be performed by a time gap manager 645.
[0108] At 1015, the method may include coordinating with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration. In some examples, aspects of the operations of 1015 may be performed by a coordination manager 630.
[0109] At 1020, the method may include performing the inter-UE communications with the associated UE based on the first wakeup time, on the second wakeup time, or both. In some examples, aspects of the operations of 1020 may be performed by an inter-UE communication manager 635.
[0110] Aspect 1: A method for wireless communications at a UE, comprising: receiving a signal that identifies a TWT configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications; coordinating with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration; and performing the inter-UE communications with the associated UE based at least in part on the first wakeup time, on the second wakeup time, or both.
[0111] Aspect 2: The method of aspect 1, wherein the TWT configuration identifies a set of TWT patterns, further comprising: selecting, based at least in part on the coordinating with the associated UE, a TWT pattern from the set of TWT patterns, wherein the first wakeup time and the second wakeup time are based at least in part on the TWT pattern.
[0112] Aspect 3: The method of any of aspects 1 through 2, wherein the TWT configuration identifies a TWT pattern for use by the UE and the associated UE, the first wakeup time and the second wakeup time are based at least in part on the TWT pattern.
[0113] Aspect 4: The method of any of aspects 1 through 3, wherein coordinating with the associated UE is based at least in part on uplink communications from the UE, from the associated UE, or both.
[0114] Aspect 5: The method of aspect 4, wherein the TWT configuration is based at least in part on the uplink communications from the UE, from the associated UE, or both.
[0115] Aspect 6: The method of any of aspects 1 through 5, wherein coordinating with the associated UE comprises: identifying a time gap between the first wakeup time and the second wakeup time, wherein the time gap is based at least in part on the UE providing paging operations to the associated UE.
[0116] Aspect 7: The method of aspect 6, wherein the time gap corresponds to a timing of paging occasions at the associated UE.
[0117] Aspect 8: The method of any of aspects 6 through 7, further comprising: receiving, during the first wakeup time, a paging signal for the associated UE; and transmitting, during the second wakeup time and according to the time gap, paging information to the associated UE according to the paging signal.
[0118] Aspect 9: The method of any of aspects 6 through 8, wherein the time gap comprises a paging processing time gap, and the paging processing time gap is based at least in part on a paging processing and communicating time associated with the UE.
[0119] Aspect 10: The method of any of aspects 6 through 9, wherein the first wakeup time at least partially overlaps in a time domain with a paging occasion of the UE, of the associated UE, or both.
[0120] Aspect 11: The method of any of aspects 1 through 10, wherein the first wakeup time and the second wakeup time comprise at least partially overlapping time periods.
[0121] Aspect 12: The method of any of aspects 1 through 11, wherein the signal that identifies the TWT configuration is received from a network entity.
[0122] Aspect 13: A UE for wireless communications, comprising a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the UE to perform a method of any of aspects 1 through 12.
[0123] Aspect 14: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 12.
[0124] Aspect 15: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 12.
[0125] It should be noted that methods described herein describe possible implementations. Other implementations in accordance with the described techniques are possible, including implementations in which operations are rearranged or otherwise modified relative to the described methods. Further, aspects from two or more of the described methods may be combined.
[0126] Although aspects of 5G or 6G systems may be described for purposes of example and corresponding terminology may be used in the description, the techniques described herein are applicable beyond 5G, or 6G networks. For example, the described techniques may be applicable to other communication systems such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.20, Flash-OFDM, or other systems and radio technologies not explicitly mentioned herein.
[0127] As used herein, a processing system (such as a processing system 140, a processing system 145) includes processor (or “processing” ) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs) , graphics processing units (GPUs) , neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , or digital signal processors (DSPs) ) , processing blocks, application-specific integrated circuits (ASICs) , programmable logic devices (PLDs) , or other discrete gate or transistor logic or circuitry (any one or more of which may be generally referred to herein individually as a “processor” or collectively as “the processor” or “the processor circuitry” ) . Such processors may be individually or collectively configurable or configured to perform functions or operations described herein. A group of processors collectively configurable or configured to cause a device to perform a set of functions may include a first processor configured to cause the device to perform a first function of the set and a second processor configured to cause the device to perform a second function of the set. In some other examples, each of a group of processors may be configured to cause a device to perform a same set of functions.
[0128] As used herein, a processing system (such as a processing system 140, a processing system 145) also includes memory circuitry in the form of one or multiple memory devices, memory blocks, memory elements, or other discrete gate or transistor logic or circuitry, each of which may include or implement tangible storage media such as random-access memory (RAM) or read-only memory (ROM) , or combinations thereof (any one or more of which may be generally referred to herein individually as a “memory” or collectively as “the memory” or “the memory circuitry” ) . One or more of the memories may be coupled (such as operatively, communicatively, electronically, electrically) with one or more processors of the processor circuitry and may individually or collectively store processor-executable code or instructions (such as software) that, when executed by one or more of the processors, may cause a device (such as configure the device, using one or more of the processors) to perform functions or operations described herein. Additionally, or alternatively, in some examples, one or more of the processors may be configured to cause a device to perform functions or operations described herein without requiring configuration by software. As used herein, “software” shall be construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0129] As used herein, a processing system (such as a processing system 140, a processing system 145) may include or be coupled with one or more modems (such as a cellular modem, a 5G-compliant modem, a 6G-compliant modem) . In some examples, one or more processors of a processing system may include or implement one or more of the modems. A processing system also may include or be coupled with multiple radios (collectively “the radio” ) , multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some examples, one or more processors of a processing system may include or implement one or more of the radios, RF chains, or transceivers. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs) , or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by processor circuitry) .
[0130] As described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code (such as processor-executable code, instructions) stored in memory circuitry (such as a non-transitory computer-readable medium, of the memory circuitry, storing code for wireless communication that is executable by a processing system) or otherwise, to perform one or more of the functions described herein.
[0131] As used herein, the term “determine” or “determining” can encompass one or more of a variety of actions. For example, “determining” can include one or more of calculating, computing, processing, deriving, detecting, estimating, looking up, inferring, ascertaining, measuring, resolving, selecting, obtaining, identifying, interpreting, demodulating, decoding, reading, establishing, forming, or generating, among other examples. In some such examples, determining can involve a processing system performing some type of calculating, computing, deriving, estimating, inferring, ascertaining, resolving, predicting, or other processing to obtain one or more numerical values, sets, elements, or other information or results. In some such examples, determining can involve a processing system identifying, looking up, investigating or otherwise obtaining some type of value, set, element, or other information or result from a table, data structure, database, or an implementation of memory, such as from a larger set of values, sets, or elements or other information or results. In some such examples, determining can involve a processing system identifying, interpreting, demodulating, decoding, detecting, reading, or otherwise obtaining some type of value, set, element, or other information or result signaled in, for example, a received wireless signal. In some such examples, determining can involve a processing system performing a measurement, such as on a received signal.
[0132] As used herein, the phrase “associated with” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, the phrase “associated with” is not to be construed as a reference to a closed set of conditions, factors, criteria, elements, components or actions, among other examples. Specifically, unless a phrase refers to “associated with only ‘a, ’ ” or the equivalent in context, whatever it is that is “associated with ‘a, ’ ” may be associated with “a” alone or associated with a combination of “a” and one or more other conditions, factors, criteria, elements, components or actions, among other examples. The phrase “associated with” may be interpreted to mean or be interchanged with “in association with, ” “in accordance with, ” “based on, ” “based at least in part on, ” “as a function of, ” “in response to, ” “responsive to, ” “using, ” “coupled with, ” in communication with, ” “configured with, ” “included with, ” or “in cooperation with, ” as appropriate in the relevant context unless otherwise explicitly indicated. Additionally, the use of such phrases does not indicate that what follows the phrase is the focal point or primary factor associated with the limitation preceding the phrase.
[0133] As used herein, a phrase referring to “at least one of” or “one or more of” a list of items refers to any combination of those items, including single members. For example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c. Additionally, as used herein, a phrase referring to “a” or “an” element refers to one or more of such elements acting individually or collectively to perform the recited function (s) . Thus, the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. For instance, for a claim that refers to “a” component performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components, and subsequent reference to a component introduced with the article “a” using the term “the” may refer to any or all of the single or multiple components. Thus, a component introduced with the article “a” may be understood to mean “one or more” components, and referring to “the” component subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more” components. Additionally, as used herein, a “set” can refer to one or more items, and a “subset” can refer to a whole set or less than the whole set, but not an empty set. Additionally, as used herein, the term “or” is intended to be interpreted in the inclusive sense, such as when referring to a series, and may be used interchangeably with the term “and / or, ” unless otherwise explicitly indicated (for example, if used in conjunction with “either” or “only one of” ) . For example, “a or b” may include a only, b only, or a combination of a and b.
[0134] The disclosure is provided to enable a person having ordinary skill in the art to implement the described techniques. Modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the techniques disclosed herein may be applied with other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.A user equipment (UE) , comprising:a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the UE to:receive a signal that identifies a target wake time (TWT) configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications;coordinate with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration; andperform the inter-UE communications with the associated UE based at least in part on the first wakeup time, on the second wakeup time, or both.2.The UE of claim 1, wherein the processing system is further configured to cause the UE to:select, based at least in part on the coordinating with the associated UE, a TWT pattern from the set of TWT patterns, wherein the first wakeup time and the second wakeup time are based at least in part on the TWT pattern.3.The UE of claim 1, wherein:the TWT configuration identifies a TWT pattern for use by the UE and the associated UE,the first wakeup time and the second wakeup time are based at least in part on the TWT pattern.4.The UE of claim 1, wherein coordinating with the associated UE is based at least in part on uplink communications from the UE, from the associated UE, or both.5.The UE of claim 4, wherein the TWT configuration is based at least in part on the uplink communications from the UE, from the associated UE, or both.6.The UE of claim 1, wherein, to coordinate with the associated UE, the processing system is configured to cause the UE to:identify a time gap between the first wakeup time and the second wakeup time, wherein the time gap is based at least in part on the UE providing paging operations to the associated UE.7.The UE of claim 6, wherein the time gap corresponds to a timing of paging occasions at the associated UE.8.The UE of claim 6, wherein the processing system is further configured to cause the UE to:receive, during the first wakeup time, a paging signal for the associated UE;andtransmit, during the second wakeup time and according to the time gap, paging information to the associated UE according to the paging signal.9.The UE of claim 6, wherein:the time gap comprises a paging processing time gap, andthe paging processing time gap is based at least in part on a paging processing and communicating time associated with the UE.10.The UE of claim 6, wherein the first wakeup time at least partially overlaps in a time domain with a paging occasion of the UE, of the associated UE, or both.11.The UE of claim 1, wherein:the first wakeup time and the second wakeup time comprise at least partially overlapping time periods.12.The UE of claim 1, wherein the signal that identifies the TWT configuration is received from a network entity.13.A method for wireless communications at a user equipment (UE) , comprising:receiving a signal that identifies a target wake time (TWT) configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications;coordinating with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration; andperforming the inter-UE communications with the associated UE based at least in part on the first wakeup time, on the second wakeup time, or both.14.The method of claim 13, wherein the TWT configuration identifies a set of TWT patterns, further comprising:selecting, based at least in part on the coordinating with the associated UE, a TWT pattern from the set of TWT patterns, wherein the first wakeup time and the second wakeup time are based at least in part on the TWT pattern.15.The method of claim 13, whereinthe TWT configuration identifies a TWT pattern for use by the UE and the associated UE,the first wakeup time and the second wakeup time are based at least in part on the TWT pattern.16.The method of claim 13, wherein coordinating with the associated UE is based at least in part on uplink communications from the UE, from the associated UE, or both.17.The method of claim 16, wherein the TWT configuration is based at least in part on the uplink communications from the UE, from the associated UE, or both.18.The method of claim 13, wherein coordinating with the associated UE comprises:identifying a time gap between the first wakeup time and the second wakeup time, wherein the time gap is based at least in part on the UE providing paging operations to the associated UE.19.The method of claim 18, wherein the time gap corresponds to a timing of paging occasions at the associated UE.20.A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:receive a signal that identifies a target wake time (TWT) configuration for application between the UE and an associated UE, the TWT configuration identifying a first wakeup time for the UE and a second wakeup time for the associated UE for inter-UE communications;coordinate with the associated UE to establish the first wakeup time for the UE and the second wakeup time for the associated UE according to the TWT configuration; andperform the inter-UE communications with the associated UE based at least in part on the first wakeup time, on the second wakeup time, or both.