Conditional handover conditions associated with height of user equipment

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a configuration of one or more conditional handover conditions associated with one or more candidate cells, where each of the one or more conditional handover conditions is based at least in part on an altitude of the UE. The UE may trigger a conditional handover procedure based at least in part on the altitude of the UE. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 806,926, filed on June 14, 2022, entitled “CONDITIONAL HANDOVER CONDITIONS ASSOCIATED WITH A HEIGHT OF A USEREQUIPMENT” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for conditional handover conditions that are highly correlated with user equipment. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

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

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on a height of the UE. The method may include triggering a conditional handover procedure based at least in part on a height of the UE.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending a configuration of one or more conditional handover conditions associated with one or more candidate cells to a UE, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE. The method may include receiving an indication from another network node associated with a candidate cell in the one or more candidate cells to perform a conditional handover procedure between the UE and the other network node, wherein the conditional handover procedure is triggered at least in part based on the height of the UE.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE. The one or more processors may be configured to trigger a conditional handover process based at least in part on the height of the UE.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a configuration of one or more conditional handover conditions associated with one or more candidate cells to a UE, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE. The one or more processors may be configured to receive an indication of performing a conditional handover process between the UE and another network node from another network node associated with a candidate cell in one or more candidate cells, wherein the conditional handover process is triggered at least in part based on the height of the UE.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to trigger a conditional handover process based at least in part on the height of the UE.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a configuration of one or more conditional handover conditions associated with one or more candidate cells to a UE, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive an indication from another network node associated with a candidate cell in the one or more candidate cells to perform a conditional handover process between the UE and the other network node, wherein the conditional handover process is triggered at least in part based on the height of the UE.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on an altitude of the apparatus. The apparatus may include means for triggering a conditional handover process based at least in part on an altitude of the apparatus.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a configuration of one or more conditional handover conditions associated with one or more candidate cells to a UE, wherein each of the one or more conditional handover conditions is based at least in part on the altitude of the UE. The apparatus may include means for receiving an indication from a network node associated with a candidate cell in the one or more candidate cells to perform a conditional handover procedure between the UE and the network node, wherein the conditional handover procedure is triggered at least in part based on the altitude of the UE.

[0015] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

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

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of a handover procedure according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a conditional handover process according to the present disclosure.

[0024] Figure 6is a diagram of an example associated with a conditional handover condition associated with a height of a UE according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0027] Fig. 9 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0028] Fig.10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0029] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functionality, or structure and functionality other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0030] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0031] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0032] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). For another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0033] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0034] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with a femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of the mobile network node 110 (e.g., a mobile network node).

[0035] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

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

[0037] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

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

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

[0040] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled and / or electrically coupled.

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

[0042] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0043] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0044] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0045] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on an altitude of UE 120; and trigger a conditional handover process based at least in part on an altitude of UE 120. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0047] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a configuration of one or more conditional handover conditions associated with one or more candidate cells to a UE (e.g., UE 120), wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE; receive an indication from another network node associated with a candidate cell in the one or more candidate cells to perform a conditional handover process between the UE and the other network node, wherein the conditional handover process is triggered at least in part based on the height of the UE. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0048] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

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

[0050] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0051] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

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

[0054] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference Figures 6 to 10 ) or any aspect of any of the methods described herein.

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

[0056] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the network node 110 may perform one or more techniques associated with a conditional handover condition associated with the height of the UE, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 7 The process 700 Figure 8 800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 7 The process 700 Figure 8 The process 800 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0057] In some aspects, the UE 120 includes means for receiving configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on the altitude of the UE 120; and / or means for triggering a conditional handover process based at least in part on the altitude of the UE 120. The means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0058] In some aspects, the network node 110 includes means for sending a configuration of one or more conditional handover conditions associated with one or more candidate cells to the UE 120, wherein each of the one or more conditional handover conditions is based at least in part on the altitude of the UE 120; and / or means for receiving an indication from another network node associated with a candidate cell of the one or more candidate cells to perform a conditional handover procedure between the UE 120 and the other network node, wherein the conditional handover procedure is triggered at least in part based on the altitude of the UE 120. In some aspects, the means for the network node 110 to perform operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0059] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0060] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0061] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0062] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0063] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0064] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0065] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0066] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0067] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

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

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

[0070] The non-RT RIC 315 may 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 updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0071] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0072] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0073] Figure 4 is a diagram illustrating an example of a handover process 400 according to the present disclosure.

[0074] The handover process may be performed by UE 120, source network node 405 (e.g., network node 110), and target network node 410 (e.g., another network node 110). As used herein, a "source network node" may refer to a network node associated with a serving cell or a network node with which UE 120 currently has an active or established connection (such as an RRC connection in a connected or active state). A "target network node" may refer to a network node associated with a cell that is identified as replacing the serving cell of UE 120 (e.g., as part of a handover process). In some examples, source network node 405 may be associated with a primary cell (PCell) or a special cell (SpCell), and target network node 410 may be associated with a target cell that replaces source network node 405 as a PCell or SpCell.

[0075] like Figure 4As shown by reference numeral 415, source network node 405 may initiate a handover of UE 120 to target network node 410 by sending a handover request message to target network node 410. Source network node 405 may send the handover request message to target network node 410 via an Xn, X2, or Next Generation Application Protocol (NGAP) interface, etc. As shown by reference numeral 420, target network node 410 may perform an admission control process associated with the handover based at least in part on receiving the handover request message. As shown by reference numeral 425, target network node 410 may send a handover request confirmation message to source network node 405 (e.g., if the admission control process indicates that target network node 410 can accept the handover of UE 120). The handover request confirmation message may include an RRC configuration for connecting to target network node 410.

[0076] As indicated by reference numeral 430, source network node 405 may send an RRC configuration to UE 120 by sending an RRC reconfiguration message including the RRC configuration of the handover request confirm message to UE 120. As indicated by reference numeral 435, UE 120 may switch to a new cell (e.g., a cell associated with target network node 410) by changing the RRC connection from source network node 405 to target network node 410 based at least in part on the RRC reconfiguration. As indicated by reference numeral 440, UE 120 may send an RRC reconfiguration complete message to target network node 410. The RRC reconfiguration complete message may indicate that UE 120 has changed the RRC connection from source network node 405 to target network node 410. As indicated by reference numeral 445, target network node 410 may send a UE context release message to source network node 405. The UE context release message may indicate that the handover of UE 120 to target network node 410 is successful.

