PRIORITIZATION OF LAYER 1 OR LAYER 2 TRIGGERED MOBILITY AND CONDITIONAL HANDOVER DURING FAILURE RECOVERY

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for prioritization of layer 1 or layer 2 triggered mobility (LTM) and conditional handover during failure recovery.

BACKGROUND

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like). 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).

A wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the network node to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and/or a wireless personal area network (WPAN) link, among other examples).

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, 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 the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) 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, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.

SUMMARY

In a layer 1 (L1) and/or layer 2 (L2) triggered mobility (LTM), a user equipment (UE) may transmit a measurement report to a network node. The network node may transmit, to the UE and based at least in part on the measurement report, a configuration of one or more LTM candidate target cells. The UE may perform measurements on the configured LTM candidate target cells, and the UE may transmit a lower-layer measurement report to the network node. The network node may determine, based at least in part on the lower-layer measurement report, to execute an LTM cell switch to a target cell. The UE may switch to a configuration of the target cell, and the UE may perform a random access procedure with the target cell.

In a conditional handover, a UE may determine to perform a handover when certain conditions are satisfied. In other words, the UE may execute the conditional handover when the certain conditions are satisfied. The UE may start evaluating execution condition(s) after receiving a conditional handover configuration from a source network node. The UE may stop evaluating the execution condition(s) after the conditional handover is executed, at which point the UE may be connected to a target network node.

A UE may be configured for both conditional handover and LTM. The UE may experience radio link failure (RLF). The UE may fail to execute a handover. The UE may need to perform a reestablishment. In these scenarios, the UE may not be configured to determine whether to perform conditional handover or LTM. In other words, a prioritization between executing conditional handover or LTM for a given cell (e.g., cell A for conditional handover or cell B for LTM) may not be defined at the UE. When the UE experiences the RLF, fails to execute the handover, and/or needs to perform the reestablishment, the UE may select to execute conditional handover, even though executing LTM may be more appropriate, or vice versa. For example, executing LTM instead of conditional handover, or vice versa, in certain situations may lead to reduced signaling and/or better network coverage. As a result, an inability to prioritize conditional handover or LTM may degrade an overall performance of the UE.

Various aspects relate generally to prioritization of LTM and conditional handover during failure recovery. Some aspects more specifically relate to LTM and conditional handover in response to RLF or handover failure. In some examples, a UE may detect a link failure, such as the RLF or the handover failure. The UE may perform, based at least in part on the link failure, LTM and/or conditional handover based at least in part on the prioritization of LTM and conditional handover during failure recovery. In some cases, LTM may be prioritized over conditional handover. Alternatively, conditional handover may be prioritized over LTM. The prioritization may be based at least in part on channel qualities of candidate special cells (SpCells) associated with LTM and/or conditional handover. The prioritization may be based at least in part on channel qualities, numbers of secondary cells (SCells), and/or numbers of beams associated with candidate cell groups, which may be configured for LTM or conditional handover. The prioritization may be based at least in part on frequency division duplex (FDD) capabilities of the candidate cell groups. The prioritization may be based at least in part on a handover interruption time. The prioritization may be based at least in part on a quality of service (QOS) of traffic on a source cell. The prioritization may be based at least in part on an artificial intelligence or machine learning (AI/ML) prediction of a handover success probability, an expected throughput, and/or a handover interruption time.

In some implementations, an apparatus for wireless communication at a UE includes one or more memories and one or more processors, coupled to the one or more memories, configured to cause the UE to: detect a link failure; and perform, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery.

In some implementations, a method of wireless communication performed by a UE includes detecting a link failure; and performing, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery.

In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: detect a link failure; and perform, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery.

In some implementations, an apparatus for wireless communication includes means for detecting a link failure; and means for performing, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

FIG. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

FIG. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

FIG. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

FIG. 4 is a diagram illustrating an example of a layer 1 (L1) or a layer 2 (L2) (L1/L2)-triggered mobility (LTM), in accordance with the present disclosure.

FIG. 5 is a diagram illustrating an example of conditional handover, in accordance with the present disclosure.

FIG. 6 is a diagram illustrating an example associated with prioritization of LTM and conditional handover during failure recovery, in accordance with the present disclosure.

FIG. 7 is a diagram illustrating an example process associated with prioritization of LTM and conditional handover during failure recovery, in accordance with the present disclosure.

FIG. 8 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

DETAILED DESCRIPTION

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by defining the prioritization of LTM and conditional handover during failure recovery, the described techniques can be used by the UE to select between LTM and conditional handover. For example, an ability to intelligently select between LTM or conditional handover may allow the UE to connect to higher quality cells and/or cell groups, connect to cells with an FDD capability, reduce a handover interruption time, and/or optimize QoS, thereby improving an overall performance of the UE.

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than 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 a claim.

Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses 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, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 110d), a UE 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and/or other entities. A network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated 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). As another example, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among 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)).

