Techniques for improving network power saving mode

Abstract

Certain aspects of the present disclosure provide techniques for improving a network energy saving (NES) mode. An example method performed by a first user equipment (UE) includes receiving configuration information from a first network entity associated with a source cell, the configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with the source cell to a second network entity associated with a target cell; receiving a trigger signal comprising a trigger command for conditional handover from a first network entity associated with the source cell; and taking one or more actions related to performing the conditional switching based on the trigger signal and the one or more conditions.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Patent Application No. 18 / 186,108, filed March 17, 2023, which is hereby incorporated by reference herein in its entirety. TECHNICAL FIELD

[0003] Aspects of the disclosure relate to wireless communications, and more particularly, to techniques for improving network energy saving (NES) mode. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various types of telecommunication content such as voice, video, data, messaging, broadcast, or other types of services. These wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and other systems.

[0005] Despite the tremendous technological advances in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Thus, there is a continuing desire to improve the technical performance of wireless communication systems, for example, including: increasing the speed and data carrying capacity of communications, increasing the efficiency of use of shared communication media, reducing the power used by transmitters and receivers in performing communications, increasing the reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, increasing the coverage area of wireless communications, increasing the number and types of devices that can access a wireless communication system, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Thus, there is a need for further improvements in wireless communication systems to overcome the aforementioned technical challenges and others. SUMMARY

[0006] One aspect provides a method for wireless communication at a first user equipment (UE). The method includes receiving, from a first network entity associated with a source cell, configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with the source cell to a second network entity associated with a target cell, receiving, from the first network entity associated with the source cell, a trigger signal including a trigger command for the conditional handover, and taking one or more actions related to performing the conditional handover based on the trigger signal and the one or more conditions.

[0007] Another aspect provides a method for wireless communication at a first network entity associated with a source cell. The method includes transmitting, to a first UE, configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with the source cell to a second network entity associated with a target cell; determining to enter a network energy savings (NES) mode; transmitting, to the first UE, a trigger signal including a trigger command for the conditional handover based on the determining to enter the NES mode; and taking one or more actions related to entering the NES mode based on the trigger signal.

[0008] Other aspects provide an apparatus operable, configured, or otherwise adapted to perform the methods previously described and those described elsewhere herein; a non-transitory computer readable medium having instructions stored thereon that, when executed by a processor of a device, cause the device to perform the methods previously described and those described elsewhere herein; a computer program product, embodied on a computer readable storage medium, comprising code for performing the methods previously described and those described elsewhere herein; and / or a device comprising means for performing the methods previously described and those described elsewhere herein. By way of example, a device can include a processing system, an apparatus with a processing system, or a processing system in cooperation with one or more networks.

[0009] The following description and drawings are illustrative of certain aspects. BRIEF DESCRIPTION OF DRAWINGS

[0010] The attached drawings illustrate certain aspects of the aspects described herein and are not intended to limit the scope of the present disclosure.

[0011] Figure 1 An example wireless communication network is depicted.

[0012] Figure 2 An example disaggregated base station architecture is depicted.

[0013] Figure 3 Aspects of an example base station and an example user equipment are depicted.

[0014] Figure 4A , 4B Various example aspects of data structures for a wireless communication network are depicted.

[0015] Figure 5 A process flow for communication between a first network entity, a second network entity, and a user equipment in a network is depicted.

[0016] Figure 6 A method for wireless communication is depicted.

[0017] Figure 7 Aspects are presented for wireless communication.

[0018] Figure 8 Aspects of example communication devices are presented.

[0019] Figure 9 Aspects of example communication devices are presented. DETAILED DESCRIPTION

[0020] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer readable media for improving network energy saving (NES) mode.

[0021] Power consumption of network entities in large scale wireless networks (e.g., 4G, 5G, and beyond) is a major concern. To help reduce this power consumption, certain network entities are capable of operating in a network energy saving (NES) mode, allowing these network entities to power down certain components to conserve power. However, in some cases, while a first network entity can determine to enter NES mode, there can still be user equipment (UEs) served by the first network entity. In such cases, the first network entity, which can be associated with a source cell, can take one or more actions to handover these UEs to a second network entity associated with a target cell.

[0022] In some cases, these UEs can be handed over to the second network entity associated with the target cell using a technique referred to as conditional handover. Conditional handover is a type of handover in which a first network entity associated with a serving cell provides a handover command / configuration to a UE, the handover command / configuration including one or more trigger conditions that allow the UE to autonomously initiate a handover to a second network entity associated with a target cell.

[0023] Accordingly, in some cases, when the first network entity determines to enter the NES mode, the first network entity can send a trigger signal to one or more UEs triggering them to evaluate one or more trigger conditions and perform a conditional handover to the second network entity when the one or more trigger conditions are satisfied. However, there can be cases where not all UEs can be handed over to the second network entity. Accordingly, if the first network entity is to proceed with entering the NES mode, this would result in radio link failures at the UEs that cannot be handed over, resulting in poor user experience associated with lost transmissions or receptions and corresponding retransmissions as well as wasted time-frequency and power resources. Moreover, even if all UEs can be handed over to the second network entity, a large number of these UEs can end up transmitting random access channel (RACH) messages at the same time (e.g., to attach to the second network entity), which can result in collisions among the UEs. These collisions can result in RLFs at the UEs, resulting in wasted time-frequency and power resources.

[0024] Accordingly, aspects of the present disclosure provide techniques for helping to avoid these issues associated with using conditional handovers when the first network entity determines to enter the NES mode. For example, in some cases, the first network entity can configure different conditional handover execution timers for different UEs, causing the times at which these UEs can transmit RACH messages for handover to the second network entity to be staggered, thereby reducing collisions among the UEs. Additionally, in some cases, when at least one UE cannot be handed over to the second network entity, the first network entity can delay entering the NES mode or can not enter the NES mode at all. Accordingly, delaying or not entering the NES mode can allow the UEs to still be served by the first network entity, thereby avoiding RLFs and associated wasted time-frequency and power resources.

[0025] Introduction to wireless communication networks

[0026] The techniques and methods described herein can be used for various wireless communication networks. While aspects are described in the context of 3G, 4G, and / or 5G wireless technology, aspects of the present disclosure can be applied to other communication systems and standards not explicitly mentioned.

[0027] Figure 1 An example of a wireless communication network 100 in which aspects described herein can be implemented is depicted.

[0028] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communication device and / or a communication function performed by a communication device (e.g., a user equipment (UE), a base station (BS), a component of a BS, a server, etc.). For example, various functions of the network and various devices associated with and interacting with the network can be considered network entities. Further, the wireless communication network 100 includes a terrestrial aspect, such as ground-based network entities (e.g., BSs 102), and a non-terrestrial aspect, such as satellites 140 and aircraft 145, which can include on-board network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0029] In the illustrated example, the wireless communication network 100 includes BSs 102, UEs 104, and one or more core networks, such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190, which interoperate to provide communication services over various communication links, including wired and wireless links.

[0030] Figure 1 Various example UEs 104 are illustrated, which can more generally include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an always-on (AON) device, an edge processing device, or other similar devices. A UE 104 can also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, etc.

[0031] The BSs 102 wirelessly communicate with UEs 104 via communication links 120 (e.g., transmit signals to or receive signals from the UEs 104). The communication links 120 between the BSs 102 and the UEs 104 can include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. The communication links 120 can use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity, among other techniques.

[0032] BS 102 can generally include NodeBs, enhanced NodeBs (eNBs), next-generation enhanced NodeBs (ng-eNBs), next-generation NodeBs (gNBs or gNodeBs), access points, base transceiver stations, radio base stations, radio transceivers, transceiver functions, transmission and reception points, etc. Each BS 102 can provide communication coverage for a respective geographic coverage area 110, which can sometimes be referred to as a cell, and which can overlap in some scenarios (e.g., small cells 102' can have a coverage area 110' that overlaps with a coverage area 110 of a macro cell). For example, BSs can provide communication coverage for macro cells (large geographic areas), pico cells, femto cells, and / or other types of cells.

[0033] While BS 102 is illustrated as a single communication device in various aspects, BS 102 can be implemented in various configurations. For example, one or more components of the base station can be split including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), near real-time (near-RT) RAN intelligent controllers (RICs), or non-RT RICs, to name a few examples. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components that are located at a single physical location or components that are located at various physical locations. In examples where the base station includes components that are located at various physical locations, the various components can each perform functions such that the components collectively implement functions similar to a base station that is located at a single physical location. In some aspects, a base station that includes components that are located at various physical locations can be referred to as a disaggregated radio access network architecture, such as an Open RAN (O-RAN) or a virtualized RAN (VRAN) architecture. Figure 2 An example disaggregated base station architecture is depicted and described.

[0034] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface). BSs 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with the 5GC 190 through second backhaul links 184. The BSs 102 can communicate with one another directly or indirectly (e.g., through the EPC 160 or 5GC 190) over third backhaul links 134 (e.g., X2 interface).

[0035] Wireless communications network 100 can subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some aspects, such subdivision is provided based on wavelength and frequency, where frequency can also be referred to as a carrier, sub-carrier, frequency channel, tone, or sub-band. For example, 3GPP currently defines frequency range 1 (FR1) to include 410- 7125 MHz, which is often (interchangeably) referred to as “Sub-6 GHz.” Similarly, 3GPP currently defines frequency range 2 (FR2) to include 24,250- 71,000 MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to sub-ranges, such as a first sub-range FR2-1 including 24,250-52,600 MHz and a second sub-range FR2-2 including 52,600-71,000 MHz. Base stations configured to communicate using mmWave / near-mmWave radio frequency spectrum bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0036] Communication links 120 between BS 102 and UEs, for example, 104 can be through one or more carriers, which can have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) and can be aggregated (e.g., according to aggregation factors of 1, 2, 3, 4, 6, 8, 10, and / or other aggregation factors). The carriers can or can not be adjacent to each other. Allocation of carriers can be asymmetric with respect to DL and UL (e.g., more or less carriers can be allocated for DL than for UL).