[0077] In some examples, UE 120 may not be able to successfully connect with target network node 410. For example, UE 120 may attempt to connect with target network node 410 (e.g., by performing a random access channel (RACH) procedure with target network node 410), but the attempt to connect with target network node 410 may fail. If UE 120 is unable to successfully connect with target network node 410, UE 120 may perform a connection reestablishment procedure to reestablish a connection with source network node 405 or another network node. For example, UE 120 may send an RRC reestablishment request message to the network (e.g., to source network node 405 or another network node). In addition, UE 120 may reset a MAC entity of UE 120, release an RRC configuration for a handover procedure, suspend all radio bearers (in some examples, except for a signaling radio bearer (SRB) indexed as SRB0), release a connection with any configured secondary cell (SCell), or release all other configurations stored by UE 120, etc. Thus, in the event that the handover process with target network node 410 fails, UE 120 may re-establish an RRC connection (eg, with source network node 405 or another network node).

[0078] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0079] Figure 5 is a diagram illustrating an example of a conditional handover process 500 according to the present disclosure. Figure 4 Unlike the handover procedure described above, for the conditional handover procedure, the UE (e.g., UE 120) may be pre-configured by the source network node with certain handover conditions, and then the handover procedure may be triggered if certain handover conditions are met. Figure 4 This may advantageously reduce handover latency compared to the handover process described above.

[0080] More specifically, Figure 5 The illustrated conditional handover process 500 may be performed by UE 120, a source network node 505 (e.g., network node 110), and one or more candidate network nodes 510, 515 (e.g., other network nodes 110). As used herein, a "candidate network node" may refer to a network node that is a candidate for serving as a target network node for a UE as part of a handover process. In some examples, source network node 505 may be associated with a PCell or SpCell, and candidate network nodes 510, 515 may be associated with a target cell that replaces source network node 505 as a PCell or SpCell.

[0081] like Figure 5As shown in FIG. 5 and 520, source network node 505 may communicate with first candidate network node 510 and second candidate network node 515 to prepare first candidate network node 510 and second candidate network node 515 for conditional handover of UE 120. For example, source network node 505 may send a handover request message to first candidate network node 510 or second candidate network node 515. First candidate network node 510 or second candidate network node 515 may send a handover request confirmation message to source network node 505, as described above in conjunction with Figure 4 described.

[0082] As indicated by reference numeral 525, the source network node 505 may send an RRC reconfiguration message to the UE 120. The RRC reconfiguration message may include a conditional handover configuration (sometimes referred to as a conditionalReconfiguration parameter and / or included in a conditionalReconfiguration information element (IE)) indicating a configuration of the candidate network nodes 510, 515, indicating one or more criteria or execution conditions (e.g., conditional thresholds) generated by the source network node 505 to trigger the handover, or indicating other information. In some examples, the execution condition may consist of one or two trigger conditions, such as one or two conditional events A3 and / or A5 (sometimes referred to as condEventA3 or condEventA5), described in more detail below in conjunction with reference numeral 535. In some cases, conditional events A3 and / or A5 are sometimes referred to as radio resource management (RRM) conditions. In some cases, the UE 120 may be configured with a single type of reference signal (e.g., a channel state information (CSI) reference signal (CSI-RS), a synchronization signal block (SSB), etc.), and up to two different trigger quantities (e.g., up to two of RSRP, RSRQ, signal to interference plus noise ratio (SINR), etc.) may be configured for simultaneous evaluation of conditional handover execution of a single candidate cell. As indicated by reference numeral 530, the UE 120 may send an RRC reconfiguration complete message to the source network node 505, which may indicate that the UE 120 has applied the RRC reconfiguration (e.g., the conditional handover configuration).

[0083] As shown by reference numeral 535, UE 120 may evaluate the conditional handover condition and / or detect a conditional handover event for the first candidate network node 510. In some cases, UE 120 may maintain a dynamic list of conditionalReconfiguration IEs, which are sometimes referred to as varConditionalReconfig parameters or varConditionalReconfig IEs. In other words, the UE 120 variable varConditionalReconfig may include an aggregated configuration of the conditional handover configuration. In some instances, varConditionalReconfig may include a plurality of conditional reconfiguration identifiers (sometimes referred to as condReconfigId), each of which corresponds to a candidate cell (e.g., a cell associated with the first candidate network node 510 or a cell associated with the second candidate network node 515). For each conditional reconfiguration identifier (e.g., for each condReconfigId), UE 120 may be configured with up to two triggering events (sometimes referred to as condExecutionCond). The conditional reconfiguration events of the two triggering events (e.g., two condExecutionCond parameters) may have the same or different event conditions, trigger amounts, trigger times, trigger thresholds, etc. UE 120 may measure certain metrics (e.g., RSRP, RSRQ, SINR, etc.) and determine that one or more criteria or execution conditions are met for triggering a handover to first candidate network node 510 (e.g., a measurement associated with a signal sent by first candidate network node 510 may meet a threshold or may be greater (by a threshold amount) than a measurement associated with a signal sent by source network node 505).

[0084] For example, in some cases, if a cell in which a candidate network node 510, 515 is associated (sometimes referred to as an adjacent cell) becomes better offset than a serving cell (e.g., SpCell), the UE 120 may trigger a handover process, such as a serving cell being a cell associated with a source network node 505 (sometimes referred to as conditional event A3 or condEventA3). In other words, conditional event A3 provides a handover trigger mechanism based on relative measurement results, such as when the RSRP, RSRQ, SINR, or similar measurement of an adjacent cell is stronger than the corresponding RSRP, RSRQ, SINR, or similar measurement of the SpCell. In some cases, a conditional event A3 handover to an adjacent cell may be triggered according to the condition Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off (sometimes referred to as a trigger condition or entry condition), and if the condition Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off (sometimes referred to as a cancellation condition or exit condition) is satisfied within a specific time period for triggering the handover (sometimes referred to as the trigger time (TTT) or timeToTrigger), the handover to the adjacent cell may be cancelled. For such conditions, Mn is the measurement result of the adjacent cell (e.g., RSRP, RSRQ, SINR, etc.), Ofn is the measurement object specific offset of the reference signal of the adjacent cell, Ocn is the cell specific offset of the adjacent cell, Hys is the hysteresis parameter associated with the trigger event, Mp is the measurement result of the SpCell (e.g., RSRP, RSRQ, SINR, etc.), Ofp is the measurement object specific offset of the SpCell, Ocp is the cell specific offset of the SpCell, and Off is the offset parameter associated with the trigger event.

[0085] In some other cases, if a cell associated with the source network node 505 (e.g., SpCell) becomes worse than a first threshold, and a cell in which a candidate network node 510, 515 is associated (e.g., an adjacent cell among adjacent cells) becomes better than a second threshold (sometimes referred to as conditional event A5 or condEventA5), the UE 120 may trigger a handover process. In some cases, a conditional event A5 handover to an adjacent cell may be triggered according to the conditions Mp + Hys < Thresh1 and Mn + Ofn + Ocn – Hys > Thresh2 (e.g., trigger conditions or entry conditions), and if the conditions Mp – Hys > Thresh1 and Mn + Ofn + Ocn + Hys < Thresh2 (e.g., cancellation conditions or exit conditions) are satisfied within the TTT, the handover to the adjacent cell may be cancelled, where Thresh1 is the first threshold parameter and Thresh2 is the second threshold parameter.

[0086] Additionally or alternatively, in some cases, UE 120 may be configured with one or more events for sending measurement reports to a network node, such as to source network node 505. For example, UE 120 may be configured with measurement report events associated with the height of UE 120 (e.g., the altitude of UE 120, or more specifically, the distance of UE 120 above sea level, the distance of UE 120 above land, the height of UE 120 relative to a reference height or altitude, etc.), sometimes referred to as event H1 (or EventH1) and / or event H2 (or EventH2). In such instances, event H1 and / or event H2 may be stored in a configured variable measurement list (sometimes referred to as a varMeasConfig list) and / or may be associated with a measurement identifier (e.g., measId). In such aspects, if one of the conditional event H1 and / or conditional event H2 conditions is satisfied (e.g., if UE 120 satisfies a height threshold associated with one of event H1 and / or event H2), UE 120 may send a measurement report indicating the height of UE 120 to source network node 505, and source network node 505 may reconfigure the conditional handover configuration accordingly, such as by repeating the handover preparation steps (e.g., the steps described in conjunction with reference numerals 520, 525, and 530) for different candidate cells. For example, cells may perform differently relative to the height of UE 120, and thus if UE 120 gains or loses sufficient height (which may be indicated to the source network entity via a measurement report), source network node 505 may reconfigure UE 120 to perform conditional handover measurements associated with different candidate cells, etc.

[0087] In some cases, UE 120 may detect a conditional handover event for more than one cell associated with a candidate network node (e.g., for both a cell associated with first candidate network node 510 and a cell associated with second candidate network node 515). In such cases, UE 120 may select one of the triggered cells as the selected cell for conditional reconfiguration execution. For example, UE 120 may select a cell based at least in part on a beam and / or beam quality associated with each triggered cell (e.g., UE 120 may select a cell associated with a preferred beam and / or a cell with a higher beam quality).

[0088] As indicated by reference numeral 545, UE 120 may change the RRC connection from source network node 505 to first candidate network node 510 based at least in part on detecting a conditional handover event or execution condition of first candidate network node 510, as described above in conjunction with Figure 4That is, UE 120 may perform handover upon detecting a conditional handover event without waiting for an RRC reconfiguration message from source network node 505. In other words, UE 120 may apply the stored configuration corresponding to the selected candidate cell and synchronize to the candidate cell. Figure 4 This can reduce handover latency compared to the handover process described above.

[0089] As indicated by reference numeral 550, UE 120 may send an RRC reconfiguration complete message to first candidate network node 510. The RRC reconfiguration complete message may indicate that UE 120 has changed the RRC connection from source network node 505 to first candidate network node 510, as described above in conjunction with Figure 4 As indicated by reference numeral 555, first candidate network node 510 may send a handover success message (e.g., indicating a successful handover of UE 120) to source network node 505. As indicated by reference numeral 560, source network node 505 may send a handover cancel message to second candidate network node 515. The handover cancel message may indicate that second candidate network node 515 is to discard the handover request message (e.g., sent as described in conjunction with reference numeral 520). As indicated by reference numeral 565, source network node 505 and first candidate network node 510 may perform a UE context release procedure to release UE 120 context at source network node 505.

[0090] In conjunction with the above Figure 4 In a similar manner, UE 120 may be unable to establish a connection with the first candidate network node 510. For example, the handover process with the first candidate network node 510 may fail. In some examples, UE 120 may attempt to perform a RACH process with the first candidate network node 510, but the RACH process may not be successful. In some examples, when the handover process with the first candidate network node 510 fails, UE 120 may maintain the conditional handover configuration instead of releasing one or more (or all) RRC configurations at UE 120. This may enable UE 120 to continue searching for or measuring the candidate network entity indicated by the conditional handover configuration. For example, UE 120 may detect a conditional handover event for the second candidate network node 515. That is, UE 120 may determine that one or more criteria or execution conditions for triggering a handover to the second candidate network node 515 are met (e.g., after a handover attempt with the first candidate network node 510 fails). Because UE 120 has not released the conditional handover configuration, UE 120 may change the RRC connection from source network node 505 to second candidate network node 515 based at least in part on detecting a conditional handover event of second candidate network node 515, as described above in conjunction with Figure 4That is, UE 120 may perform handover when detecting that the execution condition is met, without waiting for an RRC reconfiguration message from source network node 505. In addition, after a handover attempt with first candidate network node 510 fails, UE 120 may not wait for additional conditional handover reconfiguration. This may reduce the handover delay associated with conditional handover.

[0091] In some cases, UE 120 may be an aerial UE or the like that frequently changes altitude (e.g., altitude), thereby frequently triggering one or more handover or measurement events. For example, aerial UE 120 may be configured with one or more of event H1 conditions or event H2 conditions, which may be repeatedly triggered when UE 120 changes altitude. UE 120 may therefore frequently transmit measurement reports associated with event H1 and / or event H2 conditions to source network node 505, and thus source network node 505 may repeatedly reconfigure UE 120 with different candidate cells based at least in part on the current altitude of UE 120. This may result in high RRC-level signaling overhead because UE 120 may send multiple measurement reports to source network node 505, and because source network node 505 may then send multiple RRC reconfiguration messages to reconfigure UE 120 with different candidate cells. This high RRC level signaling overhead may lead to congested communication channels and therefore high latency, low throughput, and overall inefficient use of network resources.

[0092] Some techniques and apparatus described herein enable configuration of altitude-specific conditional handover conditions, thereby reducing RRC-level signaling overhead associated with an aerial UE 120, etc., that frequently changes altitude. In some aspects, a UE (e.g., UE 120) may receive a configuration of one or more conditional handover events associated with one or more candidate cells, wherein each of the one or more conditional handover events is based at least in part on the altitude of the UE. For example, the UE may receive a configuration of a conditional RRM event (e.g., conditional event A3, conditional event A5, etc.) parameterized by an altitude event (e.g., event H1, event H2, etc.), the UE may receive a configuration of a conditional altitude event (sometimes referred to as conditional event H1, conditional event H2, etc.) that triggers a handover process instead of triggering a measurement report, and / or the UE may receive multiple altitude-specific configurations and may therefore select an applicable conditional handover configuration based on the current altitude of the UE. By receiving a configuration of one or more conditional handover events associated with one or more candidate cells, wherein each of the one or more conditional handover events is based at least in part on the altitude of the UE, the UE may evaluate a conditional handover condition and / or may trigger a conditional handover procedure based at least in part on the current altitude of the UE, without requiring back-and-forth RRC signaling between the UE and a source network node as the UE changes altitude. Thus, RRC-level signaling overhead may be reduced compared to legacy conditional handover procedures, resulting in less congested communication channels, and therefore lower latency, higher throughput, and an overall more efficient use of network resources.