In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs. A network node 110 may include, for example, 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 transmission reception point (TRP), a DU, an 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, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.

In some examples, a network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a network node 110 and/or a network node subsystem serving this coverage area, depending on the context in which the term is used. A 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., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 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. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in FIG. 1, the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. A network node may support one or multiple (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node).

In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a CU, a DU, an 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 terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity 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 duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “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 terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the 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. In the example shown in FIG. 1, the network node 110d (e.g., a relay network node) may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication 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, or the like.

The wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. 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, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these 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 communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE 120 may 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, 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 vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and/or any other suitable device that is configured to communicate via a wireless or wired medium.

Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, an unmanned aerial vehicle, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

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

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

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, 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 range designations 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 referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHZ-24.25 GHZ). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHZ), and FR5 (114.25 GHZ-300 GHz). Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may 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) may be modified, and techniques described herein are applicable to those modified frequency ranges.

In some aspects, a UE (e.g., the UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may detect a link failure; and perform, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

As indicated above, FIG. 1 is provided as an example. Other examples may differ from what is described with regard to FIG. 1.

FIG. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, a 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 radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.

At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that 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(s) selected for the UE 120 and may 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., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., Toutput symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 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 through 234t.

At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the 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 through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a 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 modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A 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 examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

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.

One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, or may 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, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of FIG. 2.

On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted 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 the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 6-8).

At the network node 110, the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide 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 the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 6-8).

The controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 may perform one or more techniques associated with prioritization of LTM and conditional handover during failure recovery, 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 any other component(s) of FIG. 2 may perform or direct operations of, for example, process 700 of FIG. 7, and/or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and/or the 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 (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 700 of FIG. 7, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a UE (e.g., the UE 120) includes means for detecting a link failure; and/or means for performing, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery. The means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, an individual processor may perform all of the functions described as being performed by the one or more processors. In some aspects, one or more processors may collectively perform a set of functions. For example, a first set of (one or more) processors of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with FIG. 2. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with FIG. 2. For example, functions described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

While blocks in FIG. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to 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.

As indicated above, FIG. 2 is provided as an example. Other examples may differ from what is described with regard to FIG. 2.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. 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 a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

An aggregated base station (e.g., an aggregated network node) may 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 disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

FIG. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated 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). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces. 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 simultaneously served by multiple RUs 340.

Each of the units, including the CUS 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit-User Plane (CU-UP) functionality), control plane functionality (for example, Central Unit-Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

Each DU 330 may correspond to a logical unit that includes one or more base station functions to control 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 depending, at least in part, on a functional split, such as a functional split defined by the 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, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

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

The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized 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 operations 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 life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. 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 for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies).

As indicated above, FIG. 3 is provided as an example. Other examples may differ from what is described with regard to FIG. 3.

FIG. 4 is a diagram illustrating an example 400 of an LTM, in accordance with the present disclosure. As shown in FIG. 4, example 400 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network, such as wireless network 100.

In an LTM, the UE may be in an RRC connected state. As shown by reference number 402, the UE may transmit, to the network node, a measurement report. The UE may transmit the measurement report via RRC signaling. The network node may determine, based at least in part on the measurement report, to use LTM and may initiate a candidate LTM cell preparation. As shown by reference number 404, the network node may transmit, to the UE, an RRC reconfiguration message. The RRC reconfiguration message may indicate a candidate LTM cell configuration, which may indicate a configuration of one or multiple candidate LTM target cells. The UE may store the candidate LTM cell configuration. As shown by reference number 406, the UE may transmit, to the network node, an RRC reconfiguration complete message. The measurement report, the RRC reconfiguration message, and the RRC reconfiguration complete message may be part of an LTM preparation phase.

As shown by reference 408, the UE may perform a downlink/uplink synchronization and a timing advance (TA) acquisition with candidate target cells, which may occur before receiving an LTM cell switch command. The downlink/uplink synchronization and the TA acquisition may be associated with an early synchronization phase. The UE may perform L1 measurements on one or more configured candidate LTM target cells. As shown by reference number 410, the UE may transmit, to the network node, an L1 measurement report, which may indicate the L1 measurements on the one or more configured candidate LTM target cells. The network node may determine to execute an LTM cell switch to a target cell, which may be based at least in part on the L1 measurement report. As shown by reference number 412, the network node may transmit, to the UE, a MAC control element (MAC-CE) triggering the LTM cell switch, where the MAC-CE may indicate a candidate configuration index of the target cell. The UE may detach from a source cell. The UE may apply the candidate configuration index of the target cell. In other words, the UE may switch to a configuration of a candidate LTM target cell. The UE may detach from the source cell and attach to the target cell as part of an LTM execution phase.