[0037] Communications using higher frequency bands can have higher path loss and shorter range as compared to lower frequency communications. Thus, certain base stations (e.g., gNBs 180a, 180b) can be configured to use beamforming and / or transmit and receive beams, which can be used to improve path loss and range. Figure 1The BSs 180 can also include, or can be included within, a RAN such as the RAN 103, the RAN 104, and / or the RAN 105, illustrated in FIG. 1. In some aspects, the UE 104 can be located in a small cell 102' of the RAN 105, and can be configured to communicate with the BS 180 using a beamformed communication link 182. The BS 180 can communicate with the UE 104 using one or more transmit directions 182'. The UE 104 can communicate with the BS 180 using one or more receive directions 182". The BS 180 can also use beamforming 182 to transmit or receive data (e.g., instruction and / or data) to or from the UE 104. The BS 180 can perform the beamforming 182 in one or more directions 182' to transmit or receive data to or from the UE 104. The UE 104 can also perform the beamforming 182 in one or more directions 182" to transmit or receive data to or from the BS 180.

[0038] The wireless communication network 100 also includes a Wi-Fi access point, AP, 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum, e.g., 2.4 GHz and / or 5 GHz.

[0039] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSFCH), and / or a physical sidelink feedback channel (PSFCH).

[0040] The EPC 160 can include various function components, including a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the illustrated example. The MME 162 can be in communication with a home subscriber server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management.

[0041] Generally, user Internet Protocol (IP) packets are forwarded through the serving gateway 166, which is itself connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to the IP services 176, which can include the Internet, an intranet, an IP multimedia subsystem (IMS), a Packet Switched (PS) streaming service, and / or other IP services.

[0042] The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS Bearer Services, and / or can be used to schedule MBMS transmissions. The MBMS Gateway 168 can be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and / or can be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0043] The 5GC 190 can include various function components, including an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 can be in communication with a Unified Data Management (UDM) 196.

[0044] The AMF 192 is the control node that processes the signaling between the UE 104 and the 5GC 190. The AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0045] Internet Protocol (IP) packets are forwarded through the UPF 195, which is connected to the IP Services 197 and provides UE IP address allocation as well as other functions for the 5GC 190. The IP Services 197 can include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.

[0046] In various aspects, a network entity or network node can be implemented as an aggregated base station, disaggregated base station, component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, just to name a few examples.

[0047] Figure 2An architecture of an example disaggregated base station 200 is depicted. The disaggregated base station 200 architecture can include one or more central units (CUs) 210, which can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near-real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-RT RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CUs 210 can communicate with one or more distributed units (DUs) 230 via respective mid-haul links, such as Fl interfaces. The DUs 230 can communicate with one or more radio units (RUs) 240 via respective front-haul links. The RUs 240 can communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 can be served by multiple RUs 240 simultaneously.

[0048] Each of the units (e.g., CUs 210, DUs 230, RUs 240), as well as the near-RT RIC 225, the non-RT RIC 215, and the SMO framework 205, can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit, or an associated processor or controller providing instructions to the communication interface of the unit, can be configured to communicate with one or more other units via transmission media. For example, a unit can include a wired interface configured to receive or transmit signals from or to one or more of the other units over a wired transmission medium. Additionally or alternatively, a unit can include a wireless interface, which can include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals from or to one or more of the other units over a wireless transmission medium, or both.

[0049] In some aspects, the CU 210 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and / or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 can be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP devices can communicate bi-directionally with the CU-CP devices via an interface, such as an El interface when implemented in an O-RAN configuration. The CU 210 can be implemented to communicate with the DUs 230 for network control and signaling, as necessary.

[0050] The DU 230 can correspond to a logical unit that includes one or more base station functions to control operation of one or more RUs 240. In some aspects, depending at least in part on a functional split, such as a functional split defined by the Third Generation Partnership Project (3GPP), the DU 230 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers, such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and / or the like. In some aspects, the DU 230 can further host one or more lower PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0051] Lower layer functions can be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DU 230 can correspond to logical nodes that host RF processing functions or lower PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, and / or the like) or both based at least in part on a functional split, such as a lower layer functional split. In such an architecture, the RUs 240 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RUs 240 can be controlled by the respective DUs 230. In some scenarios, such a configuration can enable the DUs 230 and the CUs 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0052] The SMO framework 205 can be configured to support RAN deployments and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform, such as an Open Cloud (O-Cloud) 290, to perform network element lifecycle management, such as instantiating virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240, and near-RT RICs 225. In some implementations, the SMO framework 205 can communicate with hardware aspects of a 4G RAN, such as an Open eNB (O-eNB) 211, via an Ol interface. Further, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via an Ol interface. The SMO framework 205 can also include a non-RT RIC 215, which is configured to support the functionality of the SMO framework 205.

[0053] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflow (including model training and updates), or policy-based application / feature guidance in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or in communication with the near-RT RIC 225, such as via an Al interface. The near-RT RIC 225 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions on interfaces connecting one or more CUs 210, one or more DUs 230, or both, and the near-RT RIC 225, such as via an E2 interface.

[0054] In some implementations, to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 225, or received at the SMO framework 205 or the non-RT RIC 215 from non-network data sources or from network functions. In some examples, the non-RT RIC 215 or the near-RT RIC 225 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions through the SMO framework 205 (such as via O1 to reconfigure) or via creation of RAN management policies (such as Al policies).

[0055] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0056] In general, the BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively, 334), transceivers 332a-t (collectively, 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). The BS 102 can transmit data to and receive data from the UE 104, for example. The BS 102 includes a controller / processor 340 that can be configured to implement various functions related to wireless communication as described herein.

[0057] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-r (collectively, 352), transceivers 354a-r (collectively, 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions related to wireless communication as described herein.

[0058] With respect to an example downlink transmission, the BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical HARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC-PDCCH), etc. In some examples, the data can be for the physical downlink shared channel (PDSCH).

[0059] The transmit processor 320 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 can also generate reference symbols, e.g., for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS).

[0060] A transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing on the data symbols, the control symbols, and / or the reference symbols, if applicable, and can provide output symbol streams to the modulators (MODs) of the transceivers 332a-332t. Each modulator of transceivers 332a-332t can process a respective output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators of transceivers 332a-332t can be transmitted via the antennas 334a-334t, respectively.

[0061] To receive downlink transmissions, the UE 104 includes antennas 352a-352r, which can receive the downlink signals from the BS 102 and can provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator of transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0062] A MIMO detector 356 can obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0063] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364, which can receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller / processor 380. The transmit processor 364 can also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 364 can be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators 354a-354r in the transceivers (e.g., for SC-FDM, etc.), and transmitted to the BS 102.

[0064] At the BS 102, the uplink signals from the UE 104 can be received by the antennas 334a-t, processed by the modulators 332a-332t in the transceivers, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by the UE 104. The receive processor 338 can provide the decoded data to a data sink 339 and to the controller / processor 340.

[0065] The memory 342 and 382 can store data and program codes for the BS 102 and the UE 104, respectively.

[0066] The scheduler 344 can schedule UEs for data transmission on the downlink and / or uplink.

[0067] In various aspects, the BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms of outputting data, such as from the data source 312, the scheduler 344, the memory 342, the transmit processor 320, the controller / processor 340, the TX MIMO processor 330, the transceivers 332a-t, the antennas 334a-t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms of obtaining data, such as from the antennas 334a-t, the transceivers 332a-t, the RX MIMO detector 336, the controller / processor 340, the receive processor 338, the scheduler 344, the memory 342, and / or other aspects described herein.

[0068] In various aspects, the UE 104 can likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms of outputting data, such as from a data source 362, a memory 382, a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-t, an antenna 352a-t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms of obtaining data, such as from an antenna 352a-t, a transceiver 354a-t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, and / or other aspects described herein.

[0069] In some aspects, a processor can be configured to perform various operations, such as operations associated with the methods described herein, and to transmit (output) data to or receive (obtain) data from another interface, which is configured to transmit or receive data, respectively.

[0070] Figure 4A 、 4B FIGs. 4C and 4D depict aspects of data structures for a wireless communication network, such as the wireless communication network 100 of FIG. 1. Figure 1

[0071] In particular, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.

[0072] A wireless communication system can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such a system can also support half-duplex Figure 4B and 4D OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as illustrated in FIGs. 1 and 2) into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted using OFDM in the frequency domain or SC-FDM in the time domain.

[0073] ​The wireless communication frame structure can be frequency division duplex (FDD) in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to one of DL or UL. The wireless communication frame structure can also be time division duplex (TDD) in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0074] In Figure 4A and 4C , the wireless communication frame structure is TDD in which D is DL, U is UL, and X is flexible for use between DL / UL. A UE can be configured with a slot format by a received slot format indicator (SFI) (received dynamically through DL control information (DCI), or received semi-statically / statically through radio resource control (RRC) signaling). In the illustrated example, a 10 ms frame is divided into 10 equally sized 1 ms subframes. Each subframe can include one or more slots. In some examples, each slot can include 7 or 14 symbols, depending on the slot configuration. A subframe can also include mini-slots, which generally have fewer symbols than a full slot. Other wireless communication technologies can have different frame structures and / or different channels.

[0075] In certain aspects, the number of slots within a subframe is based on the slot configuration and numerology. For example, for slot configuration 0, different numerologies (μ) 0 to 6 allow for 1, 2, 4, 8, 16, 32, and 64 slots per subframe, respectively. For slot configuration 1, different numerologies 0 to 2 account for 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing can equal 2 μ x 15 kHz, where μ is the numerology 0 to 6. As such, numerology μ = 0 has a subcarrier spacing of 15 kHz, and numerology μ = 6 has a subcarrier spacing of 960 kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figure 4A 、 4B , 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0076] As Figure 4A 、 4BAs illustrated in FIGs. 4C and 4D, a resource grid can be used to represent the frame structure. Each time slot includes resource blocks (RBs) (also referred to as physical RBs (PRBs)) that extend, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0077] As illustrated in FIG. 3, some of the REs carry reference (pilot) signals (RS) for the UE (e.g., UE 104). The RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS). Figure 4A Figure 1 and 3 The RS can include a demodulation RS (DM-RS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE (e.g., UE 104). The RS can also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0078] Figure 4B An example of various DL channels within a subframe is shown. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including, for example, nine RE groups (REGs), each REG including, for example, four consecutive REs in an OFDM symbol. A search space (SS) is a time and frequency region where UEs 104 monitor PDCCH. There are two types of SSs: common search

