CN117256177A

CN117256177A - Efficient Radio Resource Management Measurements for Reduced Capability User Equipment

Info

Publication number: CN117256177A
Application number: CN202280032595.1A
Authority: CN
Inventors: 何林海; 朱西鹏; L·F·B·洛佩斯
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-05-10
Filing date: 2022-05-02
Publication date: 2023-12-19

Abstract

Aspects of the present disclosure relate generally to wireless communications. In some aspects, a User Equipment (UE) may receive system information indicating whether one or more neighbor cells support access by UEs in a reduced capability class. The UE may perform one or more radio resource management measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information. Numerous other aspects are provided.

Description

Efficient radio resource management measurements for reduced capability user equipment

Cross Reference to Related Applications

This patent application claims priority from U.S. provisional patent application No.63/201,707 entitled "EFFICIENT RADIO RESOURCE MANAGEMENT MEASUREMENTS FOR REDUCED CAPABILITY USER EQUIPMENT" filed 5/10 in 2021 and U.S. non-provisional patent application No.17/661,525 entitled "EFFICIENT RADIO RESOURCE MANAGEMENT MEASUREMENTS FOR REDUCED CAPABILITY USER EQUIPMENT" filed 29 in 4/2022, which are hereby expressly incorporated by reference.

Technical Field

Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for efficient Radio Resource Management (RRM) measurements for reduced capability (RedCap) User Equipment (UE).

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, time Division Multiple Access (TDMA) systems, frequency Division Multiple Access (FDMA) systems, orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-advanced is an enhanced set of Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the third generation partnership project (3 GPP).

A wireless network may include one or more base stations that support communication for one User Equipment (UE) or multiple UEs. The UE may communicate with the base station via downlink and uplink communications. "downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.

The above multiple access techniques have been employed in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and/or global level. The New Radio (NR), which may be referred to as 5G, is an enhanced set of LTE mobile standards promulgated by 3 GPP. NR is designed to better integrate with other open standards by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), CP-OFDM and/or single carrier frequency division multiplexing (SC-FDM) on the uplink (also known as discrete fourier transform spread OFDM (DFT-s-OFDM)), and support beamforming, multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR and other radio access technologies remain useful.

Disclosure of Invention

In some aspects, a method of wireless communication performed by a User Equipment (UE) includes: receiving system information indicating whether one or more neighbor cells support access by UEs in a reduced capability (RedCap) class; and performing one or more Radio Resource Management (RRM) measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information.

In some aspects, a method of wireless communication performed by a network node comprises: receiving information indicating whether a neighbor cell supports access of a UE in a RedCap class; and transmitting system information indicating whether the neighbor cell supports access of the UE in the RedCap class.

In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: receiving system information indicating whether one or more neighbor cells support access for UEs in the RedCap class; and performing one or more RRM measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information.

In some aspects, a network node for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: receiving information indicating whether a neighbor cell supports access of a UE in a RedCap class; and transmitting system information indicating whether the neighbor cell supports access of the UE in the RedCap class.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receiving system information indicating whether one or more neighbor cells support access for UEs in the RedCap class; and performing one or more RRM measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: receiving information indicating whether a neighbor cell supports access of a UE in a RedCap class; and transmitting system information indicating whether the neighbor cell supports access of the UE in the RedCap class.

In some aspects, an apparatus for wireless communication comprises: means for receiving system information indicating whether one or more neighbor cells support access for UEs in the RedCap class; and means for performing one or more RRM measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information.

In some aspects, an apparatus for wireless communication comprises: means for receiving information indicating whether a neighbor cell supports access by a UE in a RedCap class; and means for transmitting system information indicating whether the neighbor cell supports access for UEs in the RedCap class.

Aspects include, in general terms, methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, network nodes, wireless communication devices, and/or processing systems as substantially described herein with reference to and as illustrated by the accompanying drawings and description.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described below. 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 features of the concepts disclosed herein (both as to their organization and method of operation) together with the associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purpose of illustration and description and is not intended as a definition of the limits of the claims.

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

Drawings

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

Fig. 1 is a schematic diagram illustrating an example of a wireless network according to the present disclosure.

Fig. 2 is a schematic diagram illustrating an example in which a base station communicates with a User Equipment (UE) in a wireless network according to the present disclosure.

Fig. 3 is a schematic diagram illustrating an example of a make-before-break handoff in accordance with the present disclosure.

Fig. 4 illustrates an example of a wireless network in which a UE may operate in one or more radio resource control communication modes in accordance with the present disclosure.

Fig. 5 is a schematic diagram illustrating an example associated with efficient Radio Resource Management (RRM) measurements for reduced capability (RedCap) UEs in accordance with the present disclosure.

Fig. 6-7 are diagrams illustrating example processes associated with efficient RRM measurements for a RedCap UE according to this disclosure.

Fig. 8-9 are block diagrams of example apparatuses for wireless communication according to the present disclosure.

Detailed Description

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

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

Although aspects may be described herein using terms commonly associated with 5G or New Radio (NR) Radio Access Technologies (RATs), aspects of the disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and/or RATs after 5G (e.g., 6G).

Fig. 1 is a schematic diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or include elements of a 5G (e.g., NR) network and/or a 4G (e.g., long Term Evolution (LTE)) network, among other examples. Wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110 d), user Equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120 e), and/or other network entities. Base station 110 is the entity in communication with UE 120. Base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, nodes B, eNB (e.g., in 4G), gnbs (e.g., in 5G), access points, and/or transmit-receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the third generation partnership project (3 GPP), the term "cell" can refer to a coverage area of a base station 110 and/or a base station subsystem serving the coverage area, depending on the context in which the term is used.

The base station 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. The pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs 120 having an association with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The base station 110 for a macro cell may be referred to as a macro base station. The base station 110 for a pico cell may be referred to as a pico base station. The base station 110 for a femto cell may be referred to as a femto base station or a home base station. In the example shown in fig. 1, BS110 a may be a macro base station for macro cell 102a, BS110b may be a pico base station for pico cell 102b, and BS110c may be a femto base station for femto cell 102 c. A base station may support one or more (e.g., three) cells.

In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the base station 110 (e.g., mobile base station) that is mobile. In some examples, base stations 110 may be interconnected with each other and/or with one or more other base stations 110 or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive data transmissions from an upstream station (e.g., base station 110 or UE 120) and send data transmissions to a downstream station (e.g., UE 120 or base station 110). The relay station may be a UE 120 capable of relaying transmissions for other UEs 120. In the example shown in fig. 1, BS110d (e.g., a relay base station) may communicate with BS110a (e.g., a macro base station) and UE 120d in order to facilitate communications between BS110a and UE 120 d. The base station 110 relaying communications may be referred to as a relay station, a relay base station, a relay, etc.