As shown by reference number 414, the UE may perform a random access channel (RACH) procedure with the target cell (e.g., when a TA is not available). As shown by reference number 416, the UE may transmit, to the target cell, an indication of a successful completion of the LTM cell switch to the target cell. The indication of the successful completion of the LTM cell switch may be part of an LTM completion phase.

As indicated above, FIG. 4 is provided as an example. Other examples may differ from what is described with regard to FIG. 4.

FIG. 5 is a diagram illustrating an example 500 of conditional handover, in accordance with the present disclosure. As shown in FIG. 5, example 500 includes communication between a UE (e.g., UE 120), a source network node (e.g., network node 110a), a target network node (e.g., network node 110b), and other potential target network nodes (e.g., network node 110c). In some aspects, the UE, the source network node, the target network node, and the other potential target network nodes may be included in a wireless network, such as wireless network 100.

In a conditional handover, a UE may determine to perform a handover when certain conditions are satisfied. In other words, the UE may execute the conditional handover when the certain conditions are satisfied. The UE may start evaluating execution condition(s) after receiving a conditional handover configuration from the source network node. The UE may stop evaluating the execution condition(s) after the conditional handover is executed.

As shown by reference number 502, the UE may transmit, to the source network node, a measurement report. The measurement report may be based at least in part on a measurement configuration, which may be provided by the source network node. As shown by reference number 504, the source network node may determine to conditionally hand over the UE based at least in part on the measurement report. As shown by reference number 506, the source network node may transmit a conditional handover request to one or more candidate cells, which may be associated with one or more candidate target network nodes. The one or more candidate target network nodes may include the target network node and the other potential network nodes. The source network node may transmit a conditional handover request for each candidate target network node.

As shown by reference number 508, the target network node and the other potential network nodes may perform an admission control. As shown by reference number 510, the target network node and the other potential network nodes may transmit, to the source network node, a handover request acknowledge message. The handover request acknowledge message may indicate the conditional handover configuration. The conditional handover configuration may indicate a configuration of the one or more candidate target network nodes (e.g., conditional handover candidate cells). As shown by reference number 512, the source network node may transmit, to the UE, an RRC reconfiguration message. The RRC reconfiguration message may indicate the configuration of the one or more candidate target network nodes. The RRC reconfiguration message may indicate conditional handover execution conditions.

As shown by reference number 514, the UE may transmit, to the source network node, an RRC reconfiguration message. As shown by reference number 516, the UE may maintain a connection with the source network node after receiving the conditional handover configuration, and the UE may start evaluating the conditional handover execution conditions for the one or more candidate target network nodes. When the target network node satisfies a corresponding conditional handover execution condition, the UE may detach from the source network node, apply a stored corresponding configuration for the target network node, synchronize to the target network node, and complete an RRC handover procedure by transmitting an RRC reconfiguration complete message to the target network node. As shown by reference number 518, the UE, the source network node, and/or the target network node may perform a conditional handover completion. For example, the target network node may transmit a handover success message to the source network node to indicate that the UE has successfully accessed the target network node. The source network node may transmit a handover cancel message to the other potential target network nodes to cancel a conditional handover for the UE.

As indicated above, FIG. 5 is provided as an example. Other examples may differ from what is described with regard to FIG. 5.

A UE may be configured for both conditional handover and LTM. The UE may experience RLF. The UE may fail to execute a handover. The UE may need to perform a reestablishment. In these scenarios, the UE may not be configured to determine whether to perform conditional handover or LTM. In other words, a prioritization between executing conditional handover or LTM for a given cell (e.g., cell A for conditional handover or cell B for LTM) may not be defined at the UE. When the UE experiences the RLF, fails to execute the handover, and/or needs to perform the reestablishment, the UE may select to execute conditional handover, even though executing LTM may be more appropriate, or vice versa. For example, executing LTM instead of conditional handover, or vice versa, in certain situations may lead to reduced signaling and/or better network coverage. As a result, an inability to prioritize conditional handover or LTM may degrade an overall performance of the UE.