[0079] A primary synchronization signal (PSS) can be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104) to determine subframe / symbol timing and a physical layer identity. Figure 1 and 3 A secondary synchronization signal (SSS) can be within symbol 4 of particular subframes of a frame. The SSS is utilized by a UE to determine a physical layer cell identity group number and a radio frame timing.

[0080] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides system bandwidth configuration information and a scheduling

[0081] As illustrated in FIG. 3, some of the REs carry reference (pilot) signals (RS) for the UE (e.g., UE 104). The RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS).

[0082] As illustrated in FIG. 3, some of the REs carry reference (pilot) signals (RS) for the UE (e.g., UE 104). The RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS). Figure 4C ​As shown in the figure, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE can transmit DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS can be transmitted in the first one or two symbols of the PUSCH. The PUCCH DMRS can be transmitted with different configurations depending on whether short or long PUCCH is transmitted and depending on the particular PUCCH format used. The UE 104 can transmit a sounding reference signal (SRS). The SRS can be transmitted in the last symbol of a subframe, for example. The SRS can have a comb structure, and a UE can transmit SRS in one of the combs. The SRS can be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0083] Figure 4D An example of various UL channels within a subframe of a frame is shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0084] Aspects related to improved network energy saving (NES) mode

[0085] Power consumption of network entities in large wireless networks (e.g., 4G, 5G, and beyond) is a major concern. In some cases, these network entities (e.g., with respect to Figure 1 and Figure 3 The described BS 102 or the disaggregated BS described with respect to Figure 2 The described BS 102 or the disaggregated BS described with respect to

[0086] In some cases, when the first network entity determines to enter the NES mode, any UE served by the first network entity (e.g., in a radio resource control (RRC) connected mode) can need to be handed over to the second network entity. In this scenario, the first network entity that has determined to enter the NES mode can be associated with a source cell (e.g., a cell from which the UE will be handed over) while the second network entity can be associated with a target cell (e.g., a cell to which the UE is targeted to be handed over from the source cell).

[0087] In some cases, when the first network entity wants to transition to the NES mode, a technique known as conditional handover can be used to hand over the UE from the first network entity to the second network entity. Conditional handover is a type of handover in which the first network entity associated with a serving cell provides a handover command / configuration to the UE that includes one or more trigger conditions that allow the UE to autonomously initiate a handover to the second network entity associated with a target cell. For example, upon receiving the conditional handover command / configuration, the UE can start monitoring one or more candidate neighbor cells. If the UE detects that the one or more trigger conditions have been satisfied, the UE can autonomously initiate a handover to the second network entity associated with the target cell without requiring further assistance from the first network entity associated with the serving cell.

[0088] Accordingly, for example, when used with the NES mode, the first network entity can provide configuration information to one or more UEs that indicates one or more conditions for performing a conditional handover to hand over the one or more UEs to the second network entity associated with a target cell. At some point after providing the configuration information to the one or more UEs, the first network entity can determine to enter the NES mode to conserve power and offload the one or more UEs from the source cell. In response, the first network entity can send a trigger signal to the one or more UEs that triggers the one or more UEs to evaluate at least some of the one or more conditions for performing the conditional handover. If the one or more UEs determine that all of the one or more conditions have been satisfied, the one or more UEs can autonomously trigger a handover to the second network entity associated with the target cell. In some cases, the conditional handover can allow the first network entity to reduce signaling overhead associated with offloading the one or more UEs and quickly enter the NES mode.

[0089] While conditional handover can allow a first network entity to reduce signaling overhead associated with offloading one or more UEs, there can be instances in which some of the one or more UEs can not be able to discover a target cell that provides sufficient quality of service (QoS). This can result in radio link failure (RLF) or a substantial degradation of QoS for these UEs, resulting in wasted time-frequency resources in the wireless network associated with failed transmissions or receptions by these UEs and corresponding retransmissions as well as power resources at these UEs.

[0090] Further, in some cases, even if a second network entity associated with a target cell is available for one or more UEs to be handed over, a large number of these UEs can attempt to send random access channel (RACH) messages to the second network entity (e.g., in order to attach to the second network entity). The large number of RACH messages sent at the same time can result in collisions between the UEs and can result in RLF for some of these UEs, reducing user experience as well as wasting time-frequency resources in the wireless network and power resources at these UEs.

[0091] Accordingly, aspects of the present disclosure provide techniques for helping to avoid these issues associated with using conditional handover when a first network entity determines to enter NES mode. For example, in some cases, the techniques can involve configuring one or more UEs with a conditional handover execution timer. The conditional handover execution timers of the one or more UEs can each be set to different configured time-to-execute time values that specify a different time for each UE to execute a conditional handover to a network entity associated with a target cell. These different configured time-to-execute time values can result in RACH messages from the one or more UEs being staggered in time, avoiding collisions between the UEs and associated wasted time-frequency and power resources.

[0092] Additionally, the techniques presented herein can allow a first network entity that has determined to enter NES mode to delay or cease entering NES mode when at least one of the one or more UEs cannot be handed over to a second network entity. By delaying or not entering NES mode at all, the UEs that cannot be handed over to the second network entity can still be served by the first network entity, avoiding RLF for these UEs and the associated wasted time-frequency and power resources described above. Further, while the first network entity can not be able to enter NES mode, the first network entity can still have a lower load as at least some of the UEs are able to successfully hand over to the target cell, reducing power consumption at the first network entity without completely powering down.

[0093] Example operations of an entity in a communication network

[0094] Figure 5 A process flow including operations 500 for communication between a first network entity 502, a first user equipment (UE) 504, and a second network entity 506 in a network is depicted. In some cases, the first network entity 502 can be associated with a source cell (e.g., a cell that the first UE 504 is currently being served by), and the second network entity 506 can be associated with a target cell (e.g., a cell that the first UE 504 can be handed over to). In some aspects, the first network entity 502 and the second network entity 506 can be examples of the BS 102 depicted and described with respect to Figure 1 and Figure 3 . In other aspects, the first network entity 502 and the second network entity 506 can be examples of the disaggregated base station depicted and described with respect to Figure 2 . Similarly, the first UE 504 can be an example of the UE 104 depicted and described with respect to Figure 1 and Figure 3 . In other aspects, the first UE 504 can be another type of wireless communication device, and the first network entity 502 and the second network entity 506 can be another type of network entity or entities, such as those described herein.

[0095] As shown, the operations 500 can begin, at step 509, with the first network entity 502, the second network entity 506, and the first UE 504 performing a conditional handover setup procedure. In some cases, the conditional handover setup procedure can include steps 0-5 described with respect to Figure 9 .2.3.4.2-1 of the Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.300 version 17.3.0.

[0096] Thereafter, as shown at step 510, the first UE 504 receives configuration information from the first network entity 502 associated with the source cell, the configuration information indicating one or more conditions for performing a conditional handover from the first network entity 502 associated with the source cell to the second network entity 506 associated with the target cell. In some cases, the configuration information can be received in one or more fields of a radio resource control (RRC) message, which includes parameters for defining the one or more conditions. In some cases, the first UE 504 can be configured to perform the conditional handover only if the one or more conditions are satisfied.

[0097] For example, in some cases, the one or more conditions can include one or more signal measurements for the second network entity 506 associated with the target cell being greater than or equal to a threshold value. For example, the one or more signal measurements being greater than or equal to the threshold value can indicate that the first UE 504 can successfully handover to and be served by the second network entity 506 associated with the target cell. In some cases, the configuration information can also include an indication of the threshold value for the one or more signal measurements. In some cases, the one or more signal measurements can include a reference signal received power (RSRP) measurement associated with one or more synchronization signal blocks (SSBs) received from the second network entity 506 associated with the target cell. In some cases, rather than the condition involving the one or more signal measurements for the second network entity 506 being greater than or equal to a threshold value, in some cases, the condition can involve the one or more signal measurements for the second network entity 506 being within a particular range or offset from a signal measurement associated with the first network entity 502.

[0098] In some cases, the one or more conditions can include receiving a trigger signal for the conditional handover from the first network entity 502 associated with the source cell. As will be described below, the trigger signal can be used by the first network entity 502 to trigger one or more UEs, including the first UE 504, to determine whether to handover to a network entity associated with the target cell, such as the second network entity 506.

[0099] In some cases, the one or more conditions can also include a conditional handover execution timer expiring after receiving the trigger signal. For example, the conditional handover execution timer can be used to define a time at which to perform or invoke the conditional handover to handover the first UE 504 to the second network entity 506 associated with the target cell after receiving the trigger signal. In some cases, the conditional handover execution timer can have a starting time value that is set to a configured execution time time value. In other words, the conditional handover execution timer can start at the configured execution time time value and count down from there. In some cases, the configured execution time time value can be received in the configuration information in step 510 or the trigger signal received from the first network entity 502 (e.g., as described below with respect to step 520).

[0100] Additionally, in some cases, to avoid a large number of UEs in the source cell simultaneously sending RACH transmissions to the second network entity 506 associated with the target cell (e.g., which can result in collisions and RLFs, as described above), the configured execution time time value for the first UE 504 can be different from other configured execution time time values associated with other UEs in the source cell for performing the conditional handover. In other words, the first network entity 502 can configure different execution time time values for different UEs such that the time at which these UEs perform or invoke the conditional handover and start sending RACH transmissions to the target cell is different, thereby reducing the chances of RACH message collisions and RLFs.

[0101] As shown in step 515, once the first UE 504 has received the configuration information from the first network entity 502 associated with the source cell, the first network entity 502 can determine to enter the NES mode to conserve power, as described above. In some cases, the first network entity 502 can determine to enter the NES mode when the amount of traffic being handled by the first network entity 502 is below a threshold, traffic associated with UEs served by the first network entity 502 (including the first UE 504) can be adequately handled by other network entities (such as the second network entity 606), or the first network entity 502 is otherwise underutilized.

[0102] Thereafter, as shown in step 520, the first network entity 502 transmits, to the first UE 504 based on determining to enter the NES mode, a trigger signal including a trigger command for the conditional handover. In some cases, the trigger command can trigger the first UE 504 to start a conditional handover execution timer and evaluate one or more conditions for performing the conditional handover. In some cases, the trigger signal can include one bit to indicate the trigger command. In some cases, the trigger signal can include a layer 1 or layer 2 unicast message or a layer 1 broadcast or group message. More specifically, in some cases, the trigger signal includes one of: a unicast downlink control information (DCI) message (e.g., layer 1 signaling), a unicast medium access control-control element (MAC-CE) message (e.g., layer 2 signaling), or a broadcast group DCI message (e.g., layer 1 signaling).

[0103] Thereafter, the first UE 504 can take one or more actions related to performing the conditional handover based on the trigger signal and the one or more conditions, as described in more detail below. Similarly, the first network entity 502 can also take one or more actions related to entering the NES mode based on the trigger signal.

[0104] For example, as indicated by step 525, taking one or more actions can include the first UE 504 starting a conditional handover execution timer using the configured execution time value received in the configuration or trigger signal. Thereafter, as indicated by step 530, taking one or more actions can further include the first UE 504 evaluating whether each of the one or more conditions is satisfied based on the reception of the trigger signal, e.g., while the conditional handover execution timer is running. In some cases, the one or more conditions can be satisfied when (1) the one or more signal measurements associated with the target cell are greater than or equal to a threshold value, (2) the first UE 504 has received a trigger signal for a conditional handover, and (3) the conditional handover execution timer has expired after receiving the trigger signal.

[0105] For example, in some cases, evaluating whether each of the one or more conditions is satisfied can include the first UE 504 determining whether the one or more signal measurements associated with the target cell are greater than or equal to a threshold value. In some cases, the one or more signal measurements include a last available signal measurement associated with the target cell prior to the reception of the trigger signal. In other words, the first UE 504 can rely on measurements already performed associated with the target cell and determine whether those measurements are greater than or equal to a threshold value.

[0106] In some cases, the first UE 504 can perform additional measurements associated with the target cell. For example, in some cases, taking one or more actions can include the first UE 504 performing one or more signal measurements associated with the target cell based on the reception of the trigger signal. In some cases, the first UE 504 can perform the one or more signal measurements prior to the expiration of the conditional handover execution timer. In some cases, the first UE 504 can decide on its own whether to perform additional measurements or performing additional measurements can be based on configuration information received from the first network entity 502 or configuration information stored within a memory of the first UE 504 by a manufacturer or retailer of the first UE 504.

[0107] In some cases, when each of the one or more conditions are satisfied based on the evaluation (e.g., the one or more signal measurements are greater than or equal to the threshold, the first UE 504 has received the trigger signal, and the conditional handover execution timer has expired), the first UE 504 can then take action to perform the conditional handover to handover the first UE 504 from the first network entity associated with the source cell to the second network entity 506 associated with the target cell. For example, as shown in step 532, the first UE 504 can perform the conditional handover with the second network entity 506 to handover the first UE 504 from the first network entity to the second network entity 506. It should be noted that step 532 is shown using a dashed line to indicate that the first UE 504 can not always perform the conditional handover with the second network entity 506, such as when at least one of the one or more conditions are not satisfied.

[0108] In some cases, taking one or more actions can further include the first UE 504 transmitting feedback information to the first network entity 502 associated with the source cell using the set of time-frequency resources based on the evaluation of whether each of the one or more conditions are satisfied, as shown in step 535. In some cases, the feedback information includes hybrid automatic repeat request (HARQ) information and can be transmitted by the first UE 504 in uplink control information (UCI) with a HARQ identifier associated with the conditional handover. In some cases, the HARQ information includes an acknowledgement (ACK) to indicate that the UE is able to perform the conditional handover. In some cases, the HARQ information includes a negative acknowledgement (NACK) to indicate that the UE is not able to perform the conditional handover.

[0109] The feedback information can be transmitted by the first UE 504 in different ways. For example, as will be described in greater detail below, the feedback information can be transmitted in at least one of a scheduling request, UCI on a PUCCH, a medium access control-control element (MAC-CE) message, a RRC message, a random access channel (RACH) message.

[0110] In some cases, the set of time-frequency resources to be used to transmit the feedback information can be included within the configuration information received by the first UE 504 in step 515. In some cases, the set of time-frequency resources can be shared with multiple UEs (including the first UE 504) in the source cell. When the set of time-frequency resources is shared with multiple UEs, the first UE 504 can determine a first subset of time-frequency resources from the set of time-frequency resources to use to transmit the feedback information in a different manner. For example, in some cases, the first UE 504 can perform a sensing operation to determine whether the first subset of time-frequency resources in the set of time-frequency resources is available to use to transmit the feedback information. When the first subset of time-frequency resources is available based on the sensing operation, the first UE 504 can use the first subset of time-frequency resources to transmit the feedback information.

[0111] In some cases, when the set of time-frequency resources is shared with multiple UEs, the trigger signal can dynamically assign different subsets of time-frequency resources to different UEs of the multiple UEs in order to avoid interference between the UEs when transmitting the feedback information. For example, in some cases, the trigger signal can include an indication of a first subset of time-frequency resources from the set of time-frequency resources that is assigned to the first UE 504 to use to transmit the feedback information. The first subset of time-frequency resources can be different from at least a second subset of time-frequency resources from the set of time-frequency resources that is assigned to a second UE of the multiple UEs.

[0112] In some cases, when the trigger signal includes a unicast message, the trigger signal can include a number of bits to indicate the trigger command and the first subset of time-frequency resources. In some cases, when the trigger signal includes a broadcast message or a group message, the trigger signal can include a number of bits to indicate the trigger command, the first subset of time-frequency resources, and a second subset of time-frequency resources.

[0113] In some cases, prior to expiration of the conditional handover execution timer, the first UE 504 can transmit NACK information (e.g., a conditional handover NACK) that indicates that at least one of the one or more conditions is not satisfied and that the first UE 504 is unable to perform the conditional handover. For example, in some cases, if none of the one or more signal measurements associated with the target cell are greater than or equal to the threshold value (e.g., all of the one or more signal measurements are below the threshold value), this can mean that there is no good target cell for the first UE 504 to handover to. In this case, the first UE 504 can transmit the NACK information to inform the first network entity 502 that at least the above-described signal measurement condition is not satisfied.

[0114] In some cases, the NACK information can be transmitted in different ways. For example, the first UE 504 can transmit the NACK information in UCI on a PUCCH. In some cases, the first UE 504 can transmit the NACK information in a MAC-CE on a PUSCH.

[0115] In some cases, the first UE 504 can transmit the NACK information by transmitting a random access channel (RACH) transmission to the first network entity 502. In some cases, receiving the RACH transmission from the first UE 504 by the first network entity 502 can implicitly indicate to the first network entity 502 that the first UE 504 is unable to perform the conditional handover to the second network entity 506 associated with the target cell. In some cases, the RACH transmission can include an explicit indication that at least one of the one or more conditions is not satisfied and the first UE 504 is unable to perform the conditional handover to the second network entity 506 associated with the target cell. In some cases, the first UE 504 can transmit the RACH transmission to indicate the NACK information when there is no transmission opportunity before the conditional handover execution timer expires, or when a scheduling request (SR) cannot be transmitted before the conditional handover execution timer expires.

[0116] In some cases, the feedback information transmitted by the first UE 504 can include ACK information to indicate that all of the one or more conditions are satisfied. The ACK information can indicate to the first network entity 502 that the first UE 504 will proceed with performing the conditional handover to switch the first UE 504 from the first network entity 502 associated with the source cell to the second network entity 506 associated with the target cell.

[0117] As described above, after transmitting the trigger signal in step 520, the first network entity 502 can take one or more actions related to entering the NES mode based on the trigger signal. For example, in some cases, taking the one or more actions can include the first network entity 502 starting a NES execution timer, as shown in step 540. The NES execution timer can have a start time that is set to the execution time time value for entering the NES mode. In some cases, the execution time time value for entering the NES mode can include a value that defines a time between a time of transmission of the trigger signal and a time at which the first network entity 502 is configured to enter the NES mode.

[0118] In some cases, the execution time time value for entering the NES mode can be greater than or equal to a configured execution time time value for a conditional handover execution timer at the first UE 504. In some cases, setting the execution time time value for entering the NES mode to be greater than or equal to the configured execution time time time value for the conditional handover execution timer at the first UE 504 can help prevent a scenario in which the first network entity 502 inadvertently enters the NES mode when all UEs in the source cell are not able to complete a conditional handover to the target cell.

[0119] In some cases, in step 545, taking one or more actions related to entering the NES mode can include entering the NES mode upon expiration of the NES execution timer and without receiving NACK information from any UE in the source cell, including the first UE 504. For example, in this scenario, when the first network entity 502 fails to receive NACK information from any UE in the source cell, including the first UE 504, the first network entity 502 can assume that all UEs are able to offload from the source cell and handover to the target cell, and it is safe for the first network entity 502 to enter the NES mode. For example, in some cases, the first network entity 502 can be configured to power down one or more components, such as power amplifiers, baseband processors, RF components, transmitters, receivers, transceivers, etc.

[0120] However, in some cases, the first network entity 502 can receive NACK information from the first UE 504, such as in the feedback information received in step 535. In such cases, taking one or more actions related to entering the NES mode can include the first network entity 502 determining not to proceed with entering the NES mode, as shown in step 550. In other words, if the first network entity 502 receives a NACK from any UE in the source cell, the first network entity 502 can determine not to proceed with entering the NES mode in step 545.

[0121] However, in some cases, while the first network entity 502 can not be able to enter the NES mode, the first network entity 502 can still have a lower load (e.g., because at least some UEs were able to successfully handover to the target cell), and thus can reduce power without being completely powered down. In some cases, the first network entity 502 can reconfigure thresholds for one or more signal measurements, and can retransmit the trigger signal. Reducing the thresholds can allow any remaining UEs in the source cell to be handed over to the target cell.

[0122] As described above, in some cases, the feedback information received from the first UE 504 can include ACK information indicating that all of the one or more conditions for performing a conditional handover at the first UE 504 are satisfied. In some cases, the first network entity 502 can be configured to use this ACK information to make a determination of whether to proceed into the NES mode. For example, in some cases, to prevent scenarios in which the first network entity 502 prematurely enters the NES mode before all UEs are able to handover to the target cell, the first network entity 502 can be configured to proceed into the NES mode after receiving ACK information from all connected UEs in the source cell, including the ACK information received from the first UE 504, as shown in step 550. In other words, to prevent the first network entity 502 from entering the NES mode prematurely. In some cases, this can also help to avoid scenarios in which one or more UEs in the source cell do not correctly receive the trigger signal, such as when the trigger signal is sent as group or broadcast signaling. However, if the first network entity 502 does not receive ACK information from all connected UEs in the source cell, the first network entity 502 can be configured to refrain from entering the NES mode, as shown in step 555.

[0123] In some cases, as shown in step 555, the first network entity 502 can receive handover success information from one or more second network entities associated with one or more target cells, including the second network entity 506. In some cases, the first network entity 502 can delay entering the NES mode until the first network entity 502 receives handover success information considering all UEs in the source cell. For example, taking one or more actions can involve the first network entity 502 entering the NES mode after receiving conditional handover success information for each of the one or more UEs previously served by the first network entity 502 associated with the source cell, including the first UE 504, in step 545. In some cases, the conditional handover success information can be received from one or more respective target cells associated with each of the one or more UEs, including the second network entity 506 associated with the target cell to which the first UE 504 is handed over. In some cases, in response to receiving the handover success information from the second network entity 506 associated with the target cell, the first network entity 502 can transmit context information for the first UE 504, as shown in step 560.

[0124] In some cases, the conditional handover success information can be received in one handover success message from the second network entity associated with the target cell. In some cases, one handover success message can indicate respective conditional handover success information for multiple UEs, including the first UE 504. In some cases, the handover success message can indicate that the conditional handover has failed for which UEs. In such cases, the first network entity 502 can decide not to enter the NES mode.

[0125] Example operations of a user equipment

[0126] Figure 6 Methods of wireless communication are presented at a first UE, such as a UE 104 and / or a first UE 504 of a first UE of a UE 504, are shown in FIG. 6. Figure 1 and Figure 3 Methods of wireless communication are presented at a first UE, such as a UE 104 and / or a first UE 504 of a first UE of a UE 504, are shown in FIG. 6. Figure 5 Methods of wireless communication are presented at a first UE, such as a UE 104 and / or a first UE 504 of a first UE of a UE 504, are shown in FIG. 6.

[0127] The method 600 begins, at step 605, by receiving configuration information from a first network entity associated with a source cell, the configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with the source cell to a second network entity associated with a target cell. In some cases, the operations of this step involve the reception circuitry and / or code for receiving described with reference to Figure 8 or can be performed by the reception circuitry and / or code for receiving described with reference to Figure 8 or can be performed by the reception circuitry and / or code for receiving described with reference to

[0128] The method 600 then proceeds to step 610, where a trigger signal including a trigger command for the conditional handover is received from the first network entity associated with the source cell. In some cases, the operations of this step involve the reception circuitry and / or code for receiving described with reference to Figure 8 or can be performed by the reception circuitry and / or code for receiving described with reference to Figure 8 or can be performed by the reception circuitry and / or code for receiving described with reference to

[0129] The method 600 then proceeds to step 615, where one or more actions related to performing the conditional handover are taken based on the trigger signal and the one or more conditions. In some cases, the operations of this step involve the taking circuitry and / or code for taking described with reference to Figure 8 or can be performed by the taking circuitry and / or code for taking described with reference to Figure 8 or can be performed by the taking circuitry and / or code for taking described with reference to

[0130] In some aspects, the one or more conditions include: one or more signal measurements associated with the target cell being greater than or equal to a threshold value; reception of the trigger signal for the conditional handover; and a conditional handover execution timer having expired after the reception of the trigger signal.

[0131] In some aspects, taking the one or more actions includes: starting a conditional handover execution timer based on the reception of the trigger signal, where the conditional handover execution timer has a start time value set to a configured execution time time value.

[0132] In some aspects, the configured execution time time value is received in the configuration information or the trigger signal; and the configured execution time time value is different from other configured execution time time values associated with other UEs in the source cell for performing the conditional handover.

[0133] In some aspects, taking the one or more actions includes evaluating whether each of the one or more conditions is satisfied based on the reception of the trigger signal.

[0134] In some aspects, when each of the one or more conditions is satisfied based on the evaluation, taking the one or more actions includes performing the conditional handover to handover the UE from a first network entity associated with the source cell to a second network entity associated with the target cell.

[0135] In some aspects, evaluating whether each of the one or more conditions is satisfied includes determining whether one or more signal measurements associated with the target cell are greater than or equal to a threshold value.

[0136] In some aspects, the one or more signal measurements include a last available signal measurement associated with the target cell prior to the reception of the trigger signal.

[0137] In some aspects, taking the one or more actions further includes performing one or more signal measurements associated with the target cell based on the reception of the trigger signal prior to an expiration of a conditional handover execution timer.

[0138] In some aspects, taking the one or more actions further includes transmitting feedback information to the first network entity associated with the source cell using a set of time- frequency resources based on the evaluation of whether each of the one or more conditions is satisfied.

[0139] In some aspects, the feedback information includes hybrid automatic repeat request (HARQ) information transmitted in uplink control information (UCI) and having a HARQ identifier associated with the conditional handover. In some aspects, the HARQ information includes an acknowledgement (ACK) to indicate that the UE is capable of performing the conditional handover. In some aspects, the HARQ information includes a negative acknowledgement (NACK) to indicate that the UE is not capable of performing the conditional handover.

[0140] In some aspects, the set of time-frequency resources is indicated in the configuration information.

[0141] In some aspects, the set of time-frequency resources is shared with multiple UEs in the source cell, including the first UE.

[0142] In some aspects, the method 600 further includes performing a sensing operation to determine whether a first subset of time-frequency resources of the set of time-frequency resources is available for transmitting the feedback information. In some aspects, transmitting the feedback information includes transmitting the feedback information using the first subset of time-frequency resources when, based on the sensing operation, the first subset of time-frequency resources is available.

[0143] In some aspects, based on the set of time-frequency resources being shared with multiple UEs, the trigger signal includes an indication of a first subset of time-frequency resources from the set of time-frequency resources that is allocated to the first UE for transmitting the feedback information.

[0144] In some aspects, the first subset of time-frequency resources is different from at least a second subset of time-frequency resources from the set of time-frequency resources that is allocated to a second UE.

[0145] In some aspects, when the trigger signal includes a unicast message, the trigger signal includes a number of bits to indicate the trigger command and the first subset of time-frequency resources; and when the trigger signal includes a broadcast or group message, the trigger signal includes a number of bits to indicate the trigger command, the first subset of time-frequency resources, and a second subset of time-frequency resources.

[0146] In some aspects, transmitting the feedback information includes transmitting NACK information indicating that at least one of the one or more conditions is not satisfied before the conditional handover execution timing expires.

[0147] In some aspects, transmitting the NACK information includes at least one of: transmitting the NACK information in UCI on a PUCCH; or transmitting the NACK information in a MAC-CE on a PUSCH.

[0148] In some aspects, transmitting the NACK information includes transmitting a RACH transmission, where the RACH transmission indicates the NACK information.

[0149] In some aspects, transmitting the feedback information includes transmitting ACK information indicating that all of the one or more conditions are satisfied.

[0150] In some aspects, the trigger signal includes one bit to indicate the trigger command.

[0151] In some aspects, the trigger signal includes one of: a unicast DCI message; a unicast MAC-CE message; or a broadcast group DCI message.

[0152] In one aspect, the method 600, or any aspect related thereto, can be performed by an apparatus, such as Figure 8The communication device 800 includes various components operable, configured, or adapted to perform method 600. The communication device 800 will be described in more detail below.

[0153] Notice, Figure 6 This is just one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0154] Example operations of network entities