The wireless network 100 may be a heterogeneous network including different types of base stations 110 (such as macro base stations, pico base stations, femto base stations, relay base stations, etc.). These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different effects on interference in the wireless network 100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have a lower transmit power level (e.g., 0.1 to 2 watts).

The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. Base stations 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links.

UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a mobile station, and/or a subscriber unit. UE 120 may be a cellular telephone (e.g., a smart phone), a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, a super-book, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smartwristband, smart jewelry (e.g., a smartring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio, etc.), a vehicle component or sensor, a smart meter/sensor, an industrial manufacturing device, a global positioning system device, and/or any other suitable device configured to communicate via a wireless medium.

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

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

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

Devices of wireless network 100 may communicate using electromagnetic spectrum, which may be subdivided by frequency or wavelength into various categories, bands, channels, etc. For example, devices of wireless network 100 may communicate using one or more operating frequency bands. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be appreciated that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6GHz" frequency band in various documents and articles. Similar naming problems sometimes occur with respect to FR2, which is often (interchangeably) referred to in documents and articles as the "millimeter wave" band, although it is different from the Extremely High Frequency (EHF) band (30 GHz-300 GHz), which is identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

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

In view of the above examples, unless specifically stated otherwise, it should be understood that if the term "below 6GHz" or the like is used herein, it may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that if the term "millimeter wave" or the like is used herein, it may be broadly meant to include mid-band frequencies, frequencies that may be within FR2, FR4-a or FR4-1 and/or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4-a, FR4-1, and/or FR 5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

In some aspects, the term "base station" (e.g., base station 110) or "network node" or "network entity" may refer to an aggregated base station, a decomposed base station (e.g., as described in connection with fig. 9), an Integrated Access and Backhaul (IAB) node, a relay node, and/or one or more components thereof. For example, in some aspects, a "base station," "network node," or "network entity" may refer to a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (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," "network node," or "network entity" may refer to one device configured to perform one or more functions, such as those described herein in connection with base station 110. In some aspects, the term "base station," "network node," or "network entity" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or different geographic locations) may be configured to perform at least a portion of the functions or replicate the performance of at least a portion of the functions, and the terms "base station," "network node," or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station," "network node," or "network entity" may refer to one or more virtual base stations and/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," "network node," or "network entity" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

Deployment of a communication system, such as a 5G New Radio (NR) system, may be arranged in a number of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, mobility elements of a network, radio Access Network (RAN) nodes, core network nodes, network elements, base stations, or network devices may be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR Base Station (BS), 5G NB, gndeb (gNB), access Point (AP), transmission Reception Point (TRP), or cell) or one or more units (or one or more components) performing a base station function may be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a decomposed base station. A "network entity" or "network node" may refer to an decomposed base station or to one or more units of an decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

The aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). The decomposed base station may 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 aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as virtual units (e.g., virtual Central Units (VCUs), virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs)).

Base station type operation or network design may take into account the aggregate nature of the base station functions. For example, a split base station may be used in an Integrated Access Backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration sponsored by the O-RAN alliance), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)) to facilitate expansion of a communication system by separating base station functionality into one or more separately deployable units. A disaggregated base station may include functionality implemented across two or more units at various physical locations as well as functionality virtually implemented for at least one unit, which may enable flexibility in network design. Each unit of the base station may be configured for wired or wireless communication with at least one other unit of the base station.

In some aspects, base station 110 may serve UEs 120 in different categories associated with different capabilities. For example, base station 110 may serve one or more UEs 120 in a reduced capability (RedCap) category, which may include UEs 120 with less advanced capabilities. In some cases, UEs in the RedCap category may be referred to as RedCap UEs, NR-Lite UEs, low-end UEs, and the like. Additionally or alternatively, the base station 110 may serve one or more UEs 120 with higher-level capabilities (e.g., relative to UEs 120 in the RedCap class). In some cases, UEs 120 having higher-level capabilities than the RedCap UEs 120 may be referred to as advanced UEs, NR UEs, legacy UEs, advanced UEs, etc. (hereinafter, the term "advanced or legacy UEs" is often used). In some aspects, UEs 120 in the RedCap class may generally have a reduced feature set as compared to UEs 120 in the non-RedCap class (such as advanced or legacy UEs 120). For example, a lower maximum Modulation and Coding Scheme (MCS) may be supported (e.g., quadrature Phase Shift Keying (QPSK) as compared to 256 Quadrature Amplitude Modulation (QAM)) relative to advanced or legacy UEs 120,RedCap UE 120, lower transmit power may be supported, less advanced beamforming capabilities may be provided, a smaller maximum bandwidth may be provided, fewer antennas (e.g., transmit antennas and/or receive antennas) and/or antenna ports may be limited to half-duplex communications, and/or lower power levels may be provided. Thus, one consideration in deploying wireless network 100 is to compensate for UEs 120 with different capabilities. For example, base stations 110 serving UEs 120 with different capabilities may implement functionality to mitigate or limit performance degradation (e.g., potential coverage reduction) that may result from serving a RedCap UE 120 with reduced complexity.

In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, communication manager 140 may receive system information indicating whether one or more neighbor cells support access by UEs 120 in the RedCap class; and performing one or more Radio Resource Management (RRM) measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, a network node (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, communication manager 150 may receive information indicating whether a neighbor cell supports access by UEs 120 in the RedCap class; and transmitting system information indicating whether the neighbor cell supports access of the UE 120 in the RedCap class. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

As noted above, fig. 1 is provided as an example. Other examples may differ from the examples described with respect to fig. 1.

Fig. 2 is a schematic diagram illustrating an example 200 of a base station 110 in a wireless network 100 in communication with a UE 120 in accordance with the present disclosure. Base station 110 may be equipped with a set of antennas 234a through 234T, such as T antennas (T.gtoreq.1). UE 120 may be equipped with a set of antennas 252a through 252R, such as R antennas (r≡1).

At base station 110, transmit processor 220 may receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more Modulation and Coding Schemes (MCSs) for UE 120 based at least in part on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary Synchronization Signals (PSS) or Secondary Synchronization Signals (SSS)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232T. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream using a respective 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).

At UE 120, a set of antennas 252 (shown as antennas 252a through 252R) may receive downlink signals from base station 110 and/or other base stations 110 and a set of received signals (e.g., R received signals) may be provided to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254R). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal using a respective demodulator component to obtain input samples. Each modem 254 may use a demodulator assembly to further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain the received symbols from modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for UE 120 to a data sink 260, and may provide decoded control information and system information to controller/processor 280. The term "controller/processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of UE 120 may be included in housing 284.

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