[0093] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0094] Figure 6 6 is a diagram of an example 600 associated with a conditional handover condition associated with a height of a UE according to the present disclosure. Figure 6 As shown, UE 605 (e.g., UE 120) can communicate with one or more network nodes (e.g., one or more network nodes 110), such as source network node 610 (e.g., source network node 505) and candidate network node 615 (e.g., one of first candidate network node 510 or second candidate network node 515). In some aspects, UE 605, source network node 610, and candidate network node 615 can be part of a wireless network (e.g., wireless network 100). UE 605, source network node 610, and candidate network node 615 can be part of a wireless network (e.g., wireless network 100). Figure 6 The operations shown have previously established a wireless connection. In some aspects, the UE 605, the source network node 610, and the candidate network node 615 may be combined with a conditional handover process (such as in conjunction with Figure 5In this regard, in some aspects, the UE 605 may be associated with the conditional handover process described in the Figure 6 The operations are shown and described with a prior RRC connection established with the source network node 610 .

[0095] As shown by reference numeral 620, UE 605 may receive configuration information from source network node 610. In some aspects, UE 605 may receive configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and / or downlink control information (DCI), etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by UE 605 (e.g., known to UE 605 and / or previously indicated by source network node 610 or other network device) and / or explicit configuration information for UE 605 to configure UE 605, etc. UE 605 may configure itself based at least in part on the configuration information. In some aspects, UE 605 may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0096] In some aspects, the configuration information may include the configuration of one or more conditional handover conditions associated with one or more candidate cells. For example, the configuration information may include one or more conditionalReconfiguration IEs, which indicate one or more execution conditions for triggering the handover of each candidate cell in the one or more candidate cells. In addition, in some aspects, each of the one or more conditional handover conditions may be based at least in part on the height of the UE. In other words, the UE 605 may be configured with multiple conditional handover conditions, each conditional handover condition being associated with a specific height or height range, so that if the UE 605 changes altitude frequently, the UE 605 may continue to evaluate the conditional handover conditions without the need for back-and-forth RRC signaling with the source network node 610 (e.g., without the need for the UE 605 to send a measurement report to the source network node 610, and in response, receive an updated configuration of one or more conditional handover conditions).

[0097] In some aspects, the configuration of one or more conditional handover conditions may be further based at least in part on measurements associated with one or more candidate cells. For example, the UE 605 may be configured to measure RSRP, RSRQ, SINR, etc. associated with one or more candidate cells. In such aspects, if the measurement conditions are met and the height conditions are met, the UE 120 may trigger a handover process to the candidate cell, as described in more detail below in conjunction with reference numeral 630.

[0098] In some aspects, one or more conditional handover conditions may include one or more RRM conditions (e.g., conditional event A3, conditional event A5, etc.) parameterized by one or more height conditions (e.g., event H1, event H2, etc.). For example, one or more conditional handover conditions may include conditional event A3 parameterized by one of event H1 or event H2, sometimes referred to as condEventA3H1 or condEventA3H2 respectively. In some aspects, conditional event A3 (e.g., condEventA3H1 or condEventA3H2) parameterized by event H1 or event H2 may be triggered according to two entry conditions: Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off (sometimes referred to as the first entry condition) and Ms – Hys > Thresh + Offset (sometimes referred to as the second entry condition), and if at least one of two exit conditions occurs within the TTT: Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off (sometimes referred to as the first exit condition) or Ms + Hys < Thresh + Offset (sometimes referred to as the second exit condition), then conditional event A3 parameterized by event H1 or event H2 may be cancelled.For the first entry condition and the first exit condition, Mn refers to the measurement result of the neighboring cell without considering any offset (e.g., RSRP, RSRQ, SINR, etc.); Ofn refers to the measurement object specific offset of the reference signal of the neighboring cell (sometimes referred to as offsetMO as defined in measObjectNR corresponding to the neighboring cell); Ocn refers to the cell-specific offset of the neighboring cell (sometimes referred to as cellIndividualOffset as defined in measObjectNR corresponding to the frequency of the neighboring cell); Hys refers to the hysteresis parameter associated with the triggering event (sometimes referred to as hysteresis as defined in reportConfigNR regarding the triggering event); Mp refers to the measurement result of SpCell without considering any offset (e.g., RSRP, RSRQ, SINR, etc.); Ofp refers to The measurement object specific offset of SpCell (sometimes referred to as offsetMO as defined in measObectNR corresponding to SpCell); Ocp refers to the cell specific offset of SpCell (sometimes referred to as cellIndividualOffset as defined in measObjectNR corresponding to SpCell) and is set to zero if not configured for SpCell; and Off refers to the offset parameter associated with the triggering event (sometimes referred to as a3-Offset as defined in reportConfigNR of the triggering event); where Mn and Mp are expressed in decibel-milliwatt (dBm) in the case of RSRP, or in decibel (dB) in the case of RSRQ and SINR, and where Ofn, Ocn, Ofp, Ocp, Hys and Off are expressed in dB. For the second entry condition and the second exit condition, Ms refers to the height (e.g., altitude) of UE 605 without considering any offset; Hys refers to a hysteresis parameter associated with the triggering event (sometimes referred to as h1-hysteresis or h2-hysteresis as defined in reportConfigEUTRA with respect to the triggering event); Thresh refers to a reference threshold parameter for the triggering event (sometimes referred to as heightThreshRef as defined in measConfig); and Offset refers to an offset value (e.g., heightThreshRef) for the reference threshold parameter to obtain an absolute threshold for the triggering event (sometimes referred to as h1-ThresholdOffset or h2-ThresholdOffset as defined in reportConfig); wherein Ms is expressed in distance units such as meters, and wherein Thresh is expressed in the same units as Ms.