[0155] Figure 7 An example of a method 700 for wireless communication at a first network entity associated with a source cell is shown, the first network entity being such as Figure 1 and Figure 3 BS102, Figure 5 First network entity 502, or as per the above Figure 2 The decomposed base station under discussion.

[0156] Method 700 begins at step 705, in which configuration information is sent to a first UE, the configuration information indicating one or more conditions for performing a conditional handover from a first network entity associated with a source cell to a second network entity associated with a target cell. In some cases, the operation of this step involves, as referenced... Figure 9 The described circuitry for transmission and / or the code for transmission may be provided by reference, etc. Figure 9 The circuitry and / or code described are used to execute the transmission.

[0157] Then, method 700 proceeds to step 710, where it is determined that NES mode has been entered. In some cases, this step involves referencing... Figure 9 The circuitry and / or code described for determination, or may be derived from references Figure 9 The described circuitry and / or code are used to determine the execution.

[0158] Then, method 700 proceeds to step 715, wherein, based on determining that NES mode has been entered, a trigger signal including a trigger command for conditional handover is sent to the first UE. In some cases, the operation of this step involves, as described in reference... Figure 9 The described circuitry for transmission and / or the code for transmission may be provided by reference, etc. Figure 9 The circuitry and / or code described are used to execute the transmission.

