Handover associated with reduced capability cells

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a reduced capability (RedCap) may receive a blind handover initiating communication that includes a cell identifier (ID) associated with a target cell. The RedCap may perform a wireless communication operation associated with the target cell based on whether the cell ID is indicated in a first database of the first database and a second database stored in a memory of the RedCap UE, the first database including cell information supporting the RedCap, the cell information supporting RedCap comprises at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database comprises cell information not supporting RedCap, the non-RedCap supporting cell information includes at least one non-RedCap supporting indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication. Numerous other aspects are described.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 148,216, titled "HANDOVER ASSOCIATED WITH REDUCED CAPABILITY CELLS", filed on December 29, 2022, and this application is assigned to the assignee of the present application. The disclosure of the prior application is considered to be a part of this patent application and is incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatuses for handover associated with reduced - capability cells. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple - access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple - access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single - Carrier Frequency Division Multiple Access (SC - FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD - SCDMA) systems, and Long Term Evolution (LTE). LTE / Advanced LTE is an enhanced collection of the Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the 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., sidelink (SL), Wireless Local Area Network (WLAN) link, and / or Wireless Personal Area Network (WPAN) link, etc.).

[0006] The above multi-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, and / or global levels. New Radio (NR) (which may be referred to as 5G) is an enhanced set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectral efficiency; reducing costs; improving services; utilizing new spectra; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technology, and carrier aggregation. With the continuous increase in the demand for mobile broadband access, further improvements to LTE, NR, and other radio access technologies are still useful. SUMMARY OF THE INVENTION

[0007] Some aspects described herein relate to a Reduced-Capability (RedCap) User Equipment (UE) for wireless communication. The RedCap UE may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable (e.g., directly, indirectly, after preprocessing, without preprocessing) by the one or more processors. The instructions may be executable by the one or more processors to cause the RedCap UE to: receive a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell identifier (ID). The instructions may be executable by the one or more processors to cause the RedCap UE to: perform wireless communication operations associated with the target cell based on whether the cell ID is indicated in a first database of a first database and a second database stored in the memory, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0008] Some aspects described herein relate to a RedCap UE for wireless communication. The RedCap UE may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the RedCap UE to: receive configuration information associated with a measurement-based handover procedure. The instructions may be executable by the one or more processors to cause the RedCap UE to: obtain measurements associated with a target cell based on the configuration information. The instructions may be executable by the one or more processors to cause the RedCap UE to: perform wireless communication operations associated with the target cell based on the measurements meeting measurement conditions and based on whether the cell ID is indicated in the first database of a first database and a second database stored in the memory, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0009] Some aspects described herein relate to a method of wireless communication performed by a RedCap UE. The method may include: receiving a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell ID. The method may include: performing wireless communication operations associated with the target cell based on whether the cell ID is indicated in the first database of a first database and a second database stored in the memory of the RedCap UE, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0010] Some aspects described herein relate to a method of wireless communication performed by a RedCap UE. The method may include: receiving configuration information associated with a measurement-based handover process. The method may include: obtaining measurements associated with a target cell based on the configuration information. The method may include: performing a wireless communication operation associated with the target cell based on the measurements meeting a measurement condition and based on whether the cell ID is indicated in a first database and a second database stored in the memory of the RedCap UE, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a RedCap UE. The one or more instructions, when executed by one or more processors of the RedCap, may cause the RedCap to: receive a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell ID. The one or more instructions, when executed by one or more processors of the RedCap, may cause the RedCap to: perform a wireless communication operation associated with the target cell based on whether the cell ID is indicated in a first database and a second database stored in the memory of the RedCap UE, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a RedCap. The one or more instructions, when executed by one or more processors of the RedCap, may cause the RedCap to: receive configuration information associated with a measurement-based handover process. The one or more instructions, when executed by one or more processors of the RedCap, may cause the RedCap to: obtain measurements associated with a target cell based on the configuration information. The one or more instructions, when executed by one or more processors of the RedCap, may cause the RedCap to: perform wireless communication operations associated with the target cell based on the measurements meeting measurement conditions and based on whether the cell ID is indicated in a first database among a first database and a second database stored in a memory of the RedCap UE, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for receiving a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell ID associated with the target cell. The apparatus may include: means for performing wireless communication operations associated with the target cell based on whether the cell ID is indicated in a first database among a first database and a second database stored in a memory of the apparatus, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for receiving configuration information associated with a measurement-based handover procedure. The apparatus may include: means for obtaining measurements associated with a target cell based on the configuration information. The apparatus may include: means for performing wireless communication operations associated with the target cell based on the measurements meeting measurement conditions and based on whether the cell ID is indicated in a first database and a second database stored in the memory of the apparatus, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

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

[0016] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples 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. The characteristics of the concepts disclosed herein, both as to their organization and operation methods, as well as associated advantages, will be better understood when considered in conjunction with the following description taken in connection with the accompanying figures. Each of the figures provided in the drawings is for the purpose of illustration and description only and is not a definition of the limits of the claims.

[0017] While aspects are described herein by way of illustration of some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via an integrated chip implementation or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can 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). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] To gain a more detailed understanding of the above-described features of the present disclosure, a more specific description of the above briefly summarized inventive content can be obtained by referring to aspects, some of which are illustrated in the drawings. However, it should be noted that the drawings only illustrate certain typical aspects of the present disclosure and are therefore not considered to limit its scope, as the specification may admit other equally valid aspects. The same reference numerals in different drawings can identify the same or similar elements.

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

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

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

[0022] Figure 4A is a diagram illustrating an example associated with blind handover optimization for a reduced-capability (RedCap) UE according to the present disclosure.

[0023] Figure 4B is a diagram illustrating another example associated with blind handover optimization for a RedCap UE according to the present disclosure.

[0024] Figure 5A FIG. is an illustration of an example associated with measurement-based handover optimization for a RedCap UE according to the present disclosure.

[0025] Figure 5B FIG. is an illustration of another example associated with measurement-based handover optimization for a RedCap UE according to the present disclosure.

[0026] Figure 6 FIG. is an illustration of an example process, such as may be performed by a RedCap UE, according to the present disclosure.

[0027] Figure 7 FIG. is an illustration of an example process, such as may be performed by a RedCap UE, according to the present disclosure.

[0028] Figure 8 FIG. is an illustration of an example apparatus for wireless communication according to the present disclosure.

[0029] Figure 9 FIG. is an illustration of an example apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION

[0030] Various aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may 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 present disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, any number of the aspects set forth herein may be used to implement an apparatus or practice a method. In addition, the scope of the present disclosure is intended to cover such apparatus or methods implemented using other structures, functionality, or a combination of structures and functionality in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0031] Aspects and examples generally include methods, apparatuses, network nodes, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as described or otherwise fully described herein with reference to the accompanying drawings and the specification and as illustrated in the accompanying drawings and the specification.

[0032] The present disclosure can be readily used as a basis for modifying or designing other structures for the same purposes as those of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics (both the organization and the method of operation) of the concepts disclosed herein and the associated advantages are better understood according to the following description. Each of the drawings in the accompanying drawings is provided for purposes of illustration and description, and not as a definition of the limitations of the claims.

[0033] Although aspects are described herein by way of illustration of some examples, such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via an integrated chip implementation or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can 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). The aspects described herein can be practiced in a variety of devices, components, systems, distributed arrangements, and / or end-user devices of different sizes, shapes, and configurations.

[0034] Certain aspects of a telecommunications system 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 drawings by various blocks, modules, components, circuits, steps, processes, or algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system.

[0035] Although terms generally associated with 5G or New Radio (NR) radio access technology (RAT) may be used herein to describe aspects, the aspects of the present disclosure can be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

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

[0037] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, the 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. The 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 transmit receive point (TRP), a DU, an RU, a CU, a mobility element of the network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

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

[0039] In some aspects, the term "base station" or "network node" may refer to a centralized base station, a distributed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, 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 term "base station" or "network node" may refer to a single device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located at the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function among base station functions, rather than another base station function. In this way, a single device may include more than one base station.

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

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

[0042] The network controller 130 may be coupled 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 fronthaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless fronthaul communication link or a wired fronthaul 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.

[0043] UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. The UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The 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 computer, a camera, a gaming device, a netbook, a smartbook, a superbook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0044] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. The MTC UE and / or eMTC UE may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included inside a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0045] In some aspects, UEs can be classified according to different categories and / or can support different capabilities. For example, a network node can serve a first category of UEs with less advanced capabilities (e.g., lower capabilities and / or reduced capabilities) and a second category of UEs with more advanced capabilities (e.g., higher capabilities). Compared with the second category of UEs, the first category of UEs may have a reduced feature set and can be referred to as Reduced Capability (RedCap) UEs (which can also be interchangeably referred to as reduced capacity UEs and also have the acronym "RedCap"), low-end UEs, and / or NR Light UEs, etc. The second category of UEs can be ultra-reliable low-latency communication (URLLC) devices and / or enhanced mobile broadband (eMBB) devices and can have an advanced feature set compared with RedCap UEs. RedCap UEs can include wearable devices, IoT devices, sensors, cameras, etc. associated with limited bandwidth, power capacity, and / or transmission range, etc. The second category of UEs can be referred to as legacy UEs, baseline UEs, high-end UEs, NR UEs, and / or advanced UEs, etc. In some aspects, RedCap UEs can have the ability to meet the requirements of a first wireless communication standard but not meet the requirements of a second wireless communication standard, while the second category of UEs can have the ability to meet the requirements of the second wireless communication standard (and in some cases, also meet the requirements of the first wireless communication standard).

[0046] For example, a first category of RedCap UEs can support a lower maximum modulation and coding scheme (MCS) than a second category of UEs (e.g., support quadrature phase shift keying (QPSK) etc. compared with 256 - quadrature amplitude modulation (QAM) etc.), can support a lower maximum transmission power than a second category of UEs, can have a less advanced beamforming capability than a second category of UEs (e.g., may not be able to form as many beams as a second category of UEs), can require a longer processing time than a second category of UEs, can include less hardware than a second category of UEs (e.g., fewer antennas, fewer transmit antennas, and / or fewer receive antennas), and / or may not be able to communicate on as wide a maximum bandwidth part as a second category of UEs, etc.

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

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

[0049] Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc. according to frequency or wavelength. 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 to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is typically (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is typically (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0050] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as frequency range designations FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher 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 to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher bands falls within the EHF band.

[0051] Considering the above examples, unless otherwise specifically stated, it should be understood that if terms such as "below 6 GHz" are used herein, such terms can generally represent frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if terms such as "millimeter wave" are used herein, such terms can generally represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or can be within the EHF band. It is envisioned that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0052] In some aspects, a RedCap UE (e.g., UE 120) can include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 can receive a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell identifier (ID); and perform wireless communication operations associated with the target cell based on whether the cell ID is indicated in a first database and a second database stored in the memory of the RedCap UE, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0053] In some aspects, the communication manager 140 may receive configuration information associated with a measurement-based handover procedure; obtain measurements associated with a target cell based on the configuration information; and perform wireless communication operations associated with the target cell based on the measurements meeting measurement conditions and based on whether the cell ID is indicated in a first database and a second database stored in the memory of the RedCap UE, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0054] As indicated above, Figure 1 is provided as an example. Other examples may be different from the examples Figure 1 described with respect to

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

[0056] At network node 110, transmit processor 220 may receive data destined for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more MCSs for the UE 120 at least in part based on one or more channel quality indicators (CQIs) received from the UE 120. Network node 110 may process (e.g., encode and modulate) the data for the UE 120 at least in part based on the MCS selected for the UE 120, and may provide data symbols for the UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and may provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple input multiple output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or 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 process the corresponding output symbol stream (e.g., for OFDM) using the corresponding modulator component to obtain a stream of output samples. Each modem 232 may also process the stream of output samples (e.g., convert to analog, amplify, filter, and / or up-convert) using the corresponding modulator component to obtain a downlink signal. 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).

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

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

[0059] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc., 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, etc. The antenna panel, antenna group, set of antenna elements, and / or 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 transmit and / or receive components (such as Figure 2 one or more components among).

[0060] Each antenna element in the antenna element may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element that is cross-polarized with a second sub-element, and the second sub-element may be used to independently transmit a cross-polarized signal. The antenna element may include a patch antenna, a dipole antenna, or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between the antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements can interact or interfere with each other (e.g., to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, a half wavelength, or other fractional wavelengths of the spacing between adjacent antenna elements to allow the interaction or interference of signals transmitted by the individual antenna elements within the desired range.

[0061] The antenna element and / or sub-element may be used to generate a beam. A "beam" may refer to a directional transmission, such as a wireless signal transmitted in the direction of a receiving device. The beam may include a directional signal, the direction associated with the signal, a set of directional resources associated with the signal (e.g., angle of arrival, horizontal direction, vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal.

[0062] As indicated above, the antenna element and / or sub-element may be used to generate a beam. For example, the antenna element may be individually selected or deselected for the transmission of a signal (or signals) by controlling the amplitude of one or more corresponding amplifiers. Beamforming includes using multiple signals on different antenna elements to generate a beam, where one or more or all of the multiple signals are phase-shifted relative to each other. The formed beam may carry a physical or higher-layer reference signal or information. When each of the multiple signals radiates from the corresponding antenna element, the radiated signals interact with each other, interfere (constructive interference and destructive interference), and amplify to form the resulting beam. The shape (such as amplitude, width, and / or the presence of sidelobes) and direction (such as the angle of the beam relative to the surface of the antenna array) may be dynamically controlled by modifying the phase shift or phase offset of the multiple signals relative to each other.

[0063] Beamforming can be used for communication between a UE and a network node, such as for millimeter-wave communication and the like. In this case, the network node may provide the UE with a configuration of a transmission configuration indicator (TCI) state, and the transmission configuration indicator (TCI) state respectively indicates beams that can be used by the UE, such as for receiving a physical downlink shared channel (PDSCH). The TCI state indicates spatial parameters for communication. For example, the TCI state for communication may identify a source signal (such as a synchronization signal block, a channel state information reference signal, etc.) and spatial parameters to be derived from the source signal for the purpose of transmitting or receiving communication. For example, the TCI state may indicate a quasi co-location (QCL) type. The QCL type may indicate one or more spatial parameters to be derived from the source signal. The source signal may be referred to as a QCL source. The network node may indicate the activated TCI state to the UE, and the UE may use the activated TCI state to select a beam for receiving the PDSCH.

[0064] The beam indication may be a TCI state information element, a beam ID, spatial relation information, a TCI state ID, a closed-loop index, a panel ID, a TRP ID, and / or a sounding reference signal (SRS) set ID, etc., or include a TCI state information element, a beam ID, spatial relation information, a TCI state ID, a closed-loop index, a panel ID, a TRP ID, and / or a sounding reference signal (SRS) set ID, etc. The TCI state information element (referred to as the TCI state in this article) may indicate information associated with a beam, such as a downlink beam. For example, the TCI state information element may indicate a TCI state identifier (e.g., tci-StateID), a QCL type (e.g., qcl-Type1, qcl-Type2, qcl-TypeA, qcl-TypeB, qcl-TypeC, qcl-TypeD, etc.), a cell identifier (e.g., ServCellIndex), a bandwidth part identifier (bwp-Id), a reference signal identifier (such as a CSI-RS (e.g., NZP-CSI-RS-ResourceId, SSB-Index, etc.)), etc. The spatial relation information may similarly indicate information associated with an uplink beam.

[0065] The beam indication may be a joint or separate downlink (DL) / uplink (UL) beam indication within a unified TCI framework. In some cases, the network may use at least UE-specific (unicast) downlink control information (DCI) to indicate the joint or separate DL / UL beam indication from the active TCI state, thereby supporting layer 1 (L1)-based beam indication. In some cases, the existing DCI formats 1_1 and / or 1_2 may be reused for beam indication. The network may include a support mechanism for the UE to confirm successful decoding of the beam indication. For example, the acknowledgement / negative acknowledgement (ACK / NACK) of the PDSCH scheduled by the DCI carrying the beam indication may also be used as the ACK for the DCI.

[0066] The beam indication may be provided for a carrier aggregation (CA) scenario. In the unified TCI framework, the network may support the update and activation of the common TCI state ID to provide common QCL information and / or one or more common UL transmission spatial filters across a set of configured component carriers (CCs). This type of beam indication may be applicable to in-band CA as well as joint DL / UL beam indication and separate DL / UL beam indication. The common TCI state ID may mean that a reference signal (RS) determined according to the TCI state indicated by the common TCI state ID is used to provide the QCL type D indication and to determine the UL transmission spatial filter across the set of configured CCs.

[0067] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-coded by the TX MIMO processor 266 when applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna 252, the modem 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., refer to Figures 4A to 9 )).

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

[0069] In some aspects, controller / processor 280 may be a component of a processing system. A processing system may generally be a system or series of machines or components that receive input and process the input to produce output (which may be passed to other systems or components such as, for example, UE 120). For example, the processing system of UE 120 may be a system that includes various other components or sub-components of UE 120.

[0070] The processing system of UE 120 may interface with one or more other components of UE 120, process information (such as input or signals) received from one or more other components, or output information to one or more other components. For example, a chip or modem of UE 120 may include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and the receiver such that UE 120 may receive information or signal input and may pass the information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and the transmitter such that UE 120 may transmit information output from the chip or modem. Those of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input and the first interface may also output, transmit, or provide information.

[0071] In some aspects, the controller / processor 240 can be a component of a processing system. A processing system can generally be a system or a series of machines or components that receive inputs and process the inputs to produce outputs (which can be passed to other systems or components such as network node 110, for example). For example, the processing system of network node 110 can be a system that includes various other components or sub-components of network node 110.

[0072] The processing system of network node 110 can interface with one or more other components of network node 110, can process information (such as inputs or signals) received from one or more other components, or can output information to one or more other components. For example, a chip or modem of network node 110 can include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface can be an interface between the processing system of the chip or modem and a receiver, such that network node 110 can receive information or signal inputs and can pass the information to the processing system. In some examples, the second interface can be an interface between the processing system of the chip or modem and a transmitter, such that network node 110 can transmit information output from the chip or modem. One of ordinary skill in the art will readily recognize that the second interface can also obtain or receive information or signal inputs, and the first interface can also output, transmit, or provide information.

[0073] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 any other component of can perform one or more techniques associated with handovers associated with reduced-capability cells, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 any other component of can perform or direct the operation of, for example, Figure 6 process 600 of, Figure 7 process 700 of, and / or other processes as described herein. Memories 242 and 282 can store data and program code for network node 110 and UE 120, respectively. In some examples, memories 242 and / or 282 can include non-transitory computer-readable media storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when the one or more instructions are executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), the one or more processors, UE 120, and / or network node 110 can perform or direct the operation of, for example, Figure 6 process 600 of,Figure 7 Operations of process 700 and / or other processes as described herein. In some examples, executing instructions may include running instructions, transforming instructions, compiling instructions, and / or interpreting instructions, etc.

[0074] In some aspects, a RedCap UE (e.g., UE 120) includes: components for receiving a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell ID; and / or components for performing wireless communication operations associated with the target cell based on whether the cell ID is indicated in a first database among a first database and a second database stored in the memory of the RedCap UE, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication indicating that at least one cell supports RedCap communication associated with at least one cell, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication indicating that at least one additional cell does not support RedCap communication associated with at least one additional cell.

[0075] In some aspects, a RedCap UE includes components for receiving configuration information associated with a measurement-based handover process; components for obtaining measurements associated with a target cell based on the configuration information; and / or components for performing wireless communication operations associated with the target cell based on the measurements meeting measurement conditions and based on whether the cell ID is indicated in a first database among a first database and a second database stored in the memory of the RedCap UE, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication indicating that at least one cell supports RedCap communication associated with at least one cell, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication indicating that at least one additional cell does not support RedCap communication associated with at least one additional cell. In some aspects, components for a reduced-capability (RedCap) UE to perform the 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.

[0076] Although Figure 2The boxes in [description] are illustrated as separate components, but the functionality described above with respect to these boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by, or under the control of, the controller / processor 280.

[0077] As indicated above, Figure 2 is provided as an example. Other examples may be different from the examples described with respect to Figure 2 which are described.

[0078] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in a centralized architecture or a split architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as a centralized base station (also referred to as a stand-alone base station or a monolithic base station) or a split base station. A "network entity" or "network node" can refer to a split base station or one or more units of a split base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

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

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

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

[0083] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, among others. Each control function may be implemented using an interface that is configured to signal with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU - UP) functionality), control plane functionality (e.g., Central Unit - Control Plane (CU - CP) functionality), or a combination thereof. In some embodiments, the CU 310 may be logically split into one or more CU - UP units and one or more CU - CP units. When implemented in an O - RAN configuration, the CU - UP units may communicate bidirectionally with the CU - CP units via an interface such as the E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

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

[0085] Each RU 340 can implement low-layer functionality. In some deployments, the RU 340 controlled by the DU 330 can correspond to a logical node that hosts RF processing functions or low PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc., based on a functional split (e.g., the functional split defined by 3GPP) such as a low-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 embodiments, the real-time and non-real-time aspects of the control plane communication and user plane communication with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

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

[0087] The non-RT RIC 315 can be configured to include logic functions that can implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and update, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (such as via the A1 interface). The near-RT RIC 325 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via an interface (such as via the E2 interface) through data collection and actions, and this interface connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near-RT RIC 325.

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

[0089] As indicated above, Figure 3 is provided as an example. Other examples may be different from the examples described with respect to Figure 3 which are described.

[0090] Some cells in a wireless network may support RedCap UEs, while other cells in the wireless network may not support RedCap UEs. The cells that support RedCap UEs may be referred to as "RedCap cells", and the cells that do not support RedCap UEs may be referred to as "non-RedCap cells". For example, in order for a cell to support RedCap UEs, the cell may support additional and / or reduced operations, additional and / or reduced features, and / or additional configurations associated with RedCap UEs. Thus, some cells within the wireless network may support additional operations, additional features, and / or additional configurations, while other cells in the wireless network may not support additional operations, additional features, and / or additional configurations. For example, a network operator may configure certain cells, such as cells associated with high traffic demands, to not support RedCap UEs, and may configure other cells, such as cells associated with lower traffic demands, to support RedCap UEs (e.g., to save costs, overheads, and / or resources associated with configuring these cells to support reduced-capability UEs). A RedCap UE may not be able to establish a connection with a cell that does not support RedCap UEs. For example, the core network and / or base station associated with the cell (e.g., based on subscription information or mobility policy information) may not allow a reduced-capability UE to establish a connection with a cell that does not support RedCap UEs. Thus, a RedCap UE may experience poor radio coverage within the wireless network.

[0091] For example, when a RedCap UE physically moves through a wireless network, the RedCap UE may travel into an area served by a cell that does not support RedCap UEs (e.g., an NR cell and / or an LTE cell). Thus, the RedCap UE may not be able to establish a connection with cells in certain areas associated with the wireless network. Thus, the RedCap UE typically has to perform a full search (e.g., a search of all nearby cells) to find a RedCap cell by receiving (e.g., decoding and reading) System Information Block 1 (SIB1) from each nearby cell. Performing a full search may cause unnecessary time consumption. In some cases, reconstruction may be impossible. In either case, service interruption and power consumption may be significant, resulting in poor radio coverage, degraded performance, increased latency, inefficient operation, and / or a poor user experience, etc.

[0092] Some of the techniques and apparatuses described herein implement enhanced RedCap UE operations. For example, some aspects provide for a RedCap UE to perform a reestablishment onto a RedCap cell after triggering a radio link failure (RLF). Some aspects provide for a handover from an LTE cell to an NR RedCap cell via a blind handover process or a measurement-based handover process. In some aspects, a RedCap UE may include two databases. The first database may be configured to store RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication. The second database may be configured to store non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication. In some aspects, the first database and / or the second database may be, be similar to, include, or be included in an acquisition database that is configured to store an indication of cells to which the RedCap UE has acquired access.

[0093] In some aspects, when the network blindly redirects a RedCap UE to a target cell, the RedCap UE may determine whether the target cell is a RedCap cell based on the two databases. If the target cell is a RedCap cell, the RedCap UE may perform a random access channel (RACH) handover process to reestablish coverage on the target cell, and if not, the RedCap UE may declare an early RLF and search for a RedCap cell. If the target cell is not in one of the two databases, the RedCap UE may read system information (e.g., SIB1) to determine whether the target cell is a RedCap cell. If the target cell is a RedCap cell, the RedCap UE may perform a RACH handover process and may add an indication associated with the target cell to the first database. If the target cell is a non-RedCap cell, the RedCap UE may search for the cells indicated in the first database and may camp on any suitable cell. If no suitable cell is found, the RedCap UE may fallback to a legacy (full) search process to perform a full search.

[0094] In aspects related to measurement-based handovers, a RedCap UE may omit measurements associated with non-RedCap cells (i.e., cells that do not support the RedCap UE in the measurement report) from the measurement report. When the network configures the RedCap UE to measure and report signal quality information associated with the indicated frequencies, the RedCap UE may measure and detect cells in those frequencies that meet the measurement conditions and may provide a report indicating the measurements. The RedCap UE may determine whether a cell is a RedCap cell based on two databases and may omit measurements associated with non-RedCap cells from the measurement report. If a cell that meets the measurement conditions is not indicated in the database and if that cell is the best cell in the corresponding frequency (e.g., the cell with the highest associated signal quality and / or power in that frequency), the UE may read the SIB1 of that cell to determine whether the cell is a RedCap cell and, based on that determination, may determine whether to include the associated measurements in the measurement report. If the cell is not the best cell in the frequency and does not exist in the database, the RedCap UE may include the associated measurements in the measurement report. If the network triggers a handover to a cell, the RedCap UE may avoid reading the corresponding system information, thereby reducing the time consumption associated with the reading of the system.

[0095] Figure 4A is a diagram illustrating Example 400 associated with blind handover optimization for a RedCap UE according to the present disclosure. As Figure 4A shown, a RedCap UE 402 may communicate with a network node 404. The network node 404 may be associated with (e.g., provide) a source cell to which the RedCap UE 402 may be connected. In some aspects, the source cell may be an LTE cell. A network node 406 may be associated with a target cell. In some aspects, the target cell may be an NR cell. In some aspects, the RedCap UE 502 may be, similar to, include Figures 1 to 3 the UE 120 depicted in Figure 1 and Figure 2 or be included in the network nodes 110 depicted in Figure 3 and / or one or more components of the decomposed base station architecture 300 depicted in

[0096] As indicated by reference numeral 408, the network node 406 may send RedCap support information, and the RedCap UE 402 may receive the RedCap support information. The RedCap support information may be associated with at least one cell associated with the network node 406 (e.g., provided by the network node), and may indicate whether the at least one cell supports RedCap communication. The RedCap support information may be any information indicating whether a cell supports RedCap communication. For example, in some aspects, the RedCap support information may include an explicit indication that a cell supports RedCap communication and / or an implicit indication that a cell supports RedCap communication. The implicit indication may include the configuration and / or characteristics of a cell associated with the support for RedCap communication. Similarly, the RedCap support information may include an explicit indication that a cell does not support RedCap communication and / or an implicit indication that a cell does not support RedCap communication. The implicit indication may include the configuration and / or characteristics of a cell not associated with RedCap communication. In some aspects, the absence of an explicit indication that a cell supports RedCap communication may be RedCap support information indicating that the cell does not support RedCap communication. In some aspects, for example, the network node 406 may send system information (e.g., SIB1) including the RedCap support information, and the RedCap UE 402 may receive the system information.

[0097] As indicated by reference numeral 410, the RedCap UE 402 may store at least one RedCap support indication and / or at least one non-RedCap support indication in the first database 412 or the second database 414, respectively, based on the RedCap support information. The first database 412 may include at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication. The second database 414 may include at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0098] As indicated by reference numeral 416, network node 404 may send a blind handover initiation communication, and RedCap UE 402 may receive the blind handover initiation communication. The blind handover initiation communication may indicate the frequency that RedCap 402 may search to identify the best cell in that frequency. The identified cell may be referred to as the "target cell" (e.g., the target cell associated with network node 406). Thus, the indicated frequency may be associated with the target cell, and the target cell may have an associated cell ID. As indicated by reference numeral 418, RedCap UE 402 may perform wireless communication operations. For example, in some aspects, RedCap UE 402 may perform wireless communication operations associated with the target cell based on whether the cell ID is indicated in the first database 412. In some aspects, for example, performing the wireless communication operations may include: initiating a RACH handover process associated with the target cell based on the cell ID being indicated in the first database 412. In some aspects, performing the wireless communication operations may include: updating the first database 412 and / or the second database 414.

[0099] Figure 4B is a diagram illustrating another example 420 associated with blind handover optimization for a RedCap UE according to the present disclosure. Example 420 depicts a process that may be performed by RedCap UE 402 in conjunction with Figure 4A the example 400 depicted in.

[0100] As indicated by reference numeral 422, RedCap UE 402 may receive a blind handover indication. The blind handover indication may be associated with the target cell, and the target cell has an associated cell ID. As indicated by reference numeral 424, RedCap UE 402 may determine whether the cell ID is indicated in the first database 412. If the cell ID is indicated in the first database 412, then as indicated by reference numeral 426, RedCap UE 402 may camp on the target cell. For example, as indicated above in conjunction with Figure 4A RedCap UE 402 may initiate a RACH handover process to camp on the target cell.

[0101] If the cell ID is not indicated in the first database 412, as indicated by reference numeral 428, the RedCap UE 402 may determine whether the cell ID is indicated in the second database 414. If the cell ID is not indicated in the second database 414, as indicated by reference numeral 430, the RedCap UE 402 may receive system information. The system information may be associated with the target cell and may include RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication. As indicated by reference numeral 432, the RedCap UE 402 may determine whether the target cell is a RedCap cell based on the RedCap support information. If the target cell is a RedCap cell, as indicated by reference numeral 426, the RedCap UE 402 may camp on the target cell. In some aspects, the RedCap UE 402 may add an indication of the target cell to the first database 412. If the target cell is not a RedCap cell, as indicated by reference numeral 434, the RedCap UE 402 may add the cell ID to the second database 414. If the cell ID is indicated in the second database 414, as indicated by reference numeral 436, the RedCap UE 402 may declare RLF and, as indicated by reference numeral 438, may perform a full search. In some aspects, for example, the RedCap UE 402 may perform a search for RedCap cells indicated in the first database 412.

[0102] As indicated above, Figure 4A and Figure 4B are provided as examples. Other examples may be different from the examples described for Figure 4A and Figure 4B which.

[0103] Figure 5A is a diagram illustrating example 500 associated with measurement-based handover optimization for a RedCap UE according to the present disclosure. As Figure 5A shown, the RedCap UE 502 may communicate with a network node 504. The network node 504 may be associated with (e.g., provide) a source cell to which the RedCap UE 502 may be connected. In some aspects, the source cell may be an LTE cell. The network node 506 may be associated with a target cell. In some aspects, the target cell may be an NR cell. In some aspects, the RedCap UE 502 may be, similar to, include Figure 4A the RedCap UE 402 depicted in Figures 1 to 3The UE 120 depicted therein, or is included in these UEs. In some aspects, the network node 504 and / or the network node 506 can be the following, be similar to the following, include the following, or be included in the following: Figure 4A the network node 404 and / or the network node 406 depicted therein, Figure 1 and Figure 2 the network node 110 depicted therein, and / or Figure 3 one or more components of the base station architecture 300 depicted therein.

[0104] As indicated by reference numeral 508, the network node 506 can send RedCap support information, and the RedCap UE 502 can receive the RedCap support information. The RedCap support information can be associated with at least one cell associated with the network node 506 (e.g., provided by the network node), and can indicate whether the at least one cell supports RedCap communication. In some aspects, for example, the network node 506 can send system information (e.g., SIB1) including the RedCap support information, and the RedCap UE 502 can receive the system information.

[0105] As indicated by reference numeral 510, the RedCap UE 502 can store at least one RedCap support indication and / or at least one non-RedCap support indication in the first database 512 or the second database 514 respectively based on the RedCap support information. The first database 512 can include at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication. The second database 514 can include at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0106] As indicated by reference numeral 516, the network node 504 can send configuration information, and the RedCap UE 502 can receive the configuration information. For example, the configuration information can be associated with a measurement-based handover process. As indicated by reference numeral 518, the RedCap UE 502 can obtain at least one measurement. For example, the RedCap UE 502 can obtain at least one measurement associated with a cell (including the target cell, which can have an associated cell ID) based on the configuration information. As indicated by reference numeral 520, the RedCap UE 502 can perform wireless communication operations. For example, the RedCap UE 502 can perform wireless communication operations associated with the target cell based on the associated measurement meeting the measurement conditions and based on whether the cell ID is indicated in the first database 512.

[0107] As indicated by reference numeral 522, the RedCap UE 502 may send a measurement report, and the network node 504 may receive the measurement report. For example, in some aspects, the RedCap UE 502 may send a handover measurement report including measurements associated with a target cell based on the measurements meeting measurement conditions and being indicated in a first database 512 based on the cell ID. In some aspects, the RedCap UE 502 may send a handover measurement report omitting measurements associated with the target cell based on the measurements meeting measurement conditions and being indicated in a second database 514 based on the cell ID.

[0108] Figure 5B is a diagram illustrating another example 524 associated with measurement-based handover optimization for a RedCap UE according to the present disclosure. Example 524 depicts a process that may be performed by the RedCap UE 502 in conjunction with Figure 5A the example 500 depicted in.

[0109] As indicated by reference numeral 526, the RedCap UE 502 may receive configuration information. As indicated above in conjunction with Figure 5A The configuration information may be associated with a measurement-based handover process. In some aspects, the configuration information may indicate one or more frequencies on which to measure a signal associated with a cell. As indicated by reference numeral 528, the RedCap UE 502 may detect a target cell, and as indicated by reference numeral 530, may determine whether the cell ID associated with the target cell is indicated in the first database 512. If the cell ID is indicated in the first database 512, then as indicated by reference numeral 532, the RedCap UE 502 may include measurements associated with the target cell in the measurement report.

[0110] If the cell ID is not indicated in the first database 512, then as indicated by reference numeral 534, the RedCap UE 502 may determine whether the cell ID is indicated in the second database 514. If the cell ID is indicated in the second database 514, then as indicated by reference numeral 536, the RedCap UE 502 may exclude measurements associated with the target cell from the measurement report. If the cell ID is not indicated in the second database 514, then as indicated by reference numeral 538, the RedCap UE 502 may determine whether the target cell is the best cell associated with the frequency. The best cell associated with the frequency may be the cell having the best associated signal quality or the highest associated signal power associated with that frequency.

[0111] If the target cell is the best cell associated with the frequency, as indicated by reference numeral 540, the RedCap UE 502 may include the measurements associated with the target cell in the measurement report. If the target cell is not the best cell associated with the frequency, as indicated by reference numeral 542, the RedCap UE 502 may receive the system information associated with the target cell, and as indicated by reference numeral 544, may determine whether the target cell supports the RedCap UE based on the system information. If the target cell supports the RedCap UE, as indicated by reference numeral 546, the RedCap UE 502 may add the cell ID to the first database 512, and as indicated by reference numeral 548, may include the measurements associated with the target cell in the measurement report. If the target cell does not support the RedCap UE, as indicated by reference numeral 550, the RedCap UE 502 may add the cell ID to the second database 514, and as indicated by reference numeral 552, may exclude the measurements associated with the target cell from the measurement report.

[0112] In some aspects, if the target cell is not the best cell associated with the frequency, the RedCap UE 502 may send a handover measurement report including the measurements associated with the target cell. When the RedCap UE 502 receives a handover trigger indication associated with the target cell, the RedCap UE 502 may avoid decoding the SIB associated with the target cell based on the target cell not being the best cell associated with the frequency.

[0113] As indicated above, Figure 5A and Figure 5B are provided as examples. Other examples may be different from the examples described for Figure 5A and Figure 5B which are different.

[0114] Figure 6 is a diagram illustrating an example process 600 performed by, for example, a RedCap UE in accordance with the present disclosure. The example process 600 is an example in which a RedCap UE (e.g., RedCap UE 402) performs operations associated with blind handover optimization for a RedCap UE.

[0115] As Figure 6 shown, in some aspects, process 600 may include: receiving a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell ID (block 610). For example, RedCap (e.g., using Figure 8The communication manager 808 and / or receiving component 802 depicted therein may receive a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell ID, as described above.

[0116] As Figure 6 shown, in some aspects, process 600 may include: components for performing wireless communication operations associated with a target cell based on whether the cell ID is indicated in a first database and a second database stored in the memory of the RedCap UE, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication (block 620). For example, the RedCap (e.g., using Figure 8 the communication manager 808, receiving component 802, and / or transmitting component 804 depicted therein) may perform wireless communication operations associated with the target cell based on whether the cell ID is indicated in the first database and the second database stored in the memory of the RedCap UE, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication, as described above.

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

[0118] In a first aspect, process 600 includes: receiving RedCap support information associated with at least one cell indicating that the at least one cell supports RedCap communication, and storing at least one RedCap support indication in a first database based on the RedCap support information. In a second aspect, separately or in combination with the first aspect, performing a wireless communication operation includes: initiating a RACH handover process associated with a target cell based on being indicated in the first database by a cell ID. In a third aspect, separately or in combination with one or more of the first and second aspects, a cell ID is indicated in a second database, and performing a wireless communication operation includes: declaring an early radio link failure and searching for a RedCap cell.

[0119] In a fourth aspect, separately or in combination with one or more of the first to third aspects, a cell ID is not indicated in either the first database or the second database, and performing a wireless communication operation includes: receiving system information associated with a target cell, where the system information includes RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication; and updating the first database or the second database based on the RedCap support information associated with the target cell. In a fifth aspect, separately or in combination with the fourth aspect, the RedCap support information associated with the target cell indicates that the target cell supports RedCap communication, and updating the first database or the second database includes: storing a RedCap support indication associated with the target cell in the first database. In a sixth aspect, separately or in combination with the fourth aspect, the RedCap support information associated with the target cell indicates that the target cell does not support RedCap communication, and updating the first database or the second database includes: storing a non-RedCap support indication associated with the target cell in the second database. In a seventh aspect, separately or in combination with the sixth aspect, process 600 includes: searching for a RedCap cell indicated by the first database based on the RedCap support information associated with the target cell indicating that the target cell does not support RedCap communication.

[0120] Although Figure 6 example boxes of process 600 are shown, in some aspects, process 600 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted in Figure 6 In addition, or alternatively, two or more of the boxes of process 600 may be performed in parallel.

[0121] Figure 7FIG. is an illustration of an example process 700 performed by a RedCap UE, for example, in accordance with the present disclosure. The example process 700 is an example in which a RedCap UE (e.g., RedCap UE 502) performs operations associated with measurement-based handover optimization for a RedCap UE.

[0122] As Figure 7 shown, in some aspects, process 700 may include: receiving configuration information associated with a measurement-based handover process (block 710). For example, a RedCap UE (e.g., using the communication manager 808 and / or the receiving component 802 depicted in Figure 8 may receive configuration information associated with a measurement-based handover process, as described above.

[0123] As Figure 7 further shown, in some aspects, process 700 may include: obtaining measurements associated with a target cell based on the configuration information (block 720). For example, a RedCap UE (e.g., using the communication manager 808 and / or the receiving component 802 depicted in Figure 8 may obtain measurements associated with a target cell based on the configuration information, as described above.

[0124] As Figure 7 shown, in some aspects, process 700 may include: components for performing wireless communication operations associated with a target cell based on the measurements satisfying measurement conditions and based on whether the cell ID is indicated in a first database and a second database stored in the memory of the RedCap UE, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication (block 730). For example, a RedCap UE (e.g., using Figure 8The communication manager 808, receiving component 802, and / or transmitting component 804 depicted therein may perform wireless communication operations associated with the target cell based on a measurement meeting a measurement condition and based on whether the cell ID is indicated in the first database of the first and second databases stored in the memory of the RedCap UE. The first database includes RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database includes non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication, as described above.

[0125] Procedure 700 may include additional aspects, such as any individual aspect or any combination of aspects described below and / or in connection with one or more other procedures described elsewhere herein.

[0126] In a first aspect, procedure 700 includes: receiving RedCap support information associated with at least one cell indicating that the at least one cell supports RedCap communication, and storing at least one RedCap support indication in the first database based on the RedCap support information. In a second aspect, separately or in combination with the first aspect, procedure 700 includes: transmitting a handover measurement report including measurements associated with a target cell based on a measurement meeting a measurement condition and based on the cell ID being indicated in the first database. In a third aspect, separately or in combination with the first aspect, procedure 700 includes: transmitting a handover measurement report omitting measurements associated with a target cell based on a measurement meeting a measurement condition and based on the cell ID being indicated in the second database.

[0127] In a fourth aspect, separately or in combination with the first aspect, procedure 700 includes: receiving system information associated with a target cell based on a measurement meeting a measurement condition and based on the cell ID being omitted from the first and second databases, the system information including RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication. In a fifth aspect, separately or in combination with the fourth aspect, procedure 700 includes: transmitting a handover measurement report omitting measurements associated with a target cell based on the target cell not supporting RedCap communication. In a sixth aspect, separately or in combination with the fourth aspect, procedure 700 includes: transmitting a handover measurement report including measurements associated with a target cell based on the target cell supporting RedCap communication.

[0128] In a seventh aspect, either alone or in combination with the first aspect, process 700 includes: determining that the target cell is not the best cell associated with the frequency; sending a handover measurement report including measurements associated with the target cell; receiving a handover trigger indication associated with the target cell, wherein the target cell is associated with the frequency; and avoiding decoding a system information block associated with the target cell based on the target cell not being the best cell associated with the frequency.

[0129] Although Figure 7 example boxes of process 700 are shown, in some aspects, process 700 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted in Figure 7 . Additionally or alternatively, two or more boxes of process 700 may be performed in parallel.

[0130] Figure 8 is a diagram of an example apparatus 800 for wireless communication in accordance with the present disclosure. Apparatus 800 may be a RedCap UE, or a RedCap UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may use receiving component 802 and transmitting component 804 to communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 800 may include a communication manager 808. Communication manager 808 may include one or more components, such as a memory component 810, a search component 812, and / or a determination component 814, etc.

[0131] In some aspects, apparatus 800 may be configured to perform one or more operations described herein in connection with FIGS. 4 and 5. Additionally or alternatively, apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 process 600 of Figure 7 process 700 of Figure 8 or a combination thereof. In some aspects, Figure 2 apparatus 800 and / or one or more components shown may include one or more components of the UE described in connection with Figure 8 . Additionally or alternatively, Figure 2 one or more components shown may be implemented within one or more components described in connection with . Additionally or alternatively, one or more components in a set of components may be at least partially implemented as software stored in a memory. For example, a component (or a part 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.

[0132] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 may perform signal processing on the received communications (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of the device 800. In some aspects, the receiving component 802 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with Figure 2 the one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with

[0133] The transmitting component 804 may send communications to the device 806, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing on the generated communications (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may send the processed signals to the device 806. In some aspects, the transmitting component 804 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with Figure 2 the one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with

[0134] In some examples, the components for transmitting, outputting, or conveying (or the components for outputting for transmission) may include one or more antennas, modulators, transmitting MIMO processors, transmitting processors, or combinations thereof of the UE described above in conjunction with Figure 2 the one or more antennas, modulators, transmitting MIMO processors, transmitting processors, or combinations thereof of the UE described above in conjunction with

[0135] In some examples, the components for receiving (or the components for obtaining) may include one or more antennas, demodulators, MIMO detectors, receiving processors, or combinations thereof of the UE described above in conjunction with Figure 2 the one or more antennas, demodulators, MIMO detectors, receiving processors, or combinations thereof of the UE described above in conjunction with

[0136] In some cases, the device may not actually send, for example, signals and / or data, but may have an interface (a component for output) for outputting signals and / or data for transmission. For example, a processor may output signals and / or data for transmission to an RF front-end via a bus interface. Similarly, the device may not actually receive signals and / or data, but may have an interface (a component for obtaining) for obtaining signals and / or data received from another device. For example, a processor may obtain (or receive) signals and / or data for reception from an RF front-end via a bus interface. In various aspects, the RF front-end may include various components, including, for example, the transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc. described in the examples in Figure 2 as described in the examples in

[0137] In some examples, the components for receiving, transmitting, providing, obtaining, communicating, and / or executing may include various processing system components of the UE described above in connection with Figure 2 such as a receive processor, a transmit processor, a controller / processor, a memory, or a combination thereof.

[0138] The communication manager 808 and / or the receive component 802 may receive a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell ID. In some aspects, the communication manager 808 may include one or more antennas, a modem, a controller / processor, a memory, or a combination thereof of the UE described in connection with Figure 2 In some aspects, the communication manager 808 may include the receive component 802 and / or the transmit component 804. In some aspects, the communication manager 808 may be, be similar to, include Figure 1 and Figure 2 the communication manager 140 depicted in

[0139] The communication manager 808, the receive component 802, and / or the transmit component 804 may perform wireless communication operations associated with the target cell based on whether the cell ID is indicated in the first database among a first database and a second database stored in the memory component 810, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication. In some aspects, the memory component 810 may include in connection with Figure 2One or more of the described UE's controller / processor, memory, or a combination thereof.

[0140] The communication manager 808 and / or the receiving component 802 may receive RedCap support information indicating that at least one cell supports RedCap communication, which is associated with at least one cell. The communication manager 808 and / or the memory component 810 may store at least one RedCap support indication in a first database based on the RedCap support information. The communication manager 808 and / or the search component 812 may search for RedCap cells indicated by the first database based on the RedCap support information associated with the target cell indicating that the target cell does not support RedCap communication. In some aspects, the search component 812 may include one or more antennas, modems, controller / processor, memory, or a combination thereof of the described UE. In some aspects, the search component 812 may include the receiving component 802 and / or the transmitting component 804. Figure 2 One or more antennas, modems, controller / processor, memory, or a combination thereof of the described UE. In some aspects, the search component 812 may include the receiving component 802 and / or the transmitting component 804.

[0141] The communication manager 808 and / or the receiving component 802 may receive configuration information associated with a measurement-based handover process. The communication manager 808 and / or the receiving component 802 may obtain measurements associated with the target cell based on the configuration information. The communication manager 808, the receiving component 802, and / or the transmitting component 804 may perform wireless communication operations associated with the target cell based on the measurements meeting measurement conditions and based on whether the cell ID is indicated in the first database of a first database and a second database stored in the memory component 810. The first database includes cell information supporting RedCap, and the cell information supporting RedCap includes at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication. The second database includes cell information not supporting RedCap, and the cell information not supporting RedCap includes at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0142] The communication manager 808 and / or the receiving component 802 may receive RedCap support information indicating that at least one cell supports RedCap communication and associated with at least one cell. The communication manager 808 and / or the memory component 810 may store at least one RedCap support indication in a first database based on the RedCap support information. The communication manager 808 and / or the transmitting component 804 may transmit a handover measurement report including measurements associated with a target cell based on the measurements meeting measurement conditions and being indicated in the first database based on the cell ID. The communication manager 808 and / or the transmitting component 804 may transmit a handover measurement report omitting measurements associated with the target cell based on the measurements meeting measurement conditions and being indicated in a second database based on the cell ID.

[0143] The communication manager 808 and / or the receiving component 802 may receive system information associated with a target cell, which includes RedCap support information indicating whether the target cell supports RedCap communication and associated with the target cell, based on the measurements meeting measurement conditions and being omitted from the first database and the second database based on the cell ID. The communication manager 808 and / or the transmitting component 804 may transmit a handover measurement report omitting measurements associated with the target cell based on the target cell not supporting RedCap communication. The communication manager 808 and / or the transmitting component 804 may transmit a handover measurement report including measurements associated with the target cell based on the target cell supporting RedCap communication.

[0144] The communication manager 808 and / or the determining component 814 may determine that the target cell is not the best cell associated with a frequency; transmit a handover measurement report including measurements associated with the target cell; receive a handover trigger indication associated with the target cell, where the target cell is associated with the frequency. In some aspects, the determining component 814 may include one or more antennas, a modem, a controller / processor, a memory of the UE as described Figure 2 or a combination thereof. In some aspects, the determining component 814 may include the receiving component 802 and / or the transmitting component 804. The communication manager 808 and / or the receiving component 802 may avoid decoding a system information block associated with the target cell based on the target cell not being the best cell associated with the frequency.

[0145] Figure 8 The number and arrangement of the components shown are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 8 those shown. Additionally, Figure 8 two or more of the components shown may be implemented within a single component, or Figure 8The individual components shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 8 a collection of the (one or more) components shown may perform one or more functions described to be performed by Figure 8 another collection of components shown.

[0146] Figure 9 is a diagram of an example apparatus 900 for wireless communication in accordance with the present disclosure. The apparatus 900 may be a network node, or a network node may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902 and a transmitting component 904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using the receiving component 902 and the transmitting component 904. As further shown, the apparatus 900 may include a communication manager 908.

[0147] In some aspects, the apparatus 900 may be configured to perform one or more operations described herein with reference to FIGS. 4 and 5. In some aspects, Figure 9 the apparatus 900 shown and / or one or more components may include one or more components of the network node described in connection with Figure 2 Additional or alternative Figure 9 one or more of the components shown may be implemented within one or more of the components described in connection with Figure 2 Additional or alternative, one or more components in a collection of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and that are executable by a controller or a processor to perform the functions or operations of the component.

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

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

[0150] In some examples, the components for transmitting, outputting, or conveying (or the components for outputting for transmission) can include one or more antennas, modulators, transmit MIMO processors, transmit processors, or combinations thereof of the network node described above in conjunction with Figure 2 In some examples, the components for receiving (or the components for obtaining) can include one or more antennas, demodulators, MIMO detectors, receive processors, or combinations thereof of the network node described above in conjunction with

[0151] In some cases, the device may not actually transmit, for example, signals and / or data, but may have an interface (component for output) for outputting signals and / or data for transmission. For example, the processor can output signals and / or data to the RF front end via a bus interface for transmission. Similarly, the device may not actually receive signals and / or data, but may have an interface (component for obtaining) for obtaining signals and / or data received from another device. For example, the processor can obtain (or receive) signals and / or data from the RF front end via a bus interface for reception. In various aspects, the RF front end can include various components, including transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc., such as those described in the examples in Figure 2 In some examples, the components for transmitting, receiving, obtaining, providing, communicating, and / or executing can include various processing system components of the network node described above in conjunction with

[0152] such as receive processors, transmit processors, controllers / processors, memories, or combinations thereof. Figure 2 In some examples, the components for transmitting, receiving, obtaining, providing, communicating, and / or executing can include various processing system components of the network node described above in conjunction with

[0153] such as receive processors, transmit processors, controllers / processors, memories, or combinations thereof. Figure 2 such as receive processors, transmit processors, controllers / processors, memories, or combinations thereof.

[0154] In some aspects, the communications manager 908 may be configured to perform, manage, control and / or otherwise facilitate any number of communications operations. In some aspects, the communications manager 908 may include a combination of Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the communication manager 908 may include a receiving component 902 and / or a sending component 904. In some aspects, the communication manager 908 may be, be similar to, or include Figure 1 and Figure 2 The communication manager 150 depicted in, or included in, the communication manager.

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

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

[0157] Aspect 1: A method for wireless communication performed by a reduced capability (RedCap) user equipment (UE), the method comprising: receiving a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell identifier (ID); and performing wireless communication operations associated with the target cell based on whether the cell ID is indicated in a first database and a second database stored in a memory of the RedCapUE, the first database including RedCap-supported cell information, the RedCap-supported cell information including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including non-RedCap-supported cell information, the non-RedCap-supported cell information including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0158] Aspect 2: The method according to Aspect 1, the method further comprising: receiving RedCap support information associated with the at least one cell indicating that the at least one cell supports RedCap communication; and storing the at least one RedCap support indication in the first database based on the RedCap support information.

[0159] Aspect 3: The method according to any one of claims 1 or 2, wherein performing the wireless communication operation comprises: initiating a random access channel (RACH) handover process associated with the target cell based on being indicated in the first database by the cell ID.

[0160] Aspect 4: The method according to any one of claims 1 or 2, wherein the cell ID is indicated in the second database, and wherein performing the wireless communication operation comprises: declaring an early radio link failure and searching for a RedCap cell.

[0161] Aspect 5: The method according to any one of claims 1 or 2, wherein the cell ID is not indicated in either the first database or the second database, and wherein performing the wireless communication operation comprises: receiving system information associated with the target cell, wherein the system information includes RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication; and updating the first database or the second database based on the RedCap support information associated with the target cell.

[0162] Aspect 6: The method according to Aspect 5, wherein the RedCap support information associated with the target cell indicates that the target cell supports RedCap communication, and wherein updating the first database or the second database comprises: storing a RedCap support indication associated with the target cell in the first database.

[0163] Aspect 7: The method according to Aspect 5, wherein the RedCap support information associated with the target cell indicates that the target cell does not support RedCap communication, and wherein updating the first database or the second database comprises: storing a non-RedCap support indication associated with the target cell in the second database.

[0164] Aspect 8: The method according to Aspect 7, the method further comprising: searching for a RedCap cell indicated by the first database based on the RedCap support information associated with the target cell indicating that the target cell does not support RedCap communication.

[0165] Aspect 9: A method of wireless communication performed by a Reduced Capability (RedCap) User Equipment (UE), the method comprising: receiving configuration information associated with a measurement-based handover process; obtaining measurements associated with a target cell based on the configuration information; and performing a wireless communication operation associated with the target cell based on the measurements meeting measurement conditions and based on whether the cell ID is indicated in a first database and a second database stored in the memory of the RedCap UE, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

[0166] Aspect 10: The method according to aspect 9, the method further comprising: receiving RedCap support information associated with the at least one cell indicating that the at least one cell supports RedCap communication; and storing the at least one RedCap support indication in the first database based on the RedCap support information.

[0167] Aspect 11: The method according to any one of claims 9 or 10, the method further comprising: based on the measurements meeting the measurement conditions and based on the cell ID being indicated in the first database, sending a handover measurement report including the measurements associated with the target cell.

[0168] Aspect 12: The method according to any one of claims 9 or 10, the method further comprising: based on the measurements meeting the measurement conditions and based on the cell ID being indicated in the second database, sending a handover measurement report omitting the measurements associated with the target cell.

[0169] Aspect 13: The method according to any one of claims 9 or 10, the method further comprising: based on the measurements meeting the measurement conditions and based on the cell ID being omitted from the first database and the second database, receiving system information associated with the target cell, the system information including RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication.

[0170] Aspect 14: The method according to aspect 13, the method further comprising: transmitting a handover measurement report omitting the measurement associated with the target cell based on the target cell supporting RedCap communication.

[0171] Aspect 15: The method according to aspect 13, the method further comprising: transmitting a handover measurement report including the measurement associated with the target cell based on the target cell supporting RedCap communication.

[0172] Aspect 16: The method according to any one of claims 9 or 10, the method further comprising: determining that the target cell is not the best cell associated with the frequency; transmitting a handover measurement report including the measurement associated with the target cell; receiving a handover trigger indication associated with the target cell, wherein the target cell is associated with a frequency; and avoiding decoding a system information block associated with the target cell based on the target cell not being the best cell associated with the frequency.

[0173] Aspect 17: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 8.

[0174] Aspect 18: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the memory including instructions for the one or more processors to cause the device to perform the method according to one or more of aspects 1 to 8.

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

[0176] Aspect 20: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 8.

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

[0178] Aspect 22: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of Aspects 1 to 8.

[0179] Aspect 23: An apparatus for wireless communication at a device, the apparatus including: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of Aspects 9 to 16.

[0180] Aspect 24: A device for wireless communication, including: a memory; and one or more processors coupled to the memory, the memory including instructions for the one or more processors to cause the device to perform the method according to one or more of Aspects 9 to 16.

[0181] Aspect 25: A device for wireless communication, the device including: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of Aspects 9 to 16.

[0182] Aspect 26: An apparatus for wireless communication, the apparatus including at least one component for performing the method according to one or more of Aspects 9 to 16.

[0183] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to one or more of Aspects 9 to 16.

[0184] Aspect 28: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of Aspects 9 to 16.

[0185] While the foregoing disclosure provides illustration and description, it 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 obtained from practice of these aspects.

[0186] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. Software should 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, processes, and / or functions, and other examples, whether referred to in software, firmware, middleware, microcode, hardware description language, or other terms. As used herein, a processor is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware and / or combinations of hardware and software. The actual specific control hardware or software code used to implement these systems and / or methods does not limit the various aspects. Thus, without reference to specific software code, the operation and performance of these systems and / or methods are described herein, and it should be understood that software and hardware can be designed to implement these systems and / or methods, at least in part, based on the description herein.

[0187] As used herein, depending on the context, "meeting a threshold" can 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, etc.

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

[0189] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Additionally, as used herein, the articles "a" and "an" are intended to include one or more items and may be interchangeable with "one or more." Further, as used herein, the article "the" is intended to include one or more items referred to in connection with the article "the" and may be interchangeable with "one or more." Additionally, as used herein, the terms "set" and "group" are intended to include one or more items and may be interchangeable with "one or more." If only one item is intended to be referred to, the phrase "only one" or similar language is used. Moreover, as used herein, the terms "having," "comprising," etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element "having" A may also have B). Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise explicitly stated. Additionally, as used herein, the term "or" when used in a series is intended to be open-ended and may be interchangeable with "and / or" unless otherwise explicitly stated (e.g., if used in conjunction with "either" or "only one").

Claims

1. A Reduced Capability (RedCap) User Equipment (UE) for wireless communication, the Reduced Capability (RedCap) User Equipment (UE) comprising: a memory; and one or more processors coupled to the memory, the memory including instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: receive a blind handover initiation communication indicating a frequency associated with at least one cell, the at least one cell including a target cell having an associated cell identifier (ID); and perform wireless communication operations associated with the target cell based on whether the cell ID is indicated in the first database of a first database and a second database stored in the memory, the first database including RedCap-enabled cell information, the RedCap-enabled cell information including at least one RedCap support indication indicating that the at least one cell supports RedCap communication associated with at least one cell, and the second database including non-RedCap-enabled cell information, the non-RedCap-enabled cell information including at least one non-RedCap support indication indicating that the at least one additional cell does not support RedCap communication associated with at least one additional cell.

2. The RedCap UE according to claim 1, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: receive RedCap support information indicating that the at least one cell supports RedCap communication associated with the at least one cell; and store the at least one RedCap support indication in the first database based on the RedCap support information.

3. The RedCap UE according to claim 1, wherein the instructions are executable by the one or more processors to cause the RedCap UE to perform the wireless communication operations, and the one or more processors cause the RedCap UE to initiate a Random Access Channel (RACH) handover procedure associated with the target cell based on the cell ID being indicated in the first database.

4. The RedCap UE according to claim 1, wherein the cell ID is indicated in the second database, and wherein the instructions executable by the one or more processors to cause the RedCap UE to perform the wireless communication operations are executable by the one or more processors to cause the RedCap UE to declare an early radio link failure and search for a RedCap cell.

5. The RedCap UE according to claim 1, wherein the cell ID is not indicated in either the first database or the second database, and the instructions executable by the one or more processors to cause the RedCap UE to perform the wireless communication operations are executable by the one or more processors to cause the RedCap UE to: receive system information associated with the target cell, wherein the system information includes RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication; and update the first database or the second database based on the RedCap support information associated with the target cell.

6. The RedCap UE according to claim 5, wherein the RedCap support information associated with the target cell indicates that the target cell supports RedCap communication, and the instructions executable by the one or more processors to cause the RedCap UE to update the first database or the second database are executable by the one or more processors to cause the RedCap UE to store a RedCap support indication associated with the target cell in the first database.

7. The RedCap UE according to claim 5, wherein the RedCap support information associated with the target cell indicates that the target cell does not support RedCap communication, and the instructions executable by the one or more processors to cause the RedCap UE to update the first database or the second database are executable by the one or more processors to cause the RedCap UE to store a non-RedCap support indication associated with the target cell in the second database.

8. The RedCap UE according to claim 7, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to: search for RedCap cells indicated by the first database based on the RedCap support information associated with the target cell indicating that the target cell does not support RedCap communication.

9. A reduced-capability (RedCap) user equipment (UE) for wireless communication, the reduced-capability (RedCap) user equipment (UE) comprising: a memory; and one or more processors coupled to the memory, the memory including instructions executable by the one or more processors to cause the RedCap UE to: receive configuration information associated with a measurement-based handover procedure; obtain measurements associated with a target cell based on the configuration information; and Perform wireless communication operations associated with the target cell based on the measurement satisfying the measurement conditions and based on whether the cell identifier (ID) associated with the target cell is indicated in the first database stored in the memory and in the first database among the first database and the second database, the first database includes RedCap-enabled cell information, the RedCap-enabled cell information includes at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database includes non-RedCap-enabled cell information, the non-RedCap-enabled cell information includes at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

10. The RedCap UE according to claim 9, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: Receive RedCap support information associated with the at least one cell indicating that the at least one cell supports RedCap communication; and Store the at least one RedCap support indication in the first database based on the RedCap support information.

11. The RedCap UE according to claim 9, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: Based on the measurement satisfying the measurement conditions and based on the cell ID being indicated in the first database, send a handover measurement report including the measurement associated with the target cell.

12. The RedCap UE according to claim 9, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: Based on the measurement satisfying the measurement conditions and based on the cell ID being indicated in the second database, send a handover measurement report omitting the measurement associated with the target cell.

13. The RedCap UE according to claim 9, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: Based on the measurement satisfying the measurement conditions and based on the cell ID being omitted from the first database and the second database, receive system information associated with the target cell, the system information including RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication.

14. The RedCap UE according to claim 13, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: sending a handover measurement report omitting the measurement associated with the target cell based on the target cell not supporting RedCap communication.

15. The RedCap UE according to claim 13, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: sending a handover measurement report including the measurement associated with the target cell based on the target cell supporting RedCap communication.

16. The RedCap UE according to claim 9, wherein the memory further includes instructions executable by the one or more processors to cause the RedCap UE to perform the following operations: Determine that the target cell is not the best cell associated with the frequency; Send a handover measurement report including the measurement associated with the target cell; Receive a handover trigger indication associated with the target cell, wherein the target cell is associated with the frequency; and Avoid decoding a system information block associated with the target cell based on the target cell not being the best cell associated with the frequency.

17. A method of wireless communication performed by a reduced-capability (RedCap) user equipment (UE), the method comprising: Receiving a blind handover initiation communication including a cell identifier (ID) associated with a target cell; And Performing wireless communication operations associated with the target cell based on whether the cell ID is indicated in a first database and a second database stored in the memory of the RedCap UE, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

18. The method according to claim 17, the method further comprising: Receiving RedCap support information associated with the at least one cell indicating that the at least one cell supports RedCap communication; And Storing the at least one RedCap support indication in the first database based on the RedCap support information.

19. The method according to claim 17, wherein performing the wireless communication operation comprises: Initiating a random access channel (RACH) handover procedure associated with the target cell based on the cell ID being indicated in the first database.

20. The method according to claim 17, wherein the cell ID is indicated in the second database, and wherein performing the wireless communication operation comprises: Declaring an early radio link failure and searching for a RedCap cell.

21. The method according to claim 17, wherein the cell ID is not indicated in either the first database or the second database, and wherein performing the wireless communication operation comprises: receiving system information associated with the target cell, wherein the system information includes RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication; and updating the first database or the second database based on the RedCap support information associated with the target cell.

22. The method according to claim 21, wherein the RedCap support information associated with the target cell indicates that the target cell supports RedCap communication, and wherein updating the first database or the second database comprises: Storing a RedCap support indication associated with the target cell in the first database.

23. The method according to claim 21, wherein the RedCap support information associated with the target cell indicates that the target cell does not support RedCap communication, and wherein updating the first database or the second database comprises: Storing a non-RedCap support indication associated with the target cell in the second database.

24. The method according to claim 23, the method further comprising: Searching for RedCap cells indicated by the first database based on the RedCap support information associated with the target cell indicating that the target cell does not support RedCap communication.

25. A method of wireless communication performed by a reduced-capability (RedCap) user equipment (UE), the method comprising: receiving configuration information associated with a measurement-based handover procedure; obtaining measurements associated with a target cell based on the configuration information; and performing a wireless communication operation associated with the target cell based on the measurements meeting measurement conditions and based on whether a cell identifier (ID) associated with the target cell is indicated in a first database stored in a memory of the RedCap UE and a second database, the first database including cell information supporting RedCap, the cell information supporting RedCap including at least one RedCap support indication associated with at least one cell indicating that the at least one cell supports RedCap communication, and the second database including cell information not supporting RedCap, the cell information not supporting RedCap including at least one non-RedCap support indication associated with at least one additional cell indicating that the at least one additional cell does not support RedCap communication.

26. The method according to claim 25, the method further comprising: receiving RedCap support information associated with the at least one cell indicating that the at least one cell supports RedCap communication; and storing the at least one RedCap support indication in the first database based on the RedCap support information.

27. The method according to claim 25, the method further comprising: Based on the measurements meeting the measurement conditions and based on the cell ID being indicated in the first database, sending a handover measurement report including the measurements associated with the target cell.

28. The method according to claim 25, the method further comprising: Based on the measurements meeting the measurement conditions and based on the cell ID being indicated in the second database, sending a handover measurement report omitting the measurements associated with the target cell.

29. The method according to claim 25, the method further comprising: Receiving system information associated with the target cell based on the measurement satisfying the measurement condition and being omitted from the first database and the second database based on the cell ID, where the system information includes RedCap support information associated with the target cell indicating whether the target cell supports RedCap communication.

30. The method according to claim 29, the method further comprising: Sending a handover measurement report including the measurement associated with the target cell based on the target cell supporting RedCap communication.

Images