[0099] In some other aspects, one or more conditional handover conditions may include a conditional event A5 parameterized by one of event H1 or event H2, sometimes referred to as condEventA5H1 or condEventA5H2, respectively. In some aspects, the conditional event A5 (e.g., condEventA5H1 or condEventA5H2) parameterized by event H1 or event H2 may be triggered according to three entry conditions: Mp + Hys < Thresh1 (sometimes referred to as the first entry condition), Mn + Ofn + Ocn - Hys > Thresh2 (sometimes referred to as the second entry condition), and Ms - Hys > Thresh + Offset (sometimes referred to as the third entry condition), and if at least one of three exit conditions is satisfied within TTT: Mp - Hys > Thresh1 (sometimes referred to as the first exit condition), Mn + Ofn + Ocn + Hys < Thresh2 (sometimes referred to as the second exit condition), and Ms + Hys < Thresh + Offset (sometimes referred to as the third exit condition), the conditional event A5 parameterized by event H1 or event H2 may be cancelled. For the above conditions, the variables refer to the same parameters as described above for the conditional event A3 parameterized by event H1 or event H2, plus Thresh1 corresponding to the first measurement threshold parameter and Thresh2 corresponding to the second measurement threshold parameter, which are expressed in dBm in the case of RSRP, or in dB in the case of RSRQ and SINR.

[0100] In some aspects, one or more conditional handover conditions may be associated with multiple TTTs (e.g., multiple timeToTrigger parameters). For example, in an aspect where one or more conditional handover conditions include one or more RRM conditions (e.g., conditional event A3, conditional event A5, etc.) parameterized by one or more altitude conditions (e.g., event H1, event H2, etc.), one or more RRM conditions may be associated with a first TTT, and one or more altitude conditions may be associated with a second TTT different from the first TTT. In this regard, in order to trigger or cancel a conditional handover, an RRM condition (e.g., the first entry or exit condition associated with condEventA3H1 or condEventA3H2, or the first or second entry or exit condition associated with condEventA5H1 or condEventA5H2) may need to satisfy a different time period from the altitude condition (e.g., the second entry or exit condition associated with condEventA3H1 or condEventA3H2, or the third entry or exit condition associated with condEventA5H1 or condEventA5H2).

[0101] In some aspects, one or more conditional handover conditions may be associated with one of conditional event H1 (sometimes referred to as condEventH1) or conditional event H2 (sometimes referred to as condEventH2). Conditional event H1 (e.g., condEventH1) and conditional event H2 (e.g., condEventH2) may be similar to events H1 and H2 described above, except that conditional event H1 and conditional event H2 may trigger a conditional handover process instead of triggering a measurement report containing the height of UE 605 (as in the case of events H1 and H2). In other words, conditional event H1 and conditional event H2 may be associated with entry conditions and exit conditions of the conditional handover process, even if measurement reports are not sent to the source network node 610. Therefore, when UE 605 is configured with conditional event H1 or conditional event H2 for a particular cell, if conditional event H1 or conditional event H2 is met, UE 605 may trigger a handover to the cell, as long as any additional conditional events associated with the cell (e.g., conditional events A3 or A5, etc.) are also met. For example, if the UE 605 is configured with conditional event A3 and conditional event H1 associated with a particular cell, the UE 605 may trigger a handover to the cell when both conditional event A3 and conditional event H1 are met.

[0102] In addition, in some aspects, the configuration of one or more conditional handover conditions may include the configuration of three or more conditional handover conditions associated with each candidate cell in one or more candidate cells. In other words, the condExecutionCond parameter may be configured to include a length sequence greater than two. Therefore, in some aspects, before triggering the conditional handover process, three or more conditional handover conditions of a given cell may need to be met. For example, for a specific candidate cell, the configuration of one or more conditional handover conditions may include the configuration of an RRM condition event (e.g., one of condEventA3 or condEventA5) based at least in part on a measurement type (e.g., one of RSRP measurement, RSRQ measurement, SINR measurement, etc.), another RRM condition event (e.g., another of condEventA3 or condEventA5) based at least in part on another measurement type (e.g., another of RSRP measurement, RSRQ measurement, SINR measurement, etc.), and one or more high condition events (e.g., at least one of condEventH1 or condEventH2). In such aspects, to trigger the conditional handover process, the UE 605 may need to be within a specific altitude range, etc. (as indicated by the configuration of one or more altitude condition events associated with the specific cell) in addition to certain measurements associated with the specific cell satisfying the triggering criteria.

[0103] In some aspects, the configuration information described in conjunction with reference numeral 620 may include multiple configurations. For example, in some aspects, UE 605 may receive multiple configurations of one or more conditional handover conditions associated with one or more candidate cells, wherein the first configuration in the multiple configurations is associated with the first altitude range of UE 605, and the second configuration in the multiple configurations is associated with the second altitude range of UE 605. In some aspects, each configuration may include an indication of the corresponding altitude range. For example, in some aspects, a UE state configuration identifier parameter (sometimes referred to as a ueStatusConfigID parameter) associated with each configuration may be used to indicate the altitude range associated with the corresponding configuration. In some aspects, UE 605 may be configured with multiple altitude variables (sometimes referred to as H1, H2, etc.), and each configuration of one or more conditional handover conditions may correspond to a specific altitude range associated with the altitude variable. For example, when UE 605 is within a first altitude interval (such as when UE 605 is at an altitude less than H1), a first configuration may be applied, and when UE 605 is within a second altitude interval (such as when UE 605 is at an altitude greater than H1 and less than H2), a second configuration may be applied, and so on.

[0104] In some aspects, the configuration of one or more conditional handover conditions associated with one or more candidate cells may be based at least in part on the three-dimensional location of the UE 605. For example, the configuration of the conditional handover conditions and / or a subset of the conditional handover conditions may be associated with a given three-dimensional region so that the UE 605 may only monitor the handover conditions applicable to the three-dimensional region where the UE 605 is currently located. In addition, in some aspects, in addition to or as an alternative to the RRM conditions (e.g., condition event A3, condition event A5, etc.) and / or altitude conditions (e.g., event H1, event H2, condition event H1, condition event H2, etc.) described above, the configuration of the conditional handover conditions and / or a subset of the conditional handover conditions may be associated with different condition triggers. For example, in some aspects, one or more conditional handover conditions may be further based at least in part on at least one of a timer and / or time interval (sometimes referred to as condEventT1), a distance between the UE and a reference point (sometimes referred to as condEventD1), etc. For example, in some aspects, the UE 605 may be configured to apply certain conditional handover conditions when the UE 605 is within a particular zone (sometimes referred to as a geo-fence) at a certain time of day, etc.

[0105] As shown in reference numeral 625, in some aspects, UE 605 may evaluate one or more conditional handover conditions. For example, UE 605 may monitor the altitude of UE 605 and / or measure certain reference signals (CSI-RS, SSB) to determine whether one or more conditional handover conditions are met. In this regard, UE 605 may perform certain actions similar to those described in conjunction with reference numeral 535. In addition, in some aspects, UE 605 may select certain handover conditions to be evaluated based at least in part on the altitude of UE 605. For example, in aspects where UE 605 receives multiple conditional handover configurations, each of which is associated with a different altitude range (as described above in conjunction with reference numeral 620), UE 605 may select one of the first configuration or the second configuration based at least in part on the altitude of UE 605.

[0106] As indicated by reference numeral 630, in some aspects, the UE 605 may trigger a conditional handover process based at least in part on the altitude of the UE 605. For example, in response to satisfying one or more conditional handover conditions associated with the candidate network node 615, the UE 605 may trigger the conditional handover process by connecting to the candidate network node 615. For example, in aspects where the one or more conditional handover conditions include one or more RRM conditions (e.g., one or more of conditional events A3, conditional events A5, etc.) parameterized by one or more altitude conditions (e.g., one or more of event H1, event H2, etc.), the UE 605 may trigger the conditional handover process based at least in part on measurements associated with one or more candidate cells satisfying one or more entry conditions associated with the RRM conditions and the altitude of the UE 605 satisfying the one or more altitude conditions. Additionally or alternatively, when the one or more conditional handover conditions are associated with one of conditional event H1 or conditional event H2, the UE 605 may trigger the conditional handover process based at least in part on the altitude of the UE satisfying the conditional event H1 or conditional event H2. Additionally or alternatively, when UE 605 receives multiple configurations of one or more conditional handover conditions associated with one or more candidate cells, UE 605 may trigger a conditional handover process associated with the configuration corresponding to the current altitude of UE 605.

[0107] In addition, as described in conjunction with reference numeral 555, in some aspects, candidate network node 615 may indicate to source network node 610 that UE 605 performs a conditional handover procedure with candidate network node 615. More specifically, as shown in reference numeral 635, in some aspects, source network node 610 may receive an indication from another network node (e.g., candidate network node 615) associated with a candidate cell in one or more candidate cells to perform a conditional handover procedure between UE 605 and the other network node. In this regard, source network node 610 may perform in conjunction with Figure 5 The handover completion steps described, such as sending a handover cancel message to other candidate network nodes, as described above in conjunction with reference numeral 560, performing a UE context release procedure, as described above in conjunction with reference numeral 565, and / or performing similar actions.

[0108] Based at least in part on UE 605 being configured with one or more conditional handover conditions based at least in part on the altitude of UE 605, UE 605 and / or one or more network nodes (e.g., source network node 610, candidate network node 615, and / or other candidate network nodes) may save computational, power, network, and / or communication resources that may otherwise have been consumed by RRC signaling when UE 605 changes altitude. For example, based at least in part on UE 605 being configured with one or more conditional handover conditions based at least in part on the altitude of UE 605, UE 605 and one or more network nodes may communicate with reduced RRC-level signaling overhead as compared to a legacy conditional handover procedure, thereby resulting in a less congested communication channel, and therefore, resulting in lower latency, higher throughput, and an overall more efficient use of network resources.

[0109] As indicated above, Figure 6 are provided as examples. Other examples can be found in relation to Figure 6 The examples described are different.

[0110] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a UE in accordance with the present disclosure. Example process 700 is an example in which a UE (eg, UE 605) performs operations associated with a conditional handover condition associated with the UE's altitude.

[0111] like Figure 7 As shown, in some aspects, process 700 may include receiving a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on a height of the UE (block 710). For example, a UE (e.g., using Fig. 9The depicted communications manager 140 and / or receiving component 902) may receive a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on a height of the UE, as described above.

[0112] like Figure 7 As further shown, in some aspects, process 700 may include triggering a conditional handover process based at least in part on the altitude of the UE (block 720). Fig. 9 The depicted communications manager 140 and / or handover component 908) can trigger a conditional handover process based at least in part on the altitude of the UE, as described above.

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

[0114] In a first aspect, configuration of the one or more conditional handover conditions is further based at least in part on measurements associated with the one or more candidate cells, and triggering the conditional handover procedure is further based at least in part on measurements associated with the one or more candidate cells.

[0115] In a second aspect, alone or in combination with the first aspect, the one or more conditional handover conditions include one or more RRM conditions parameterized by one or more height conditions.

[0116] In a third aspect, alone or in combination with one or more of the first and second aspects, one or more RRM conditions are associated with at least one of condition event A3 or condition event A5.

[0117] In a fourth aspect, alone or in combination with one or more of the first to third aspects, one or more conditional handover conditions are associated with one of the conditional event H1 or the conditional event H2.

[0118] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the configuration of one or more conditional handover conditions includes the configuration of three or more conditional handover conditions associated with each of the one or more candidate cells.

[0119] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 700 comprises receiving multiple configurations of one or more conditional handover conditions associated with one or more candidate cells, wherein a first configuration of the multiple configurations is associated with a first altitude range of the UE, and wherein a second configuration of the multiple configurations is associated with a second altitude range of the UE.

[0120] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 700 includes selecting one of the first configuration or the second configuration based at least in part on an altitude of the UE.

[0121] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the configuration of one or more conditional handover conditions associated with one or more candidate cells is further based at least in part on a three-dimensional position of the UE.

[0122] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, each of the one or more conditional handover conditions is further based at least in part on at least one of a measurement associated with a corresponding candidate cell in the one or more candidate cells, a time interval, or a distance of the UE from a reference point.

[0123] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks of the blocks of process 700 may be performed in parallel.

[0124] Figure 8 is a diagram illustrating an example process 800, performed, for example, by a network node, in accordance with the present disclosure. Example process 800 is an example in which a network node (eg, source network node 610) performs operations associated with a conditional handover condition associated with a height of a UE.

[0125] like Figure 8 As shown, in some aspects, process 800 may include sending a configuration of one or more conditional handover conditions associated with one or more candidate cells to a UE, wherein each of the one or more conditional handover conditions is based at least in part on the altitude of the UE (block 810). For example, a network node (e.g., using Fig.10 The depicted communications manager 150 and / or transmitting component 1004) may transmit to the UE a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on the altitude of the UE, as described above.

[0126] like Figure 8As further shown, in some aspects, process 800 may include receiving an indication from another network node associated with a candidate cell of the one or more candidate cells to perform a conditional handover process between the UE and the other network node, wherein the conditional handover process is triggered based at least in part on the altitude of the UE (block 820). For example, the network node (e.g., using Fig.10 The depicted communication manager 150 and / or receiving component 1002) may receive an indication from another network node associated with a candidate cell in one or more candidate cells to perform a conditional handover process between the UE and the other network node, wherein the conditional handover process is triggered at least in part based on the altitude of the UE, as described above.

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

[0128] In the first aspect, configuration of the one or more conditional handover conditions is further based at least in part on measurements associated with the one or more candidate cells.

[0129] In a second aspect, alone or in combination with the first aspect, the one or more conditional handover conditions include one or more RRM conditions parameterized by one or more height conditions.

[0130] In a third aspect, alone or in combination with one or more of the first and second aspects, one or more RRM conditions are associated with at least one of condition event A3 or condition event A5.