[0159] Method 700 then proceeds to step 720, where one or more actions related to entering NES mode are taken based on a trigger signal. In some cases, this step involves referencing... Figure 9The described circuitry for taking and / or code for taking, or that can be executed by the reference Figure 8 The described circuitry for taking and / or code for taking, or that can be executed by the reference

[0160] In some aspects, the one or more conditions include: one or more signal measurements associated with the target cell being greater than or equal to a threshold value; reception of a trigger signal for the conditional handover; and a conditional handover execution timer having expired after the reception of the trigger signal at the first UE.

[0161] In some aspects, the conditional handover execution timer is based on a configured execution time time value for the first UE; the configured execution time time value is transmitted in the configuration information or the trigger signal; and the configured execution time time value for the first UE is different from other configured execution time time values associated with other UEs in the source cell for performing the conditional handover.

[0162] In some aspects, the configured execution time time value for the first UE is less than or equal to an execution time time value for entering the NES mode.

[0163] In some aspects, taking one or more actions related to entering the NES mode includes: starting a NES execution timer, where the NES execution timer has a start time set to an execution time time value for entering the NES mode; and entering the NES mode upon expiration of the NES execution timer and in the absence of receiving NACK information from any UE in the source cell, including the first UE.

[0164] In some aspects, the method 700 further includes receiving feedback information from the first UE using a set of time-frequency resources. In some cases, the operations of this step involve the reference Figure 9 The described circuitry for receiving and / or code for receiving, or that can be executed by the reference Figure 8 The described circuitry for receiving and / or code for receiving, or that can be executed by the reference