In various aspects of techniques and apparatuses described herein, a UE may detect a link failure, such as the RLF or the handover failure. The UE may perform, based at least in part on the link failure, LTM and/or conditional handover based at least in part on the prioritization of LTM and conditional handover during failure recovery. The UE may be configured for both LTM and conditional handover. In some cases, LTM may be prioritized over conditional handover. Alternatively, conditional handover may be prioritized over LTM. The prioritization may be based at least in part on channel qualities of candidate SpCells associated with LTM and/or conditional handover. The prioritization may be based at least in part on channel qualities, numbers of SCells, and/or numbers of beams associated with candidate cell groups, which may be configured for LTM or conditional handover. The prioritization may be based at least in part on FDD capabilities of the candidate cell groups. The prioritization may be based at least in part on a handover interruption time. The prioritization may be based at least in part on a QoS of traffic on a source cell. The prioritization may be based at least in part on an AI/ML prediction of a handover success probability, an expected throughput, and/or a handover interruption time.

In some aspects, by defining the prioritization of LTM and conditional handover during failure recovery, the UE may be able to select between LTM and conditional handover. For example, an ability to intelligently select between LTM or conditional handover may allow the UE to connect to higher quality cells and/or cell groups, connect to cells with an FDD capability, reduce a handover interruption time, and/or optimize QoS, thereby improving an overall performance of the UE.

FIG. 6 is a diagram illustrating an example 600 associated with prioritization of LTM and conditional handover during failure recovery, in accordance with the present disclosure. As shown in FIG. 6, example 600 includes communication between a UE (e.g., UE 120), a source network node (e.g., network node 110a), and a target network node (e.g., network node 110b). In some aspects, the UE, the source network node, and the target network node may be included in a wireless network, such as wireless network 100.

As shown by reference number 602, the UE may detect or experience a link failure, such as RLF or handover failure. A radio link associated with the UE may fail during RLF, which may reduce reliability and/or increase latency for the UE. The handover failure may occur when the UE is not successfully handed over from the source network node to the target network node. When the UE detects or experiences RLF or handover failure, the UE may need to perform a reestablishment.

As shown by reference number 604, the UE may perform, based at least in part on the link failure, LTM and/or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery. During LTM or conditional handover, the UE may receive and/or transmit signaling to detach from the source network node and connect to the target network node. In some cases, LTM may be prioritized over conditional handover. In other cases, conditional handover may be prioritized over LTM. The UE may be configured to select between LTM or conditional handover depending on certain conditions. As a result, the UE may be able to appropriately select to perform LTM or conditional handover depending on the conditions.

In some aspects, the UE may attempt to perform the LTM. The UE may perform the conditional handover based at least in part on the LTM being unsuccessful. The LTM may be attempted to be performed prior to the conditional handover based at least in part on an RRC configuration received from the network node. In some aspects, the UE may attempt to perform the LTM. The UE may perform a legacy layer 3 (L3) reestablishment based at least in part on the LTM being unsuccessful. The LTM may be attempted to be performed prior to the legacy L3 reestablishment based at least in part on the RRC configuration. In some aspects, the UE may attempt to perform the conditional handover. The UE may perform the LTM based at least in part on the conditional handover being unsuccessful. The conditional handover may be attempted to be performed prior to the LTM based at least in part on the RRC configuration received from the network node. In some aspects, the UE may attempt to perform the conditional handover. The UE may perform a legacy L3 reestablishment based at least in part on the conditional handover being unsuccessful. The conditional handover may be attempted to be performed prior to the legacy L3 reestablishment based at least in part on the RRC configuration.

In some aspects, the UE may perform the LTM. The UE may perform a reestablishment by executing the conditional handover based at least in part on a failure associated with the LTM. In some aspects, the UE may perform the conditional handover. The UE may perform a reestablishment by executing the LTM based at least in part on a failure associated with the conditional handover. In some aspects, the UE may perform the LTM. The UE may perform a reestablishment or a recovery using another LTM based at least in part on a failure associated with the LTM. In some aspects, the UE may perform the conditional handover. The UE may perform a reestablishment or a recovery using another conditional handover based at least in part on a failure associated with the conditional handover.

In some aspects, the UE may prioritize conditional handover or LTM based at least in part on a UE implementation. A cell selection may also be based at least in part on the UE implementation. In some aspects, the UE may prioritize conditional handover or LTM based at least in part on a specification, such as a 3GPP specification. When RLF or handover failure occurs, the UE may first perform LTM, and if the LTM is unsuccessful, the UE may then perform conditional handover. Alternatively, when RLF or handover failure occurs, the UE may first perform conditional handover, and if the conditional handover is unsuccessful, the UE may then perform LTM. When RLF or handover failure occurs, the UE may be configured to perform conditional handover or LTM on a per candidate cell basis. The UE may first perform LTM and then conditional handover, or vice versa, based at least in part on an RRC configuration received from the network node.