[0131] In a fourth aspect, alone or in combination with one or more of the first to third aspects, one or more conditional handover conditions are associated with one of the conditional event H1 or the conditional event H2.

[0132] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the configuration of one or more conditional handover conditions includes the configuration of three or more conditional handover conditions associated with each of the one or more candidate cells.

[0133] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 800 comprises sending to a UE multiple configurations of one or more conditional handover conditions associated with one or more candidate cells, wherein a first configuration of the multiple configurations is associated with a first altitude range of the UE, and wherein a second configuration of the multiple configurations is associated with a second altitude range of the UE.

[0134] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, configuration of one or more conditional handover conditions associated with one or more candidate cells is further based at least in part on a three-dimensional position of the UE.

[0135] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, each of the one or more conditional handover conditions is further based at least in part on at least one of a measurement associated with a corresponding candidate cell in the one or more candidate cells, a time interval, or a distance of the UE from a reference point.

[0136] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0137] Fig. 9 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a UE (e.g., UE 605), or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 140. Communication manager 140 may include one or more of a handover component 908 or a selection component 910, among others.

[0138] In some aspects, the apparatus 900 may be configured to perform Figure 6 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0139] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 The UE 120 is described as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0140] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the depicted UE 120. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0141] Receiving component 902 and / or handover component 908 can receive a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE. Handover component 908 can trigger a conditional handover process based at least in part on the height of the UE.

[0142] The receiving component 902 and / or the handover component 908 can receive a plurality of configurations of one or more conditional handover conditions associated with one or more candidate cells, wherein a first configuration in the plurality of configurations is associated with a first altitude range of the UE, and wherein a second configuration in the plurality of configurations is associated with a second altitude range of the UE. The selecting component 910 can select one of the first configuration or the second configuration based at least in part on the altitude of the UE.

[0143] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The component set (one or more components) shown may be described as being executable by Fig. 9 Another component shown may be a collection of components that perform one or more functions.

[0144] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a network node (e.g., source network node 610), or a network node may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 150. Communication manager 150 may include configuration component 1008, etc.

[0145] In some aspects, the apparatus 1000 may be configured to perform Figure 6 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.10 The device 1000 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0146] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 The network node 110 is depicted as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0147] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the depicted network node 110. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0148] The sending component 1004 and / or the configuring component 1008 can send a configuration of one or more conditional handover conditions associated with one or more candidate cells to the UE, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE. The receiving component 1002 can receive an indication from another network node associated with a candidate cell in the one or more candidate cells to perform a conditional handover procedure between the UE and the another network node, wherein the conditional handover procedure is triggered at least in part based on the height of the UE.

[0149] Sending component 1004 and configuring component 1008 may send a plurality of configurations of one or more conditional handover conditions associated with one or more candidate cells to the UE, wherein a first configuration of the plurality of configurations is associated with a first altitude range of the UE, and wherein a second configuration of the plurality of configurations is associated with a second altitude range of the UE.

[0150] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.10 Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The component set (one or more components) shown may be described as being executable by Fig.10 Another component shown may be a collection of components that perform one or more functions.

[0151] The following provides an overview of some aspects of the disclosure:

[0152] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE; and triggering a conditional handover process based at least in part on the height of the UE.

[0153] Aspect 2: A method according to Aspect 1, wherein the configuration of the one or more conditional handover conditions is further based at least in part on measurements associated with the one or more candidate cells, and wherein triggering the conditional handover process is further based at least in part on the measurements associated with the one or more candidate cells.

[0154] Aspect 3: The method according to any one of aspects 1 to 2, wherein the one or more conditional handover conditions include one or more RRM conditions parameterized by one or more height conditions.

[0155] Aspect 4: The method according to aspect 3, wherein the one or more RRM conditions are associated with at least one of condition event A3 or condition event A5.

[0156] Aspect 5: The method according to any one of aspects 1 to 4, wherein the one or more conditional handover conditions are associated with one of condition event H1 or condition event H2.

[0157] Aspect 6: The method according to any one of aspects 1 to 5, wherein the configuration of the one or more conditional handover conditions may include a configuration of three or more conditional handover conditions associated with each of the one or more candidate cells.

[0158] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes receiving multiple configurations of one or more conditional handover conditions associated with the one or more candidate cells, wherein a first configuration in the multiple configurations is associated with a first height range of the UE, and wherein a second configuration in the multiple configurations is associated with a second height range of the UE.

[0159] Aspect 8: The method according to aspect 7, the method further comprising selecting one of the first configuration or the second configuration based at least in part on the altitude of the UE.

[0160] Aspect 9: The method according to any one of aspects 1 to 8, wherein the configuration of the one or more conditional handover conditions associated with the one or more candidate cells is further based at least in part on the three-dimensional position of the UE.

[0161] Aspect 10: A method according to any one of Aspects 1 to 9, wherein each of the one or more conditional handover conditions is further based at least in part on at least one of: a measurement associated with a corresponding candidate cell among the one or more candidate cells, a time interval, or a distance of the UE from a reference point.

[0162] Aspect 11: A method of wireless communication performed by a network node, the method comprising: sending a configuration of one or more conditional handover conditions associated with one or more candidate cells to a UE, wherein each of the one or more conditional handover conditions is based at least in part on the height of the UE; and receiving an indication from another network node associated with a candidate cell in the one or more candidate cells to perform a conditional handover process between the UE and the other network node, wherein the conditional handover process is triggered at least in part based on the height of the UE.

[0163] Aspect 12: The method according to aspect 11, wherein the configuration of the one or more conditional handover conditions is further based at least in part on measurements associated with the one or more candidate cells.

[0164] Aspect 13: The method according to any one of aspects 11 to 12, wherein the one or more conditional handover conditions include one or more RRM conditions parameterized by one or more height conditions.

[0165] Aspect 14: The method according to Aspect 13, wherein the one or more RRM conditions are associated with at least one of condition event A3 or condition event A5.

[0166] Aspect 15: The method according to any one of aspects 11 to 14, wherein the one or more conditional handover conditions are associated with one of conditional event H1 or conditional event H2.

[0167] Aspect 16: The method according to any one of aspects 11 to 15, wherein the configuration of the one or more conditional handover conditions may include a configuration of three or more conditional handover conditions associated with each of the one or more candidate cells.

[0168] Aspect 17: According to the method described in any one of Aspects 11 to 16, the method further includes sending multiple configurations of one or more conditional handover conditions associated with the one or more candidate cells to the UE, wherein a first configuration in the multiple configurations is associated with a first height range of the UE, and wherein a second configuration in the multiple configurations is associated with a second height range of the UE.

[0169] Aspect 18: The method according to any one of aspects 11 to 17, wherein the configuration of the one or more conditional handover conditions associated with the one or more candidate cells is further based at least in part on a three-dimensional position of the UE.

[0170] Aspect 19: A method according to any one of Aspects 11 to 18, wherein each of the one or more conditional handover conditions is further based at least in part on at least one of: a measurement associated with a corresponding candidate cell in the one or more candidate cells, a time interval, or a distance of the UE from a reference point.

[0171] Aspect 20: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 10.

[0172] Aspect 21: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 10.

[0173] Aspect 22: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 10.

[0174] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 10.

[0175] Aspect 24: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 10.

[0176] Aspect 25: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 11 to 19.

[0177] Aspect 26: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 11 to 19.

[0178] Aspect 27: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 11 to 19.

[0179] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 11 to 19.

[0180] Aspect 29: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 11 to 19.

[0181] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or may be acquired from practice of the various aspects.

[0182] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures and / or functions, etc. As used herein, a "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to a specific software code, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0183] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0184] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically set forth in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0185] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on a height of the UE; as well as A conditional handover procedure is triggered based at least in part on the altitude of the UE.

2. The apparatus of claim 1 , wherein the configuration of the one or more conditional handover conditions is further based at least in part on measurements associated with the one or more candidate cells, and wherein triggering the conditional handover process is further based at least in part on the measurements associated with the one or more candidate cells.

3. The apparatus of claim 1, wherein the one or more conditional handover conditions comprise one or more radio resource management (RRM) conditions parameterized by one or more height conditions.

4. The apparatus of claim 3, wherein the one or more RRM conditions are associated with at least one of condition event A3 or condition event A5. 5 . The apparatus of claim 1 , wherein the one or more conditional handover conditions are associated with one of conditional event H1 or conditional event H2 .

6. The apparatus of claim 1, wherein the configuration of the one or more conditional handover conditions comprises a configuration of three or more conditional handover conditions associated with each of the one or more candidate cells.

7. The apparatus of claim 1 , wherein the one or more processors are further configured to receive a plurality of configurations of one or more conditional handover conditions associated with the one or more candidate cells, wherein a first configuration of the plurality of configurations is associated with a first altitude range of the UE, and wherein a second configuration of the plurality of configurations is associated with a second altitude range of the UE.

8. The apparatus of claim 7, wherein the one or more processors are further configured to select one of the first configuration or the second configuration based at least in part on the altitude of the UE.

9. The apparatus of claim 1, wherein the configuration of the one or more conditional handover conditions associated with the one or more candidate cells is further based at least in part on a three-dimensional location of the UE.

10. The apparatus of claim 1, wherein each of the one or more conditional handover conditions is further based at least in part on at least one of: measurements associated with a corresponding candidate cell of the one or more candidate cells, time interval, or The distance between the UE and the reference point.

11. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: sending a configuration of one or more conditional handover conditions associated with one or more candidate cells to a user equipment (UE), wherein each of the one or more conditional handover conditions is based at least in part on a height of the UE; as well as An indication is received from another network node associated with a candidate cell of the one or more candidate cells to perform a conditional handover procedure between the UE and the another network node, wherein the conditional handover procedure is triggered based at least in part on the altitude of the UE.

12. The apparatus of claim 11, wherein the configuration of the one or more conditional handover conditions is further based at least in part on measurements associated with the one or more candidate cells.

13. The apparatus of claim 11, wherein the one or more conditional handover conditions comprise one or more radio resource management (RRM) conditions parameterized by one or more height conditions.

14. The apparatus of claim 13, wherein the one or more RRM conditions are associated with at least one of condition event A3 or condition event A5. 15 . The apparatus of claim 11 , wherein the one or more conditional handover conditions are associated with one of conditional event H1 or conditional event H2.

16. The apparatus of claim 11, wherein the configuration of the one or more conditional handover conditions comprises a configuration of three or more conditional handover conditions associated with each of the one or more candidate cells.

17. The apparatus of claim 11, wherein the one or more processors are further configured to send a plurality of configurations of one or more conditional handover conditions associated with the one or more candidate cells to the UE, wherein a first configuration of the plurality of configurations is associated with a first altitude range of the UE, and wherein a second configuration of the plurality of configurations is associated with a second altitude range of the UE.

18. The apparatus of claim 11, wherein the configuration of the one or more conditional handover conditions associated with the one or more candidate cells is further based at least in part on a three-dimensional location of the UE.

19. The apparatus of claim 11, wherein each of the one or more conditional handover conditions is further based at least in part on at least one of: measurements associated with a corresponding candidate cell of the one or more candidate cells, time interval, or The distance between the UE and the reference point.

20. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration of one or more conditional handover conditions associated with one or more candidate cells, wherein each of the one or more conditional handover conditions is based at least in part on a height of the UE; as well as A conditional handover procedure is triggered based at least in part on the altitude of the UE.

21. The method of claim 20, wherein the one or more conditional handover conditions comprise one or more radio resource management (RRM) conditions parameterized by one or more height conditions.

22. The method of claim 20, wherein the one or more conditional handover conditions are associated with one of conditional event H1 or conditional event H2.

23. The method of claim 20, wherein the configuration of the one or more conditional handover conditions comprises a configuration of three or more conditional handover conditions associated with each of the one or more candidate cells.

24. The method of claim 20, further comprising receiving a plurality of configurations of one or more conditional handover conditions associated with the one or more candidate cells, wherein a first configuration of the plurality of configurations is associated with a first altitude range of the UE, and wherein a second configuration of the plurality of configurations is associated with a second altitude range of the UE.

25. The method of claim 24, further comprising selecting one of the first configuration or the second configuration based at least in part on the altitude of the UE.

26. A method of wireless communication performed by a network node, the method comprising: sending a configuration of one or more conditional handover conditions associated with one or more candidate cells to a user equipment (UE), wherein each of the one or more conditional handover conditions is based at least in part on a height of the UE; as well as An indication is received from another network node associated with a candidate cell of the one or more candidate cells to perform a conditional handover procedure between the UE and the another network node, wherein the conditional handover procedure is triggered based at least in part on the altitude of the UE.

27. The method of claim 26, wherein the one or more conditional handover conditions comprise one or more radio resource management (RRM) conditions parameterized by one or more height conditions.

28. The method of claim 26, wherein the one or more conditional handover conditions are associated with one of condition event H1 or condition event H2.

29. The method of claim 26, wherein the configuration of the one or more conditional handover conditions comprises a configuration of three or more conditional handover conditions associated with each of the one or more candidate cells.

30. The method of claim 26, further comprising sending a plurality of configurations of one or more conditional handover conditions associated with the one or more candidate cells to the UE, wherein a first configuration of the plurality of configurations is associated with a first altitude range of the UE, and wherein a second configuration of the plurality of configurations is associated with a second altitude range of the UE.

Images