Techniques for improving network energy saving modes

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, 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 performing one or more actions related to performing the conditional handover based on the trigger signal and the one or more conditions.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to U.S. Patent Application No. 18 / 186,108, filed March 17, 2023, which is incorporated herein by reference. [Background technology]

[0002] Field of Disclosure Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for improving network energy saving (NES) modes.

[0003] 2. Description of Related Art Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with the users.

[0004] While wireless communication systems have made significant technological advances over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continuing desire to improve the technical performance of wireless communication systems, including, for example, improving the speed and data-carrying capacity of communication, improving the efficiency of use of a shared communication medium, reducing the power used by transmitters and receivers during communication, improving the reliability of wireless communication, avoiding redundant transmissions and / or receptions and associated processing, improving the coverage area of ​​wireless communication, increasing the number and types of devices that can access a wireless communication system, improving the ability for different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, further improvements in wireless communication systems are needed to overcome the aforementioned technical challenges and others. Summary of the Invention [Means for solving the problem]

[0005] One aspect provides a method for wireless communication in a first user equipment (UE), the method including: receiving configuration information from a first network entity associated with a source cell 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 from the first network entity associated with the source cell including a trigger command for the conditional handover; and performing one or more actions related to performing the conditional handover based on the trigger signal and the one or more conditions.

[0006] Another aspect provides a method for wireless communication in a first network entity associated with a source cell, the method including: transmitting, to a first UE, 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 a target cell; determining to enter a network energy saving (NES) mode; based on the decision to enter the NES mode, transmitting, to the first UE, a trigger signal including a trigger command for the conditional handover; and performing, based on the trigger signal, one or more actions related to entering the NES mode.

[0007] Other aspects provide an apparatus operable, configured, or adapted to perform any one or more of the foregoing methods and / or methods described elsewhere herein; a non-transitory computer-readable medium including instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium including code for performing the foregoing methods and methods described elsewhere herein; and / or an apparatus comprising means for performing the foregoing methods and methods described elsewhere herein. By way of example, the apparatus may include a processing system, a device having a processing system, or processing systems cooperating over one or more networks.

[0008] The following description and the accompanying drawings set forth certain features for purposes of illustration.

[0009] The accompanying figures illustrate certain features of the various aspects described herein and should not be construed as limiting the scope of the present disclosure. [Brief explanation of the drawings]

[0010] [Figure 1]1 illustrates an exemplary wireless communication network. [Figure 2] 1 illustrates an exemplary split base station architecture. [Figure 3] 1 illustrates aspects of an exemplary base station and exemplary user equipment. [Figure 4A] 1 illustrates various example aspects of data structures for a wireless communication network. [Figure 4B] 1 illustrates various example aspects of data structures for a wireless communication network. [Figure 4C] 1 illustrates various example aspects of data structures for a wireless communication network. [Figure 4D] 1 illustrates various example aspects of data structures for a wireless communication network. [Figure 5] 1 illustrates a process flow for communication within a network between a first network entity, a second network entity, and user equipment. [Figure 6] SUMMARY OF THE INVENTION A method for wireless communication is presented. [Figure 7] SUMMARY OF THE INVENTION A method for wireless communication is presented. [Figure 8] 1 illustrates aspects of an exemplary communications device. [Figure 9] 1 illustrates aspects of an exemplary communications device. DETAILED DESCRIPTION OF THE INVENTION

[0011] Aspects of the present disclosure provide an apparatus, method, processing system, and computer-readable medium for improving network energy saving (NES) modes.

[0012] 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 may be capable of operating in a network energy saving (NES) mode, which allows these network entities to power down certain components to conserve power. However, in some cases, while a first network entity may decide to enter the NES mode, there may still be user equipments (UEs) being served by the first network entity. In such cases, the first network entity, which may be associated with a source cell, may take one or more actions to hand over these UEs to a second network entity, which is associated with a target cell.

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

[0014] Thus, in some cases, when a first network entity decides to enter the NES mode, the first network entity may send a trigger signal to one or more UEs to trigger them to evaluate one or more trigger conditions and, if the one or more trigger conditions are satisfied, perform a conditional handover to the second network entity. However, not all of the UEs may be able to be handed over to the second network entity. Therefore, if the first network entity proceeds to enter the NES mode, this may result in a poor user experience by causing radio link failures in the UEs that could not be handed over, and waste of time-frequency and power resources associated with missing transmissions or receptions and corresponding retransmissions. Furthermore, even if all of the UEs are able to be handed over to the second network entity, many of these UEs may end up transmitting random access channel (RACH) messages simultaneously (e.g., to connect to the second network entity), which may result in collisions between the UEs. These collisions may result in RLF in these UEs, leading to wasted time-frequency and power resources.

[0015] Accordingly, aspects of the present disclosure provide techniques to help avoid these problems associated with the use of conditional handover when a first network entity decides to enter an NES mode. For example, in some cases, the first network entity may configure different conditional handover execution timers for different UEs to stagger the times at which these UEs can transmit RACH messages to hand over to the second network entity, thereby reducing collisions between UEs. Furthermore, in some cases, the first network entity may delay entering the NES mode or not enter the NES mode at all if at least one UE cannot be handed over to the second network entity. Therefore, by delaying or not entering the NES mode, these UEs can still be served by the first network entity, thereby avoiding wasting RLF and associated time-frequency and power resources.

[0016] Introduction to Wireless Communication Networks The techniques and methods described herein may be used in connection with various wireless communication networks. Although aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technology, aspects of the present disclosure may be equally applicable to other communication systems and standards not explicitly mentioned herein.

[0017] FIG. 1 illustrates an example of a wireless communication network 100 in which aspects described herein may be implemented.