In some aspects, when an LTM execution fails, the UE may perform a reestablishment by executing conditional handover. On the other hand, when a conditional handover execution fails, the UE may perform the reestablishment by executing LTM. In some aspects, the UE may use one procedure (e.g., conditional handover or LTM), which may be prioritized over the other procedure, and then the UE may reuse the same procedure when the procedure initially fails. For example, when LTM fails, the UE may perform an LTM cell selection and recovery, instead of conditional handover. The UE may reuse LTM without utilizing the other procedure.

In some aspects, the UE may determine the prioritization between conditional handover and LTM (e.g., whether conditional handover should be prioritized over LTM, or vice versa) based at least in part on various conditions. The conditions may be defined via RRC signaling and/or via the specification. The conditions may be associated with a channel quality of a best conditional handover or LTM candidate SpCell, an SCell consideration, an FDD capability of a candidate cell group for conditional handover or LTM, a handover interruption time, a QoS of traffic on a source cell, an AI/ML prediction, a frequency band of a candidate conditional handover or LTM cell group, and/or an intra-central-unit (intra-CU) scenario versus inter-central-unit (inter-CU) scenario.

In some aspects, the prioritization of LTM and conditional handover during failure recovery may be based at least in part on channel qualities of candidate SpCells associated with LTM and channel qualities of candidate SpCells associated with conditional handover. The channel qualities of candidate SpCells associated with LTM and the channel qualities of candidate SpCells associated with conditional handover may be based at least in part on channel qualities of beams and/or numbers of beams having channel qualities that satisfy a threshold.

In some aspects, the UE may determine the prioritization between conditional handover and LTM based at least in part on the channel quality of the best conditional handover or LTM SpCell (e.g., among different cells). The UE may select conditional handover or LTM depending on the best candidate SpCell. For example, when the best candidate SpCell is associated with conditional handover, the UE may prioritize conditional handover over LTM. When the best candidate SpCell is associated with LTM, the UE may prioritize LTM over conditional handover. The UE may select the best candidate SpCell based at least in part on a channel quality of a best beam, in relation to channel qualities of best beams associated with other candidate SpCells. The UE may select the best candidate SpCell based at least in part on a number of beams with sufficiently good channel quality per SpCell candidate. For example, the UE may select the best candidate SpCell when the channel quality is above a specified threshold, or when a delta between a conditional handover candidate SpCell and an LTM candidate SpCell, in terms of channel quality, falls within a certain limit. The UE may select the best candidate SpCell based at least in part on a highest average cell quality, in relation to other candidate SpCells.

In some aspects, the prioritization of LTM and conditional handover during failure recovery may be based at least in part on channel qualities, numbers of SCells, and/or numbers of beams, which may be associated with candidate cell groups configured for LTM and candidate cell groups configured for conditional handover, respectively. In some aspects, the UE may determine the prioritization between conditional handover and LTM based at least in part on the SCell consideration, such as a number of SCells with sufficiently good channel quality that are configured with a given candidate SpCell. The UE may consider, in addition to candidate SpCells, a channel quality, a number of cells, and/or a number of beams of an entire candidate cell group (including SCells) configured for conditional handover or LTM. For example, one candidate SpCell for conditional handover may be associated with two SCells with sufficiently good channel quality, and one candidate SpCell for LTM may be associated with one SCell with sufficiently good channel quality. In this case, the UE may prioritize conditional handover over LTM due to the two SCells versus the one SCell.

In some aspects, the prioritization of LTM and conditional handover during failure recovery may be based at least in part on an FDD capability of a candidate cell group for LTM and an FDD capability of a candidate cell group for conditional handover. In some aspects, the UE may determine the prioritization between conditional handover and LTM based at least in part on the FDD capability of the candidate cell group for conditional handover or LTM. The UE may prioritize a candidate cell group for conditional handover over a candidate cell group for LTM, when the candidate cell group for conditional handover is associated with an FDD capability and the candidate cell group for LTM is not associated with an FDD capability. Alternatively, the UE may prioritize the candidate cell group for LTM over the candidate cell group for conditional handover, when the candidate cell group for LTM is associated with an FDD capability and the candidate cell group for conditional handover is not associated with an FDD capability. The UE may prioritize a candidate cell group having an FDD capability when channel quality is sufficiently good, which may occur when the channel quality is above the certain threshold, or when the delta between the conditional handover candidate SpCell and the LTM candidate SpCell, in terms of channel quality, falls within the certain limit.

In some aspects, the prioritization of LTM and conditional handover during failure recovery may be based at least in part on a handover interruption time. The UE may determine the prioritization between conditional handover and LTM based at least in part on the handover interruption time. The UE may select a handover execution type with a smaller interruption time. For example, LTM may have a smaller interruption time, as compared to conditional handover, when the UE already has a timing of an LTM candidate cell and does not need to perform a RACH on a target cell. The handover interruption time may be considered in conjunction with the channel quality. For example, a lower interruption time approach may be prioritized when a channel quality of an SpCell is sufficiently good, which may be defined in absolute or relative terms.