The one or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252 r) may include or be included within: one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples. The antenna panel, antenna group, antenna element set, 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 one or more components of fig. 2).

On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information from controller/processor 280 (e.g., for reports including RSRP, RSSI, RSRQ and/or CQI). Transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, modem 254 of UE 120 may include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, and/or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller/processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., with reference to fig. 5-9).

At base station 110, uplink signals from UE 120 and other UEs may be received by antennas 234, processed by modems 232 (e.g., the demodulator components of modems 232, shown as DEMODs), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, modem 232 of base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modems 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 fig. 5-9).

The controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component in fig. 2 may perform one or more techniques associated with efficient Radio Resource Management (RRM) measurements for reduced capability (RedCap) UEs, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component in fig. 2 may perform or direct operations such as process 600 of fig. 6, process 700 of fig. 7, and/or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and/or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and/or UE 120 (e.g., directly, or after compilation, conversion, and/or interpretation), may cause the one or more processors, UE 120, and/or base station 110 to perform or direct operations such as process 600 of fig. 6, process 700 of fig. 7, and/or other processes as described herein. In some aspects, the execution instructions may include execution instructions, conversion instructions, compilation instructions, and/or interpretation instructions, among other examples.

In some aspects, UE 120 includes: means for receiving system information indicating whether one or more neighbor cells support access for UEs in the RedCap class; and/or means for performing one or more RRM measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information. The means for UE 120 to perform the operations described herein may include, for example, one or more of communications manager 140, antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller/processor 280, or memory 282.

In some aspects, a network node (e.g., base station 110) includes: means for receiving information indicating whether a neighbor cell supports access by a UE in a RedCap class; and/or means for transmitting system information indicating whether the neighbor cell supports access by UEs in the RedCap class. The means for base station 110 to perform the operations described herein may include, for example, one or more of communications manager 150, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

Although the blocks in fig. 2 are shown as distinct components, the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and/or TX MIMO processor 266 may be performed by or under the control of controller/processor 280.

As noted above, fig. 2 is provided as an example. Other examples may differ from the example described with respect to fig. 2.

Fig. 3 is a schematic diagram illustrating an example 300 of a make-before-break handoff in accordance with the present disclosure.

As shown in fig. 3, a Make Before Break (MBB) handover procedure may involve a UE 305, a source base station 310, a target base station 315, a User Plane Function (UPF) device 320, and an access and mobility management function (AMF) device 325.UE 305 may correspond to UE 120 described elsewhere herein. The source base station 310 and/or the target base station 315 may correspond to the base station 110 described elsewhere herein. The UPF devices 320 and/or AMF devices 325 may correspond to the network controller 130 described elsewhere herein. The UE 305 and the source base station 310 may be connected via a serving cell or source cell (e.g., may have a Radio Resource Control (RRC) connection), and the UE 305 may perform a handover to the target base station 315 via the target cell. The UPF devices 320 and/or AMF devices 325 may be located within a core network. The source base station 310 and the target base station 315 may communicate with the core network to implement mobility support and user plane functions. The MBB handover procedure may include an enhanced MBB (eMBB) handover procedure.

As shown, the MBB handover procedure may include a handover preparation phase 330, a handover execution phase 335, and a handover completion phase 340. During the handover preparation phase 330, the UE 305 may perform one or more Radio Resource Management (RRM) measurements on the source base station 310 and/or one or more neighbor base stations (e.g., including the target base station 315), and may report RRM measurements that prepare the source base station 310 and/or the target base station 315 for the handover and trigger performance of the handover. During the handover execution phase 335, the UE 305 may perform a handover by performing a random access procedure with the target base station 315 and establishing an RRC connection with the target base station 315. During the handover complete phase 340, the source base station 310 may forward the store communication associated with the UE 305 to the target base station 315 and the UE 305 may release from the connection with the source base station 310.

As indicated by reference numeral 345, the UE 305 may perform one or more RRM measurements and may send a measurement report to the source base station 310 based at least in part on performing the one or more measurements (e.g., serving cell measurements and/or neighbor cell measurements). The measurement report may indicate, for example, RSRP parameters, RSRQ parameters, RSSI parameters, and/or signal-to-interference plus noise ratio (SINR) parameters (e.g., for the serving cell and/or one or more neighbor cells). The source base station 310 may use the measurement report to determine whether to trigger a handover to the target base station 315. For example, the source base station 310 may trigger a handover of the UE 305 to the target base station 315 if one or more measurements satisfy a condition (e.g., the RSRP measurement associated with the target base station 315 satisfies a threshold and/or exceeds the RSRP measurement associated with the source base station 310).

As indicated by reference numeral 350, the source base station 310 and the target base station 315 may communicate with each other to prepare for a handover of the UE 305. As part of the handover preparation, the source base station 310 may send a handover request to the target base station 315 to indicate that the target base station 315 is ready for handover. The source base station 310 may transmit RRC context information associated with the UE 305 and/or configuration information associated with the UE 305 to the target base station 315. The target base station 315 may prepare for the handover by reserving resources for the UE 305. After reserving the resources, the target base station 315 may send an Acknowledgement (ACK) to the source base station 310 in response to the handover request.

As indicated by reference numeral 355, the source base station 310 may send an RRC reconfiguration message to the UE 305. The RRC reconfiguration message may include a handover command that instructs the UE 305 to perform a handover procedure from the source base station 310 to the target base station 315. The handover command may include information associated with the target base station 315, such as a Random Access Channel (RACH) preamble assignment for accessing the target base station 315. Receipt of an RRC reconfiguration message including a handover command by the UE 305 may trigger the start of the handover execution phase 335.

As indicated by reference numeral 360, during a handover execution phase 335 of the MBB handover, the UE 305 may perform the handover by performing a random access procedure with the target base station 315 (e.g., including synchronization with the target base station 315) while continuing to communicate with the source base station 310. For example, when the UE 305 is performing a random access procedure with the target base station 315, the UE 305 may transmit uplink data, uplink control information, and/or uplink reference signals (e.g., sounding reference signals) to the source base station 310, and/or may receive downlink data, downlink control information, and/or downlink reference signals from the source base station 310.

As indicated by reference numeral 365, after successfully establishing a connection with the target base station 315 (e.g., via a random access procedure), the UE may send an RRC reconfiguration complete message to the target base station 315. Receipt of the RRC reconfiguration message by the target base station 315 may trigger the start of the handover complete phase 340.