[0165] In some aspects, the feedback information includes hybrid automatic repeat request (HARQ) information received in uplink control information (UCI) and having a HARQ identifier associated with the conditional handover. In some aspects, the HARQ information includes an acknowledgement (ACK) to indicate that the UE is able to perform the conditional handover. In some aspects, the HARQ information includes a negative acknowledgement (NACK) to indicate that the UE is not able to perform the conditional handover.

[0166] In some aspects, the set of time-frequency resources is indicated in the configuration information.

[0167] In some aspects, the set of time-frequency resources is shared with multiple UEs, including the first UE, in the source cell.

[0168] In some aspects, based on the set of time-frequency resources being shared with multiple UEs, the trigger signal includes an indication of a first subset of time-frequency resources from the set of time-frequency resources that is allocated to the first UE for transmitting the feedback information.

[0169] In some aspects, the first subset of time-frequency resources is different from at least a second subset of time-frequency resources from the set of time-frequency resources that is allocated to a second UE.

[0170] In some aspects, when the trigger signal includes a unicast message, the trigger signal includes a number of bits to indicate the trigger command and the first subset of time-frequency resources; and when the trigger signal includes a broadcast or group message, the trigger signal includes a number of bits to indicate the trigger command, the first subset of time-frequency resources, and the second subset of time-frequency resources.

[0171] In some aspects, receiving the feedback information includes receiving NACK information indicating that at least one of the one or more conditions is not satisfied.

[0172] In some aspects, the NACK information is received from the first UE prior to an expiration of a conditional handover execution timer associated with the first UE; and taking the one or more actions includes not entering the NES mode based on the reception of the NACK information.

[0173] In some aspects, receiving the NACK information includes at least one of: receiving the NACK information in UCI on a PUCCH; or receiving the NACK information in a MAC-CE on a PUSCH.

[0174] In some aspects, receiving the NACK information includes receiving a RACH transmission from the first UE, where the RACH transmission indicates the NACK information.

[0175] In some aspects, receiving the feedback information includes receiving ACK information from the first UE indicating that all of the one or more conditions are satisfied.

[0176] In some aspects, taking the one or more actions includes entering the NES mode after receiving ACK information from all connected UEs in the source cell, including the ACK information received from the first UE.

[0177] In some aspects, taking the one or more actions includes entering the NES mode only after receiving conditional handover success information for each of one or more UEs (including the first UE) previously served by a first network entity associated with the source cell.

[0178] In some aspects, the conditional handover success information is received from a second network entity associated with the target cell in a handover success message indicating conditional handover success information for a plurality of UEs including the first UE.

[0179] In some aspects, the conditional handover success information is received from a second network entity associated with the target cell in a handover success message indicating conditional handover success information for a plurality of UEs including the first UE.

[0180] In some aspects, the trigger signal includes one bit to indicate the trigger command.

[0181] In some aspects, the trigger signal includes one of: a unicast DCI message; a unicast MAC-CE message; or a broadcast group DCI message.

[0182] In one aspect, the method 700, or any aspect related thereto, can be performed by an apparatus, such as Figure 9 the communication device 900 including various components operative!y configured or adapted to perform the method 700. The communication device 900 will be described in more detail below.

[0183] Note that Figure 7 is just one example of a method and other methods including fewer, additional, or alternative steps are possible and consistent with the present disclosure.

[0184] Example communication device

[0185] Figure 8 Aspects of an example communication device 800 are depicted. In some aspects, the communication device 800 is a user equipment, such as the UE 104 described above with respect to Figure 1 and / or the first UE 504 described above with respect to Figure 3 . Figure 5 .

[0186] The communication device 800 includes a processing system 805 coupled to a transceiver 845 (e.g., a transmitter and / or a receiver). The transceiver 845 is configured to transmit and receive signals for the communication device 800 via an antenna 850, such as the various signals as described herein. The processing system 805 can be configured to perform processing functions for the communication device 800, including processing signals to be received and / or transmitted by the communication device 800.

[0187] The processing system 805 can include one or more processors 810. In various aspects, the one or more processors 810 can represent a single core processor, or can include Figure 3one or more of the described receive processor 358, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380. The one or more processors 810 are coupled to a computer-readable medium / memory 825 via a bus 840. In certain aspects, the computer-readable medium / memory 825 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 810, cause the one or more processors 810 to perform Figure 6 the described method 600, or any of the aspects related thereto. Note that reference to a processor that performs a function of the communication device 800 can include one or more processors 810 that perform that function of the communication device 800.

[0188] In the depicted example, the computer-readable medium / memory 825 stores code (e.g., executable instructions), such as code 830 for receiving and code 835 for taking one or more actions. Processing of the code 830 for receiving and the code 835 for taking one or more actions can cause the communication device 800 to perform the described method 600, or any of the aspects related thereto. Figure 6 the described method 600, or any of the aspects related thereto.

[0189] The one or more processors 810 include circuitry configured to implement (e.g., to perform) code stored in the computer-readable medium / memory 825, including code such as circuitry for receiving 815 and circuitry for taking 820. Processing with the circuitry for receiving 815 and the circuitry for taking 820 can cause the communication device 800 to perform the described method 600, or any of the aspects related thereto. Figure 6 the described method 600, or any of the aspects related thereto.

[0190] The various components of the communication device 800 can provide means for performing the described method 600, or any of the aspects related thereto. For example, means for transmitting, sending, or outputting for transmission can include the transceiver 845 and / or the antenna 850 of the communication device 800 in Figure 6 the described method 600, or any of the aspects related thereto. For example, means for transmitting, sending, or outputting for transmission can include the transceiver 354 and / or the antenna 352 of the UE 104 shown in FIG. 13, and / or Figure 3 the communication device 800 in Figure 8 the described method 600, or any of the aspects related thereto. For example, means for transmitting, sending, or outputting for transmission can include the transceiver 354 and / or the antenna 352 of the UE 104 shown in FIG. 13, and / or Figure 3 the communication device 800 in Figure 8 the described method 600, or any of the aspects related thereto. For example, means for transmitting, sending, or outputting for transmission can include the transceiver 354 and / or the antenna 352 of the UE 104 shown in FIG. 13, and / or

[0191] Figure 9 Aspects of an example communication device 900 are depicted. In some aspects, the communication device 900 is a network entity, such as Figure 1 and Figure 3BS 102, the above regarding Figure 5 the first network entity 502 described, or as discussed regarding Figure 2 the disaggregated base station.

[0192] The communication device 900 includes a processing system 905 coupled to a transceiver 965 (e.g., a transmitter and / or a receiver) and / or a network interface 975. The transceiver 965 is configured to transmit and receive signals for the communication device 900 via an antenna 970, such as the various signals as described herein. The network interface 975 is configured to obtain and send signals for the communication device 900 via a communication link, such as a backhaul link, a midhaul link, and / or a front haul link as described herein, for example, with respect to Figure 2 described. The processing system 905 can be configured to perform processing functions for the communication device 900, including processing signals to be received and / or transmitted by the communication device 900.

[0193] The processing system 905 can include one or more processors 910. In various aspects, the one or more processors 910 can represent one or more of the receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340 as described with respect to Figure 3 the base station 102 described. The one or more processors 910 are coupled to a computer- readable medium / memory 935 via bus 960. In certain aspects, the computer-readable medium / memory 935 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 910, cause the one or more processors 910 to perform the method 700 described with respect to Figure 7 or any aspects related thereto. Note that references to processors of the communication device 900 performing functions can include one or more processors 910 of the communication device 900 performing the function.

[0194] In the depicted example, the computer-readable medium / memory 935 stores code (e.g., executable instructions), such as code for transmitting 940, code for determining 945, code for taking one or more actions 950, and code for receiving 955. Processing of the code for transmitting 940, code for determining 945, code for taking one or more actions 950, and code for receiving 955 can cause the communication device 900 to perform the method 700 described with respect to Figure 7 or any aspects related thereto.

[0195] The one or more processors 910 include circuitry configured to implement (e.g., to perform) code stored in the computer-readable medium / memory 935, including code to: circuitry 915 for transmitting, circuitry 920 for determining, circuitry 925 for taking, and circuitry 930 for receiving. The processing of the circuitry 915 for transmitting, circuitry 920 for determining, circuitry 925 for taking, and circuitry 930 for receiving can be facilitated by the Figure 7 The described method 700 or any aspects related thereto.

[0196] The various components of the communication device 900 can provide means for performing the methods described herein Figure 7 The described method 700 or any aspects related thereto. Means for transmitting, sending, or outputting for transmission can include the transceiver 332 and / or the antenna 334 of the BS 102 as illustrated in FIG. 3 and / or the transceiver 965 and the antenna 970 of the communication device 900 in Figure 3 The described method 700 or any aspects related thereto. Means for transmitting, sending, or outputting for transmission can include the transceiver 332 and / or the antenna 334 of the BS 102 as illustrated in FIG. 3 and / or the transceiver 965 and the antenna 970 of the communication device 900 in Figure 9 The described method 700 or any aspects related thereto. Means for transmitting, sending, or outputting for transmission can include the transceiver 332 and / or the antenna 334 of the BS 102 as illustrated in FIG. 3 and / or the transceiver 965 and the antenna 970 of the communication device 900 in Figure 3 The described method 700 or any aspects related thereto. Means for transmitting, sending, or outputting for transmission can include the transceiver 332 and / or the antenna 334 of the BS 102 as illustrated in FIG. 3 and / or the transceiver 965 and the antenna 970 of the communication device 900 in Figure 9 The described method 700 or any aspects related thereto. Means for transmitting, sending, or outputting for transmission can include the transceiver 332 and / or the antenna 334 of the BS 102 as illustrated in FIG. 3 and / or the transceiver 965 and the antenna 970 of the communication device 900 in

[0197] Example Clauses

[0198] Implementation examples are described in the following numbered clauses:

[0199] Clause 1 : A method for wireless communication at a first UE, comprising: receiving, from a first network entity associated with a source cell, configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with the source cell to a second network entity associated with a target cell; receiving, from the first network entity associated with the source cell, a trigger signal comprising a trigger command for the conditional handover; and taking one or more actions related to performing the conditional handover based on the trigger signal and the one or more conditions.

[0200] Clause 2: The method of clause 1, wherein the one or more conditions comprise: one or more signal measurements associated with the target cell being greater than or equal to a threshold value; the reception of the trigger signal for the conditional handover; and a conditional handover execution timer having expired after the reception of the trigger signal.

[0201] Clause 3: The method of clause 2, wherein taking the one or more actions comprises: starting the conditional handover execution timer based on the reception of the trigger signal, wherein the conditional handover execution timer has a start time value set to a configured execution time time value.

[0202] Clause 4: The method of clause 3, wherein the configured execution time time value is received in the configuration information or the trigger signal; and the configured execution time time value is different from other configured execution time time values associated with other UEs in the source cell for performing conditional handover.

[0203] Clause 5: The method of any of clauses 3-4, wherein taking the one or more actions comprises: evaluating whether each of the one or more conditions is satisfied based on the reception of the trigger signal.

[0204] Clause 6: The method of clause 5, wherein when each of the one or more conditions is satisfied based on the evaluation, taking the one or more actions comprises: performing the conditional handover to switch the UE from the first network entity associated with the source cell to the second network entity associated with the target cell.

[0205] Clause 7: The method of any of clauses 5-6, wherein evaluating whether each of the one or more conditions is satisfied comprises: determining whether the one or more signal measurements associated with the target cell are greater than or equal to the threshold value.

[0206] Clause 8: The method of clause 7, wherein the one or more signal measurements comprise last available signal measurements associated with the target cell prior to the reception of the trigger signal.

[0207] Clause 9: The method of clause 7, wherein taking the one or more actions further comprises: performing the one or more signal measurements associated with the target cell based on the reception of the trigger signal prior to expiration of the conditional handover execution timer.

[0208] Clause 10: The method of any of clauses 5-9, wherein taking the one or more actions further comprises: transmitting feedback information to the first network entity associated with the source cell using a set of time-frequency resources based on the evaluation of whether each of the one or more conditions is satisfied.

[0209] Clause 11: The method of clause 10, wherein: the feedback information comprises hybrid automatic repeat request (HARQ) information, the HARQ information being transmitted in uplink control information (UCI) and having a HARQ identifier associated with the conditional handover; the HARQ information comprises an acknowledgement (ACK) to indicate that the UE is capable of performing the conditional handover; and the HARQ information comprises a negative acknowledgement (NACK) to indicate that the UE is not capable of performing the conditional handover.

[0210] Clause 12: The method of any of clauses 10-11, wherein the set of time- frequency resources is indicated in the configuration information.

[0211] Clause 13: The method of any of clauses 10-12, wherein the set of time- frequency resources is shared with a plurality of UEs in the source cell, including the first UE.

[0212] Clause 14: The method of clause 13, performing a sensing operation to determine whether a first subset of time-frequency resources of the set of time-frequency resources is available for transmitting the feedback information, wherein transmitting the feedback information comprises: transmitting the feedback information using the first subset of time-frequency resources when the first subset of time-frequency resources is available based on the sensing operation.

[0213] Clause 15: The method of clause 13, wherein, based on the set of time- frequency resources being shared with the plurality of UEs, the trigger signal comprises an indication of a first subset of time-frequency resources from the set of time- frequency resources that is assigned to the first UE for transmitting the feedback information.

[0214] Clause 16: The method of clause 15, wherein the first subset of time- frequency resources is different from at least a second subset of time-frequency resources from the set of time-frequency resources that is assigned to a second UE.

[0215] Clause 17: The method of clause 16, wherein: when the trigger signal comprises a unicast message, the trigger signal comprises a plurality of bits to indicate the trigger command and the first subset of time-frequency resources; and when the trigger signal comprises a broadcast or group message, the trigger signal comprises a plurality of bits to indicate the trigger command, the first subset of time- frequency resources, and the second subset of time-frequency resources.

[0216] Clause 18: The method of any of clauses 10-17, wherein transmitting the feedback information comprises transmitting, prior to expiration of the conditional handover execution timer, NACK information indicating that at least one of the one or more conditions is not satisfied.

[0217] Clause 19: The method of clause 18, wherein transmitting the NACK information comprises at least one of: transmitting the NACK information in UCI on a PUCCH; or transmitting the NACK information in a MAC-CE on a PUSCH.

[0218] Clause 20: The method of clause 18, wherein transmitting the NACK information comprises transmitting a RACH transmission, wherein the RACH transmission indicates the NACK information.

[0219] Clause 21: The method of any of clauses 10-17, wherein transmitting the feedback information comprises transmitting ACK information indicating that all of the one or more conditions are satisfied.

[0220] Clause 22: The method of any of clauses 1-21, wherein the trigger signal comprises one bit indicating the trigger command.

[0221] Clause 23: The method of any of clauses 1-22, wherein the trigger signal comprises one of: a unicast DCI message; a unicast MAC-CE message; or a broadcast group DCI message.

[0222] Clause 24: A method for wireless communication at a first network entity associated with a source cell, comprising: transmitting, to a first UE, configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with the source cell to a second network entity associated with a target cell; determining to enter an NES mode; transmitting, to the first UE based on the determination to enter the NES mode, a trigger signal comprising a trigger command for the conditional handover; and taking one or more actions related to entering an NES mode based on the trigger signal.

[0223] Clause 25: The method of clause 24, wherein the one or more conditions comprise: one or more signal measurements associated with the target cell being greater than or equal to a threshold; the reception of the trigger signal for the conditional handover; and a conditional handover execution timer having expired after reception of the trigger signal at the first UE.

[0224] Clause 26: The method of clause 25, wherein the conditional handover execution timer is based on a configured execution time time value for the first UE; the configured execution time time value is transmitted in the configuration information or the trigger signal; and the configured execution time time value for the first UE is different from other configured execution time time values associated with other UEs in the source cell for performing conditional handover.

[0225] Clause 27: The method of clause 26, wherein the configured execution time time value for the first UE is less than or equal to an execution time time value for entering the NES mode.

[0226] Clause 28: The method of clause 27, wherein taking the one or more actions related to entering the NES mode comprises: starting a NES execution timer, wherein the NES execution timer has a start time set to the execution time time value for entering the NES mode; and entering the NES mode upon expiration of the NES execution timer and in the absence of receiving NACK information from any UE in the source cell, including the first UE.

[0227] Clause 29: The method of any of clauses 24-28, further comprising: receiving feedback information from the first UE using a set of time-frequency resources.

[0228] Clause 30: The method of clause 29, wherein: the feedback information comprises hybrid automatic repeat request (HARQ) information, the HARQ information is received in uplink control information (UCI) and has a HARQ identifier associated with the conditional handover; the HARQ information comprises an acknowledgement (ACK) to indicate that the UE is able to perform the conditional handover; and the HARQ information comprises a negative acknowledgement (NACK) to indicate that the UE is not able to perform the conditional handover.

[0229] Clause 31: The method of any of clauses 29-30, wherein the set of time-frequency resources is indicated in the configuration information.

[0230] Clause 32: The method of any of clauses 29-31, wherein the set of time-frequency resources is shared with multiple UEs in the source cell, including the first UE.

[0231] Clause 33: The method of clause 32, wherein, based on the set of time-frequency resources being shared with the plurality of UEs, the trigger signal comprises an indication of a first subset of time-frequency resources from the set of time-frequency resources that is allocated to the first UE for transmitting the feedback information.

[0232] Clause 34: The method of clause 33, wherein the first subset of time-frequency resources is different from at least a second subset of time-frequency resources from the set of time-frequency resources that is allocated to a second UE.

[0233] Clause 35: The method of clause 34, wherein: when the trigger signal comprises a unicast message, the trigger signal comprises a plurality of bits to indicate the trigger command and the first subset of time-frequency resources; and when the trigger signal comprises a broadcast or group message, the trigger signal comprises a plurality of bits to indicate the trigger command, the first subset of time-frequency resources, and the second subset of time-frequency resources.

[0234] Clause 36: The method of any of clauses 29-35, wherein receiving the feedback information comprises receiving NACK information indicating that at least one of the one or more conditions is not satisfied.

[0235] Clause 37: The method of clause 36, wherein: the NACK information is received from the first UE prior to an expiration of a conditional handover execution timer associated with the first UE; and taking the one or more actions comprises not entering the NES mode based on the reception of the NACK information.

[0236] Clause 38: The method of any of clauses 36-37, wherein receiving the NACK information comprises at least one of: receiving the NACK information in UCI on a PUCCH; or receiving the NACK information in a MAC-CE on a PUSCH.

[0237] Clause 39: The method of any of clauses 36-37, wherein receiving the NACK information comprises receiving a RACH transmission from the first UE, wherein the RACH transmission indicates the NACK information.

[0238] Clause 40: The method of any of clauses 29-35, wherein receiving the feedback information comprises receiving ACK information from the first UE indicating that all of the one or more conditions are satisfied.

[0239] Clause 41 : The method of clause 40, wherein taking the one or more actions comprises entering the NES mode after receiving ACK information from all connected UEs in the source cell, the ACK information including ACK information received from the first UE.

[0240] Clause 42: The method of any of clauses 24-41, wherein taking the one or more actions comprises entering the NES mode only after receiving conditional handover success information for each of one or more UEs, including the first UE, previously served by the first network entity associated with the source cell.

[0241] Clause 43: The method of clause 42, wherein the conditional handover success information is received from one or more respective target cells associated with each of the one or more UEs, the one or more respective target cells including a target cell associated with the first UE.

[0242] Clause 44: The method of clause 42, wherein the conditional handover success information is received in one handover success message from the second network entity associated with the target cell, the handover success message indicating conditional handover success information for multiple UEs including the first UE.

[0243] Clause 45: The method of any of clauses 24-44, wherein the trigger signal includes one bit to indicate the trigger command.

[0244] Clause 46: The method of any of clauses 24-45, wherein the trigger signal comprises one of: a unicast DCI message; a unicast MAC-CE message; or a broadcast group DCI message.

[0245] Clause 47: An apparatus comprising: memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method of any of clauses 1-46.

[0246] Clause 48: An apparatus comprising means for performing the method of any of clauses 1-46.

[0247] Clause 49: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the method of any of clauses 1-46.

[0248] Clause 50: A computer program product, embodied on a computer- readable storage medium, comprising code for performing a method in accordance with any of Clauses 1-46.

[0249] Additional Considerations

[0250] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting in terms of the scope, applicability, or configurations set forth in the claims. Various modifications can be made by those skilled in the art to the

[0251] The various illustrative logical blocks, modules, and circuits described in connection with the present disclosure can be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an ASIC, a Field Programmable Gate Array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any commercially available processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a

[0252] As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination of multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

[0253] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing, and the like.

[0254] The methods disclosed herein comprise one or more actions for implementing the methods. The actions of the methods can be interchanged with one another without departing from the scope of the claims. That is, the order of the specific actions can be modified and / or used unless a specific order is specified, without departing from the scope of the claims. Furthermore, various operations of the methods described above can be performed by any suitable means including, but not limited to, any type of hardware, software, and / or firmware, including the functionality of any suitable components under the control of a processor. Means for performing the operations of the various aspects can include any suitable components and / or means for performing the functions of the various aspects.

[0255] The appended claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within the claims, the term “comprises” does not exclude the presence of other elements or steps. Furthermore, unless otherwise noted, the use of the negative “does not” does not exclude the presence of a positive element or step. The use of the positive “comprises” does not preclude the presence of unknown or other elements or steps. The words “a” or “an” do not denote the singular which per se, but rather denote either the singular or plural. The recitation of multiple references to elements does not constitute an admission that any or all of these numerous elements are commonly- owned, unless otherwise indicated. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

1. A method for wireless communication at a first user equipment (UE), comprising: Receive configuration information from a first network entity associated with the source cell, the configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with the source cell to a second network entity associated with the target cell; Receive a trigger signal including a trigger command for the conditional handover from the first network entity associated with the source cell; as well as Based on the trigger signal and the one or more conditions, take one or more actions related to performing the conditional switch.

2. The method according to claim 1, wherein, The one or more conditions include: One or more signal measurements associated with the target cell are greater than or equal to a threshold; The reception of the trigger signal used for the conditional switching; and The conditional switching execution timer expired after receiving the trigger signal.

3. The method according to claim 2, wherein, Taking one or more of the aforementioned actions includes: The conditional switching execution timer is started based on the receipt of the trigger signal, wherein the conditional switching execution timer has a start time value set to a configured execution time value; and The reception of the trigger signal is used to evaluate whether each of the one or more conditions is met.

4. The method according to claim 3, wherein: The configured execution time value is received from the configuration information or the trigger signal; and The execution time value of the configuration is different from the execution time value of other configurations associated with other UEs in the source cell for performing conditional handover.

5. The method according to claim 3, wherein, When each of the one or more conditions is met based on the evaluation, taking the one or more actions includes: performing the conditional handover to switch the UE from the first network entity associated with the source cell to the second network entity associated with the target cell.

6. The method according to claim 3, wherein: Evaluating whether each of the one or more conditions is met includes: determining whether the one or more signal measurements associated with the target cell are greater than or equal to the threshold; and One of the following: The one or more signal measurements include the last available signal measurement associated with the target cell prior to the reception of the trigger signal; or Taking the one or more actions further includes performing the one or more signal measurements associated with the target cell based on the reception of the trigger signal before the conditional handover execution timer expires.

7. The method according to claim 3, wherein: Taking the one or more actions further includes: based on the assessment of whether each of the one or more conditions is met, using a time-frequency resource set to send feedback information to the first network entity associated with the source cell; and The time-frequency resource set is indicated in the configuration information.

8. The method according to claim 7, wherein: The feedback information includes Hybrid Automatic Repeat Request (HARQ) information, which is sent in uplink control information (UCI) and has a HARQ identifier associated with the conditional handover; The HARQ information includes an ACK indicating that the UE can perform the conditional handover; and The HARQ information includes a negative acknowledgment (NACK) to indicate that the UE cannot perform the conditional handover.

9. The method according to claim 7, wherein, The time-frequency resource set is shared with multiple UEs in the source cell, including the first UE.

10. The method of claim 9, further comprising: Perform a sensing operation to determine whether a first time-frequency resource subset in the time-frequency resource set is available for sending the feedback information, wherein sending the feedback information includes: when the first time-frequency resource subset is available based on the sensing operation, using the first time-frequency resource subset to send the feedback information.

11. The method according to claim 9, wherein: Since the time-frequency resource set is shared with the multiple UEs, the trigger signal includes an indication of a first time-frequency resource subset from the time-frequency resource set that is allocated to the first UE for sending the feedback information; as well as The first time-frequency resource subset is different from the at least second time-frequency resource subset allocated to the second UE from the time-frequency resource set.

12. The method according to claim 7, wherein: Sending the feedback information includes: before the conditional switch execution timer expires, sending a negative acknowledgment (NACK) message indicating that at least one of the one or more conditions is not met; and Sending the NACK message includes at least one of the following: The NACK information is transmitted in the uplink control information (UCI) on the physical uplink control channel (PUCCH); The NACK information is sent in the Media Access Control-Control Element (MAC-CE) on the Physical Uplink Shared Channel (PUSCH); or Send a random access channel (RACH) transmission, wherein the RACH transmission indicates the NACK information.

13. The method according to claim 7, wherein, Sending the feedback information includes sending an acknowledgment (ACK) message indicating that all conditions in the one or more conditions have been met.

14. The method according to claim 1, wherein, The trigger signal includes one of the following: Unicast downlink control information (DCI) message; Unicast Media Access Control-Control Element (MAC-CE) message; or Broadcast group downlink control information (DCI) message.

15. A method for wireless communication at a first network entity associated with a source cell, comprising: Send configuration information to a first user equipment (UE), the configuration information indicating one or more conditions for performing a conditional handover from a first network entity associated with the source cell to a second network entity associated with the target cell; Confirm entry into Network Energy Saving (NES) mode; Based on the determination of entering the NES mode, a trigger signal including a trigger command for the conditional handover is sent to the first UE; and One or more actions related to entering the NES mode are taken based on the trigger signal.

16. The method according to claim 15, wherein, The one or more conditions include: One or more signal measurements associated with the target cell are greater than or equal to a threshold; The reception of the trigger signal used for the conditional switching; and The conditional switching execution timer expired after the first UE received the trigger signal.

17. The method of claim 16, wherein: The conditional handover execution timer is based on the execution time value configured for the first UE; The configured execution time value is sent in the configuration information or the trigger signal; as well as The execution time value of the configuration for the first UE is different from the execution time value of other configurations associated with other UEs in the source cell for performing conditional handover.

18. The method of claim 17, wherein: The execution time value of the configuration for the first UE is less than or equal to the execution time value for entering the NES mode; as well as Taking one or more actions related to entering the NES mode includes: Start the NES execution timer, wherein the NES execution timer has a start time set to an execution time value for entering the NES mode; and When the NES execution timer expires and no negative acknowledgment (NACK) information is received from any UE in the source cell, including the first UE, the NES mode is entered.

19. The method of claim 15, further comprising: Using a time-frequency resource set, feedback information is received from the first UE, wherein the time-frequency resource set is indicated in the configuration information.

20. The method of claim 19, wherein: The feedback information includes Hybrid Automatic Repeat Request (HARQ) information, which is received in uplink control information (UCI) and has a HARQ identifier associated with the conditional handover; The HARQ information includes an ACK indicating that the UE can perform the conditional handover; and The HARQ information includes a negative acknowledgment (NACK) to indicate that the UE cannot perform the conditional handover.

21. The method according to claim 19, wherein, The time-frequency resource set is shared with multiple UEs in the source cell, including the first UE.

22. The method according to claim 21, wherein: Since the time-frequency resource set is shared with the multiple UEs, the trigger signal includes an indication of a first time-frequency resource subset from the time-frequency resource set that is allocated to the first UE for sending the feedback information; as well as The first time-frequency resource subset is different from the at least second time-frequency resource subset allocated to the second UE from the time-frequency resource set.

23. The method according to claim 19, wherein, Receiving the feedback information includes receiving a negative acknowledgment (NACK) message indicating that at least one of the one or more conditions has not been met.

24. The method according to claim 23, wherein: The NACK information is received from the first UE before the conditional handover execution timer associated with the first UE expires; and Taking one or more of the actions includes not entering the NES mode based on the receipt of the NACK information.

25. The method according to claim 23, wherein, Receiving the NACK information includes at least one of the following: Receive the NACK information in the uplink control information (UCI) on the Physical Uplink Control Channel (PUCCH); or The NACK information is received in the Media Access Control-Control Element (MAC-CE) on the Physical Uplink Shared Channel (PUSCH); or The first UE receives a random access channel (RACH) transmission, wherein the RACH transmission indicates the NACK information.

26. The method according to claim 19, wherein: Receiving the feedback information includes: receiving acknowledgment (ACK) information from the first UE indicating that all conditions in the one or more conditions have been met; and Taking one or more of the actions includes: entering the NES mode after receiving ACK information from all connected UEs in the source cell, the ACK information including ACK information received from the first UE.

27. The method of claim 15, wherein: Taking the one or more actions includes: entering the NES mode only after receiving a conditional handover success message for each of one or more UEs, including the first UE, previously served by the first network entity associated with the source cell; and One of the following: The conditional handover success information is received from one or more corresponding target cells associated with each of the one or more UEs, the one or more corresponding target cells including the target cell associated with the first UE; or The conditional handover success information is received from the second network entity associated with the target cell in a handover success message, the handover success message indicating the conditional handover success information for a plurality of UEs including the first UE.

28. The method according to claim 15, wherein, The trigger signal includes one of the following: Unicast downlink control information (DCI) message; Unicast Media Access Control-Control Element (MAC-CE) message; or Broadcast group downlink control information (DCI) message.

29. A first user equipment (UE), comprising: Memory, which includes executable instructions; as well as A processor configured to execute the executable instructions and cause the first UE to perform the following operations: Receive configuration information from a first network entity associated with the source cell, the configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with the source cell to a second network entity associated with the target cell; Receive a trigger signal including a trigger command for the conditional handover from the first network entity associated with the source cell; as well as Based on the trigger signal and the one or more conditions, take one or more actions related to performing the conditional switch.

30. A first network entity, comprising: Memory, which includes executable instructions; as well as A processor configured to execute the executable instructions and cause the first network entity to perform the following operations: Send configuration information to a first user equipment (UE), the configuration information indicating one or more conditions for performing a conditional handover from a first network entity associated with the source cell to a second network entity associated with the target cell; Confirm entry into Network Energy Saving (NES) mode; Based on the determination of entering the NES mode, a trigger signal including a trigger command for the conditional handover is sent to the first UE; and One or more actions related to entering the NES mode are taken based on the trigger signal.

Images