In some aspects, the prioritization of LTM and conditional handover during failure recovery may be based at least in part on a QoS of traffic on a source cell. The UE may determine the prioritization between conditional handover and LTM based at least in part on the QoS of the traffic on the source cell. For delay sensitive traffic, the handover interruption time may be prioritized, while for data heavy traffic, a throughput on an SpCell candidate cell may be prioritized.

In some aspects, the prioritization of LTM and conditional handover during failure recovery may be based at least in part on an AI/ML prediction of a handover success probability, an expected throughput, and/or a handover interruption time. The UE may determine the prioritization between conditional handover and LTM based at least in part on the AI/ML prediction. For example, the UE may select a handover approach (e.g., condition handover or LTM) which yields a better handover success probability, a higher expected throughput, and/or a smaller interruption time, in relation to the other handover approach.

In some aspects, the prioritization of LTM and conditional handover during failure recovery may be based at least in part on a frequency band of a candidate cell group for LTM and a frequency band of a candidate cell group for conditional handover. The UE may determine the prioritization between conditional handover and LTM based at least in part on the frequency band of the candidate conditional handover or LTM cell group.

In some aspects, the prioritization of LTM and conditional handover during failure recovery may be based at least in part on a presence of an intra-CU scenario or an inter-CU scenario. The UE may determine the prioritization between conditional handover and LTM based at least in part on the intra-CU scenario versus inter-CU scenario. For example, the UE may prioritize LTM for the intra-CU scenario, whereas the UE may prioritize conditional handover for the inter-CU scenario.

In some aspects, the UE may perform one or more LTM recovery attempts and/or one or more conditional handover recovery attempts, which may be based at least in part on multiple recovery attempts being permitted at different cells. The UE may be configured to be capable of the multiple recovery attempts, which may include a combination of LTM recovery attempts and conditional handover recovery attempts.

In legacy conditional handover, a recovery attempt may be performed only once because successive conditional handover was not defined. In some aspects, multiple recovery attempts may be allowed at different cells. Multiple recovery attempts may be allowed for LTM due to the possibility of successive LTM. Multiple recovery attempts may be allowed for conditional handover (e.g., in the order of cells fulfilling an execution condition). In some aspects, the multiple recovery attempts may involve a mixed conditional handover and LTM subsequent recovery. For example, a first cell may be given a higher priority to conditional handover (e.g., the first cell may always be given the higher priority to conditional handover), and subsequent cells may only be associated with LTM. As another example, a recovery may first be performed on LTM candidate cells, and then conditional handover may be performed.

In some aspects, the UE may initially perform LTM or conditional handover based at least in part on the prioritization. The LTM or conditional handover may fail. In this case, the UE may perform an appropriate action. The UE may release a configuration and perform a recovery in a legacy manner (e.g., without LTM or conditional recovery). Alternatively, the UE may perform a recovery using LTM and/or conditional handover, which may be based at least in part on a configuration from the network node.

As indicated above, FIG. 6 is provided as an example. Other examples may differ from what is described with regard to FIG. 6.

FIG. 7 is a diagram illustrating an example process 700 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 700 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with prioritization of LTM and conditional handover during failure recovery.

As shown in FIG. 7, in some aspects, process 700 may include detecting a link failure (block 710). For example, the UE (e.g., using communication manager 806, depicted in FIG. 8) may detect a link failure, as described above.

As further shown in FIG. 7, in some aspects, process 700 may include performing, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery (block 720). For example, the UE (e.g., using communication manager 806, depicted in FIG. 8) may perform, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery, as described above.

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

In a first aspect, the link failure is associated with an RLF or a handover failure.

In a second aspect, alone or in combination with the first aspect, process 700 includes attempting to perform the LTM, and performing the conditional handover based at least in part on the LTM being unsuccessful, wherein the LTM is attempted to be performed prior to the conditional handover based at least in part on an RRC configuration.

In a third aspect, alone or in combination with one or more of the first and second aspects, process 700 includes attempting to perform the LTM; and performing a legacy L3 reestablishment based at least in part on the LTM being unsuccessful, wherein the LTM is attempted to be performed prior to the legacy L3 reestablishment based at least in part on an RRC configuration.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 700 includes attempting to perform the conditional handover, and performing the LTM based at least in part on the conditional handover being unsuccessful, wherein the conditional handover is attempted to be performed prior to the LTM based at least in part on an RRC configuration.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 700 includes attempting to perform the conditional handover; and performing a legacy L3 reestablishment based at least in part on the conditional handover being unsuccessful, wherein the conditional handover is attempted to be performed prior to the legacy L3 reestablishment based at least in part on an RRC configuration.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 700 includes performing the LTM, and performing a reestablishment by executing the conditional handover based at least in part on a failure associated with the LTM.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process 700 includes performing the conditional handover, and performing a reestablishment by executing the LTM based at least in part on a failure associated with the conditional handover.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process 700 includes performing the LTM, and performing a reestablishment or a recovery using another LTM based at least in part on a failure associated with the LTM.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process 700 includes performing the conditional handover, and performing a reestablishment or a recovery using another conditional handover based at least in part on a failure associated with the conditional handover.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the prioritization of LTM and conditional handover during failure recovery is based at least in part on channel qualities of candidate SpCells associated with LTM and channel qualities of candidate SpCells associated with conditional handover.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the channel qualities of candidate SpCells associated with LTM and the channel qualities of candidate SpCells associated with conditional handover are based at least in part on one or more of channel qualities of beams or numbers of beams having channel qualities that satisfy a threshold.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the prioritization of LTM and conditional handover during failure recovery is based at least in part on one or more of channel qualities, numbers of SCells, or numbers of beams, associated with candidate cell groups configured for LTM and candidate cell groups configured for conditional handover.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the prioritization of LTM and conditional handover during failure recovery is based at least in part on an FDD capability of a candidate cell group for LTM and an FDD capability of a candidate cell group for conditional handover.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the prioritization of LTM and conditional handover during failure recovery is based at least in part on a handover interruption time.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the prioritization of LTM and conditional handover during failure recovery is based at least in part on a QoS of traffic on a source cell.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the prioritization of LTM and conditional handover during failure recovery is based at least in part on an AI/ML prediction of one or more of a handover success probability, an expected throughput, or a handover interruption time.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the prioritization of LTM and conditional handover during failure recovery is based at least in part on a frequency band of a candidate cell group for LTM and a frequency band of a candidate cell group for conditional handover.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the prioritization of LTM and conditional handover during failure recovery is based at least in part on a presence of an intra-CU scenario or an inter-CU scenario.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, process 700 includes performing at least one of one or more LTM recovery attempts or one or more conditional handover recovery attempts based at least in part on multiple recovery attempts being permitted at different cells.

Although FIG. 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.

FIG. 8 is a diagram of an example apparatus 800 for wireless communication, in accordance with the present disclosure. The apparatus 800 may be a UE, or a UE may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802, a transmission component 804, and/or a communication manager 806, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager 806 is the communication manager 140 described in connection with FIG. 1. As shown, the apparatus 800 may communicate with another apparatus 808, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 802 and the transmission component 804.

In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with FIG. 6. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 700 of FIG. 7. In some aspects, the apparatus 800 and/or one or more components shown in FIG. 8 may include one or more components of the UE described in connection with FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 8 may be implemented within one or more components described in connection with FIG. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. 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 executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 808. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 800. In some aspects, the reception component 802 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection with FIG. 2.

The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 808. In some aspects, the transmission component 804 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 808. In some aspects, the transmission component 804 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection with FIG. 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in one or more transceivers.

The communication manager 806 may support operations of the reception component 802 and/or the transmission component 804. For example, the communication manager 806 may receive information associated with configuring reception of communications by the reception component 802 and/or transmission of communications by the transmission component 804. Additionally, or alternatively, the communication manager 806 may generate and/or provide control information to the reception component 802 and/or the transmission component 804 to control reception and/or transmission of communications.

The communication manager 806 may detect a link failure. The communication manager 806 may perform, based at least in part on the link failure, one or more of LTM or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery.

The number and arrangement of components shown in FIG. 8 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 8. Furthermore, two or more components shown in FIG. 8 may be implemented within a single component, or a single component shown in FIG. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in FIG. 8 may perform one or more functions described as being performed by another set of components shown in FIG. 8.

The following provides an overview of some Aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: detecting a link failure; and performing, based at least in part on the link failure, one or more of layer 1 or layer 2 triggered mobility (LTM) or conditional handover based at least in part on a prioritization of LTM and conditional handover during failure recovery.

Aspect 2: The method of Aspect 1, wherein the link failure is associated with a radio link failure (RLF) or a handover failure.

Aspect 3: The method of any of Aspects 1-2, wherein performing one or more of LTM or conditional handover further comprises: attempting to perform the LTM; and performing the conditional handover based at least in part on the LTM being unsuccessful, wherein the LTM is attempted to be performed prior to the conditional handover based at least in part on a radio resource control (RRC) configuration.

Aspect 4: The method of any of Aspects 1-3, wherein performing one or more of LTM or conditional handover further comprises: attempting to perform the LTM; and performing a legacy layer 3 (L3) reestablishment based at least in part on the LTM being unsuccessful, wherein the LTM is attempted to be performed prior to the legacy L3 reestablishment based at least in part on a radio resource control (RRC) configuration.

Aspect 5: The method of any of Aspects 1-4, wherein performing one or more of LTM or conditional handover further comprises: attempting to perform the conditional handover; and performing the LTM based at least in part on the conditional handover being unsuccessful, wherein the conditional handover is attempted to be performed prior to the LTM based at least in part on a radio resource control (RRC) configuration.

Aspect 6: The method of any of Aspects 1-5, wherein performing one or more of LTM or conditional handover further comprises: attempting to perform the conditional handover; and performing a legacy layer 3 (L3) reestablishment based at least in part on the conditional handover being unsuccessful, wherein the conditional handover is attempted to be performed prior to the legacy L3 reestablishment based at least in part on a radio resource control (RRC) configuration.

Aspect 7: The method of any of Aspects 1-6, wherein performing one or more of LTM or conditional handover further comprises: performing the LTM; and performing a reestablishment by executing the conditional handover based at least in part on a failure associated with the LTM.

Aspect 8: The method of any of Aspects 1-7, wherein performing one or more of LTM or conditional handover further comprises: performing the conditional handover; and performing a reestablishment by executing the LTM based at least in part on a failure associated with the conditional handover.

Aspect 9: The method of any of Aspects 1-8, wherein performing one or more of LTM or conditional handover further comprises: performing the LTM; and performing a reestablishment or a recovery using another LTM based at least in part on a failure associated with the LTM.

Aspect 10: The method of any of Aspects 1-9, wherein performing one or more of LTM or conditional handover further comprises: performing the conditional handover; and performing a reestablishment or a recovery using another conditional handover based at least in part on a failure associated with the conditional handover.

Aspect 11: The method of any of Aspects 1-10, wherein the prioritization of LTM and conditional handover during failure recovery is based at least in part on channel qualities of candidate special cells (SpCells) associated with LTM and channel qualities of candidate SpCells associated with conditional handover.

Aspect 12: The method of Aspect 11, wherein the channel qualities of candidate SpCells associated with LTM and the channel qualities of candidate SpCells associated with conditional handover are based at least in part on one or more of: channel qualities of beams or numbers of beams having channel qualities that satisfy a threshold.

Aspect 13: The method of any of Aspects 1-12, wherein the prioritization of LTM and conditional handover during failure recovery is based at least in part on one or more of: channel qualities, numbers of secondary cells (SCells), or numbers of beams, associated with candidate cell groups configured for LTM and candidate cell groups configured for conditional handover.

Aspect 14: The method of any of Aspects 1-13, wherein the prioritization of LTM and conditional handover during failure recovery is based at least in part on a frequency division duplex (FDD) capability of a candidate cell group for LTM and an FDD capability of a candidate cell group for conditional handover.

Aspect 15: The method of any of Aspects 1-14, wherein the prioritization of LTM and conditional handover during failure recovery is based at least in part on a handover interruption time.

Aspect 16: The method of any of Aspects 1-15, wherein the prioritization of LTM and conditional handover during failure recovery is based at least in part on a quality of service (QOS) of traffic on a source cell.

Aspect 17: The method of any of Aspects 1-16, wherein the prioritization of LTM and conditional handover during failure recovery is based at least in part on an artificial intelligence or machine learning (AI/ML) prediction of one or more of: a handover success probability, an expected throughput, or a handover interruption time.

Aspect 18: The method of any of Aspects 1-17, wherein the prioritization of LTM and conditional handover during failure recovery is based at least in part on a frequency band of a candidate cell group for LTM and a frequency band of a candidate cell group for conditional handover.

Aspect 19: The method of any of Aspects 1-18, wherein the prioritization of LTM and conditional handover during failure recovery is based at least in part on a presence of an intra-central-unit (intra-CU) scenario or an inter-central-unit (inter-CU) scenario.

Aspect 20: The method of any of Aspects 1-19, wherein performing one or more of LTM or conditional handover further comprises: performing at least one of one or more LTM recovery attempts or one or more conditional handover recovery attempts based at least in part on multiple recovery attempts being permitted at different cells.

Aspect 21: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-20.

Aspect 22: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-20.

Aspect 23: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-20.

Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-20.

Aspect 25: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-20.

Aspect 26: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-20.

Aspect 27: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-20.

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 above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

The hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some aspects, particular processes and methods may be performed by circuitry that is specific to a given function.

As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

Even though particular combinations of features are recited 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 may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).

PRIORITIZATION OF LAYER 1 OR LAYER 2 TRIGGERED MOBILITY AND CONDITIONAL HANDOVER DURING FAILURE RECOVERY

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims