EP4674177A1

EP4674177A1 - Faster handover procedures for reduced capability user equipment

Info

Publication number: EP4674177A1
Application number: EP24714346.4A
Authority: EP
Inventors: Nazmul Islam; Prashant SHARMA; Chun-Hao Hsu; Akshaya MITTAL; Arnab Pal; Sai Srinivas PANDRINKI; Srinivas Pola
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-02-27
Filing date: 2024-02-22
Publication date: 2026-01-07
Also published as: CN120731636A; WO2024182205A1

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a handover command indicating that the UE is to perform a handover procedure to a bandwidth part (BWP) of a target cell. The UE may identify that a first set of synchronization signal block (SSB) measurement metrics associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with the target cell and a third set of SSB measurement metrics associated with the target cell are available for the handover procedure. The UE may select one of the second set of SSB measurement metrics or the third set of SSB measurement metrics and perform the handover procedure using the selected set of SSB measurement metrics. Numerous other aspects are described.

Description

FASTER HANDOVER PROCEDURES FOR

REDUCED CAPABILITY USER EQUIPMENT

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to India Provisional Patent Application No. 202341013207, filed on February 27, 2023, entitled “FASTER HANDOVER PROCEDURES FOR REDUCED CAPABILITY USER EQUIPMENT,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.

FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for faster handover procedures for reduced capability user equipment.

BACKGROUND

[0003] 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).

[0004] 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).

[0005] 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

[0006] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive a handover command indicating that the UE is to perform a handover procedure to a bandwidth part (BWP) associated with a target cell. The one or more processors may be configured to identify that a first set of synchronization signal block (SSB) measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The one or more processors may be configured to select one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure. The one or more processors may be configured to perform the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

[0007] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The one or more processors may be configured to perform, with the UE, the handover procedure to the BWP using a selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure.

[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell. The method may include identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The method may include selecting one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure. The method may include performing the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

[0009] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The method may include performing, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell. The set of instructions, when executed by one or more processors of the UE, may cause the UE to identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The set of instructions, when executed by one or more processors of the UE, may cause the UE to select one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure. The set of instructions, when executed by one or more processors of the UE, may cause the UE to perform the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The set of instructions, when executed by one or more processors of the network node, may cause the network node to perform, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a handover command indicating that the apparatus is to perform a handover procedure to a BWP associated with a target cell. The apparatus may include means for identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The apparatus may include means for selecting one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure. The apparatus may include means for performing the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The apparatus may include means for performing, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure.

[0014] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell. The method may include identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure. The method may include performing the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics.

[0015] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure. The method may include performing, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure.

[0016] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell. The one or more processors may be configured to identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure. The one or more processors may be configured to perform the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics.

[0017] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure. The one or more processors may be configured to perform, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell. The set of instructions, when executed by one or more processors of the UE, may cause the UE to identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure. The set of instructions, when executed by one or more processors of the UE, may cause the UE to perform the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics.

[0019] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure. The set of instructions, when executed by one or more processors of the network node, may cause the network node to perform, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a handover command indicating that the apparatus is to perform a handover procedure to a BWP associated with a target cell. The apparatus may include means for identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure. The apparatus may include means for performing the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure. The apparatus may include means for performing, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure.

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

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

[0024] 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-modulecomponent 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

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

[0026] Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

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

[0028] Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0029] Fig. 4 is a diagram illustrating an example of make-before-break handover, in accordance with the present disclosure.

[0030] Fig. 5 is a diagram illustrating an example of a synchronization signal hierarchy, in accordance with the present disclosure.

[0031] Fig. 6 is a diagram illustrating an example of multiple synchronization signal blocks associated with a target cell, in accordance with the present disclosure.

[0032] Fig. 7 is a diagram illustrating an example associated with faster handover procedures for reduced capability (RedCap) UEs, in accordance with the present disclosure.

[0033] Fig. 8 is a diagram of an example associated with faster handover procedures for RedCap UEs, in accordance with the present disclosure.

[0034] Fig. 9 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0035] Fig. 10 is a diagram illustrating an example process performed, for example, by a network node, in accordance with the present disclosure.

[0036] Fig. 11 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0037] Fig. 12 is a diagram illustrating an example process performed, for example, by a network node, in accordance with the present disclosure.

[0038] Fig. 13 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

[0039] Fig. 14 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure. DETAILED DESCRIPTION

[0040] In some examples, a reduced capability (RedCap) user equipment (UE) and/or an enhanced RedCap (eRedCap) UE (sometimes collectively referred to herein as a RedCap UE for ease of discussion) may be configured with multiple synchronization signal blocks (SSBs), such as for purposes of cell or beam mobility. A RedCap UE may be a UE that is designed to achieve lower cost, reduced complexity, longer battery life, and/or a smaller form factor than a non-RedCap UE (e.g., a UE exhibiting normal capabilities and functionality). For example, in some cases, a RedCap UE may exhibit lower complexity than a non-RedCap UE because a RedCap UE is associated with a maximum bandwidth smaller than that of a non-RedCap UE. In some examples, a RedCap UE may be configured with one cell-defining SSB (CD-SSB) per carrier and/or one or more non-cell-defining SSBs (NCD-SSBs) per carrier for beam mobility and/or cell mobility. In some cases, a network node may transmit a handover command to the RedCap UE, triggering a handover to a target cell. In some examples, the network node may trigger a handover from a current serving cell (sometimes referred to a source cell) to any BWP of a target cell (sometimes referred to an active BWP of the target cell).

[0041] In some examples, the active BWP of the target cell may be associated with a CD- SSB or an NCD-SSB (e.g., the active BWP may encompass a CD-SSB or an NCD-SSB). Moreover, an SSB associated with the active BWP of the target cell may not have been measured by the RedCap UE. For example, a home target cell measurement object (sometimes referred to as a homeTargetCellMO information element (IE)) may not have been configured on the SSB of the active BWP of the target cell. In some other aspects, the RedCap UE may have previously measured the SSB associated with the active BWP of the target cell, but the measurement may have been performed long ago and thus may be stale. For example, the RedCap UE may have measured the SSB more than a time threshold (e.g., more than 2.56 seconds or 5.12 seconds) prior to the cell switch command. In such examples, the RedCap UE may treat the handover procedure as a blind handover and/or attempt a handover acquisition procedure to decode an SSB on the target cell’s BWP to retrieve cell information. This handover procedure introduces delay into the handover procedure and high power consumption at the RedCap UE, and/or may introduce communication errors if the resulting handover procedure takes longer than a handover timeline specified by a wireless communication standard.

[0042] Some techniques and apparatuses described herein enable a RedCap UE to copy SSB measurement metrics associated with a target cell when performing a handover procedure to a BWP encompassing an un-measured SSB, thereby eliminating the need to perform a handover acquisition procedure associated with a blind handover, and otherwise enabling a RedCap UE to perform a handover procedure to an un-measured BWP. In some aspects, if an SSB of a target BWP does not have any measurement metrics available (e.g., if a RedCap UE performed no search and/or measurements associated with a target BWP, and/or a homeTargetCellMO IE was not configured for the BWP), the RedCap UE may identify whether any measurement metrics are available for the same target cell as part of any other configured SSB. In aspects in which measurement metrics of the same target cell are identified on other SSBs (e.g., in aspects in which the same target cell was measured as part of one or more other SSBs not more than a time threshold prior to receiving the handover command), the UE may treat the handover procedure as a known handover procedure and thus skip a handover acquisition procedure completely, such as by copying a master information block (MIB) payload from the other SSB measurement metrics, a cell timing value from the other SSB measurement metrics, a gain state value from the other SSB measurement metrics, and/or cell quality metrics information from the other SSB measurement metrics. By copying information from a measured SSB to an un-measured SSB associated with the target active BWP, the RedCap UE may eliminate the need to perform a handover acquisition procedure and/or decode additional SSBs even though an SSB of the target active BWP is not available. This may reduce latency in a handovertimeline (e.g., may reduce the handovertimeline by approximately 20 ms), save UE battery power and/or reduce power consumption associated with a handover acquisition procedure, and otherwise reduce communication errors between a RedCap UE and a network node, thus resulting in reduced computing, power, and network resource consumption that would otherwise be required to correct communication errors.

[0043] 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. [0044] 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. [0045] 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).

[0046] 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 1 lOd), 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)).

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

[0048] 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).

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

[0050] 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 1 lOd (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.

[0051] 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).

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

[0053] 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. [0054] 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, a drone, 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 Intemet-of-Things (loT) devices, and/or may be implemented as NB-IoT (narrowband loT) 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.

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

[0056] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link 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.

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

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

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

[0060] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell; identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure; and perform the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics. In some other aspects, the communication manager 140 may receive a handover command indicating that the UE is to perform a handover procedure to BWP associated with a target cell; identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; select one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure; and perform the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0061] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure; and perform, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure. In some other aspects, the communication manager 150 may transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; and perform, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

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

[0064] 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., T output 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, fdter, 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.

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

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

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

[0068] 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. 7-14). [0069] 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. 7-14).

[0070] 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 faster handover procedures for reduced capability UEs, 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 900 of Fig. 9, process 1000 of Fig. 10, process 1100 of Fig. 11, process 1200 of Fig. 12, 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 900 of Fig. 9, process 1000 of Fig. 10, process 1100 of Fig. 11, process 1200 of Fig. 12, 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.

[0071] In some aspects, the UE 120 includes means for receiving a handover command indicating that the UE 120 is to perform a handover procedure to a BWP associated with a target cell; means for identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure; and/or means for performing the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics. In some other aspects, the UE 120 includes means for receiving a handover command indicating that the UE 120 is to perform a handover procedure to a BWP associated with a target cell; means for identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; means for selecting one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure; and/or means for performing the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics. The means for the UE 120 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.

[0072] In some aspects, the network node 110 includes means for transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure; and/or means for performing, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure. In some other aspects, the network node 110 includes means for transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; and/or means for performing, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure. The means for the network node 110 to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

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

[0074] 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. [0075] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

[0076] 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).

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

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

[0079] 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 Fl 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.

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

[0081] 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 El 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.

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

[0083] 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. [0084] 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 01 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 02 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 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective 01 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

[0085] 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, Artificial Intelligence/Machine Learning (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 Al interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-realtime 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.

[0086] 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 01 interface) or via creation of RAN management policies (such as Al interface policies).

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

[0088] Fig. 4 is a diagram illustrating an example 400 of make-before-break handover, in accordance with the present disclosure.

[0089] As shown in Fig. 4, a make-before-break (MBB) handover procedure may involve a UE 405, a source network node 410, a target network node 415, a user plane function (UPF) device 420, and an access and mobility management function (AMF) device 425. In some examples, actions described as being performed by a network node may be performed by multiple different network nodes. For example, configuration actions and/or core network communication actions may be performed by a first network node (e.g., a CU or a DU), and radio communication actions may be performed by a second network node (e.g., a DU or an RU). The UE 405 may correspond to the UE 120 described elsewhere herein. The source network node 410 and/or the target network node 415 may correspond to the network node 110 described elsewhere herein. The UPF device 420 and/or the AMF device 425 may correspond to the network controller 130 described elsewhere herein. The UE 405 and the source network node 410 may be connected (e.g., may have an RRC connection) via a serving cell or a source cell, and the UE 405 may undergo a handover to the target network node 415 via a target cell. The UPF device 420 and/or the AMF device 425 may be located within a core network. The source network node 410 and the target network node 415 may be in communication with the core network for mobility support and user plane functions. The MBB handover procedure may include an enhanced MBB (eMBB) handover procedure.

[0090] As shown, the MBB handover procedure may include a handover preparation phase 430, a handover execution phase 435, and a handover completion phase 440. During the handover preparation phase 430, the UE 405 may report measurements that cause the source network node 410 and/or the target network node 415 to prepare for handover and trigger execution of the handover. During the handover execution phase 435, the UE 405 may execute the handover by performing a random access procedure with the target network node 415 and establishing an RRC connection with the target network node 415. During the handover completion phase 440, the source network node 410 may forward stored communications associated with the UE 405 to the target network node 415, and the UE 405 may be released from a connection with the source network node 410.

[0091] As shown by reference number 445, the UE 405 may perform one or more measurements, and may transmit a measurement report to the source network node 410 based at least in part on performing the one or more measurements (e.g., serving cell measurements and/or neighbor cell measurements). The measurement report may indicate, for example, an RSRP parameter, an RSRQ parameter, an RS SI parameter, and/or a signal -to-interference-plus- noise-ratio (SINR) parameter (e.g., for the serving cell and/or one or more neighbor cells). The source network node 410 may use the measurement report to determine whether to trigger a handover to the target network node 415. For example, if one or more measurements satisfy a condition, then the source network node 410 may trigger a handover of the UE 405 to the target network node 415.

[0092] As shown by reference number 450, the source network node 410 and the target network node 415 may communicate with one another to prepare for a handover of the UE 405. As part of the handover preparation, the source network node 410 may transmit a handover request to the target network node 415 to instruct the target network node 415 to prepare for the handover. The source network node 410 may communicate RRC context information associated with the UE 405 and/or configuration information associated with the UE 405 to the target network node 415. The target network node 415 may prepare for the handover by reserving resources for the UE 405. After reserving the resources, the target network node 415 may transmit an acknowledgement (ACK) to the source network node 410 in response to the handover request.

[0093] As shown by reference number 455, the source network node 410 may transmit an RRC reconfiguration message to the UE 405. The RRC reconfiguration message may include a handover command instructing the UE 405 to execute a handover procedure from the source network node 410 to the target network node 415. The handover command may include information associated with the target network node 415, such as a random access channel (RACH) preamble assignment for accessing the target network node 415. Reception of the RRC reconfiguration message, including the handover command, by the UE 405 may trigger the start of the handover execution phase 435.

[0094] As shown by reference number 460, during the handover execution phase 435 of the MBB handover, the UE 405 may execute the handover by performing a random access procedure with the target network node 415 (e.g., including synchronization with the target network node 415) while continuing to communicate with the source network node 410. For example, while the UE 405 is performing the random access procedure with the target network node 415, the UE 405 may transmit uplink data, uplink control information, and/or an uplink reference signal (e.g., a sounding reference signal) to the source network node 410, and/or may receive downlink data, downlink control information, and/or a downlink reference signal from the source network node 410.

[0095] As shown by reference number 465, upon successfully establishing a connection with the target network node 415 (e.g., via a random access procedure), the UE may transmit an RRC reconfiguration completion message to the target network node 415. Reception of the RRC reconfiguration message by the target network node 415 may trigger the start of the handover completion phase 440.

[0096] As shown by reference number 470, the source network node 410 and the target network node 415 may communicate with one another to prepare for release of the connection between the source network node 410 and the UE 405. In some aspects, the target network node 415 may determine that a connection between the source network node 410 and the UE 405 is to be released, such as after receiving the RRC reconfiguration message from the UE 405. In this case, the target network node 415 may transmit a handover connection setup completion message to the source network node 410. The handover connection setup completion message may cause the source network node 410 to stop transmitting data to the UE 405 and/or to stop receiving data from the UE 405. Additionally, or alternatively, the handover connection setup completion message may cause the source network node 410 to forward communications associated with the UE 405 to the target network node 415 and/or to notify the target network node 415 of a status of one or more communications with the UE 405. For example, the source network node 410 may forward, to the target network node 415, buffered downlink communications (e.g., downlink data) for the UE 405 and/or uplink communications (e.g., uplink data) received from the UE 405. Additionally, or alternatively, the source network node 410 may notify the target network node 415 regarding a PDCP status associated with the UE 405 and/or a sequence number to be used for a downlink communication with the UE 405. [0097] As shown by reference number 475, the target network node 415 may transmit an RRC reconfiguration message to the UE 405 to instruct the UE 405 to release the connection with the source network node 410. Upon receiving the instruction to release the connection with the source network node 410, the UE 405 may stop communicating with the source network node 410. For example, the UE 405 may refrain from transmitting uplink communications to the source network node 410 and/or may refrain from monitoring for downlink communications from the source network node 410.

[0098] As shown by reference number 480, the UE may transmit an RRC reconfiguration completion message to the target network node 415 to indicate that the connection between the source network node 410 and the UE 405 is being released or has been released.

[0099] As shown by reference number 485, the target network node 415, the UPF device 420, and/or the AMF device 425 may communicate to switch a user plane path of the UE 405 from the source network node 410 to the target network node 415. Prior to switching the user plane path, downlink communications for the UE 405 may be routed through the core network to the source network node 410. After the user plane path is switched, downlink communications for the UE 405 may be routed through the core network to the target network node 415. Upon completing the switch of the user plane path, the AMF device 425 may transmit an end marker message to the source network node 410 to signal completion of the user plane path switch. As shown by reference number 490, the target network node 415 and the source network node 410 may communicate to release the source network node 410.

[0100] As part of the MBB handover procedure, the UE 405 may maintain simultaneous connections with the source network node 410 and the target network node 415 during a time period 495. The time period 495 may start at the beginning of the handover execution phase 435 (e.g., upon reception by the UE 405 of a handover command from the source network node 410) when the UE 405 performs a random access procedure with the target network node 415. The time period 495 may end upon release of the connection between the UE 405 and the source network node 410 (e.g., upon reception by the UE 405 of an instruction, from the target network node 415, to release the source network node 410). By maintaining simultaneous connections with the source network node 410 and the target network node 415, the handover procedure can be performed with zero or a minimal interruption to communications, thereby reducing latency. [0101] In some aspects, the UE 405 may be configured with one or more SSBs for purposes of beam and/or cell mobility (e.g., for purposes of switching between beams associated with a network node and/or for purposes of switching between network nodes, as described above). Aspects of SSBs are described in more detail below in connection with Fig. 5.

[0102] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.

[0103] Fig. 5 is a diagram illustrating an example 500 of a synchronization signal (SS) hierarchy, in accordance with the present disclosure. As shown in Fig. 5, the SS hierarchy may include an SS burst set 505, which may include multiple SS bursts 510, shown as SS burst 0 through S S burst N- 1 , where A is a maximum number of repetitions of the S S burst 510 that may be transmitted by one or more network nodes. As further shown, each SS burst 510 may include one or more SSBs 515, shown as SSB 0 through SSB M-l, where M is a maximum number of SSBs 515 that can be carried by an SS burst 510. In some aspects, different SSBs 515 may be beam-formed differently (e.g., transmitted using different beams), and may be used for cell search, cell acquisition, beam management, and/or beam selection (e.g., as part of an initial network access procedure). An SS burst set 505 may be periodically transmitted by a wireless node (e.g., a network node 110), such as every X milliseconds, as shown in Fig. 5. In some aspects, an SS burst set 505 may have a fixed or dynamic length, shown as Y milliseconds in Fig. 5. In some cases, an SS burst set 505 or an SS burst 510 may be referred to as a discovery reference signal (DRS) transmission window or an SSB measurement time configuration (SMTC) window.

[0104] In some examples, an SSB 515 may include resources that carry a PSS 520, an SSS 525, and/or a physical broadcast channel (PBCH) 530. In some cases, multiple SSBs 515 are included in an SS burst 510 (e.g., with transmission on different beams), and the PSS 520, the SSS 525, and/or the PBCH 530 may be the same across each SSB 515 of the SS burst 510. In some examples, a single SSB 515 may be included in an SS burst 510. In some cases, the SSB 515 may be at least four symbols (e.g., OFDM symbols) in length, where each symbol carries one or more of the PSS 520 (e.g., occupying one symbol), the SSS 525 (e.g., occupying one symbol), and/or the PBCH 530 (e.g., occupying two symbols). In some examples, an SSB 515 may be referred to as an SS/PBCH block.

[0105] In some cases, the symbols of an SSB 515 are consecutive, as shown in Fig. 5. In some examples, the symbols of an SSB 515 are non-consecutive. Similarly, in some cases, one or more SSBs 515 of the SS burst 510 may be transmitted in consecutive radio resources (e.g., consecutive symbols) during one or more slots. Additionally, or alternatively, one or more SSBs 515 of the SS burst 510 may be transmitted in non-consecutive radio resources. [0106] In some examples, the SS bursts 510 may have a burst period, and the SSBs 515 of the SS burst 510 may be transmitted by a wireless node (e.g., a network node 110) according to the burst period. In this case, the SSBs 515 may be repeated during each SS burst 510. In some cases, the SS burst set 505 may have a burst set periodicity, whereby the SS bursts 510 of the SS burst set 505 are transmitted by the wireless node according to the fixed burst set periodicity. In other words, the SS bursts 510 may be repeated during each SS burst set 505.

[0107] In some examples, an SSB 515 may include an SSB index, which may correspond to a beam used to carry the SSB 515. A UE 120 may monitor for and/or measure SSBs 515 using different receive (Rx) beams during an initial network access procedure and/or a cell search procedure, among other examples. Based at least in part on the monitoring and/or measuring, the UE 120 may indicate one or more SSBs 515 with a best signal parameter (e.g., an RSRP parameter) to a network node 110 (e.g., directly or via one or more other network nodes). The network node 110 and the UE 120 may use the one or more indicated SSBs 515 to select one or more beams to be used for communication between the network node 110 and the UE 120 (e.g., for a RACH procedure). Additionally, or alternatively, the UE 120 may use the SSB 515 and/or the SSB index to determine a cell timing for a cell via which the SSB 515 is received (e.g., a serving cell).

[0108] In some cases, a UE 120 may perform beam and/or cell mobility based on a CD-SSB. In some other cases, a cell may transmit one or more NCD-SSBs. A CD-SSB may be associated with a control resource set (CORESET) indexed as CORESETO, while an NCD-SSB may not be associated with CORESETO (e.g., an NCD-SSB may be associated with a CORESET indexed other than CORESETO). Additionally, or alternatively, a cell may only transmit one CD-SSB in each carrier, and a cell may transmit multiple NCD-SSBs in each carrier.

[0109] In some cases, one or more NCD-SSBs may be transmitted for use by a RedCap UE and/or an eRedCap UE (collectively referred to herein as RedCap UEs for ease of discussion). A RedCap UE may be a UE that is designed to achieve lower cost, reduced complexity, longer battery life, and/or a smaller form factor than a non-RedCap UE (e.g., a UE exhibiting normal capabilities and functionality). For example, in some cases, a RedCap UE may exhibit lower complexity than a non-RedCap UE because a RedCap UE is associated with a maximum bandwidth smaller than that of a non-RedCap UE. In some cases, a maximum bandwidth of a RedCap UE operating in FR1 during and after initial access may be 20 MHz, and/or a maximum bandwidth of a RedCap UE operating in FR2 during and after initial access may be 100 MHz. Moreover, in some cases, a RedCap UE may not support carrier aggregation and/or dual connectivity operation. [0110] Additionally, or alternatively, in some cases, a RedCap UE may exhibit lower complexity than a non-RedCap UE because a RedCap UE is associated with a reduced minimum number of reception branches as compared to a non-RedCap UE. For example, with respect to frequency bands where a non-RedCap UE is required to be equipped with a minimum of two or four reception antenna ports, a RedCap UE may only be required to be equipped with a minimum of one or two reception antenna ports, respectively. Additionally, or alternatively, in some cases, a RedCap UE may exhibit lower complexity than a non-RedCap UE because a RedCap UE may be associated with a lower maximum number of downlink MIMO layers as compared to a non-RedCap UE. For example, in cases in which a RedCap UE is associated with one reception branch, one downlink MIMO layer may be supported, while in cases in which a RedCap UE is associated with two reception branches, two downlink MIMO layers may be supported. Additionally, or alternatively, a RedCap UE may exhibit lower complexity than a non-RedCap UE because a RedCap UE may be associated with a relaxed maximum modulation order. For example, while a non-RedCap UE may be required to support 256 quadrature amplitude modulation (QAM), support of 256 QAM may be optional for a RedCap UE (e.g., a RedCap UE may only be required to support 64 QAM).

[OHl] In some cases, a RedCap UE may be configured with one CD-SSB per carrier and/or one or more NCD-SSBs per carrier for beam mobility and/or cell mobility. The RedCap UE may periodically transmit a measurement report based at least in part on serving and/or neighboring cell measurements, such as the measurement report described above in connection with reference number 445. Based at least in part on the measurement report, a network node may trigger a handover command to the RedCap UE to perform a handover to a target cell, as described above in connection with reference number 455. In some examples, the network node may trigger a handover from a current serving cell (sometimes referred to a source cell) to any BWP of a target cell (sometimes referred to an active BWP of the target cell).

[0112] In some examples, the active BWP of the target cell may be associated with a CD- SSB or an NCD-SSB (e.g., the active BWP may encompass a CD-SSB or an NCD-SSB). Moreover, an SSB associated with the active BWP of the target cell may not have been measured by the RedCap UE. For example, a home target cell measurement object (sometimes referred to as a homeTargetCellMO IE) may not have been configured on the SSB of the active BWP of the target cell. In some other aspects, the RedCap UE may have previously measured the SSB associated with the active BWP of the target cell, but the measurement may have been performed long ago and thus may be stale. For example, the RedCap UE may have measured the SSB more than a time threshold (e.g., more than 2.56 seconds or 5.12 seconds) prior to the cell switch command. In such examples, the RedCap UE may treat the handover procedure as a blind handover. Accordingly, the RedCap UE may attempt a handover acquisition procedure to decode an SSB on the target cell’s BWP to retrieve cell information. Aspects of a RedCap UE performing a blind handover and/or a handover acquisition procedure are described in more detail in connection with Fig. 6.

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

[0114] Fig. 6 is a diagram illustrating an example 600 of multiple SSBs associated with a target cell, in accordance with the present disclosure.

[0115] As shown in Fig. 6, a RedCap UE may be associated with a serving cell 602 (e.g., a source cell) and a target cell 604. Each of the serving cell 602 and the target cell 604 may be associated with multiple BWPs and/or SSBs. For example, the serving cell 602 and the target cell 604 may be associated with two dedicated BWPs, configured as N 1 and N2, in addition to an initial BWP. Each SSB may be associated with a corresponding BWP. For example, the initial BWP of the serving cell 602 and the target cell 604 may be associated with a CD-SSB, and each dedicated BWP (e.g., each of N1 and N2) of the serving cell 602 and the target cell 604 may be associated with a corresponding NCD-SSB.

[0116] In some cases, a network node may trigger a handover procedure to any BWP of the target cell 604. For example, the active target BWP may be N1 encompassing an NCD-SSB, N2 encompassing another NCD-SSB, or the BWP encompassing the CD-SSB. In the example shown in Fig. 6, as indicated by reference number 606, the network node may trigger handover to the active BWP of the target cell 604, which, in this example, is N1 (e.g., one of the two dedicated BWPs associated with an NCD-SSB). If a measurement result is available on the target active BWP (e.g., if the RedCap UE collected SSB measurements based at least in part on the SSB associated with the target active BWP within a time threshold, such as 2.56 seconds or 5.12 seconds), then the serving cell 602 to target cell 604 handover procedure may be considered as a known handover procedure.

[0117] However, as indicated by reference number 608, in some examples a measurement result may not be available on the target active BWP. More particularly, in this example, the RedCap UE may have measured certain SSBs associated with the target cell 604, such as an NCD-SSB associated with another dedicated BWP (e.g., N2) or a CD-SSB associated with an initial BWP of the target cell 604. However, the RedCap UE may not have measured an SSB (e.g., an NCD-SSB) associated with the target active BWP (e.g., Nl) or else has not measured an SSB associated with the target active BWP within a time threshold (e.g., 2.56 seconds or 5.12 seconds).

[0118] In such examples, and as indicated by reference number 610, if a measurement result is not available for the target active BWP (e.g., a current target BWP has no SSB which was measured by the RedCap UE and/or no SSB which was measured within a time threshold prior to the handover command), the RedCap UE may consider the handover procedure a blind handover, and thus may perform a handover acquisition procedure (shown in Fig. 6 as “HO ACQ”). More particularly, as indicated by reference number 612, in this example the handover acquisition procedure is needed to decode an SSB associated with the target active BWP (e.g., Nl) because the RedCap UE does not have a measurement result available for the target active BWP (e.g., the RedCap UE must perform a blind handover procedure to Nl). Accordingly, as indicated by reference number 614, the RedCap UE may attempt to decode SSBs on the target cell’s active BWP (e.g., Nl) to obtain cell information. In some aspects, the handover acquisition procedure may introduce delay into the handover procedure, because the handover acquisition procedure may be relatively lengthy, such as approximately 20 milliseconds (ms). Once the handover acquisition is complete (e.g., once a handover acquisition confirmation (CNF) is received), the RedCap UE may attempt a RACH procedure on the target active BWP and proceed with the handover procedure in a similar manner as described above in connection with Fig 4.

[0119] In some cases, a UE performing a handover procedure may be associated with a handover timeline (sometimes referred to as an interruption time) specified by a wireless communication standard, such as a standard promulgated by the 3GPP. In some examples, the interruption time may be a time between an end of a last transmission time interval (TTI) (e.g., a last slot) containing an RRC command on an old physical downlink shared channel (PDSCH) (e.g., a PDSCH associated with the source and/or serving cell) and the time at which the UE starts transmission of the new PRACH (e.g., the time at which the UE starts transmission of a PRACH on a target cell), excluding any RRC procedure delay. In some cases, a wireless communication standard may specify that, when intra-frequency or inter-frequency handover is commanded by a network node, the interruption time (sometimes referred to as shall be less than In such cases, is the time required to search the target cell when the target cell is not already known when the handover command is received by the UE (e.g., when an SSB associated with the target cell has not previously been measured or has not been measured within a time threshold). If the target cell is known, then = 0 ms. If the target cell is an unknown intra-frequency cell and the target cell Es/Iot > -2 dB, then ms (where is the SMTC periodicity of the target NR cell). If the target cell is an unknown inter-frequency cell and the target cell Es/Iot > -2 dB, then ms. In some examples, regardless of whether discontinuous reception (DRX) is in use by the shall still be based on non-DRX target cell search times. Moreover, is time for fine time tracking and acquiring full timing information of the target cell, with is time for UE processing, which can be up to 20 ms. time for SSB postprocessing, which can be up to 2 ms. And TRJ is the interruption uncertainty in acquiring the first available PRACH occasion in the new cell (e.g., target cell). TRJ can be up to the summation of an S SB to PRACH occasion association period (which may be defined by table 8.1-1 of the Technical Specification (TS) 38.213 promulgated by the 3GPP) and 10 ms.

[0120] In some examples, the above interruption time (e.g., T_interrupt) may apply to RedCap UEs, with some additional time permitted for known inter-frequency handovers. More particularly, in cases in which a RedCap UE performs a measurement on an SSB and handover is commanded to a BWP with an un-measured SSB, the interruption time specified above may apply for the scenario where the measured SSB and the SSB in the target BWP for handover belong to the same target cell (e.g., where the measured SSB and the target SSB for handover of the same target cell are a first NCD-SSB and a second NCD-SSB, respectively; a CD-SSB and an NCD-SSB, respectively; or an NCD-SSB and a CD-SSB, respectively). In some cases, one additional sample (e.g., one additional T_rs and/or one additional period of time equal to the SMTC periodicity of the target NR cell) may be provided for inter-frequency handover.

[0121] In some cases, an additional delay caused by the handover acquisition procedure described above in connection with reference number 614 may lead to increased latency associated with handover procedures and high power consumption at the RedCap UE. Moreover, in some cases, the additional delay caused by the handover acquisition procedure described above in connection with reference number 614 may result in a handover timeline that is longer than the interruption time specified by a wireless communication standard (e.g., specified by a 3GPP standard). In such cases, performing a blind handover to a BWP including an un-measured SSB may result in communication errors or radio link failure (RLF), leading to high computing, power, and network resource consumption for correcting communication errors.

[0122] Some techniques and apparatuses described herein enable a RedCap UE to copy SSB measurement metrics associated with a target cell when performing a handover procedure to a BWP encompassing an un-measured SSB, thereby eliminating the need to perform a handover acquisition procedure associated with a blind handover and otherwise enabling a RedCap UE to perform a handover procedure to an un-measured BWP within an interruption time specified by a wireless communication standard. In some aspects, if an SSB of a target BWP does not have any measurement metrics available (e.g., if a RedCap UE performed no search and/or measurements associated with a target BWP, and/or a homeTargetCellMO IE was not configured for the BWP), the RedCap UE may identify whether any measurement metrics are available for the same target cell as part of any other configured SSB. In aspects in which measurement metrics of same target cell are identified on other SSBs (e.g., in aspects in which the same target cell was measured as part of one or more other SSBs not more than a time threshold prior to receiving the handover command), the UE may treat the handover procedure as a known handover procedure and thus skip a handover acquisition procedure completely, such as by copying an MIB payload from the other SSB measurement metrics, a cell timing value from the other SSB measurement metrics, a gain state value from the other SSB measurement metrics, and/or cell quality metrics information from the other SSB measurement metrics. By copying information from a measured SSB to an un-measured SSB associated with the target active BWP, the RedCap UE may eliminate the need to perform a handover acquisition procedure and/or decode additional SSBs, even though an SSB of the target active BWP is not available. This may reduce latency in a handover timeline (e.g., may reduce the handover timeline by approximately 20 ms), save UE battery power and/or reduce power consumption associated with a handover acquisition procedure, and otherwise reduce communication errors between a RedCap UE and a network node, thus resulting in reduced computing, power, and network resource consumption that would otherwise be required to correct communication errors.

[0123] As indicated above, Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.

[0124] Fig. 7 is a diagram illustrating an example 700 associated with faster handover procedures for RedCap UEs, in accordance with the present disclosure. The example 700 may be associated with communication between a network node 110 and a UE 120 (e.g., a RedCap UE). In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0125] As shown in Fig. 7, a RedCap UE may be associated with a serving cell 702 (e.g., a source cell) and a target cell 704, which may be substantially similar to the serving cell 602 and the target cell 604 described above in connection with Fig 6. In that regard, each of the serving cell 702 and the target cell 704 may be associated with multiple BWPs and/or SSBs. For example, the serving cell 702 and the target cell 704 may be associated with two dedicated BWPs, configured as N1 and N2, in addition to an initial BWP. Each BWP may be associated with a corresponding SSB. For example, the initial BWP of the serving cell 702 and the target cell 704 may be associated with a CD-SSB, and each dedicated BWP (e.g., each of N1 and N2) of the serving cell 702 and the target cell 704 may be associated with a corresponding NCD- SSB.

[0126] In some cases, a network node may trigger a handover procedure to any BWP of the target cell 704. For example, in a similar manner as described above in connection with Fig. 6, the active target BWP may be N1 encompassing an NCD-SSB, N2 encompassing another NCD- SSB, or the BWP encompassing the CD-SSB. In the example shown in Fig. 7, as indicated by reference number 706, the network node may trigger handover to the active BWP of the target cell 704, which, in the example shown in Fig. 7, is N1 (e.g., one of the two dedicated BWPs associated with an NCD-SSB). If a measurement result is available on the target active BWP (e.g., if the RedCap UE collected SSB measurements based at least in part on the SSB associated with the target active BWP within a time threshold, such as 2.56 seconds or 5.12 seconds), then the serving cell 702 to target cell 704 handover procedure may be considered as a known handover procedure.

[0127] However, as described above in connection with Fig. 6 and as indicated by reference number 708, in some examples a measurement result may not be available on the target active BWP. More particularly, in this example, the RedCap UE may have measured certain SSBs associated with the target cell 704, such as an NCD-SSB associated with another dedicated BWP (e.g., N2) or a CD-SSB associated with an initial BWP of the target cell 704. However, the RedCap UE may not have measured an SSB (e.g., an NCD-SSB) associated with the target active BWP (e.g., Nl) or else may not have measured an SSB associated with the target active BWP within a time threshold (e.g., 2.56 seconds or 5.12 seconds).

[0128] In some aspects, and as indicated by reference number 710, if a measurement result is not available for the target active BWP (e.g., if a current target BWP has no SSB which was measured by the RedCap UE and/or no SSB which was measured within a time threshold prior to the handover command), but a measurement result is available for another SSB associated with the target cell, the RedCap UE may consider the handover procedure a known handover (e.g., may skip performing a handover acquisition procedure) but utilizing information from the measurement result associated with the other SSB associated with the target cell. More particularly, as indicated by reference number 712, and unlike the example described above in connection with reference number 612, in this example the handover acquisition procedure is not needed to decode an SSB associated with the target active BWP (e.g., Nl) because the RedCap UE may use a measurement result associated with another SSB associated with the target cell. Accordingly, as indicated by reference number 714, the RedCap UE may reduce latency associated with a handover procedure by approximately 20 ms (e.g., the time it would have taken to perform the handover acquisition procedure). In this regard, the RedCap UE may reduce power consumption otherwise required to perform blind handover procedures and/or may complete handover procedures within an interruption time specified by a wireless communication standard, thereby reducing communication errors and thus conserving power, computing, and network resources otherwise needed to correct communication errors. Aspects of utilizing measured SSBs associated with a target cell for performing a handover procedure to an un-measured BWP of the target cell are described in more detail below in connection with Fig. 8.

[0129] As indicated above, Fig. 7 is provided as an example. Other examples may differ from what is described with respect to Fig. 7.

[0130] Fig. 8 is a diagram of an example 800 associated with faster handover procedures for RedCap UEs, in accordance with the present disclosure. As shown in Fig. 8, a network node 805 (e.g., network node 110, source network node 410, a CU, a DU, and/or an RU) may communicate with a UE 810 (e.g., UE 120, UE 405). In some aspects, the UE 810 may be one of a RedCap UE or an eRedCap UE (shown simply as “RedCap UE” in Fig. 8 for ease of discussion). In some aspects, the network node 805 and the UE 810 may be part of a wireless network (e.g., wireless network 100). The network node 805 and the UE 810 may have established a wireless connection prior to operations shown in Fig. 8. In some aspects, the UE 810 may be associated with a reduced bandwidth as compared to a non-RedCap UE and/or may be configured to communicate using a BWP of a component carrier, as described above in connection with Fig. 5.

[0131] As shown by reference number 815, the network node 805 may transmit, and the UE 810 may receive, configuration information. In some aspects, the UE 810 may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and/or downlink control information (DCI), among other examples. In some aspects, the configuration information may include an indication of one or more configuration parameters (e.g., already known to the UE 810 and/or previously indicated by the network node 805 or other network device) for selection by the UE 810, and/or explicit configuration information for the UE 810 to use to configure the UE 810, among other examples.

[0132] In some aspects, the configuration may include a configuration of one or more SSBs associated with a target cell (e.g., the target cell associated with the target network node 415 described above in connection with Fig. 4). For example, as described above in connection with Fig. 7, the configuration information may configure a CD-SSB and/or one or more NCD-SSBs. In some aspects, one or more SSBs may be associated with a BWP of the target cell. For example, as described above in connection with Fig. 7, the CD-SSB may be associated with an initial BWP of the target cell, a first NCD-SSB may be associated with a first dedicated BWP of the target cell (e.g., Nl), a second NCD-SSB may be associated with a second dedicated BWP of the target cell (e.g., N2), and so forth.

[0133] In some aspects, the configuration information may configure the UE 810 with one or more SSB measurement objects (e.g., one or more homeTargetCellMO IES). In that regard, the configuration information may indicate which of multiple SSBs are to be measured by the UE 810. In some aspects, the UE 810 may be configured to measure less than all of the SSBs associated with a target cell. For example, as described above in connection with reference number 708, in some aspects the UE 810 may be configured to measure a CD-SSB associated with an initial BWP of the target cell and a second NCD-SSB associated with a second dedicated BWP of the target cell (e.g., N2), but the UE 810 may not be configured to measure a first NCD-SSB associated with a first dedicated BWP of the target cell (e.g., Nl). The configuration information may include additional parameters, such as additional information associated with performing a handover procedure. [0134] The UE 810 may configure itself based at least in part on the configuration information. In some aspects, the UE 810 may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0135] As shown by reference number 820, the UE 810 may measure one or more SSBs associated with the target cell. For example, the UE 810 may measure one or more SSBs configured via the configuration information described above in connection with reference number 815, such as by measuring one or more SSBs configured with an SSB measurement object (e.g., configured via a corresponding homeTargetCellMO IE). Moreover, as shown by reference number 825, the UE 810 may periodically transmit, and the network node 805 may periodically receive, a measurement report reporting various measurements associated with a source cell and/or neighboring cells, such as the target cell, which may be substantially similar to the measurement report described above in connection with reference number 445. For example, the measurement report may indicate an RSRP parameter, an RSRQ parameter, an RSSI parameter, and/or an SINR parameter (e.g., for the serving cell and/or one or more neighbor cells). The network node 805 may use the measurement report to determine whether to trigger a handover to the target cell. For example, if one or more measurements satisfy a condition, then the network node 805 may trigger a handover of the UE 810 to the target cell. [0136] More particularly, as indicated by reference number 830, the network node 805 may transmit, and the UE 810 may receive, a handover command indicating that the UE 810 is to perform a handover procedure to a BWP associated with a target cell. In some aspects, the network node 805 may transmit the handover command via an RRC message, such as the RRC message described above in connection with reference number 455. In some aspects, the handover command, which may indicate the BWP of the target cell and/or a corresponding SSB, may be indicated via a reconfiguration without synchronization IE (sometimes referred to as a ReconfigurationWithinSync IE). The handover command may indicate that the UE 810 is to perform a handover procedure to a BWP (e.g., an active BWP) associated with the target cell. Moreover, in some aspects, the BWP may not encompass an SSB previously measured by the UE 810 in connection with the operations described above in connection with reference number 820. For example, as described above in connection with reference number 708, the active BWP may be a BWP that encompasses an SSB (e.g., an NCD-SSB) that was not previously measured by the UE 810 (e.g., which was not configured to be measured by a homeTargetCellMO IE) and/or the active BWP may be a BWP that does not otherwise encompass an SSB. In this regard, under legacy procedures, the UE 810 would be required to treat the handover as a blind handover and thereby perform a handover acquisition procedure, as described above in connection with reference numbers 612 and 614.

[0137] However, in some aspects, the UE 810 may copy information from a measured SSB associated with the target cell when performing a handover procedure to an un-measured BWP, thereby treating the handover procedure as a known handover procedure and thus reducing or eliminating latency associated with performing a handover acquisition procedure, as described above in connection with reference numbers 710, 712, and 714. More particularly, as indicated by reference number 835, the UE 810 may identify that, although no SSB measurement metrics associated with the active target BWP are available for the handover procedure, SSB measurement metrics associated with the target cell (e.g., SSB measurements associated with other BWPs associated with the target cell and/or associated with SSBs transmitted by the target cell) are available for the handover procedure. Put another way, in some aspects the UE 810 may identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, but that one or more sets of SSB measurement metrics (e.g., a second set of SSB measurement metrics associated with a second SSB associated with the target cell, a third set of SSB measurement metrics associated with a third SSB associated with the target cell, and so forth) are available for the handover procedure. For example, as indicated by reference number 835, in some aspects the UE 810 may identify that a second set of SSB measurement metrics associated with the target cell and a third set of SSB measurement metrics associated with the target cell are available, among other examples. In some aspects, an SSB may be associated with a BWP if the BWP encompasses the SSB, while, in some other aspects (and depending on UE capability), an SSB may be associated with a BWP even though the SSB may lie outside of the BWP (e.g., some UEs may not require an SSB to be within an active BWP in order to be associated with the BWP). Moreover, in some aspects, the sets of SSB measurement metrics available for the handover procedure may correspond to SSBs configured as parts of measurement objects of the source cell prior to handover. For example, the second SSB, the third SSB, and so forth may have been configured as parts of measurement objects of the source cell prior to handover.

[0138] In some aspects, the UE 810 may identify whether SSB measurement metrics are available for the handover procedure based at least in part on whether the UE 810 measured a corresponding SSB within a time threshold prior to receiving the handover command, such as the time threshold shown by reference number 840. Put another way, identifying that the first set of SSB measurement metrics is not available for the handover procedure may be based at least in part on the UE 810 not measuring the first SSB within the time threshold, and/or identifying that the second set of SSB measurement metrics and/or the third set of SSB measurement metrics is available for the handover procedure may be based at least in part on the UE 810 measuring the second SSB and/or the third SSB within the time threshold. In some aspects, the time threshold may be equal to approximately 5 seconds. For example, the time threshold may be equal to 5.12 seconds. In some other aspects, the time threshold may be equal to another value, such as 2.56 seconds or another time value. In some aspects, the time threshold may be indicated to the UE 810 by the network node 805 or another network device. For example, the time threshold may be indicated to the UE 810 via the configuration information described above in connection with reference number 815, via an RRC message, via a MAC-CE, and/or via DCL In some other aspects, the UE 810 may be preconfigured, hard- coded, and/or specified with the time threshold.

[0139] As indicated by reference number 845, the UE 810 may select a set of SSB measurement metrics, from the one or more sets of SSB measurement metrics available for the handover procedure, that is to be used for the handover procedure. For example, in aspects in which no measurement metrics associated with the active BWP of the target cell are available for the handover procedure (e.g., the first set of SSB measurement metrics is not available) but at least two other sets of measurement metrics are available for the handover procedure (e.g., the second and third sets of SSB measurement metrics are available), the UE 810 may select one of the other sets of measurement metrics to be used for the handover procedure. Put another way, as shown by reference number 845, the UE 810 may select one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure.

[0140] In some aspects, the UE 810 may check for the most recent SSB, of the configured SSBs, that was detected for the target cell, and utilize a set of measurement metrics associated with the last detected SSB (e.g., the UE 810 may choose the SSB associated with the most recent measurement of target cell). For example, in aspects in which both the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure, the UE 810 may identify that the second set of SSB measurement metrics is to be used for the handover procedure based at least in part on the second set of SSB measurement metrics being collected by the UE 810 more recently than the third set of SSB measurement metrics.

[0141] In some other aspects, the UE 810 may choose a set of measurement metrics to utilize for the handover procedure based at least in part on corresponding cell quality metrics associated with each set of measurement metrics. For example, in aspects in which both the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure, with the second set of SSB measurement metrics including a first cell quality metric and the third set of SSB measurement metrics including a second cell quality metric, the UE 810 may identify that the second set of SSB measurement metrics is to be used for the handover procedure based at least in part on at least one of the first cell quality metric or the second cell quality metric. In some aspects, the UE 810 may be configured, pre-configured, hard-coded, and/or specified with a cell quality threshold (e.g., an RSRP and/or RSRQ threshold of X decibel-milliwatts (dBm)), and the UE 810 may identify that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on one of the first cell quality metric or the second cell quality metric satisfying the cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0142] For example, in aspects in which the UE 810 needs to transmit an initial RACH message to the target cell with a relatively low power, such as for purposes of avoiding interference to other communications in the same frequency, the UE 810 may select a set of SSB measurement metrics associated with a cell quality metric that is greater than the cell quality threshold (e.g., that is higher than % dBm). In aspects in which the UE 810 needs to transmit an initial RACH message to the target cell with a relatively high power, such as for purposes of meeting a RACH link budget, the UE 810 may select a set of SSB measurement metrics associated with a cell quality metric that is less than the cell quality threshold (e.g., that is lower than X dBm).

[0143] In some aspects, the UE 810 may filter (e.g., average) measurement metrics associated with multiple SSBs, such as when cell quality metrics associated with multiple SSBs satisfy the cell quality threshold (e.g.. A dBm). For example, in aspects in which the UE 810 identifies that the first cell quality metric and the second cell quality metric both satisfy the cell quality threshold, the UE 810 may filter (e.g., average) the first cell quality metric and the second cell quality metric for purposes of performing the handover procedure.

[0144] In some other aspects, the UE 810 may choose a set of measurement metrics to utilize for the handover procedure based at least in part on a corresponding SSB being near to an SSB associated with the target BWP. For example, in aspects in which both the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure, the UE 810 may identify that the second set of SSB measurement metrics is to be used for the handover procedure based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0145] In some other aspects, the UE 810 may choose a set of measurement metrics to utilize for the handover procedure based at least in part on a corresponding SSB being transmitted in a same frequency band as an SSB associated with the target BWP. For example, the network node 805 or other network device may indicate to the UE 810 a corresponding frequency band associated with each configured SSB measurement object, such as via a corresponding frequency band indicator IE (sometimes referred to as a freqBandlndicatorNR IE). In aspects in which multiple sets of SSB measurement metrics are available for the handover procedure, the UE 810 may check if any of the corresponding SSBs fall in a different frequency band as the SSB associated with the active BWP and, if so, the UE 810 may refrain from utilizing the measurement metrics associated with SSBs falling within the different frequency band. Put another way, in aspects in which both the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure, the UE 810 may identify that the second set of SSB measurement metrics is to be used for the handover procedure based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0146] In some other aspects, the UE 810 may utilize measurement metrics associated with an SSB that becomes known as a CD-SSB of the target cell during handover. Put another way, in aspects in which both the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure, the UE 810 may identify that the second set of SSB measurement metrics is to be used for the handover procedure based at least in part on the second SSB being associated with a CD-SSB associated with the target cell during the handover procedure. In this way, if a measured SSB gets known as a CD-SSB of target cell during handover, the UE 810 may ensure that the measured SSB corresponding to the CD-SSB and the SSB of the active BWP of the target cell belong to the same component carrier.

[0147] In some aspects, an SSB may get known as a CD-SSB of a target cell during handover via the network (e.g., via the network node 805 or another network device) explicitly configuring the UE 810 with a CD-SSB of the target cell, such as via a frequency information downlink IE (sometimes referred to as frequencylnfoDL IE) of the target cell during handover, which may be aligned with a previously measured SSB (e.g., the second SSB or the third SSB in the above described example). In some other aspects, the network may not explicitly configure the UE 810 with a CD-SSB (e.g., the network may not configure the UE 810 with a CD-SSB via the frequencylnfoDL IE), but the UE 810 may identify that the target cell’s CD-SSB is aligned with the source cell’s CD-SSB, which may be aligned with a previously measured SSB (e.g., the second SSB or the third SSB in the above described example). In some aspects, the UE 810 may prioritize measurement metrics of the SSB that becomes known as the CD-SSB of the target cell during handover.

[0148] As shown by reference number 850, the UE 810 may perform the handover procedure to the un-measured BWP (e.g., the active BWP for which an SSB measurement result is not available) based at least in part on measurement results from another SSB associated with the target cell (e.g., measurement results of an SSB not encompassed by the BWP). More particularly, returning to the above example in which the UE 810 identifies that the first set of SSB measurement metrics associated with the first SSB associated with the BWP is not available for the handover procedure, but that the second set of SSB measurement metrics associated with the second SSB associated with the target cell is available for the handover procedure and that the third set of SSB measurement metrics associated with the third SSB associated with the target cell is available for the handover procedure, the UE 810 may perform the handover procedure to the BWP using the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics. In this regard, and as described above in connection with reference numbers 712 and 714, in some aspects, performing the handover procedure to the BWP may include skipping a handover acquisition procedure associated with the BWP, even though no measurement results are available for the BWP. Instead, the UE 810 may copy certain metrics from the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics for use in performing the handover procedure to the BWP. For example, performing the handover procedure to the BWP may include utilizing, from the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, an MIB payload, a cell timing value, a gain state value, and/or cell quality information (e.g., one or more of SS-RSRP, SS-RSRQ, layer 1 (Ll)-RSRP, or similar information). Put another way, the UE 810 may utilize measurement metrics of a measured SSB associated with the target cell when performing a handover procedure to an un-measured BWP of the target cell to set the UE 810’s low noise amplifier (LNA) gain state and/or RSRP setting based on the measurement metrics, to detect the target cell and adjust the UE 810’s timing and frequency based on the target cell, and/or to transmit RACH to the target cell.

[0149] Based at least in part on the UE 810 utilizing measurement metrics of a measured SSB associated with a target cell when performing a handover procedure to an un-measured BWP of the target cell, the UE 810 and/or the network node 805 may conserve computing, power, network, and/or communication resources that may have otherwise been consumed by the UE 810 performing a blind handover procedure. For example, based at least in part on the UE 810 utilizing measurement metrics of a measured SSB associated with a target cell when performing a handover procedure to an un-measured BWP of the target cell, the UE 810 and the network node 805 may communicate with reduced latency and/or with a reduced error rate, which may conserve computing, power, network, and/or communication resources that may have otherwise been consumed to perform legacy handover procedures, detect and/or correct communication errors, and/or reestablish a connection following RLF.

[0150] As indicated above, Fig. 8 is provided as an example. Other examples may differ from what is described with respect to Fig. 8.

[0151] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a UE, in accordance with the present disclosure. Example process 900 is an example where the UE (e.g., UE 810) performs operations associated with faster handover procedures for RedCap UEs.

[0152] As shown in Fig. 9, in some aspects, process 900 may include receiving a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell (block 910). For example, the UE (e.g., using reception component 1302 and/or communication manager 1306, depicted in Fig. 13) may receive a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, as described above. [0153] As further shown in Fig. 9, in some aspects, process 900 may include identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure (block 920). For example, the UE (e.g., using communication manager 1306, depicted in Fig. 13) may identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure, as described above.

[0154] As further shown in Fig. 9, in some aspects, process 900 may include performing the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics (block 930). For example, the UE (e.g., using communication manager 1306, depicted in Fig. 13) may perform the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics, as described above.

[0155] Process 900 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.

[0156] In a first aspect, identifying that the first set of SSB measurement metrics is not available for the handover procedure is based at least in part on the UE not measuring the first SSB within a time threshold, and identifying that the second set of SSB measurement metrics is available for the handover procedure is based at least in part on the UE measuring the second SSB within the time threshold.

[0157] In a second aspect, alone or in combination with the first aspect, performing the handover procedure to the BWP includes skipping a handover acquisition procedure associated with the BWP.

[0158] In a third aspect, alone or in combination with one or more of the first and second aspects, performing the handover procedure to the BWP includes utilizing, from the second set of SSB measurement metrics, at least one of a master information block payload, a cell timing value, a gain state value, or celling quality information.

[0159] In a fourth aspect, alone or in combination with one or more of the first through third aspects, at least one of: the first set of SSB measurement metrics is associated with only one SSB, or the second set of measurement metrics is associated with only one SSB.

[0160] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the UE is one of a reduced capability UE or an enhanced reduced capability UE. [0161] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, at least one of: the first SSB is one of a cell-defining S SB or a non-cell-defining SSB, or the second SSB is one of the cell-defining SSB or the non-cell-defining SSB.

[0162] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process 900 includes identifying that a third set of SSB measurement metrics associated with a third SSB associated with the target cell is available for the handover procedure, and identifying that the second set of SSB measurement metrics is to be used for the handover procedure.

[0163] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

[0164] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the second set of SSB measurement metrics includes a first cell quality metric, the third set of SSB measurement metrics includes a second cell quality metric, and identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on at least one of the first cell quality metric or the second cell quality metric.

[0165] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0166] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 900 includes identifying that the first cell quality metric and the second cell quality metric satisfy a cell quality threshold, and performing the handover procedure based at least in part filtering the first cell quality metric and the second cell quality metric.

[0167] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0168] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0169] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part the second SSB being associated with a celldefining SSB associated with the target cell during the handover procedure.

[0170] Although Fig. 9 shows example blocks of process 900, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0171] Fig. 10 is a diagram illustrating an example process 1000 performed, for example, by a network node, in accordance with the present disclosure. Example process 1000 is an example where the network node (e.g., network node 805) performs operations associated with faster handover procedures for RedCap UEs.

[0172] As shown in Fig. 10, in some aspects, process 1000 may include transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure (block 1010). For example, the network node (e.g., using transmission component 1404 and/or communication manager 1406, depicted in Fig. 14) may transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, as described above.

[0173] As further shown in Fig. 10, in some aspects, process 1000 may include performing, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure (block 1020). For example, the network node (e.g., using communication manager 1406, depicted in Fig. 14) may perform, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics associated with a second SSB, associated with the target cell, being available for the handover procedure, as described above.

[0174] Process 1000 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.

[0175] In a first aspect, the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not being configured to measure the first SSB within a time threshold, and the second set of SSB measurement metrics is available for the handover procedure based at least in part on the UE being configured to measure the second SSB within the time threshold. [0176] In a second aspect, alone or in combination with the first aspect, performing the handover procedure to the BWP includes skipping a handover acquisition procedure associated with the BWP.

[0177] In a third aspect, alone or in combination with one or more of the first and second aspects, performing the handover procedure to the BWP is based at least in part on at least one of a master information block payload associated with the second set of SSB measurement metrics, a cell timing value associated with the second set of SSB measurement metrics, a gain state value associated with the second set of SSB measurement metrics, or celling quality information associated with the second set of SSB measurement metrics.

[0178] In a fourth aspect, alone or in combination with one or more of the first through third aspects, at least one of: the first set of SSB measurement metrics is associated with only one SSB, or the second set of measurement metrics is associated with only one SSB.

[0179] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the UE is one of a reduced capability UE or an enhanced reduced capability UE.

[0180] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, at least one of: the first SSB is one of a cell-defining SSB or a non-cell-defining SSB, or the second SSB is one of the cell-defining SSB or the non-cell-defining SSB.

[0181] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, a third set of SSB measurement metrics associated with a third SSB associated with the target cell is available for the handover procedure, and performing the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics is further based at least in part on an identification that the second set of SSB measurement metrics is to be used for the handover procedure.

[0182] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics. [0183] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the second set of SSB measurement metrics includes a first cell quality metric, the third set of SSB measurement metrics includes a second cell quality metric, and the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on at least one of the first cell quality metric or the second cell quality metric.

[0184] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0185] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the first cell quality metric and the second cell quality metric satisfy a cell quality threshold, and performing the handover procedure is further based at least in part on a filtering of the first cell quality metric and the second cell quality metric.

[0186] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0187] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0188] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being associated with a cell-defining SSB associated with the target cell during the handover procedure.

[0189] Although Fig. 10 shows example blocks of process 1000, in some aspects, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0190] Fig. 11 is a diagram illustrating an example process 1100 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 1100 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with faster handover procedures for RedCap UEs.

[0191] As shown in Fig. 11, in some aspects, process 1100 may include receiving a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell (block 1110). For example, the UE (e.g., using reception component 1302 and/or communication manager 1306, depicted in Fig. 13) may receive a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, as described above.

[0192] As further shown in Fig. 11, in some aspects, process 1100 may include identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure (block 1120). For example, the UE (e.g., using communication manager 1306, depicted in Fig. 13) may identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure, as described above.

[0193] As further shown in Fig. 11, in some aspects, process 1100 may include selecting one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure (block 1130). For example, the UE (e.g., using communication manager 1306, depicted in Fig. 13) may select one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure, as described above.

[0194] As further shown in Fig. 11, in some aspects, process 1100 may include performing the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics (block 1140). For example, the UE (e.g., using communication manager 1306, depicted in Fig. 13) may perform the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, as described above.

[0195] Process 1100 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.

[0196] In a first aspect, process 1100 may include identifying that the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not measuring the first SSB within a time threshold, and identifying that the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure based at least in part on the UE measuring the second SSB and the third SSB within the time threshold.

[0197] In a second aspect, alone or in combination with the first aspect, the UE of claim 1, process 1100 may include, when performing the handover procedure to the BWP, omitting decoding the first SSB as part of the handover procedure.

[0198] In a third aspect, alone or in combination with the first through second aspects, process 1100 may include, when performing the handover procedure to the BWP, utilizing, from the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, at least one of a master information block payload, a cell timing value, a gain state value, or cell quality information. [0199] In a fourth aspect, alone or in combination with the first through third aspects, at least one of the first set of SSB measurement metrics is associated with only one SSB, the second set of SSB measurement metrics is associated with only one SSB, or the third set of SSB measurement metrics is associated with only one SSB.

[0200] In a fifth aspect, alone or in combination with the first through fourth aspects, the UE is one of a reduced capability UE or an enhanced reduced capability UE.

[0201] In a sixth aspect, alone or in combination with the first through fifth aspects, at least one of the first SSB is one of a cell-defining SSB or a non-cell-defining SSB, the second SSB is one of the cell -defining SSB or the non-cell-defining SSB, or the third SSB is one of the celldefining SSB or the non-cell-defining SSB.

[0202] In a seventh aspect, alone or in combination with the first through sixth aspects, process 1100 may include selecting the second set of SSB measurement metrics to be used for the handover procedure, and performing the handover procedure to the BWP using the second set of SSB measurement metrics.

[0203] In an eighth aspect, alone or in combination with the first through seventh aspects, process 1100 may include, when selecting the second set of SSB measurement metrics to be used for the handover procedure, selecting the second set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

[0204] In a ninth aspect, alone or in combination with the first through eighth aspects, the second set of SSB measurement metrics includes a first cell quality metric, the third set of SSB measurement metrics includes a second cell quality metric, and process 1100 may include, when selecting the second set of SSB measurement metrics to be used for the handover procedure, selecting the second set of SSB measurement metrics based at least in part on at least one of the first cell quality metric or the second cell quality metric.

[0205] In a tenth aspect, alone or in combination with the first through ninth aspects, process 1100 may include, when selecting the second set of SSB measurement metrics to be used for the handover procedure, selecting the second set of SSB measurement metrics based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0206] In an eleventh aspect, alone or in combination with the first through tenth aspects, process 110 may include identifying that the first cell quality metric and the second cell quality metric satisfy a cell quality threshold, and performing the handover procedure based at least in part filtering the first cell quality metric and the second cell quality metric. [0207] In a twelfth aspect, alone or in combination with the first through eleventh aspects, process 1100 may include, when selecting the second set of SSB measurement metrics to be used for the handover procedure, selecting the second set of SSB measurement metrics based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0208] In a thirteenth aspect, alone or in combination with the first through twelfth aspects, process 1100 may include, when selecting the second set of SSB measurement metrics to be used for the handover procedure, selecting the second set of SSB measurement metrics based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0209] In a fourteenth aspect, alone or in combination with the first through thirteenth aspects, process 1100 may include, when selecting the second set of SSB measurement metrics to be used for the handover procedure, selecting the second set of SSB measurement metrics based at least in part the second SSB being associated with a cell-defining SSB associated with the target cell during the handover procedure.

[0210] Although Fig. i l shows example blocks of process 1100, in some aspects, process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0211] Fig. 12 is a diagram illustrating an example process 1200 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process 1200 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with faster handover procedures for RedCap UEs. [0212] As shown in Fig. 12, in some aspects, process 1200 may include transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure (block 1210). For example, the network node (e.g., using transmission component 1404 and/or communication manager 1406, depicted in Fig. 14) may transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure, as described above.

[0213] As further shown in Fig. 12, in some aspects, process 1200 may include performing, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure (block 1220). For example, the network node (e.g., using communication manager 1406, depicted in Fig. 14) may perform, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure, as described above.

[0214] Process 1200 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.

[0215] In a first aspect, the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not being configured to measure the first SSB within a time threshold, and the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure based at least in part on the UE being configured to measure the second SSB and the third SSB within the time threshold.

[0216] In a second aspect, alone or in combination with the first aspect, process 1200 may include, when performing the handover procedure to the BWP, performing the handover procedure to the BWP based at least in part on at least one of a master information block payload associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, a cell timing value associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, a gain state value associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, or cell quality information associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

[0217] In a third aspect, alone or in combination with the first through second aspects, process 1200 may include, when performing the handover procedure to the BWP, performing the handover procedure based at least in part on a selection of the second set of SSB measurement metrics to be used for the handover procedure.

[0218] In a fourth aspect, alone or in combination with the first through third aspects, the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

[0219] In a fifth aspect, alone or in combination with the first through fourth aspects, the second set of SSB measurement metrics includes a first cell quality metric, the third set of SSB measurement metrics includes a second cell quality metric, and the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on at least one of the first cell quality metric or the second cell quality metric.

[0220] In a sixth aspect, alone or in combination with the first through fifth aspects, the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0221] In a seventh aspect, alone or in combination with the first through sixth aspects, the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0222] In an eighth aspect, alone or in combination with the first through seventh aspects, the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0223] In a ninth aspect, alone or in combination with the first through eighth aspects, the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being associated with a cell-defining SSB associated with the target cell during the handover procedure.

[0224] Although Fig. 12 shows example blocks of process 1200, in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0225] Fig. 13 is a diagram of an example apparatus 1300 for wireless communication, in accordance with the present disclosure. The apparatus 1300 may be a UE, or a UE may include the apparatus 1300. In some aspects, the apparatus 1300 includes a reception component 1302, a transmission component 1304, and/or a communication manager 1306, 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 1306 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 1300 may communicate with another apparatus 1308, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1302 and the transmission component 1304.

[0226] In some aspects, the apparatus 1300 may be configured to perform one or more operations described herein in connection with Figs. 7-8. Additionally, or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as process 900 of Fig. 9 and/or process 1100 of Fig. 11. In some aspects, the apparatus 1300 and/or one or more components shown in Fig. 13 may include one or more components of the UE 120 described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 13 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 a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0227] The reception component 1302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1308. The reception component 1302 may provide received communications to one or more other components of the apparatus 1300. In some aspects, the reception component 1302 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 1300. In some aspects, the reception component 1302 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE 120 described in connection with Fig. 2.

[0228] The transmission component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1308. In some aspects, one or more other components of the apparatus 1300 may generate communications and may provide the generated communications to the transmission component 1304 for transmission to the apparatus 1308. In some aspects, the transmission component 1304 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 1308. In some aspects, the transmission component 1304 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE 120 described in connection with Fig. 2. In some aspects, the transmission component 1304 may be co-located with the reception component 1302 in a transceiver.

[0229] The communication manager 1306 may support operations of the reception component 1302 and/or the transmission component 1304. For example, the communication manager 1306 may receive information associated with configuring reception of communications by the reception component 1302 and/or transmission of communications by the transmission component 1304. Additionally, or alternatively, the communication manager 1306 may generate and/or provide control information to the reception component 1302 and/or the transmission component 1304 to control reception and/or transmission of communications. [0230] The reception component 1302 may receive a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell. The communication manager 1306 may identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure. The communication manager 1306 may perform the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics.

[0231] The communication manager 1306 may identify that a third set of SSB measurement metrics associated with a third SSB associated with the target cell is available for the handover procedure.

[0232] The communication manager 1306 may identify that the second set of SSB measurement metrics is to be used for the handover procedure.

[0233] The communication manager 1306 may identify that the first cell quality metric and the second cell quality metric satisfy a cell quality threshold.

[0234] The communication manager 1306 may perform the handover procedure based at least in part filtering the first cell quality metric and the second cell quality metric.

[0235] The communication manager 1306 may identify that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The communication manager 1306 may select one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure. The communication manager 1306 may perform the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics. [0236] The communication manager 1306 may identify that the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not measuring the first SSB within a time threshold. The communication manager 1306 may identify that the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure based at least in part on the UE measuring the second SSB and the third SSB within the time threshold.

[0237] The communication manager 1306 may select the second set of SSB measurement metrics to be used for the handover procedure. The communication manager 1306 may perform the handover procedure to the BWP using the second set of SSB measurement metrics.

[0238] The communication manager 1306 may identify that the first cell quality metric and the second cell quality metric satisfy a cell quality threshold. The communication manager 1306 may perform the handover procedure based at least in part filtering the first cell quality metric and the second cell quality metric.

[0239] The number and arrangement of components shown in Fig. 13 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. 13. Furthermore, two or more components shown in Fig. 13 may be implemented within a single component, or a single component shown in Fig. 13 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 13 may perform one or more functions described as being performed by another set of components shown in Fig. 13.

[0240] Fig. 14 is a diagram of an example apparatus 1400 for wireless communication, in accordance with the present disclosure. The apparatus 1400 may be a network node, or a network node may include the apparatus 1400. In some aspects, the apparatus 1400 includes a reception component 1402, a transmission component 1404, and/or a communication manager 1406, 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 1406 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 1400 may communicate with another apparatus 1408, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1402 and the transmission component 1404.

[0241] In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein in connection with Figs. 7-8. Additionally, or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as process 1000 of Fig. 10 and/or process 1200 of Fig. 12. In some aspects, the apparatus 1400 and/or one or more components shown in Fig. 14 may include one or more components of the network node 110 described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 14 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 a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0242] The reception component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1408. The reception component 1402 may provide received communications to one or more other components of the apparatus 1400. In some aspects, the reception component 1402 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 1400. In some aspects, the reception component 1402 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network node 110 described in connection with Fig. 2. In some aspects, the reception component 1402 and/or the transmission component 1404 may include or may be included in a network interface. The network interface may be configured to obtain and/or output signals for the apparatus 1400 via one or more communications links, such as a backhaul link, a midhaul link, and/or a fronthaul link.

[0243] The transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1408. In some aspects, one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmission component 1404 for transmission to the apparatus 1408. In some aspects, the transmission component 1404 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 1408. In some aspects, the transmission component 1404 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network node 110 described in connection with Fig. 2. In some aspects, the transmission component 1404 may be co-located with the reception component 1402 in a transceiver.

[0244] The communication manager 1406 may support operations of the reception component 1402 and/or the transmission component 1404. For example, the communication manager 1406 may receive information associated with configuring reception of communications by the reception component 1402 and/or transmission of communications by the transmission component 1404. Additionally, or alternatively, the communication manager 1406 may generate and/or provide control information to the reception component 1402 and/or the transmission component 1404 to control reception and/or transmission of communications. [0245] The transmission component 1404 may transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure. The communication manager 1406 may perform, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure.

[0246] The transmission component 1404 may transmit, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure. The communication manager 1406 may perform, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure.

[0247] The number and arrangement of components shown in Fig. 14 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. 14. Furthermore, two or more components shown in Fig. 14 may be implemented within a single component, or a single component shown in Fig. 14 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 14 may perform one or more functions described as being performed by another set of components shown in Fig. 14.

[0248] The following provides an overview of some Aspects of the present disclosure: [0249] Aspect 1 : A method of wireless communication performed by a UE, comprising: receiving a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell; identifying that a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell is available for the handover procedure; and performing the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics. [0250] Aspect 2: The method of Aspect 1, wherein identifying that the first set of SSB measurement metrics is not available for the handover procedure is based at least in part on the UE not measuring the first SSB within a time threshold, and wherein identifying that the second set of SSB measurement metrics is available for the handover procedure is based at least in part on the UE measuring the second SSB within the time threshold.

[0251] Aspect 3: The method of any of Aspects 1-2, wherein performing the handover procedure to the BWP includes skipping a handover acquisition procedure associated with the BWP.

[0252] Aspect 4: The method of any of Aspects 1-3, wherein performing the handover procedure to the BWP includes utilizing, from the second set of SSB measurement metrics, at least one of: a master information block payload, a cell timing value, a gain state value, or cell quality information.

[0253] Aspect 5: The method of any of Aspects 1-4, wherein at least one of: the first set of SSB measurement metrics is associated with only one SSB, or the second set of measurement metrics is associated with only one SSB.

[0254] Aspect 6: The method of any of Aspects 1-5, wherein the UE is one of a reduced capability UE or an enhanced reduced capability UE.

[0255] Aspect 7: The method of any of Aspects 1-6, at least one of: the first SSB is one of a cell-defining SSB or a non-cell-defining SSB, or the second SSB is one of the cell-defining SSB or the non-cell-defining SSB.

[0256] Aspect 8: The method of any of Aspects 1-7, further comprising: identifying that a third set of SSB measurement metrics associated with a third SSB associated with the target cell is available for the handover procedure; and identifying that the second set of SSB measurement metrics is to be used for the handover procedure.

[0257] Aspect 9: The method of Aspect 8, wherein identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

[0258] Aspect 10: The method of Aspect 8, wherein the second set of SSB measurement metrics includes a first cell quality metric, wherein the third set of SSB measurement metrics includes a second cell quality metric, and wherein identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on at least one of the first cell quality metric or the second cell quality metric. [0259] Aspect 11 : The method of Aspect 10, wherein identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0260] Aspect 12: The method of Aspect 10, further comprising: identifying that the first cell quality metric and the second cell quality metric satisfy a cell quality threshold; and performing the handover procedure based at least in part filtering the first cell quality metric and the second cell quality metric.

[0261] Aspect 13: The method of Aspect 8, wherein identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0262] Aspect 14: The method of Aspect 8, wherein identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0263] Aspect 15: The method of Aspect 8, wherein identifying that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part the second SSB being associated with a cell-defining SSB associated with the target cell during the handover procedure.

[0264] Aspect 16: A method of wireless communication performed by a network node, comprising: transmitting, to a UE, a handover command indicating that the UE is to perform a handover procedure to a BWP associated with a target cell, wherein a first set of SSB measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure; and performing, with the UE, the handover procedure to the BWP based at least in part on a second set of SSB measurement metrics, associated with a second SSB associated with the target cell, being available for the handover procedure.

[0265] Aspect 17: The method of Aspect 16, wherein the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not being configured to measure the first SSB within a time threshold, and wherein the second set of SSB measurement metrics is available for the handover procedure based at least in part on the UE being configured to measure the second SSB within the time threshold.

[0266] Aspect 18: The method of any of Aspects 16-17, wherein performing the handover procedure to the BWP includes skipping a handover acquisition procedure associated with the BWP. [0267] Aspect 19: The method of any of Aspects 16-18, wherein performing the handover procedure to the BWP is based at least in part on at least one of: a master information block payload associated with the second set of SSB measurement metrics, a cell timing value associated with the second set of SSB measurement metrics, a gain state value associated with the second set of SSB measurement metrics, or cell quality information associated with the second set of SSB measurement metrics.

[0268] Aspect 20: The method of any of Aspects 16-19, wherein at least one of: the first set of SSB measurement metrics is associated with only one SSB, or the second set of measurement metrics is associated with only one SSB.

[0269] Aspect 21: The method of any of Aspects 16-20, wherein the UE is one of a reduced capability UE or an enhanced reduced capability UE.

[0270] Aspect 22: The method of any of Aspects 16-21, wherein at least one of: the first SSB is one of a cell-defining SSB or a non-cell-defining SSB, or the second SSB is one of the celldefining SSB or the non-cell-defining SSB.

[0271] Aspect 23: The method of any of Aspects 16-22, wherein a third set of SSB measurement metrics associated with a third SSB associated with the target cell is available for the handover procedure, and wherein performing the handover procedure to the BWP based at least in part on the second set of SSB measurement metrics is further based at least in part on an identification that the second set of SSB measurement metrics is to be used for the handover procedure.

[0272] Aspect 24: The method of Aspect 23, wherein the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

[0273] Aspect 25: The method of Aspect 23, wherein the second set of SSB measurement metrics includes a first cell quality metric, wherein the third set of SSB measurement metrics includes a second cell quality metric, and wherein the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on at least one of the first cell quality metric or the second cell quality metric.

[0274] Aspect 26: The method of Aspect 25, wherein the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0275] Aspect 27: The method of Aspect 25, wherein the first cell quality metric and the second cell quality metric satisfy a cell quality threshold, and wherein performing the handover procedure is further based at least in part on a filtering of the first cell quality metric and the second cell quality metric.

[0276] Aspect 28: The method of Aspect 23, wherein the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0277] Aspect 29: The method of Aspect 23, wherein the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0278] Aspect 30: The method of Aspect 23, wherein the identification that the second set of SSB measurement metrics is to be used for the handover procedure is based at least in part on the second SSB being associated with a cell-defining SSB associated with the target cell during the handover procedure.

[0279] Aspect 31 : A method of wireless communication performed by a user equipment (UE), comprising: receiving a handover command indicating that the UE is to perform a handover procedure to a bandwidth part (BWP) associated with a target cell; identifying that a first set of synchronization signal block (SSB) measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; selecting one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure; and performing the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

[0280] Aspect 32: The method of Aspect 31, further comprising: identifying that the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not measuring the first SSB within a time threshold; and identifying that the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure based at least in part on the UE measuring the second SSB and the third SSB within the time threshold.

[0281] Aspect 33: The method of any of Aspects 31-32, wherein performing the handover procedure to the BWP includes omitting decoding the first SSB as part of the handover procedure.

[0282] Aspect 34: The method of any of Aspects 31-33, wherein performing the handover procedure to the BWP includes utilizing, from the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, at least one of: a master information block payload, a cell timing value, a gain state value, or cell quality information.

[0283] Aspect 35: The method of any of Aspects 31-34, wherein at least one of: the first set of SSB measurement metrics is associated with only one SSB, the second set of SSB measurement metrics is associated with only one SSB, or the third set of SSB measurement metrics is associated with only one SSB.

[0284] Aspect 36: The method of any of Aspects 31-35, wherein the UE is one of a reduced capability UE or an enhanced reduced capability UE.

[0285] Aspect 37: The method of any of Aspects 31-36, wherein at least one of: the first SSB is one of a cell-defining SSB or a non-cell-defining SSB, the second SSB is one of the celldefining SSB or the non-cell-defining SSB, or the third SSB is one of the cell-defining SSB or the non-cell-defining SSB.

[0286] Aspect 38: The method of any of Aspects 31-37, further comprising : selecting the second set of SSB measurement metrics to be used for the handover procedure; and performing the handover procedure to the BWP using the second set of SSB measurement metrics.

[0287] Aspect 39: The method of Aspect 38, wherein selecting the second set of SSB measurement metrics to be used for the handover procedure includes selecting the second set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

[0288] Aspect 40: The method of Aspect 38, wherein the second set of SSB measurement metrics includes a first cell quality metric, wherein the third set of SSB measurement metrics includes a second cell quality metric, and wherein selecting the second set of SSB measurement metrics to be used for the handover procedure includes selecting the second set of SSB measurement metrics based at least in part on at least one of the first cell quality metric or the second cell quality metric.

[0289] Aspect 41 : The method of Aspect 40, wherein selecting the second set of SSB measurement metrics to be used for the handover procedure includes selecting the second set of SSB measurement metrics based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0290] Aspect 42: The method of Aspect 40, further comprising: identifying that the first cell quality metric and the second cell quality metric satisfy a cell quality threshold; and performing the handover procedure based at least in part filtering the first cell quality metric and the second cell quality metric.

[0291] Aspect 43: The method of Aspect 38, wherein selecting the second set of SSB measurement metrics to be used for the handover procedure includes selecting the second set of SSB measurement metrics based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0292] Aspect 44: The method of Aspect 38, wherein selecting the second set of SSB measurement metrics to be used for the handover procedure includes selecting the second set of SSB measurement metrics based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0293] Aspect 45: The method of Aspect 38, wherein selecting the second set of SSB measurement metrics to be used for the handover procedure includes selecting the second set of SSB measurement metrics based at least in part the second SSB being associated with a celldefining SSB associated with the target cell during the handover procedure.

[0294] Aspect 46: A method of wireless communication performed by a network node, comprising: transmitting, to a user equipment (UE), a handover command indicating that the UE is to perform a handover procedure to a bandwidth part (BWP) associated with a target cell, wherein a first set of synchronization signal block (SSB) measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; and performing, with the UE, the handover procedure to the BWP using a selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure.

[0295] Aspect 47: The method of Aspect 46, wherein the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not being configured to measure the first SSB within a time threshold, and wherein the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure based at least in part on the UE being configured to measure the second SSB and the third SSB within the time threshold.

[0296] Aspect 48: The method of any of Aspects 46-47, wherein performing the handover procedure to the BWP includes perform the handover procedure to the BWP based at least in part on at least one of: a master information block payload associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, a cell timing value associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, a gain state value associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, or cell quality information associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

[0297] Aspect 49: The method of any of Aspects 46-48, wherein performing the handover procedure to the BWP includes performing the handover procedure based at least in part on a selection of the second set of SSB measurement metrics to be used for the handover procedure. [0298] Aspect 50: The method of Aspect 49, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

[0299] Aspect 51 : The method of Aspect 49, wherein the second set of SSB measurement metrics includes a first cell quality metric, wherein the third set of SSB measurement metrics includes a second cell quality metric, and wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on at least one of the first cell quality metric or the second cell quality metric.

[0300] Aspect 52: The method of Aspect 51, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

[0301] Aspect 53: The method of Aspect 49, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

[0302] Aspect 54: The method of Aspect 49, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being located in a same frequency band as the first SSB.

[0303] Aspect 55: The method of Aspect 49, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being associated with a cell-defining SSB associated with the target cell during the handover procedure.

[0304] Aspect 56: 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-55. [0305] Aspect 57: 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-55.

[0306] Aspect 58: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-55.

[0307] Aspect 59: 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-55.

[0308] Aspect 60: 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-55.

[0309] Aspect 61 : 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-55.

[0310] Aspect 62: 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-55.

[0311] 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. [0312] 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.

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

[0314] 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).

[0315] 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’).

Claims

WHAT IS CLAIMED IS:

1. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more memories including instructions executable by the one or more processors to cause the UE to: receive a handover command indicating that the UE is to perform a handover procedure to a bandwidth part (BWP) associated with a target cell; identify that a first set of synchronization signal block (SSB) measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; select one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure; and perform the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

2. The UE of claim 1, wherein the one or more memories further include instructions executable by the one or more processors to cause the UE to: identify that the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not measuring the first SSB within a time threshold; and identify that the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure based at least in part on the UE measuring the second SSB and the third SSB within the time threshold.

3. The UE of claim 1, wherein the one or more memories include instructions executable by the one or more processors to cause the UE to, when performing the handover procedure to the BWP, omit decoding the first SSB as part of the handover procedure.

4. The UE of claim 1, wherein the one or more memories include instructions executable by the one or more processors to cause the UE to, when performing the handover procedure to the BWP, utilize, from the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, at least one of: a master information block payload, a cell timing value, a gain state value, or cell quality information.

5. The UE of claim 1, wherein at least one of: the first set of SSB measurement metrics is associated with only one SSB, the second set of SSB measurement metrics is associated with only one SSB, or the third set of SSB measurement metrics is associated with only one SSB.

6. The UE of claim 1, wherein the UE is one of a reduced capability UE or an enhanced reduced capability UE.

7. The UE of claim 1, wherein at least one of: the first SSB is one of a cell-defining SSB or a non-cell-defining SSB, the second SSB is one of the cell-defining SSB or the non-cell- defining SSB, or the third SSB is one of the cell-defining SSB or the non-cell-defining SSB.

8. The UE of claim 1, wherein the one or more memories further include instructions executable by the one or more processors to cause the UE to: select the second set of SSB measurement metrics to be used for the handover procedure; and perform the handover procedure to the BWP using the second set of SSB measurement metrics.

9. The UE of claim 8, wherein the one or more memories include instructions executable by the one or more processors to cause the UE to, when selecting the second set of SSB measurement metrics to be used for the handover procedure, select the second set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

10. The UE of claim 8, wherein the second set of SSB measurement metrics includes a first cell quality metric, wherein the third set of SSB measurement metrics includes a second cell quality metric, and wherein the one or more memories include instructions executable by the one or more processors to cause the UE to, when selecting the second set of SSB measurement metrics to be used for the handover procedure, select the second set of SSB measurement metrics based at least in part on at least one of the first cell quality metric or the second cell quality metric.

11. The UE of claim 10, wherein the one or more memories include instructions executable by the one or more processors to cause the UE to, when selecting the second set of SSB measurement metrics to be used for the handover procedure, select the second set of SSB measurement metrics based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

12. The UE of claim 10, wherein the one or more memories further include instructions executable by the one or more processors to cause the UE to: identify that the first cell quality metric and the second cell quality metric satisfy a cell quality threshold; and perform the handover procedure based at least in part filtering the first cell quality metric and the second cell quality metric.

13. The UE of claim 8, wherein the one or more memories include instructions executable by the one or more processors to cause the UE to, when selecting the second set of SSB measurement metrics to be used for the handover procedure, select the second set of SSB measurement metrics based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

14. The UE of claim 8, wherein the one or more memories include instructions executable by the one or more processors to cause the UE to, when selecting the second set of SSB measurement metrics to be used for the handover procedure, select the second set of SSB measurement metrics based at least in part on the second SSB being located in a same frequency band as the first SSB.

15. The UE of claim 8, wherein the one or more memories include instructions executable by the one or more processors to cause the UE to, when selecting the second set of SSB measurement metrics to be used for the handover procedure, select the second set of SSB measurement metrics based at least in part the second SSB being associated with a cell -defining SSB associated with the target cell during the handover procedure.

16. A network node for wireless communication, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more memories including instructions executable by the one or more processors to cause the network node to: transmit, to a user equipment (UE), a handover command indicating that the UE is to perform a handover procedure to a bandwidth part (BWP) associated with a target cell, wherein a first set of synchronization signal block (SSB) measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; and perform, with the UE, the handover procedure to the BWP using a selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure.

17. The network node of claim 16, wherein the first set of SSB measurement metrics is not available for the handover procedure based at least in part on the UE not being configured to measure the first SSB within a time threshold, and wherein the second set of SSB measurement metrics and the third set of SSB measurement metrics are available for the handover procedure based at least in part on the UE being configured to measure the second SSB and the third SSB within the time threshold.

18. The network node of claim 16, wherein the one or more memories include instructions executable by the one or more processors to cause the network node to, when performing the handover procedure to the BWP, perform the handover procedure to the BWP based at least in part on at least one of: a master information block payload associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, a cell timing value associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, a gain state value associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics, or cell quality information associated with the selected one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

19. The network node of claim 16, wherein the one or more memories include instructions executable by the one or more processors to cause the network node to, when performing the handover procedure to the BWP, perform the handover procedure based at least in part on a selection of the second set of SSB measurement metrics to be used for the handover procedure.

20. The network node of claim 19, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second set of SSB measurement metrics being collected by the UE more recently than the third set of SSB measurement metrics.

21. The network node of claim 19, wherein the second set of SSB measurement metrics includes a first cell quality metric, wherein the third set of SSB measurement metrics includes a second cell quality metric, and wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on at least one of the first cell quality metric or the second cell quality metric.

22. The network node of claim 21, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on one of the first cell quality metric or the second cell quality metric satisfying a cell quality threshold, and the other one of the first cell quality metric or the second cell quality metric not satisfying the cell quality threshold.

23. The network node of claim 19, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

24. The network node of claim 19, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being located in a same frequency band as the first SSB.

25. The network node of claim 19, wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being associated with a cell-defining SSB associated with the target cell during the handover procedure.

26. A method of wireless communication performed by a user equipment (UE), comprising: receiving a handover command indicating that the UE is to perform a handover procedure to a bandwidth part (BWP) associated with a target cell; identifying that a first set of synchronization signal block (SSB) measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure and that a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; selecting one of the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure; and performing the handover procedure to the BWP using the one of the second set of SSB measurement metrics or the third set of SSB measurement metrics.

27. The method of claim 26, wherein the selecting the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure includes selecting the second set of SSB measurement metrics to be used for the handover procedure, and wherein the selecting the second set of SSB measurement metrics is based at least in part on the second SSB being closer, in a frequency domain, to the first SSB than the third SSB is to the first SSB.

28. The method of claim 26, wherein the selecting the second set of SSB measurement metrics or the third set of SSB measurement metrics to be used for the handover procedure includes selecting the second set of SSB measurement metrics to be used for the handover procedure, and wherein the selecting the second set of SSB measurement metrics is based at least in part on the second SSB being located in a same frequency band as the first SSB.

29. A method of wireless communication performed by a network node, comprising: transmitting, to a user equipment (UE), a handover command indicating that the UE is to perform a handover procedure to a bandwidth part (BWP) associated with a target cell, wherein a first set of synchronization signal block (SSB) measurement metrics associated with a first SSB associated with the BWP is not available for the handover procedure, and wherein a second set of SSB measurement metrics associated with a second SSB associated with the target cell and a third set of SSB measurement metrics associated with a third SSB associated with the target cell are available for the handover procedure; and performing, with the UE, the handover procedure to the BWP using a selected on the second set of SSB measurement metrics or the third set of SSB measurement metrics based at least in part on the second set of SSB measurement metrics and the third set of SSB measurement metrics being available for the handover procedure.

30. The method of claim 29, wherein the performing the handover procedure to the BWP includes performing the handover procedure based at least in part on a selection of the second set of SSB measurement metrics to be used for the handover procedure, and wherein the selection of the second set of SSB measurement metrics to be used for the handover procedure is based at least in part on the second SSB being located in a same frequency band as the first SSB.