[0018] Generally, the wireless communication network 100 includes various network entities (or alternatively, network elements or network nodes). A network entity generally refers to a communication device and / or a communication function performed by a communication device (e.g., a user equipment (UE), a base station (BS), components of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with the network can be considered network entities. Furthermore, the wireless communication network 100 includes terrestrial aspects, such as a ground-based network entity (e.g., a BS 102), and non-terrestrial aspects, such as a satellite 140 and an 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.

[0019] In the illustrated embodiment, wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and a 5G Core (5G Core, 5GC) network 190, which interoperate to provide communication services over various communication links, including wired and wireless links.

[0020] 1 illustrates various exemplary UEs 104, which may 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, 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. The UEs 104 may 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.

[0021] The BS 102 communicates wirelessly with the UE 104 (e.g., transmits signals to or receives signals from the UE 104) via a communication link 120. The communication link 120 between the BS 102 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from the BS 102 to the UE 104. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0022] The BSs 102 may generally include a NodeB, an enhanced NodeB (eNB), a next generation enhanced NodeB (ng-eNB), a next generation NodeB (gNB or gNodeB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a transmission / reception point, etc. Each of the BSs 102 may provide communication coverage for a corresponding geographic coverage area 110, which may also be referred to as a cell and, in some cases, may overlap (e.g., a small cell 102′ may have a coverage area 110′ that overlaps with the coverage area 110 of a macro cell). A BS may provide communication coverage for, for example, a macrocell (covering a relatively large geographic area), a picocell (covering a relatively smaller geographic area, such as a sports stadium), a femtocell (covering a relatively smaller geographic area (e.g., a home)), and / or other types of cell.

[0023] Although the BS 102 is shown in various aspects as an integrated communications device, the BS 102 may be implemented in various configurations. For example, one or more components of a base station may be separated, including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a near-real time (RT) RAN intelligent controller (RIC), or a non-real time (Non-RT) RIC, to name a few. In alternative embodiments, various aspects of a base station may be virtualized. More generally, a base station (e.g., the BS 102) may include components located at a single physical location or components located at various physical locations. In embodiments in which a base station includes components located at various physical locations, the various components may each perform functions such that the various components collectively achieve the same functionality as a base station located at a single physical location. In some aspects, a base station that includes components located at different physical locations may be referred to as a disaggregated radio access network architecture, such as an Open RAN (O-RAN) architecture or a Virtualized RAN (VRAN) architecture. Figure 2 illustrates and describes an exemplary disaggregated base station architecture.

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

[0025] The wireless communication network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other characteristics. In some aspects, this subdivision is provided based on wavelength and frequency, where the frequency may also be referred to as a carrier, subcarrier, frequency channel, tone, or subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz to 7125 MHz, which is often (interchangeably) referred to as "sub-6 GHz." Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24,250 MHz to 71,000 MHz, which may (interchangeably) be referred to as "millimeter wave" ("mmW" or "mm-wave"). In some cases, FR2 may be further defined in terms of subranges, such as a first subrange FR2-1 including 24,250 MHz to 52,600 MHz, and a second subrange FR2-2 including 52,600 MHz to 71,000 MHz. A base station configured to communicate using mm-wave / quasi-mm-wave radio frequency bands (e.g., mm-wave base station such as BS180) may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0026] The communication link 120 between the BS 102 and, for example, the UE 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 in various aspects. The carriers may or may not be adjacent to one another. The allocation of carriers may be asymmetric for the DL and UL (e.g., more or fewer carriers may be allocated for the DL than for the UL).

[0027] Communications using higher frequency bands may have higher path loss and shorter range compared to communications at lower frequencies. Therefore, a particular base station (e.g., 180 in FIG. 1) may utilize beamforming 182 with the UE 104 to improve path loss and range. For example, the BS 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive the beamformed signal from the BS 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the BS 180 in one or more transmit directions 182″. The BS 180 may also receive the beamformed signal from the UE 104 in one or more receive directions 182′. In that case, the BS 180 and the UE 104 may perform beam training to determine the best receive and transmit directions for each of the BS 180 and the UE 104. In particular, the transmit and receive directions for the BS 180 may or may not be the same. Similarly, the transmit and receive directions for the UE 104 may or may not be the same.

[0028] The wireless communication network 100 further includes a Wi-Fi AP 150 that communicates with Wi-Fi stations (STAs) 152 via communication links 154, for example, in the 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.

[0029] Particular UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may 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), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0030] The EPC 160 may include various functional components, including, such as in the illustrated embodiment, 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. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management.

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

[0032] The BM-SC 170 may provide functionality related to provisioning and distribution of MBMS user services. The BM-SC 170 may act as an entry point for content provider MBMS transmissions and may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN) and / or may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to deliver MBMS traffic to BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a particular service, and / or may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0033] The 5GC 190 may include various functional 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 may communicate with a Unified Data Management (UDM) 196.

[0034] The AMF 192 is a control node that handles signaling between the UE 104 and the 5GC 190. The AMF 192 provides, for example, quality of service (QoS), flow and session management.

[0035] Internet Protocol (IP) packets are forwarded through UPF 195, which connects to IP services 197 and provides UE IP address allocation and other functions for 5GC 190. IP services 197 may include, for example, the Internet, intranet, IMS, PS streaming services, and / or other IP services.

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

[0037] 2 illustrates the architecture of an exemplary separated base station 200. The separated base station 200 architecture may include one or more central units (CUs) 210 that can communicate directly with the core network 220 via a backhaul link or indirectly with the core network 220 through one or more separated base station units (e.g., a near-real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (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 corresponding midhaul links, such as an F1 interface. The DUs 230 can communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. The RUs 240 can communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 240 simultaneously.

[0038] Each of the units, e.g., CU 210, DU 230, RU 240, quasi-RT RIC 225, non-RT RIC 215, and SMO framework 205, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of those units, may be configured to communicate with one or more of the other units over a transmission medium. For example, the units may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally or alternatively, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., a radio frequency (RF) transceiver) configured to receive, transmit, or receive signals over a wireless transmission medium to one or more of the other units.

[0039] In some aspects, the CU 210 can host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may implement an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may 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 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may bidirectionally communicate with the CU-CP units via an interface, such as an E1 interface. The CU 210 may be implemented to communicate with the DU 230 as needed for network control and signaling.

[0040] The DU 230 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (e.g., modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional division such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 230 may further host one or more lower PHY layers. Each layer (or module) may implement 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.

[0041] The lower layer functions may be performed by one or more RUs 240. In some deployments, the RUs 240 controlled by the DUs 230 may correspond to logical nodes hosting RF processing functions, lower PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, the RU(s) 240 may 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 RU(s) 240 may be controlled by the corresponding DUs 230. In some scenarios, this configuration may enable the DU(s) 230 and CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0042] The SMO framework 205 can be configured to support RAN deployment 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 related to RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (e.g., an open cloud (O-cloud) 290) via a cloud computing platform interface (e.g., an O2 interface) to perform lifecycle management of the network element (e.g., to instantiate virtualized network elements). Such virtualized network elements can include, but are not limited to, the CU 210, the DU 230, the RU 240, and the quasi-RT RIC 225. In some implementations, the SMO framework 205 can communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 211, via the O1 interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0043] The non-RT RIC 215 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / functions in the quasi-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the quasi-RT RIC 225 (e.g., via an A1 interface). The quasi-RT RIC 225 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action via interfaces (e.g., via an E2 interface) that connect one or more CUs 210, one or more DUs 230, or both, and the O-eNB to the quasi-RT RIC 225.

[0044] In some implementations, the non-RT RIC 215 can receive parameters or external enrichment information from an external server to generate AI / ML models to be deployed in the quasi-RT RIC 225. Such information can be utilized by the quasi-RT RIC 225 and can be received at the SMO framework 205 or the non-RT RIC 215 from non-network data sources or from network functions. In some embodiments, the non-RT RIC 215 or the quasi-RT RIC 225 can be configured to adjust RAN behavior or performance. For example, the non-RT RIC 215 can employ AI / ML models to monitor long-term trends and patterns in performance and take corrective action through the SMO framework 205 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0045] FIG. 3 illustrates aspects of an example BS 102 and UE 104.

[0046] Generally, 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 other aspects that enable wireless reception of data (e.g., data sink 339). For example, the BS 102 can transmit and receive data between the BS 102 and the UE 104. The BS 102 includes a controller / processor 340 that can be configured to perform various functions described herein related to wireless communications.

[0047] Generally, 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 a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communication.

[0048] For an exemplary downlink transmission, 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 a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. In some embodiments, the data can be for a physical downlink shared channel (PDSCH).

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

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

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

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

[0053] For an exemplary uplink transmission, the UE 104 further includes a transmit processor 364 that can receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 can also generate reference symbols for a reference signal (e.g., for a 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 a modulator in the transceivers 354a-354r (e.g., for SC-FDM, etc.), and transmitted to the BS 102.

[0054] At BS 102, uplink signals from UE 104 may be received by antennas 334a-t, processed by demodulators in transceivers 332a-t, 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 UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to a controller / processor 340.

[0055] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0056] A scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0057] In various aspects, the BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data 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" may refer to various mechanisms for obtaining data, such as obtaining data 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.

[0058] In various aspects, the UE 104 may also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data 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" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-t, a transceiver 354a-t, an RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0059] In some aspects, the processor may be configured to perform various operations, such as those associated with the methods described herein, to transmit (output) data to or receive (obtain) data from another interface configured to transmit or receive data, respectively.

[0060] 4A, 4B, 4C, and 4D illustrate aspects of data structures for a wireless communication network, such as wireless communication network 100 of FIG.

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

[0062] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers (e.g., as shown in FIGS. 4B and 4D). Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0063] The wireless communication frame structure may be frequency division duplex (FDD) where, for a particular set of subcarriers, subframes within that set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD) where, for a particular set of subcarriers, subframes within that set of subcarriers are dedicated to both DL and UL.

[0064] In Figures 4A and 4C, the wireless communication frame structure is TDD, where D is DL, U is UL, and X is flexible with respect to usage between DL / UL. The UE can be configured with the slot format through a received slot format indicator (SFI) (either dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). In the illustrated embodiment, a 10 ms frame is divided into ten equally sized 1 ms subframes. Each subframe may include one or more time slots. In some embodiments, each slot may include 7 or 14 symbols, depending on the slot format. A subframe may also include a minislot, which typically has fewer symbols than an entire slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0065] In certain aspects, the number of slots in a subframe is based on the slot configuration and numerology. For example, for slot configuration 0, different numerologies (μ) 0-6 allow for 1, 2, 4, 8, 16, 32, and 64 slots per subframe, respectively. For slot configuration 1, different numerologies 0-2 allow for 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. Subcarrier spacing and symbol length / duration are functions of numerology. Subcarrier spacing is 2 μThe symbol length / duration can be equal to 15 μs × 15, where μ is a numerology between 0 and 6. Therefore, 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. Figures 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.

[0066] As shown in Figures 4A, 4B, 4C, and 4D, a resource grid can be used to represent the frame structure. Each time slot includes resource blocks (RBs) (also called physical RBs (PRBs)), for example, spanning 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.

[0067] As shown in Figure 4A, some of the REs carry reference (pilot) signals (RS) for the UE (e.g., the UE 104 in Figures 1 and 3). The RSs may include demodulation RSs (DMRSs) and / or channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and / or phase tracking RSs (PT-RSs).

[0068] 4B shows an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including, for example, 9 RE groups (REGs), each REG including, for example, 4 consecutive REs within an OFDM symbol.

[0069] A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE (e.g., 104 in Figures 1 and 3) to determine subframe / symbol timing and physical layer identification information.

[0070] A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identity and the timing of the radio frame.

[0071] Based on the physical layer identity and the group number of the physical layer cell identity, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. A physical broadcast channel (PBCH) carrying a master information block (MIB) may be logically grouped with a PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and a system frame number (SFN). A physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and / or paging messages.

[0072] As shown in FIG. 4C , some of the REs carry DMRS (shown as R for one particular configuration, although 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, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE 104 can transmit a sounding reference signal (SRS). The SRS can be transmitted, for example, in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS in one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

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

[0074] Aspects Related to Network Energy Saving (NES) Mode Improvements Power consumption of network entities in large-scale wireless networks (e.g., 4G, 5G, and beyond) is a major concern. In some cases, these network entities (e.g., BS 102 described with respect to FIGS. 1 and 3, or a separate BS as described with respect to FIG. 2) may use a network energy saving (NES) mode to help reduce this power consumption. While operating in NES mode, power consumption may be reduced by putting the network entity to a sleep state, allowing one or more components of the network entity (e.g., a power amplifier, a baseband processor, RF components, a transmitter, a receiver, a transceiver, etc.) to be powered down. In some cases, a network entity may decide to enter NES mode when it is not serving any user equipment (UEs), when there is little or no traffic associated with any UEs being served, or when the coverage provided by the network entity to any UEs being served can be adequately provided by another network entity in the wireless network.

[0075] In some cases, when a first network entity decides to enter the NES mode, any UEs served by the first network entity (e.g., in a Radio Resource Control (RRC) connected mode) may need to be handed over to a second network entity. In this scenario, the first network entity that decided to enter the NES mode may be associated with a source cell (e.g., a cell from which the UE is to be handed over), while the second network entity may be associated with a target cell (e.g., a cell that is being targeted for handing over the UE from the source cell).

[0076] In some cases, if the first network entity desires to transition to the NES mode, it may use a technique known as a conditional handover to hand over the UE from the first network entity to the second network entity. A conditional handover is a type of handover in which a first network entity associated with a serving cell provides the UE with a handover command / configuration that includes one or more trigger conditions that enable the UE to autonomously initiate a handover to a second network entity associated with a target cell. For example, upon receiving the conditional handover command / configuration, the UE may begin monitoring one or more candidate neighbor cells. If the UE detects that one or more trigger conditions are met, the UE may autonomously initiate a handover to a second network entity associated with the target cell without further assistance from the first network entity associated with the serving cell.

[0077] Thus, for example, when used in the NES mode, a first network entity may provide configuration information to one or more UEs indicating one or more conditions for performing a conditional handover to hand over the one or more UEs to a 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 may decide to enter the NES mode to save power and offload one or more UEs from the source cell. In response, the first network entity may trigger the one or more UEs to evaluate at least some of the one or more conditions for performing a conditional handover by sending a trigger signal to the one or more UEs. If the one or more UEs determine that all of the one or more conditions are met, the one or more UEs may autonomously trigger a handover to the second network entity associated with the target cell. In some cases, the conditional handover may enable the first network entity to quickly enter NES mode, reducing the signaling overhead associated with offloading one or more UEs.

[0078] Although conditional handover may enable a first network entity to reduce signaling overhead associated with offloading one or more UEs, there may be instances where some of the one or more UEs may not be able to find a target cell that provides sufficient Quality of Service (QoS), which may lead to radio link failure (RLF) or significant degradation of QoS for these UEs, resulting in wasted time-frequency resources in the wireless network and wasted power resources in these UEs associated with failed transmissions or receptions by these UEs and corresponding retransmissions.

[0079] Furthermore, in some cases, even if a second network entity associated with the target cell is available to one or more UEs to be handed over, many of these UEs may attempt to transmit Random Access Channel (RACH) messages to the second network entity (e.g., to connect to the second network entity). This simultaneous transmission of many RACH messages may result in collisions between UEs and may lead to RLF for some of these UEs, thereby degrading the user experience and wasting time-frequency resources in the wireless network and power resources in these UEs.

[0080] Accordingly, aspects of the present disclosure provide techniques to help avoid these problems associated with the use of conditional handover when a first network entity decides to enter NES mode. For example, in some cases, these techniques may involve configuring one or more UEs with a conditional handover execution timer. By setting the conditional handover execution timers of one or more UEs to different configured advance notice execution time values, each UE can specify a different time for executing a conditional handover to the network entity associated with the target cell. These different configured advance notice execution time values ​​can result in RACH messages from one or more UEs being staggered in time, thereby avoiding collisions between UEs and the associated waste of time-frequency and power resources.

[0081] Furthermore, the techniques presented herein may enable a first network entity that has decided to enter NES mode to delay or stop entering NES mode if at least one of one or more UEs is unable to be handed over to a second network entity. By delaying or not entering NES mode at all, UEs that are unable to be handed over to a second network entity can still be served by the first network entity, thereby avoiding the RLF and associated waste of time-frequency and power resources for these UEs described above. Furthermore, because the first network entity may not be able to enter NES mode, but at least some UEs may be able to successfully handover to a target cell, the first network entity still has a lower load and, therefore, power consumption at the first network entity can be reduced without being completely powered off.

[0082] Exemplary Operation of Entities in a Communication Network 5 illustrates a process flow including operations 500 for communication within a network between a first network entity 502, a first user equipment (UE) 504, and a second network entity 506. In some cases, the first network entity 502 may be associated with a source cell (e.g., a cell to which the first UE 504 is currently served), and the second network entity 506 may be associated with a target cell (e.g., a cell to which the first UE 504 can be handed over). In some aspects, the first network entity 502 and the second network entity 506 may be an embodiment of the BS 102 illustrated and described with respect to FIGS. 1 and 3 or the separate base station illustrated and described with respect to FIG. 2. Similarly, the first UE 504 may be an embodiment of the UE 104 illustrated and described with respect to FIGS. 1 and 3. However, in other aspects, the first UE 504 may be another type of wireless communication device, and the first network entity 502 and the second network entity 506 may be another type of network entity or network node, such as those described herein.

[0083] As shown, the operations 500 may begin at step 509, where the first network entity 502, the second network entity 506, and the first UE 504 perform a conditional handover setup procedure. In some cases, the conditional handover setup procedure may include steps 0 through 5, described with reference to Figure 9.2.3.4.2-1 of 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.300, version 17.3.0.

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

[0085] For example, in some cases, the one or more conditions may include one or more signal measurements related to the second network entity 506 associated with the target cell being equal to or greater than a threshold. For example, the one or more signal measurements being equal to or greater than a threshold may indicate that the first UE 504 has been successfully handed over to, and is capable of being served by, the second network entity 506 associated with the target cell. In some cases, the configuration information may further include an indication of a threshold for the one or more signal measurements. In some cases, the one or more signal measurements may 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, this condition does not involve one or more signal measurements for the second network entity 506 being above a threshold, and in some cases, this condition may involve one or more signal measurements for the second network entity 506 being within a particular range or offset from the signal measurements associated with the first network entity 502.

[0086] In some cases, the one or more conditions may include receiving a trigger signal for a conditional handover from a first network entity associated with the source cell 502. As 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 hand over to a network entity associated with the target cell, such as a second network entity 506.

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

[0088] Furthermore, in some cases, to avoid many of the 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 RLF, as described above), the configured advance notice time value for execution for the first UE 504 may be different from other configured advance notice time values ​​for execution for performing a conditional handover that are associated with other UEs in the source cell. In other words, the first network entity 502 may configure different advance notice time values ​​for execution for different UEs, thereby reducing the likelihood of RACH message collisions and RLF by causing these UEs to perform or invoke a conditional handover and start sending RACH transmissions to the target cell at different times.

[0089] When the first UE 504 receives configuration information from the first network entity 502 associated with the source cell, as shown in step 515, the first network entity 502 may decide to enter the NES mode to conserve power, as described above. In some cases, the first network entity 502 may decide to enter the NES mode if the amount of traffic being processed by the first network entity 502 falls below a threshold, traffic associated with UEs (including the first UE 504) served by the first network entity 502 can be adequately processed by other network entities, such as the second network entity 606, or the first network entity 502 is underutilized.

[0090] Thereafter, as shown in step 520, the first network entity 502 transmits a trigger signal including a trigger command for a conditional handover to the first UE 504 based on the decision to enter the NES mode. In some cases, the trigger command may trigger the first UE 504 to start a conditional handover execution timer and to evaluate one or more conditions for executing the conditional handover. In some cases, the trigger signal may include one bit to indicate the trigger command. In some cases, the trigger signal may include a Layer 1 or Layer 2 unicast message, or a Layer 1 broadcast message 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 media access control-control element (MAC-CE) message (e.g., Layer 2 signaling), or a broadcast group DCI message (e.g., Layer 1 signaling).

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

[0092] For example, as shown in step 525, taking the one or more actions may include the first UE 504 starting a conditional handover execution timer using a configured execution advance time value received in the configuration signal or the trigger signal. Thereafter, as shown in step 530, taking the one or more actions may further include the first UE 504 evaluating whether each of one or more conditions is met based on receipt of the trigger signal, e.g., while the conditional handover execution timer is running. In some cases, the one or more conditions may be met if (1) one or more signal measurements associated with the target cell are greater than or equal to a threshold, (2) the first UE 504 receives a trigger signal for a conditional handover, and (3) after receipt of the trigger signal, the conditional handover execution timer expires.

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

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

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

[0096] In some cases, taking the one or more actions may 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 an evaluation of whether each of the one or more conditions is met, as shown in step 535. In some cases, the feedback information may include hybrid automatic repeat request (HARQ) information and may be transmitted by the first UE 504 as transmitted in uplink control information (UCI) with a HARQ identifier associated with the conditional handover. In some cases, the HARQ information includes an acknowledgement (ACK) indicating that the UE is capable of performing the conditional handover. In some cases, the HARQ information includes a negative acknowledgement (NACK) indicating that the UE is unable to perform the conditional handover.

[0097] The feedback information may be transmitted by the first UE 504 in various manners. For example, as described in more detail below, the feedback information may be transmitted within at least one of a scheduling request, a UCI on a PUCCH, a Medium Access Control - Control Element (MAC-CE) message, an RRC message, or a Random Access Channel (RACH) message.

[0098] In some cases, the set of time frequency resources used to transmit the feedback information may be included in the configuration information received by the first UE 504 in step 515. In some cases, the set of time frequency resources may be shared with multiple UEs in the source cell, including the first UE 504. If the set of time frequency resources is shared with multiple UEs, the first UE 504 may determine a first subset of time frequency resources from the set of time frequency resources to be used to transmit the feedback information in a different manner. For example, in some cases, the first UE 504 may perform a sensing operation to determine whether a first subset of time frequency resources from the set of time frequency resources is available for transmitting the feedback information. If the first subset of time frequency resources is available based on the sensing operation, the first UE 504 may transmit the feedback information using the first subset of time frequency resources.

[0099] In some cases, when a set of time-frequency resources is shared with multiple UEs, the trigger signal may dynamically allocate different subsets of the time-frequency resources to different UEs among the multiple UEs to avoid interference between the UEs when transmitting feedback information. For example, in some cases, the trigger signal may include an indication of a first subset of time-frequency resources from the set of time-frequency resources allocated to a first UE 504 for transmitting feedback information. This first subset of time-frequency resources may be different from at least a second subset of time-frequency resources from the set of time-frequency resources allocated to a second UE among the multiple UEs.

[0100] In some cases, if the trigger signal comprises a unicast message, the trigger signal may include multiple bits to indicate the trigger command and the first subset of time-frequency resources. In some cases, if the trigger signal comprises a broadcast message or a group message, the trigger signal may include multiple bits to indicate the trigger command, the first subset of time-frequency resources, and the second subset of time-frequency resources.

[0101] In some cases, prior to expiration of the conditional handover execution timer, the first UE 504 may transmit NACK information (e.g., a conditional handover NACK) indicating that at least one of the one or more conditions is not met and that the first UE 504 is not capable of performing the conditional handover. For example, in some cases, if none of the one or more signal measurements associated with the target cell is above or equal to a threshold (e.g., all of the one or more signal measurements are below a threshold), this may mean that there is no good target cell to handover the first UE 504 to. In this case, the first UE 504 may transmit NACK information to notify the first network entity 502 that at least the above-mentioned signal measurement conditions are not met.

[0102] In some cases, the NACK information may be transmitted in various manners. For example, the first UE 504 may transmit the NACK information within the UCI on the PUCCH. In some cases, the first UE 504 may transmit the NACK information within the MAC-CE on the PUSCH.

[0103] In some cases, the first UE 504 may 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 may implicitly indicate to the first network entity 502 that the first UE 504 was unable to perform a conditional handover to the second network entity 506 associated with the target cell. In some cases, the RACH transmission may include an explicit indication that at least one of the one or more conditions is not met and that the first UE 504 was unable to perform a conditional handover to the second network entity 506 associated with the target cell. In some cases, the first UE 504 may transmit a RACH transmission to indicate the NACK information if a transmission opportunity does not exist before expiration of a conditional handover execution timer or if it is not able to transmit a scheduling request (SR) before expiration of the conditional handover execution timer.

[0104] In some cases, the feedback information transmitted by the first UE 504 may include ACK information indicating that all conditions in the one or more conditions have been met. The ACK information may indicate to the first network entity 502 that the first UE 504 proceeds with executing a conditional handover to hand over 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.

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

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

[0107] In some cases, performing one or more actions related to entering the NES mode in step 545 may include entering the NES mode without receiving NACK information from any UE in the source cell, including the first UE 504, upon expiration of the NES execution timer. For example, in this scenario, if the first network entity 502 is unable to receive NACK information from any UE in the source cell, including the first UE 504, the first network entity 502 may assume that all UEs were able to be offloaded from the source cell and handed over to the target cell and that it is safe for the first network entity 502 to enter the NES mode. For example, in some cases, the first network entity 502 may be configured to power down one or more components, such as a power amplifier, a baseband processor, RF components, a transmitter, a receiver, a transceiver, etc.

[0108] However, in some cases, the first network entity 502 may receive NACK information from the first UE 504, such as in the feedback information received in step 535. In such a case, performing one or more actions related to entering the NES mode may include the first network entity 502 deciding 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 may decide not to proceed with entering the NES mode in step 545.

[0109] However, in some cases, the first network entity 502 may not be able to enter NES mode, but the first network entity 502 may still have a lower load (e.g., because at least some UEs may be able to successfully handover to the target cell), thereby allowing it to reduce power without powering off completely. In some cases, the first network entity 502 may reconfigure thresholds for one or more signal measurements and resend the trigger signal. Lowering the thresholds may allow any remaining UEs in the source cell to be handed over to the target cell.

[0110] As described above, in some cases, the feedback information received from the first UE 504 may include ACK information indicating that all conditions in one or more conditions for performing a conditional handover at the first UE 504 have been met. In some cases, the first network entity 502 may be configured to use this ACK information to make a decision on whether to proceed with entering the NES mode. For example, in some cases, to prevent a scenario 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 may be configured to proceed with entering the NES mode, as shown in step 550, after receiving ACK information from all connected UEs in the source cell, including the ACK information received from the first UE 504. In other words, to prevent the first network entity In some cases, this may also help to avoid a scenario in which one or more UEs in the source cell do not receive the trigger signal correctly, such as when the trigger signal is transmitted as group signaling or broadcast signaling. However, in the case of the first network entity

[0111] In some cases, as shown in step 555, the first network entity 502 may receive handover success information from one or more second network entities associated with the one or more target cells, including the second network entity 506. In some cases, the first network entity 502 may delay entering the NES mode until the first network entity 502 receives handover success information that takes into account all (previous) UEs in the source cell. For example, performing the one or more actions may involve the first network entity 502 entering the NES mode in step 545 after receiving conditional handover success information for each UE of one or more UEs previously served by the first network entity 502 associated with the source cell, including the first UE 504. In some cases, the conditional handover success information may be received from one or more corresponding target cells associated with each UE 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 handover success information from the second network entity 506 associated with the target cell, the first network entity 502 may transmit context information regarding the first UE 504, as shown in step 560.

[0112] In some cases, the conditional handover success information may be received in a single handover success message from a second network entity associated with the target cell. In some cases, the single handover success message may indicate corresponding conditional handover success information for multiple UEs, including the first UE 504. In some cases, the handover success message may indicate for which UEs the conditional handover failed. In such cases, the first network entity 502 may decide not to enter NES mode.

[0113] Exemplary Operation of User Equipment FIG. 6 illustrates one embodiment of a method 600 of wireless communication in a first UE, such as the UE 104 of FIGS. 1 and 3 and / or the first UE 504 of FIG.

[0114] Method 600 begins at step 605 of 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 may refer to or be performed by circuitry and / or code for receiving, such as those described with reference to FIG. 8.

[0115] The method 600 then proceeds to step 610, which involves receiving a trigger signal from a first network entity associated with the source cell, the trigger signal including a trigger command for a conditional handover. In some cases, the operations of this step may refer to or be performed by circuitry and / or code for receiving, such as those described with reference to FIG. 8.

[0116] Method 600 then proceeds to step 615, where, based on the trigger signal and the one or more conditions, one or more actions associated with performing a conditional handover are performed. In some cases, the operations of this step may refer to or be performed by circuitry and / or code for performing one or more actions, such as those described with reference to FIG.

[0117] In some aspects, the one or more conditions include one or more signal measurements associated with the target cell being equal to or greater than a threshold, receiving a trigger signal for a conditional handover, and expiring a conditional handover execution timer after receiving the trigger signal.

[0118] In some aspects, performing the one or more actions includes starting a conditional handover execution timer based on receipt of the trigger signal, the conditional handover execution timer having a start time value set to a configured execution advance time value.

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

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

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

[0122] 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.

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

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

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

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

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

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

[0129] 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 are 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 if the first subset of time frequency resources is available based on the sensing operation.

[0130] 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 are allocated to a first UE for transmitting feedback information.

[0131] 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 allocated to the second UE.

[0132] In some aspects, if the trigger signal comprises a unicast message, the trigger signal comprises a plurality of bits for indicating a trigger command and a first subset of time-frequency resources, and if the trigger signal comprises a broadcast message or a group message, the trigger signal comprises a plurality of bits for indicating a trigger command, the first subset of time-frequency resources, and a second subset of time-frequency resources.

[0133] In some aspects, transmitting the feedback information includes transmitting NACK information indicating that at least one of the one or more conditions is not met prior to expiration of the conditional handover execution timer.

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

[0135] In some aspects, transmitting the NACK information includes transmitting a RACH transmission, the RACH transmission indicating the NACK information.

[0136] In some aspects, transmitting the feedback information includes transmitting ACK information indicating that all conditions in the one or more conditions have been met.

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

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

[0139] In one aspect, method 600, or any aspect related thereto, may be performed by an apparatus such as communications device 800 of Figure 8, which includes various components operable, configured, or adapted to perform method 600. Communications device 800 is described in further detail below.

[0140] It should be noted that FIG. 6 is merely one example of a method, and that other methods including fewer, additional, or alternative steps are possible without contradicting this disclosure.

[0141] Exemplary Operation of a Network Entity FIG. 7 illustrates one embodiment of a method 700 of wireless communication at a first network entity associated with a source cell, such as BS 102 of FIGS. 1 and 3, first network entity 502 of FIG. 5, or a separate base station as discussed with respect to FIG. 2.

[0142] Method 700 begins with step 705 of transmitting configuration information to a first UE 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 operations of this step may refer to or be performed by circuitry and / or code for transmitting, such as those described with reference to FIG. 9.

[0143] Method 700 then proceeds to step 710, where it is determined to enter NES mode. In some cases, the operations of this step may refer to or be performed by circuitry and / or code for making the determination, such as those described with reference to FIG.

[0144] Method 700 then proceeds to step 715, where, based on the decision to enter the NES mode, the first UE transmits a trigger signal including a trigger command for a conditional handover. In some cases, the operations of this step may refer to or be performed by circuitry and / or code for transmitting, such as those described with reference to FIG.

[0145] Method 700 then proceeds to step 720, which involves performing one or more actions associated with entering NES mode based on the trigger signal. In some cases, the operations of this step may refer to or be performed by circuitry and / or code for performing one or more actions, such as those described with reference to FIG.

[0146] In some aspects, the one or more conditions include one or more signal measurements associated with the target cell being equal to or greater than a threshold, receipt of a trigger signal for a conditional handover, and expiration of a conditional handover execution timer at the first UE after receipt of the trigger signal.

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

[0148] In some aspects, the configured advance notice time value for the first UE is less than or equal to the advance notice time value for entering the NES mode.

[0149] In some aspects, performing one or more actions related to entering the NES mode includes starting an NES execution timer, the NES execution timer having a start time set to an execution advance time value for entering the NES mode, and upon expiration of the NES execution timer, entering the NES mode without receiving NACK information from any UE in the source cell, including the first UE.

[0150] In some aspects, the method 700 further includes receiving feedback information from the first UE using the set of time-frequency resources. In some cases, the operations of this step may refer to or be performed by circuitry and / or code for receiving, such as those described with reference to FIG.

[0151] 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) indicating that the UE is able to perform the conditional handover. In some aspects, the HARQ information includes a negative acknowledgement (NACK) indicating that the UE is unable to perform the conditional handover.

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

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

[0154] 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 are allocated to a first UE for transmitting feedback information.

[0155] 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 allocated to the second UE.

[0156] In some aspects, if the trigger signal comprises a unicast message, the trigger signal comprises a plurality of bits for indicating a trigger command and a first subset of time-frequency resources, and if the trigger signal comprises a broadcast message or a group message, the trigger signal comprises a plurality of bits for indicating a trigger command, the first subset of time-frequency resources, and a second subset of time-frequency resources.

[0157] In some aspects, receiving feedback information includes receiving NACK information indicating that at least one of the one or more conditions has not been met.

[0158] In some aspects, the NACK information is received from the first UE prior to 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 receipt of the NACK information.

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

[0160] In some aspects, receiving the NACK information includes receiving a RACH transmission from the first UE, the RACH transmission indicating the NACK information.

[0161] In some aspects, receiving the feedback information includes receiving ACK information from the first UE indicating that all conditions in the one or more conditions have been met.

[0162] In some aspects, performing 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.

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

[0164] In some aspects, the conditional handover success information is received from one or more corresponding target cells associated with each UE of the one or more UEs, including the target cell associated with the first UE.

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

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

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

[0168] In one aspect, method 700, or any aspect related thereto, may be performed by an apparatus such as communications device 900 of Figure 9, which includes various components operable, configured, or adapted to perform method 700. Communications device 900 is described in further detail below.

[0169] It should be noted that FIG. 7 is merely one example of a method, and that other methods including fewer, additional, or alternative steps are possible without contradicting this disclosure.

[0170] Exemplary Communication Devices 8 illustrates aspects of an exemplary communications device 800. In some aspects, the communications device 800 is user equipment, such as the UE 104 described above with respect to FIGS. 1 and 3 and / or the first UE 504 described above with respect to FIG.

[0171] The communications 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 communications device 800 via an antenna 850, such as various signals as described herein. The processing system 805 can be configured to perform processing functions for the communications device 800, including processing signals received by the communications device 800 and / or signals to be transmitted.

[0172] The processing system 805 includes one or more processors 810. In various aspects, the one or more processors 810 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380, as described with respect to FIG. 3. The one or more processors 810 are coupled to a computer-readable medium / memory 825 via a bus 840. In particular 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 the method 600 described with respect to FIG. 6, or any aspects related thereto. It should be noted that reference to a processor performing a function of the communications device 800 may include one or more processors 810 performing that function of the communications device 800.

[0173] In the illustrated embodiment, computer-readable medium / memory 825 stores code (e.g., executable instructions), such as code for receiving 830 and code for performing one or more actions 835. Processing of code for receiving 830 and code for performing one or more actions 835 can cause communications device 800 to perform method 600 described with respect to FIG.

[0174] The one or more processors 810 include circuitry configured to execute (e.g., run) code stored in a computer-readable medium / memory 825, including circuitry such as a circuit for receiving 815 and a circuit for performing 820. Processing by the circuit for receiving 815 and the circuit for performing 820 may cause the communications device 800 to perform the method 600 described with respect to FIG. 6, or any aspect related thereto.

[0175] Various components of communications device 800 may provide means for performing method 600 or any aspect related thereto described with respect to Figure 6. For example, means for transmitting, emitting or outputting for transmission may include transceiver 354 and / or antenna(s) 352 of UE 104 shown in Figure 3 and / or transceiver 845 and antenna 850 of communications device 800 of Figure 8. Means for receiving or acquiring may include transceiver 354 and / or antenna(s) 352 of UE 104 shown in Figure 3 and / or transceiver 845 and antenna 850 of communications device 800 of Figure 8.

[0176] 9 illustrates aspects of an exemplary communications device 900. In some aspects, the communications device 900 is a network entity, such as the BS 102 of FIGS. 1 and 3, the first network entity 502 described above with respect to FIG. 5, or a separate base station as discussed with respect to FIG. 2.

[0177] The communications 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 communications device 900 via an antenna 970, such as various signals as described herein. The network interface 975 is configured to obtain and transmit signals for the communications device 900 via communication link(s), such as a backhaul link, a midhaul link, and / or a fronthaul link, as described herein, such as with respect to FIG. 2 . The processing system 905 can be configured to perform processing functions for the communications device 900, including processing signals received by the communications device 900 and / or signals to be transmitted.

[0178] The processing system 905 includes one or more processors 910. In various aspects, the one or more processors 910 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340, as described with respect to FIG. 3. The one or more processors 910 are coupled to a computer-readable medium / memory 935 via a bus 960. In particular 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 FIG. 7, or any aspects related thereto. It should be noted that reference to a processor of the communications device 900 performing a function may include the one or more processors 910 of the communications device 900 performing that function.

[0179] In the illustrated embodiment, 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 code for transmitting 940, code for determining 945, code for taking one or more actions 950, and code for receiving 955 can cause communications device 900 to perform method 700 described in connection with FIG.

[0180] The one or more processors 910 include circuitry configured to execute (e.g., run) code stored in a computer-readable medium / memory 935, including circuitry such as a circuit for transmitting 915, a circuit for determining 920, a circuit for performing 925, and a circuit for receiving 930. Processing by the circuit for transmitting 915, the circuit for determining 920, the circuit for performing 925, and the circuit for receiving 930 may cause the communications device 900 to perform the method 700 described in connection with FIG.

[0181] Various components of the communications device 900 may provide means for performing the method 700 described with respect to Figure 7, or any aspect related thereto. The means for transmitting, emitting or outputting for transmission may include the transceiver 332 and / or the antenna(s) 334 of the BS 102 shown in Figure 3 and / or the transceiver 965 and antenna 970 of the communications device 900 of Figure 9. The means for receiving or acquiring may include the transceiver 332 and / or the antenna(s) 334 of the BS 102 shown in Figure 3 and / or the transceiver 965 and antenna 970 of the communications device 900 of Figure 9.

[0182] Example clauses The following numbered clauses describe example implementations.

[0183] Clause 1: A method for wireless communication in a first UE, the method comprising: 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 from the first network entity associated with the source cell, the trigger signal including a trigger command for the conditional handover; and performing one or more actions related to performing the conditional handover based on the trigger signal and the one or more conditions.

[0184] Clause 2: The method of clause 1, wherein the one or more conditions include one or more signal measurements associated with the target cell being equal to or greater than a threshold, receiving a trigger signal for a conditional handover, and expiring a conditional handover execution timer after receiving the trigger signal.

[0185] Clause 3: The method of clause 2, wherein performing one or more actions includes starting a conditional handover execution timer based on receipt of a trigger signal, the conditional handover execution timer having a start time value set to a configured execution advance time value.

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

[0187] Clause 5: The method of any one of clauses 3 or 4, wherein performing the one or more actions includes evaluating whether each of the one or more conditions is satisfied based on receiving the trigger signal.

[0188] Clause 6: The method of clause 5, wherein if each of the one or more conditions is met based on the evaluation, taking the one or more actions includes performing a conditional handover to hand over the UE from a first network entity associated with the source cell to a second network entity associated with the target cell.

[0189] Clause 7: The method of any one of clauses 5 or 6, wherein 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.

[0190] Clause 8: The method of clause 7, wherein the one or more signal measurements include a last available signal measurement associated with the target cell prior to receipt of the trigger signal.

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

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

[0193] Clause 11: The method of clause 10, wherein the feedback information includes Hybrid Automatic Repeat Request (HARQ) information transmitted within uplink control information (UCI) and having a HARQ identifier associated with the conditional handover, the HARQ information including an acknowledgement (ACK) indicating that the UE is capable of performing the conditional handover, and the HARQ information including a negative acknowledgement (NACK) indicating that the UE is not capable of performing the conditional handover.

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

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

[0196] Clause 14: The method of clause 13, further comprising: 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; and transmitting the feedback information comprises, if the first subset of time-frequency resources is available based on the sensing operation, transmitting the feedback information using the first subset of time-frequency resources.

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

[0198] 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 allocated to the second UE.

[0199] Clause 17: The method of clause 16, wherein, if the trigger signal comprises a unicast message, the trigger signal comprises a plurality of bits for indicating a trigger command and a first subset of time-frequency resources, and, if the trigger signal comprises a broadcast message or a group message, the trigger signal comprises a plurality of bits for indicating a trigger command, the first subset of time-frequency resources, and a second subset of time-frequency resources.

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

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

[0202] Clause 20: The method of clause 18, wherein transmitting the NACK information includes transmitting a RACH transmission, the RACH transmission indicating the NACK information.

[0203] Clause 21: The method of any one of clauses 10 to 17, wherein sending feedback information includes sending ACK information indicating that all conditions in the one or more conditions are satisfied.

[0204] Clause 22: The method of any one of clauses 1 to 21, wherein the trigger signal includes one bit to indicate a trigger command.

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

[0206] Clause 24: A method for wireless communication in a first network entity associated with a source cell, the method comprising: sending configuration information to a first 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 a target cell; deciding to enter an NES mode; based on the decision to enter the NES mode, sending to the first UE a trigger signal including a trigger command for the conditional handover; and based on the trigger signal, performing one or more actions related to entering the NES mode.

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

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

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

[0210] Clause 28: The method of clause 27, wherein performing one or more actions related to entering the NES mode includes starting an NES execution timer, the NES execution timer having a start time set to a warning time value for entering the NES mode, and upon expiration of the NES execution timer, entering the NES mode without receiving NACK information from any UE in the source cell, including the first UE.

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

[0212] Clause 30: The method of clause 29, wherein 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, the HARQ information including an acknowledgement (ACK) indicating that the UE is capable of performing the conditional handover, and the HARQ information including a negative acknowledgement (NACK) indicating that the UE is not capable of performing the conditional handover.

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

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

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

[0216] 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 allocated to the second UE.

[0217] Clause 35: The method of clause 34, wherein, if the trigger signal comprises a unicast message, the trigger signal comprises a plurality of bits for indicating a trigger command and a first subset of time-frequency resources, and, if the trigger signal comprises a broadcast message or a group message, the trigger signal comprises a plurality of bits for indicating a trigger command, the first subset of time-frequency resources, and a second subset of time-frequency resources.

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

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

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

[0221] Clause 39: The method of any one of clauses 36 or 37, wherein receiving the NACK information includes receiving a RACH transmission from the first UE, the RACH transmission indicating the NACK information.

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

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

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

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

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

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

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

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

[0230] Clause 48: An apparatus comprising means for carrying out a method according to any one of clauses 1 to 46.

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

[0232] Clause 50: A computer program product, embodied on a computer-readable storage medium, comprising code for carrying out a method according to any one of clauses 1 to 46.

[0233] Additional Considerations The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of the elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. Furthermore, the scope of the disclosure is intended to encompass apparatuses or methods that are practiced using other structure, functions, or structure and functions in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0234] The various illustrative logic blocks, modules, and circuits described in connection with this disclosure may be implemented or performed using 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. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0235] 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. By way of example, "at least one of a, b, or c" is intended to encompass a, b, c, ab, ac, bc, and abc, as well as any combination having multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other permutation of a, b, and c).

[0236] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., searching a table, database, or another data structure), ascertaining, etc. "Determining" may also include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. "Determining" may also include resolving, selecting, choosing, establishing, etc.

[0237] The methods disclosed herein include one or more actions for achieving the method. The actions of those methods may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Furthermore, the various actions of the methods described above may be performed by any suitable means capable of performing the corresponding functions. These means may include various hardware and / or software component(s), including, but not limited to, circuits, application specific integrated circuits (ASICs), or processors, and / or various hardware and / or software module(s).

[0238] The following claims are not intended to be limited to the embodiments set forth herein, but are to be accorded the full scope consistent with the language of the claims. Within the claims, reference to an element by the singular is intended to mean "one and only one," unless expressly stated otherwise, and rather "one or more." Unless expressly stated otherwise, the term "some" refers to one or more. No element of a claim is to be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for." All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made available to the public, regardless of whether such disclosure is expressly recited in the claims.

Claims

1. 1. A method for wireless communication in a first user equipment (UE), comprising: 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 from the first network entity associated with the source cell, the trigger signal including a trigger command for the conditional handover; and performing one or more actions associated with performing the conditional handover based on the trigger signal and the one or more conditions.

2. The one or more conditions are: one or more signal measurements associated with the target cell are equal to or greater than a threshold; and the receiving of the trigger signal for the conditional handover; and a conditional handover execution timer expiring after receiving the trigger signal.

3. performing the one or more actions based on receipt of the trigger signal, starting the conditional handover execution timer, the conditional handover execution timer having a start time value set to a configured execution advance time value; and evaluating whether each of the one or more conditions is satisfied based on the receipt of the trigger signal.

4. the configured execution time value is received within the configuration information or the trigger signal; the configured advance notice time value is different from other configured advance notice time values ​​for performing a conditional handover associated with other UEs in the source cell; The method of claim 3.

5. 4. The method of claim 3, wherein if 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 hand over the first UE from the first network entity associated with the source cell to the second network entity associated with the target cell.

6. evaluating whether each of the one or more conditions is satisfied includes determining whether the one or more signal measurements associated with the target cell are greater than or equal to the threshold; the one or more signal measurements include a last available signal measurement associated with the target cell prior to receipt of the trigger signal; or performing 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; One of the The method of claim 3.

7. performing 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; the set of time-frequency resources is indicated in the configuration information; The method of claim 3.

8. the feedback information includes Hybrid Automatic Repeat Request (HARQ) information transmitted within Uplink Control Information (UCI) and having a HARQ identifier associated with the conditional handover; the HARQ information includes an acknowledgement (ACK) indicating that the first UE is able to perform the conditional handover; the HARQ information includes a negative acknowledgement (NACK), indicating that the first UE is unable to perform the conditional handover. The method of claim 7.

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

10. 10. The method of claim 9, further comprising: performing a sensing operation to determine whether a first subset of time frequency resources of the set of time frequency resources are available for transmitting the feedback information; and transmitting the feedback information comprises, if the first subset of time frequency resources is available based on the sensing operation, transmitting the feedback information using the first subset of time frequency resources.

11. based on the set of time frequency resources being shared with the plurality of UEs, the trigger signal including an indication of a first subset of time frequency resources from the set of time frequency resources allocated to the first UE for transmitting the feedback information; 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 allocated to a second UE; 10. The method of claim 9.

12. transmitting the feedback information includes transmitting, prior to expiration of the conditional handover execution timer, negative acknowledgement (NACK) information indicating that at least one of the one or more conditions is not satisfied; transmitting the NACK information, transmitting the NACK information within uplink control information (UCI) on a physical uplink control channel (PUCCH); transmitting the NACK information in a Medium Access Control - Control Element (MAC-CE) on a Physical Uplink Shared Channel (PUSCH); or transmitting a random access channel (RACH) transmission indicating the NACK information. The method of claim 7.

13. 8. The method of claim 7, wherein transmitting the feedback information comprises transmitting acknowledgement (ACK) information indicating that all conditions in the one or more conditions have been met.

14. The trigger signal is unicast Downlink Control Information (DCI) messages; a unicast Medium Access Control - Control Element (MAC-CE) message, or 10. The method of claim 1, comprising one of a broadcast group downlink control information (DCI) message.

15. 1. A method for wireless communication in a first network entity associated with a source cell, comprising: transmitting, to a first user equipment (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 saving (NES) mode; sending, to the first UE, a trigger signal including a trigger command for the conditional handover based on the decision to enter the NES mode; and performing one or more actions associated with entering the NES mode based on a trigger signal.

16. The one or more conditions are: one or more signal measurements associated with the target cell are equal to or greater than a threshold; and receiving the trigger signal for the conditional handover; and a conditional handover execution timer expiring after receiving the trigger signal at the first UE.

17. the conditional handover execution timer is based on a configured execution advance time value for the first UE; The configured execution notice time value is transmitted within the configuration information or the trigger signal; the configured execution time advance notice time value for the first UE is different from other configured execution time advance notice time values ​​for performing a conditional handover associated with other UEs in the source cell; 17. The method of claim 16.

18. the configured advance notice time value for the first UE is less than or equal to the advance notice time value for entering the NES mode; performing the one or more actions associated with entering the NES mode; starting an NES execution timer having a start time set to the execution warning time value for entering the NES mode; Upon expiration of the NES execution timer, entering the NES mode without receiving negative acknowledgement (NACK) information from any UE in the source cell, including the first UE.

18. The method of claim 17.

19. 16. The method of claim 15, further comprising receiving feedback information from the first UE using a set of time-frequency resources, the set of time-frequency resources being indicated in the configuration information.

20. 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; the HARQ information includes an acknowledgement (ACK) indicating that the first UE is able to perform the conditional handover; the HARQ information includes a negative acknowledgement (NACK), indicating that the first UE is unable to perform the conditional handover.

20. The method of claim 19.

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

22. based on the set of time frequency resources being shared with the plurality of UEs, the trigger signal including an indication of a first subset of time frequency resources from the set of time frequency resources allocated to the first UE for transmitting the feedback information; 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 allocated to a second UE; 22. The method of claim 21.

23. 20. The method of claim 19, wherein receiving the feedback information comprises receiving negative acknowledgement (NACK) information indicating that at least one of the one or more conditions is not met.

24. the NACK information is received from the first UE prior to expiration of a conditional handover execution timer associated with the first UE; taking the one or more actions includes not entering the NES mode based on the receipt of the NACK information.

24. The method of claim 23.

25. receiving the NACK information, receiving the NACK information in uplink control information (UCI) on a physical uplink control channel (PUCCH); or receiving the NACK information in a Medium Access Control - Control Element (MAC-CE) on a Physical Uplink Shared Channel (PUSCH); or 24. The method of claim 23, comprising at least one of: receiving a random access channel (RACH) transmission from the first UE indicating the NACK information.

26. receiving the feedback information includes receiving acknowledgement (ACK) information from the first UE indicating that all conditions in the one or more conditions are met; performing 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; 20. The method of claim 19.

27. performing the one or more actions includes entering the NES mode only after receiving conditional handover success information for each UE of one or more UEs previously served by the first network entity associated with the source cell, including the first UE; the conditional handover success information is received from one or more respective target cells associated with each UE of the one or more UEs, 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 one handover success message indicating the conditional handover success information for a plurality of UEs including the first UE; or One of the 16. The method of claim 15.

28. The trigger signal is unicast Downlink Control Information (DCI) messages; a unicast Medium Access Control - Control Element (MAC-CE) message, or 16. The method of claim 15, comprising one of a broadcast group downlink control information (DCI) message.

29. a first user equipment (UE), a memory containing executable instructions; Executing the executable instructions to cause the first UE to: 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 from the first network entity associated with the source cell, the trigger signal including a trigger command for the conditional handover; a processor configured to cause one or more actions associated with performing the conditional handover based on the trigger signal and the one or more conditions.

30. a first network entity, a memory containing executable instructions; Executing the executable instructions to cause the first network entity to: causing a first user equipment (UE) to transmit configuration information indicating one or more conditions for performing a conditional handover from the first network entity associated with a source cell to a second network entity associated with a target cell; Decide to enter Network Energy Saver (NES) mode, causing the first UE to send a trigger signal including a trigger command for the conditional handover based on the decision to enter the NES mode; a processor configured to cause, based on a trigger signal, one or more actions associated with entering the NES mode.

Images