As indicated by reference numeral 370, the source base station 310 and the target base station 315 may communicate with each other in preparation for releasing the connection between the source base station 310 and the UE 305. In some aspects, the target base station 315 may determine that the connection between the source base station 310 and the UE 305 is to be released, such as after receiving an RRC reconfiguration complete message from the UE 305. In this case, the target base station 315 may transmit a handover connection setup complete message to the source base station 310. The handover connection setup complete message may cause the source base station 310 to cease transmitting data to the UE 305 and/or to cease receiving data from the UE 305. Additionally or alternatively, the handover connection setup complete message may cause the source base station 310 to forward communications associated with the UE 305 to the target base station 315 and/or to notify the target base station 315 of the status of one or more communications with the UE 305. For example, the source base station 310 may forward buffered downlink communications (e.g., downlink data) for the UE 305 and/or uplink communications (e.g., uplink data) received from the UE 305 to the target base station 315. Additionally or alternatively, the source base station 310 can inform the target base station 315 of a Packet Data Convergence Protocol (PDCP) status associated with the UE 305 and/or a sequence number to be used for downlink communication with the UE 305.

As indicated by reference numeral 375, the target base station 315 may send an RRC reconfiguration message to the UE 305 to instruct the UE 305 to release the connection with the source base station 310. Upon receiving the instruction to release the connection with the source base station 310, the UE 305 may stop communicating with the source base station 310. For example, the UE 305 may refrain from transmitting uplink communications to the source base station 310 and/or may refrain from monitoring downlink communications from the source base station 310.

As indicated by reference numeral 380, the UE may send an RRC reconfiguration complete message to the target base station 315 to indicate that the connection between the source base station 310 and the UE 305 is being released or has been released.

As indicated by reference numeral 385, the target base station 315, the UPF device 320, and/or the AMF device 325 may communicate to hand over the user plane path of the UE 305 from the source base station 310 to the target base station 315. Downlink communications for the UE 305 may be routed through the core network to the source base station 310 prior to switching user plane paths. After switching the user plane path, downlink communications for the UE 305 may be routed through the core network to the target base station 315. Upon completion of the user plane path switch, the AMF device 325 may send an end marker message to the source base station 310 to signal completion of the user plane path switch. As indicated by reference numeral 390, the target base station 315 and the source base station 310 may communicate to release the source base station 310.

As part of the MBB handover procedure, the UE 305 may remain connected with the source base station 310 and the target base station 315 simultaneously during a period 395. When the UE 305 performs a random access procedure with the target base station 315, the period 395 may begin at the beginning of the handover execution phase 335 (e.g., when the UE 305 receives a handover command from the source base station 310). The period 395 may end when the connection between the UE 305 and the source base station 310 is released (e.g., when the UE 305 receives an instruction from the target base station 315 to release the source base station 310). By maintaining simultaneous connections with the source base station 310 and the target base station 315, the handoff procedure may be performed with zero or minimal interruption to communications, thereby reducing latency.

As noted above, fig. 3 is provided as an example. Other examples may differ from the example described with respect to fig. 3.

Fig. 4 illustrates an example 400 of a wireless network (e.g., wireless network 100) in which a UE (e.g., UE 120) may operate in one or more RRC communication modes in accordance with the present disclosure. The UE may be communicatively connected with a source base station in a wireless network. Further, in some aspects, the UE may be located within or near the coverage area of one or more neighbor base stations.

As shown in fig. 4, a UE may support a connected communication mode (e.g., RRC active mode 402), an idle communication mode (e.g., RRC idle mode 404), and an inactive communication mode (e.g., RRC inactive mode 406). The RRC inactive mode 406 may be functionally located between the RRC active mode 402 and the RRC idle mode 404.

The UE may transition between different modes based at least in part on various commands and/or communications received from the source base station. For example, the UE may transition from RRC active mode 402 or RRC inactive mode 406 to RRC idle mode 404 based at least in part on receiving an RRCRelease communication from the source base station. As another example, the UE may transition from the RRC active mode 402 to the RRC inactive mode 406 based at least in part on receiving an RRCRelease communication with a supensconfig from the source base station. As another example, the UE may transition from the RRC idle mode 404 to the RRC active mode 402 based at least in part on receiving an rrcsetup request communication from the source base station. As another example, the UE may transition from RRC inactive mode 406 to RRC active mode 402 based at least in part on receiving an rrcresmerequest communication from the source base station.

When transitioning to the RRC inactive mode 406, the UE and/or the source base station may store UE context (e.g., access Stratum (AS) context and/or higher layer configuration). This allows the UE and/or the source base station to apply the stored UE context when the UE transitions from the RRC inactive mode 406 to the RRC active mode 402 in order to resume communication with the source base station, which reduces the latency of the transition to the RRC active mode 402 relative to the transition from the RRC idle mode 404 to the RRC active mode 402. Additionally or alternatively, the source base station may provide stored UE context to the neighbor base stations to facilitate handover for the UE, as described in further detail elsewhere herein.

In some cases, the UE may be communicatively connected with the new source base station when transitioning from the RRC idle mode 404 or the RRC inactive mode 406 to the RRC active mode 402 (e.g., the UE may perform a cell reselection to a neighbor base station if one or more RRM measurements associated with the source base station or the neighbor base station satisfy the condition).

In all RRC states, the UE may periodically perform RRM measurements on one or more neighbor cells. For example, in some aspects, the source base station may transmit a System Information Block (SIB) indicating a set of neighbor cells associated with the source base station, and when the UE is in RRC active mode 402, RRC idle mode 404, RRC inactive mode 406, or any other suitable RRC mode, the UE may perform RRM measurements on the set of neighbor cells indicated in the SIB. For example, the neighbor cell set may be indicated in SIB2 (which contains parameters related to intra-frequency, inter-frequency and/or inter-RAT cell reselection), in SIB3 (which contains only parameters related to intra-frequency cell reselection), in SIB4 (which contains only parameters related to inter-frequency cell reselection) and/or in SIB5 (which contains only parameters related to inter-RAT cell reselection). In this case, when the UE is in the RRC idle mode 404 or the RRC inactive mode 406, the UE may reselect a neighbor cell associated with the neighbor base station to a new serving cell based on one or more RRM measurements meeting a condition (e.g., when the RSRP measurement associated with the neighbor base station meets a threshold and/or exceeds the RSRP measurement associated with the source base station, as well as other examples).

Additionally or alternatively, in the RRC active mode 402, the source base station may provide a measurement configuration to the UE, and the measurement configuration may indicate one or more neighbor cells to be measured by the UE and/or frequencies of one or more neighbor cells indicated in the measurement configuration to be measured by the UE. Thus, in the RRC active mode 402, the UE may send measurement reports to the source base station periodically, on demand, and/or based on a trigger event (e.g., RSRP measurements associated with one or more neighbor cells meet a configured threshold). In some aspects, as described herein, a source cell (e.g., a source base station) may decide whether and/or when to facilitate a handover of a UE to a new serving cell (e.g., a target cell provided by a neighbor base station) based on measurement reports provided by the UE.

Thus, as described herein, a UE may perform (e.g., obtain) and report RRM measurements in all RRC states in order to support mobility and improved performance for the UE (e.g., to determine whether to perform cell reselection to a neighbor cell in RRC idle mode 404 or RRC inactive mode 406, and/or to determine whether to initiate a handover to a neighbor cell in RRC active mode 402, which may provide better performance than the UE is experiencing in the source cell). However, performing RRM measurements on one or more neighbor cells may result in inefficiency in cases where the UE is in a reduced capability (RedCap) category. For example, as described herein, a RedCap UE may support a lower maximum MCS (e.g., quadrature Phase Shift Keying (QPSK) as compared to 256 Quadrature Amplitude Modulation (QAM)), may support lower transmit power, may have less advanced beamforming capabilities, may have less maximum bandwidth, may have fewer antennas (e.g., transmit antennas and/or receive antennas) and/or antenna ports, may be limited to half-duplex communications, and/or may have lower power levels relative to advanced or legacy UEs.

Thus, in some cases, the base station may implement functionality to mitigate or limit performance degradation (e.g., potential coverage reduction) that may result from serving the RedCap UE, which may require more network resources to serve due to limited capabilities. For example, in the case of a RedCap UE having one (1) receive antenna, there may be at least a 6 decibel (dB) loss in the link budget. To compensate for the loss in link budget, the base station serving the RedCap UE may use multiple repetitions for downlink transmissions to the RedCap UE to ensure that the RedCap UE has the same coverage as a non-RedCap (e.g., advanced or legacy) UE. Thus, separately from the non-RedCap UE, the base station may prohibit the RedCap UE from accessing the cell provided by the base station. For example, when the cell load increases, the base station may block the RedCap UE from accessing the cell, whereby cell barring for the RedCap UE may be more dynamic (e.g., change more frequently) than for non-RedCap legacy UEs. Thus, in the case where the RedCap UE performs RRM measurements on one or more neighbor cells, performing RRM measurements (e.g., by increasing power consumption) on neighbor cells that do not support access by the RedCap UE (e.g., temporarily or permanently prohibiting access by the RedCap UE to the neighbor cells) wastes limited resources of the RedCap UE. Furthermore, inefficiencies (e.g., increased handover latency and/or signaling overhead) may occur if the source cell is to initiate a handover of the RedCap UE to a target cell that does not support access by the RedCap UE. For example, a target cell that does not support access by a RedCap UE may reject a handover request from a source cell, which then must attempt to initiate a handover to a different target cell, which may also reject the handover request if another target cell does not support access by a RedCap UE.

Some aspects described herein relate to techniques and apparatus for increasing efficiency of RRM measurements by a RedCap UE. For example, a cell (e.g., a base station) in the wireless network may exchange information with neighbor cells to indicate whether the respective cell supports access by the RedCap UE (e.g., allows the RedCap UE to access the cell) or does not support access by the RedCap UE (e.g., temporarily or permanently prohibits the RedCap UE from accessing the cell). Each cell may send system information to indicate whether the neighbor cell supports or prohibits access by the RedCap UE so that the RedCap UE may determine whether to measure the neighbor cell in RRC idle mode 404 or RRC inactive mode 406 (e.g., the RedCap UE may refrain from measuring or attempting to perform cell reselection to neighbor cells that do not support access by the RedCap UE). Additionally or alternatively, the measurement configuration provided by the cell to the RedCap UE in RRC active mode 402 may exclude any neighbor cells that do not support access by the RedCap UE, such that the RedCap UE does not measure neighbor cells that do not support access by the RedCap UE in RRC active mode 402. Furthermore, the serving cell of the RedCap UE may exclude any neighbor cells that do not support access of the RedCap UE from the handover decision of the RedCap UE. In this way, the RedCap UE may save resources that would otherwise be wasted on neighbor cells that do not support access by the RedCap UE and/or reduce signaling overhead and handover latency by excluding neighbor cells that do not support access by the RedCap UE from measurement and/or handover decisions in the RRC active mode 402.

As noted above, fig. 4 is provided as an example. Other examples may differ from the example described with respect to fig. 4.

Fig. 5 is a schematic diagram illustrating an example 500 associated with efficient RRM measurements for a RedCap UE in accordance with the present disclosure. As shown in fig. 5, example 500 includes communication between a UE (e.g., UE 120) and a serving base station (e.g., base station 110) and communication between a serving base station and a neighbor base station (e.g., base station 110). In some aspects, the UE, serving base station, and neighbor base stations may be included in a wireless network (such as wireless network 100). The serving base station and the UE may communicate via a wireless access link, which may include an uplink and a downlink. Further, the serving base station and the neighbor base stations may communicate via backhaul links, such as operations, administration and management (OAM) interfaces or inter-node messaging interfaces (e.g., an F1 interface, an NG interface, and/or an Xn interface). In some aspects, as described herein, the UE may be a RedCap UE, the serving base station may be referred to as a serving cell, and the neighbor base station may be referred to as a neighbor cell.

As in fig. 5 and shown by reference numeral 510, a cell in a wireless network may exchange information indicating whether access by a RedCap UE is supported (e.g., allowed) or not supported (e.g., temporarily or permanently restricted). For example, as shown, a serving cell associated with the UE may transmit and a neighbor cell may receive (e.g., via an OAM or inter-node messaging interface) information indicating whether the serving cell supports access by the RedCap UE. Further, the neighbor cell may transmit and the serving cell may receive (e.g., via an OAM or inter-node messaging interface) information indicating whether the neighbor cell supports access by the RedCap UE. In some aspects, a cell may generally transmit information indicating whether access of a RedCap UE is supported or not supported based on a change in settings related to whether access of the RedCap UE is supported or not supported. For example, when there is a change from supporting access to a non-supporting RedCap UE or a change from non-supporting access to a supporting RedCap UE, the serving cell and/or neighbor cell may send information to announce whether access to the RedCap UE is supported or not. In this way, each cell in the wireless network may be aware of whether each neighbor cell currently supports or does not support access for the RedCap UE, such that system information and/or measurement configuration may be configured to enable more efficient RRM measurements for the RedCap UE and/or more efficient handover decisions for the RedCap UE.

For example, as shown by reference numeral 520, the serving cell may transmit and the UE may receive system information and/or measurement configuration based at least in part on support for access to the RedCap UE in one or more neighbor cells. For example, the serving cell may transmit a SIB identifying a set of neighbor cells associated with the serving cell, and the SIB may further indicate whether each neighbor cell supports or does not support access by the RedCap UE. In some aspects, the SIB indicating whether the neighbor cell supports or does not support access by the RedCap UE may be a SIB containing information related to cell reselection parameters applicable to the RedCap UE. For example, the SIB indicating whether the neighbor cell supports or does not support access by the RedCap UE may be SIB2 (which contains parameters related to intra-frequency, inter-frequency and/or inter-RAT cell reselection), SIB3 (which contains only parameters related to intra-frequency cell reselection), or SIB4 (which contains only parameters related to inter-frequency cell reselection). In this way, when the UE performs RRM measurement in the RRC idle mode or the RRC inactive mode, the UE may identify any neighbor cells that do not support access of the RedCap UE based on the system information received from the serving cell, and avoid performing RRM measurement on such neighbor cells. In other words, when the UE performs RRM measurement in the RRC idle mode or the RRC inactive mode, system information indicating whether the neighbor cell supports or does not support access of the RedCap UE may enable the UE to measure only one or more neighbor cells supporting access of the RedCap UE. In this way, the UE may avoid wasting resources for measuring or attempting to perform cell reselection to neighbor cells that do not support access by the RedCap UE.

Additionally or alternatively, when the UE is in RRC connected or active mode, the serving cell may transmit a measurement configuration identifying one or more neighbor cells on which the UE is to perform RRM measurements. In this case, the serving cell may exclude from the measurement configuration any neighbor cells that do not support access for the RedCap UE. In other words, the measurement configuration provided to the UE in RRC connected or active mode may include only one or more neighbor cells supporting access of the RedCap UE, so that the UE may avoid wasting resources for measuring or attempting to perform handover to neighbor cells not supporting access of the RedCap UE. Furthermore, the serving cell may exclude any neighbor cells that do not support access for the RedCap UE from handover decisions for UEs in the RedCap category.

As shown in fig. 5 and further by reference numeral 530, the UE may perform one or more RRM measurements on one or more neighbor cells based on system information or measurement configuration received from the serving base station. For example, in RRC idle or inactive mode, the UE may identify the neighbor cell set in system information received from the serving cell (e.g., in SIB2, SIB3, or SIB 4). As described above, the system information may indicate whether each neighbor cell supports or does not support access by the RedCap UE. Thus, when performing RRM measurements in RRC idle or inactive mode, the UE may perform RRM measurements on one or more neighbor cells supporting access by the RedCap UE and may avoid performing RRM measurements on any neighbor cells not supporting access by the RedCap UE. In this way, indicating in the system information whether the neighbor cell supports or does not support access for the RedCap UE may enable the UE to save resources that might otherwise be wasted on measuring neighbor cells that do not support access for the RedCap UE and/or performing cell reselection to neighbor cells that do not support access for the RedCap UE.

Additionally or alternatively, in RRC connected or active mode, the UE may determine one or more neighbor cells to measure based on a measurement configuration provided by the serving cell. In this case, as described above, the measurement configuration may exclude any neighbor cells that do not support access of the RedCap UE. Thus, when performing RRM measurements in RRC connected or active mode, the UE may perform RRM measurements only on neighbor cells supporting access by the RedCap UE. In this way, excluding neighbor cells that do not support access for the RedCap UE from the measurement configuration may enable the UE to save resources that might otherwise be wasted measuring neighbor cells that do not support access for the RedCap UE and/or attempting to initiate a handover to neighbor cells that do not support access for the RedCap UE.

As noted above, fig. 5 is provided as an example. Other examples may differ from the example described with respect to fig. 5.

Fig. 6 is a schematic diagram illustrating an example process 600 performed, for example, by a UE, in accordance with the present disclosure. Example process 600 is an example in which a UE (e.g., UE 120) performs operations associated with efficient RRM measurements for a RedCap UE.

As shown in fig. 6, in some aspects, process 600 may include: system information is received indicating whether one or more neighbor cells support access for UEs in the RedCap class (block 610). For example, the UE (e.g., using the communication manager 140 and/or the receiving component 802 depicted in fig. 8) may receive system information indicating whether one or more neighbor cells support access for UEs in the RedCap class, as described above.

As further shown in fig. 6, in some aspects, process 600 may include: one or more RRM measurements are performed on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information or measurement configuration (block 620). For example, the UE (e.g., using the communication manager 140 and/or the measurement component 808 depicted in fig. 8) may perform one or more RRM measurements on one or more neighbor cells identified as supporting access for the UE in the RedCap category based at least in part on the system information or measurement configuration, as described above.

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.

In a first aspect, system information is received in a SIB containing information related to cell reselection parameters.

In a second aspect, alone or in combination with the first aspect, the SIB is SIB2, SIB3 or SIB4.

In a third aspect, alone or in combination with one or more of the first and second aspects, the process 600 includes: a measurement configuration is received, wherein one or more neighbor cells on which to perform one or more RRM measurements are identified based at least in part on the measurement configuration.

In a fourth aspect, alone or in combination with one or more aspects of the first to third aspects, the measurement configuration excludes any neighbor cells that do not support access by UEs in the RedCap class.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the process 600 includes: determining at least one neighbor cell that does not support access for UEs in the RedCap class based at least in part on the system information; and avoiding performing RRM measurements on at least one neighbor cell that does not support access for UEs in the RedCap class.

While fig. 6 shows example blocks of process 600, in some aspects process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in fig. 6. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

Fig. 7 is a schematic diagram illustrating an example process 700 performed, for example, by a base station, in accordance with the present disclosure. The example process 700 is an example in which a base station (e.g., the base station 110) performs operations associated with efficient RRM measurements for a RedCap UE.

As shown in fig. 7, in some aspects, process 700 may include: information is received indicating whether the neighbor cell supports access for UEs in the RedCap class (block 710). For example, the base station (e.g., using the communication manager 150 and/or the receiving component 902 depicted in fig. 9) can receive information indicating whether the neighbor cell supports access for UEs in the RedCap class, as described above.

As further shown in fig. 7, in some aspects, process 700 may include: system information indicating whether the neighbor cell supports access by UEs in the RedCap class is transmitted (block 720). For example, the base station (e.g., using the communication manager 150 and/or the transmitting component 904 depicted in fig. 9) may transmit system information indicating whether the neighbor cell supports access for UEs in the RedCap class, as described above.

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

In a first aspect, information indicating whether a neighbor cell supports access by a UE in a RedCap class is received based at least in part on a neighbor cell changing a setting related to whether a neighbor cell supports access by a UE in a RedCap class.

In a second aspect, information indicating whether or not a neighbor cell supports access by a UE in the RedCap class is received via an OAM interface or inter-node messaging, alone or in combination with the first aspect.

In a third aspect, alone or in combination with one or more of the first and second aspects, the system information is transmitted in a SIB containing information related to the cell reselection parameters.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the SIB is SIB2, SIB3 or SIB4.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the process 700 includes: the method includes transmitting, to a UE in a RedCap class, a measurement configuration including one or more neighbor cells on which the UE is to perform radio resource management measurements based at least in part on information indicating whether the neighbor cells support access by the UE in the RedCap class.

In a sixth aspect, alone or in combination with one or more aspects of the first to fifth aspects, the measurement configuration excludes the neighbor cell based at least in part on an indication that the neighbor cell does not support access by UEs in the RedCap class.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the process 700 includes: the neighbor cells are excluded from the candidate set of target cells for handover of the UE in the RedCap class based at least in part on an indication that the neighbor cells do not support access by the UE in the RedCap class.

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

Fig. 8 is a block diagram of an example apparatus 800 for wireless communication. The apparatus 800 may be a UE, or the UE may include the apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 800 can communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using a receiving component 802 and a transmitting component 804. As further shown, the apparatus 800 may include a communication manager 140. The communications manager 140 may include one or more of a measurement component 808 or a determination component 810, as well as other examples.

In some aspects, apparatus 800 may be configured to perform one or more operations described herein in connection with fig. 5. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of fig. 6. In some aspects, the apparatus 800 and/or one or more components shown in fig. 8 may include one or more components of the UE described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 8 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 802 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 806. The receiving component 802 can provide the received communication to one or more other components of the apparatus 800. In some aspects, the receiving component 802 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, among other examples) on the received communication and can provide the processed signal to one or more other components of the apparatus 800. In some aspects, the receiving component 802 can include one or more antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof for a UE as described in connection with fig. 2.

The transmitting component 804 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 806. In some aspects, one or more other components of apparatus 800 may generate a communication and may provide the generated communication to sending component 804 for transmission to apparatus 806. In some aspects, the transmitting component 806 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication, and can transmit the processed signal to the device 806. In some aspects, the transmit component 804 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the UE described in connection with fig. 2. In some aspects, the transmitting component 804 may be co-located with the receiving component 802 in a transceiver.

The receiving component 802 can receive system information indicating whether one or more neighbor cells support access for UEs in the RedCap class. The measurement component 808 can perform one or more RRM measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information.

The receiving component 802 can receive the measurement configuration and the measuring component 808 can identify one or more neighbor cells on which to perform one or more RRM measurements based at least in part on the measurement configuration.

The determining component 810 may determine at least one neighbor cell that does not support access for a UE in the RedCap class based at least in part on the system information. The measurement component 808 can refrain from performing RRM measurements on at least one neighbor cell that does not support access for UEs in the RedCap class.

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

Fig. 9 is a block diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a base station or the base station may include the apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using a receiving component 902 and a transmitting component 904. As further shown, apparatus 900 may include a communication manager 150. The communications manager 150 can include a switching component 908, as well as other examples.

In some aspects, apparatus 900 may be configured to perform one or more operations described herein in connection with fig. 5. Additionally or alternatively, apparatus 900 may be configured to perform one or more processes described herein, such as process 700 of fig. 7. In some aspects, the apparatus 900 and/or one or more components shown in fig. 9 may include one or more components of a base station described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 9 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 902 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the apparatus 906. The receiving component 902 can provide the received communication to one or more other components of the apparatus 900. In some aspects, the receiving component 902 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, among other examples) on the received communication and can provide the processed signal to one or more other components of the apparatus 900. In some aspects, the receiving component 902 can include one or more antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof for a base station described in connection with fig. 2.

The transmitting component 904 can transmit a communication, such as a reference signal, control information, data communication, or a combination thereof, to the device 906. In some aspects, one or more other components of apparatus 900 may generate a communication and may provide the generated communication to sending component 904 for transmission to apparatus 906. In some aspects, the sending component 906 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and can send the processed signal to the device 906. In some aspects, the transmit component 904 can include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the base station described in connection with fig. 2. In some aspects, the transmitting component 904 may be co-located with the receiving component 902 in a transceiver.

The receiving component 902 may receive information indicating whether a neighbor cell supports access for UEs in the RedCap class. The transmitting component 904 may transmit system information indicating whether the neighbor cell supports access for UEs in the RedCap class.

The transmitting component 904 can transmit a measurement configuration to the UE in the RedCap class based at least in part on information indicating whether the neighbor cells support access by the UE in the RedCap class, the measurement configuration including one or more neighbor cells on which the UE is to perform radio resource management measurements.

The handover component 908 can exclude neighbor cells from a set of candidate target cells for handover of a UE in the RedCap class based at least in part on an indication that the neighbor cells do not support access by the UE in the RedCap class.

The number and arrangement of components shown in fig. 9 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than those shown in fig. 9. Further, two or more components shown in fig. 9 may be implemented within a single component, or a single component shown in fig. 9 may be implemented as multiple distributed components. Additionally or alternatively, the set of component(s) shown in fig. 9 may perform one or more functions described as being performed by another set of components shown in fig. 9.

The following provides a summary of some aspects of the disclosure:

aspect 1: a method of wireless communication performed by a UE, comprising: receiving system information indicating whether one or more neighbor cells support access for UEs in the RedCap class; and performing one or more RRM measurements on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information.

Aspect 2: the method of aspect 1, wherein the system information is received in a SIB containing information related to cell reselection parameters.

Aspect 3: the method of aspect 2, wherein the SIB is SIB2, SIB3 or SIB4.

Aspect 4: the method of any one of aspects 1-3, further comprising: a measurement configuration is received, wherein the one or more neighbor cells on which the one or more RRM measurements are performed are identified based at least in part on the measurement configuration.

Aspect 5: the method of aspect 4, wherein the measurement configuration excludes any neighbor cells that do not support access for UEs in the RedCap class.

Aspect 6: the method of any one of aspects 1-5, further comprising: determining at least one neighbor cell that does not support access for a UE in the RedCap class based at least in part on the system information; and refraining from performing RRM measurements on the at least one neighbor cell that does not support access for UEs in the RedCap class.

Aspect 7: a method of wireless communication performed by a network node, comprising: receiving information indicating whether a neighbor cell supports access of a UE in a RedCap class; and transmitting system information indicating whether the neighbor cell supports access of the UE in the RedCap class.

Aspect 8: the method of aspect 7, wherein the information indicating whether the neighbor cell supports access by UEs in the RedCap class is received based at least in part on a setting of the neighbor cell change regarding whether the neighbor cell supports access by UEs in the RedCap class.

Aspect 9: the method of any of aspects 7-8, wherein the information indicating whether the neighbor cell supports access for UEs in the RedCap class is received via an operations, administration and management interface or inter-node messaging.

Aspect 10: the method according to any of the claims 7-9, wherein the system information is sent in a SIB containing information related to cell reselection parameters.

Aspect 11: the method of aspect 10, wherein the SIB is SIB2, SIB3 or SIB4.

Aspect 12: the method of any of aspects 7-11, further comprising: transmitting a measurement configuration to a UE in the RedCap class based at least in part on the information indicating whether the neighbor cell supports access by the UE in the RedCap class, the measurement configuration including one or more neighbor cells on which the UE is to perform radio resource management measurements.

Aspect 13: the method of aspect 12, wherein the measurement configuration excludes the neighbor cell based at least in part on an indication that the neighbor cell does not support access by UEs in the RedCap class.

Aspect 14: the method of any one of aspects 7-13, further comprising: the neighbor cell is excluded from a set of candidate target cells for handover of the UE in the RedCap class based at least in part on an indication that the neighbor cell does not support access by the UE in the RedCap class.

Aspect 15: an apparatus for wireless communication at a device, 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-6.

Aspect 16: an apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-6.

Aspect 17: an apparatus for wireless communication, comprising at least one unit to perform the method of one or more of aspects 1-6.

Aspect 18: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-6.

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

Aspect 20: an apparatus for wireless communication at a device, 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 7-14.

Aspect 21: an apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 7-14.

Aspect 22: an apparatus for wireless communication, comprising at least one unit to perform the method of one or more of aspects 7-14.

Aspect 23: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 7-14.

Aspect 24: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 7-14.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

As used herein, the term "component" is intended to be broadly interpreted as hardware and/or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, should be broadly interpreted to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, and other examples. 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 may be implemented in various forms of hardware and/or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems and/or methods is not limiting of the aspects. Thus, the operations and behavior of the systems and/or methods were described without reference to the specific software code-as one of ordinary skill in the art would understand that software and hardware could be designed to implement the systems and/or methods based at least in part on the description herein.

As used herein, a "meeting a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than or equal to a threshold, not equal to a threshold, etc., depending on the context.

Even if specific combinations of features are recited in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of the various aspects includes the combination of each dependent claim with each other claim in the set of claims. As used herein, a phrase referring to "at least one of a list of items" refers to any combination of those items, including individual members. For example, "at least one of a, b, or c" is intended to encompass a, b, c, a +b, a+c, b+c, and a+b+c, as well as any combination of the same elements as multiples thereof (e.g., a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+c, c+c, and c+c, or any other ordering of a, b, and c).

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

Claims

1. A method of wireless communication performed by a User Equipment (UE), comprising:

receiving system information indicating whether one or more neighbor cells support access by UEs in a reduced capability (RedCap) class; and

one or more Radio Resource Management (RRM) measurements are performed on one or more neighbor cells identified as supporting access for UEs in the RedCap class based at least in part on the system information.

2. The method of claim 1, wherein the system information is received in a System Information Block (SIB) containing information related to cell reselection parameters.

3. The method of claim 2, wherein the SIB is SIB2, SIB3, or SIB4.

4. The method of claim 1, further comprising:

a measurement configuration is received, wherein the one or more neighbor cells on which the one or more RRM measurements are performed are identified based at least in part on the measurement configuration.

5. The method of claim 4, wherein the measurement configuration excludes any neighbor cells that do not support access for UEs in the RedCap class.

6. The method of claim 1, further comprising:

Determining at least one neighbor cell that does not support access for a UE in the RedCap class based at least in part on the system information; and

RRM measurements are avoided from being performed on the at least one neighbor cell that does not support access for UEs in the RedCap class.

7. A method of wireless communication performed by a network node, comprising:

receiving information indicating whether a neighbor cell supports access of a User Equipment (UE) in a reduced capability (RedCap) class; and

and sending system information indicating whether the neighbor cell supports access of the UE in the RedCAP class.

8. The method of claim 7, wherein the information indicating whether the neighbor cell supports access by UEs in the RedCap class is received based at least in part on a setting of the neighbor cell change regarding whether the neighbor cell supports access by UEs in the RedCap class.

9. The method of claim 7, wherein the information indicating whether the neighbor cell supports access for UEs in the RedCap class is received via an operations, administration and management interface, or inter-node messaging.

10. The method of claim 7, wherein the system information is transmitted in a System Information Block (SIB) containing information related to cell reselection parameters.

11. The method of claim 10, wherein the SIB is SIB2, SIB3, or SIB4.

12. The method of claim 7, further comprising:

transmitting a measurement configuration to a UE in the RedCap class based at least in part on the information indicating whether the neighbor cell supports access by the UE in the RedCap class, the measurement configuration including one or more neighbor cells on which the UE is to perform radio resource management measurements.

13. The method of claim 12, wherein the measurement configuration excludes the neighbor cell based at least in part on an indication that the neighbor cell does not support access for UEs in the RedCap class.

14. The method of claim 7, further comprising:

the neighbor cell is excluded from a set of candidate target cells for handover of the UE in the RedCap class based at least in part on an indication that the neighbor cell does not support access by the UE in the RedCap class.

15. A User Equipment (UE) for wireless communication, comprising:

a memory; and

one or more processors coupled to the memory configured to:

16. The UE of claim 15, wherein the system information is received in a System Information Block (SIB) containing information related to cell reselection parameters.

17. The UE of claim 16, wherein the SIB is SIB2, SIB3, or SIB4.

18. The UE of claim 15, wherein the one or more processors are further configured to:

19. The UE of claim 18, wherein the measurement configuration excludes any neighbor cells that do not support access for UEs in the RedCap class.

20. The UE of claim 15, wherein the one or more processors are further configured to:

21. A network node for wireless communication, comprising:

a memory; and

one or more processors coupled to the memory configured to:

22. The network node of claim 21, wherein the information indicating whether the neighbor cell supports access by UEs in the RedCap class is received based at least in part on a setting of the neighbor cell change regarding whether the neighbor cell supports access by UEs in the RedCap class.

23. The network node of claim 21, wherein the information indicating whether the neighbor cell supports access for UEs in the RedCap class is received via an operations, administration and management interface or inter-node messaging.

24. The network node of claim 21, wherein the system information is transmitted in a System Information Block (SIB) containing information related to cell reselection parameters.

25. The network node of claim 24, wherein the SIB is SIB2, SIB3, or SIB4.

26. The network node of claim 21, wherein the one or more processors are further configured to:

27. The network node of claim 26, wherein the measurement configuration excludes the neighbor cell based at least in part on an indication that the neighbor cell does not support access by UEs in the RedCap class.

28. The network node of claim 21, wherein the one or more processors are further configured to: