Idle / Inactive Mode Procedures for Reduced Capability User Equipment - Patent application

Abstract

Certain aspects of the disclosure provide techniques for wireless communication by a user equipment (UE), the techniques generally including receiving, from a network entity, a configuration for a first downlink (DL) bandwidth portion (BWP), a first control resource set (CORESET) configured on the first DL BWP, and one or more first search space (SS) sets within the first CORESET; receiving, from the network entity, a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets within the second CORESET; receiving signaling to configure the UE for physical downlink control channel (PDCCH) monitoring adaptation; and monitoring the PDCCH in accordance with the PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. patent application Ser. No. 17 / 676,097, filed Feb. 18, 2022, which is assigned to the assignee of the present application and is expressly incorporated by reference in its entirety into this specification as if fully set forth below and for all applicable purposes. [Background technology]

[0002] Field of Disclosure Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for certain procedures involving user equipment (UE).

[0003] 2. Description of Related Art

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, or other similar types of services. These wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with those users.

[0004]

[0004] Although wireless communication systems have made great technological advances over the years, challenges remain. For example, complex and dynamic environments may still attenuate or block signals between wireless transmitters and wireless receivers. Thus, there remains a desire to improve the technical performance of wireless communication systems, including, for example, improving the speed and data carrying capacity of communication, improving the efficiency of use of the shared communication medium, reducing the power used by the transmitter and receiver while performing communication, improving the reliability of wireless communication, avoiding redundant transmission and / or reception and associated processing, improving the coverage area of ​​wireless communication, increasing the number and types of devices that can access the wireless communication system, improving the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, and the like. Thus, further improvements in wireless communication systems are needed to overcome the aforementioned technical challenges and others. Summary of the Invention

[0005]

[0005] One aspect provides a method for wireless communication by a user equipment (UE), the method including receiving from a network entity a configuration for a first downlink (DL) bandwidth portion (BWP), a first control resource set (CORESET) configured on the first DL BWP, and one or more first search space (SS) sets within the first CORESET, receiving from the network entity a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets within the second CORESET, receiving signaling configuring the UE for physical downlink control channel (PDCCH) monitoring adaptation, and monitoring the PDCCH in accordance with the PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP.

[0006]

[0006] One aspect provides a method for wireless communication by a network entity, the method including: transmitting to a UE a configuration for a first DL BWP, a first CORESET configured on the first DL BWP, and one or more first SS sets within the first CORESET; transmitting to the UE a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets within the second CORESET; transmitting signaling to configure the UE for PDCCH monitoring adaptation; and transmitting a PDCCH in accordance with the PDCCH monitoring adaptation when participating with the UE in one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP.

[0007]

[0007] Other aspects provide an apparatus operable, configured or otherwise adapted to perform the above-mentioned method as well as methods described elsewhere herein, a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the above-mentioned method as well as methods described elsewhere herein, a computer program product embodied on a computer-readable storage medium comprising code for performing the above-mentioned method as well as methods described elsewhere herein, and an apparatus comprising means for performing the above-mentioned method as well as methods described elsewhere herein. By way of example, the apparatus may comprise a processing system, a device having a processing system, or processing systems cooperating over one or more networks.

[0008]

[0008] The following description and the annexed drawings set forth certain features for purposes of illustration. [Brief description of the drawings]

[0009]

[0009] The accompanying drawings illustrate certain features of the various aspects described herein and should not be considered as limiting the scope of the disclosure. [Figure 1]

[0010] 1 illustrates an exemplary wireless communication network. [Diagram 2]

[0011] 1 illustrates an exemplary split base station architecture. [Diagram 3]

[0012] 1 illustrates aspects of an exemplary base station and exemplary user equipment. [Figure 4A]

[0013] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4B] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4C] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4D] 1 illustrates various example aspects of a data structure for a wireless communication network. [Diagram 5]

[0014] 1 illustrates an example New Radio (NR) reduced capability (RedCap) user equipment (UE). [Figure 6A]

[0015] 1 shows a call flow diagram for a four-step Random Access Channel (RACH) procedure. [Figure 6B] 1 shows a call flow diagram for a two-step random access channel (RACH) procedure. [Figure 7]

[0016] 1 illustrates an exemplary association of SSB to RACH occasions (ROs). [Figure 8]

[0017] 1 illustrates exemplary features for RedCap and non-RedCap bandwidth portions (BWPs). [Figure 9A]

[0018] 1 illustrates an option for look-up table (LUT) based resource mapping, according to an aspect of the present disclosure. [Figure 9B] 1 illustrates an option for look-up table (LUT) based resource mapping, according to an aspect of the present disclosure. [Figure 10]

[0019] 1 illustrates an example of a downlink reference signal (DL-RS) in a RedCap-specific initial downlink bandwidth portion (DL-BWP) in accordance with an aspect of the present disclosure. [Figure 11] 1 illustrates an example of a downlink reference signal (DL-RS) in a RedCap-specific initial downlink bandwidth portion (DL-BWP) in accordance with an aspect of the present disclosure. [Figure 12] 1 illustrates an example of a downlink reference signal (DL-RS) in a RedCap-specific initial downlink bandwidth portion (DL-BWP) in accordance with an aspect of the present disclosure. [Figure 13] 1 illustrates an example of a downlink reference signal (DL-RS) in a RedCap-specific initial downlink bandwidth portion (DL-BWP) in accordance with an aspect of the present disclosure. [Figure 14]

[0020] 1 illustrates an example of a BWP switch according to an embodiment of the present disclosure. [Figure 15] 1 illustrates an example of a BWP switch according to an embodiment of the present disclosure. [Figure 16]

[0021] 1 illustrates an example of bandwidth allocation according to an aspect of the present disclosure. [Figure 17]

[0022] SUMMARY OF THE DISCLOSURE A method for wireless communication is disclosed. [Figure 18]

[0023] SUMMARY OF THE DISCLOSURE A method for wireless communication is disclosed. [Figure 19]

[0024] 1 illustrates aspects of an exemplary communications device. [Figure 20]

[0025] 1 illustrates aspects of an exemplary communications device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010]

[0026] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for performing various procedures by a UE that may be configured to operate in a bandwidth portion (BWP) that may be reserved for a particular type of UE, such as an initial downlink BWP reserved for reduced capacity (RedCap) UEs.

[0011]

[0027] Different types of UEs may have capabilities tailored to suit specific purposes. For example, some UEs may be designed to be scalable and deployable in a more efficient and cost-effective manner. These types of UEs may have reduced capabilities (RedCap) relative to traditional (more expensive) UEs such as high-end smartphones. RedCap UEs may have reduced latency and / or reliability requirements.

[0012]

[0028] The network may configure separate frequency resources, called Bandwidth Parts (BWPs), for RedCap UEs to perform specific functions, such as Random Access Channel (RACH) procedures. In some cases, a RedCap UE may only have a single radio (e.g., to control costs), meaning that a RedCap UE may only be able to operate on one BWP at a time. However, this may present some challenges, as the UE may need to retune its radio to receive a particular type of signal used for a particular purpose.

[0013]

[0029] For example, the network may configure a RedCap UE with a downlink BWP in which no specific signal is transmitted (a DL BWP dedicated to RedCap UEs). The DL BWP may be configured for the UE to perform certain idle or inactive mode procedures. However, the DL BWP may not be configured with specific DL signals, which may present challenges. For example, in some cases, synchronization signal blocks (SSBs) may not be transmitted in the initial DL BWP. In such cases, the RedCap UE may need to perform a BWP switch to a conventional BWP used by RedCap and non-RedCap UEs to detect SSBs for various purposes. Managing procedures involving different BWPs presents challenges, as the BWP switch may consume power and increase the latency of certain procedures.

[0014]

[0030] However, aspects of the present disclosure provide various signaling mechanisms that may help improve the flexibility of various RedCap UE procedures, such as cell selection and cell reselection, subject to constraints on reduced UE complexity. In some cases, the mechanisms may help limit or avoid BWP switching when performing such procedures, which may help reduce latency and power consumption when performing such procedures.

[0015] Introduction to wireless communication networks

[0031] The techniques and methods described herein can be used for a variety of wireless communication networks. Although aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure may be applicable to other communication systems and standards not explicitly mentioned herein.

[0016]

[0032] FIG. 1 illustrates an example of a wireless communication network 100 in which aspects described herein may be implemented.

[0017]

[0033] Generally, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communication device and / or a communication function performed by a communication device. For example, various functions of the network, as well as various devices associated with and interacting with the network, can be considered network entities.

[0018]

[0034] In the illustrated example, the wireless communication network 100 includes base stations (BSs) 102, user equipment (UEs) 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and a 5G Core (5GC) network 190, which interoperate to provide communication services over various communication links, including wired and wireless links.

[0019]

[0035] 1 illustrates various exemplary UEs 104, which may more generally include a mobile phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an internet of things (IoT) device, an always on (AON) device, an edge processing device, or other similar devices. The UEs 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, or the like.

[0020]

[0036] The BS 102 communicates wirelessly with the UE 104 via a communication link 120. The communication link 120 between the BS 102 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the BS 102, and / or downlink (DL) (also referred to as forward link) transmissions from the BS 102 to the UE 104. The communication link 120 may use Multiple-Input and Multiple-Output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0021]

[0037] The BSs 102 may generally include a NodeB, an enhanced NodeB (eNB), a next generation enhanced NodeB (ng-eNB), a next generation NodeB (gNB or gNodeB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a transmit / receive point, etc. Each of the BSs 102 may provide communication coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell and may overlap in some cases (e.g., a small cell 102′ may have a coverage area 110′ that overlaps with a coverage area 110 of a macro cell). The BSs may provide communication coverage for, for example, a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively smaller geographic area, such as a sports stadium), a femto cell (covering a relatively smaller geographic area (e.g., a home)), and / or other types of cells.

[0022]

[0038] Although the BS 102 is shown in various aspects as a single communications device, the BS 102 may be implemented in various configurations. For example, one or more components of a base station may be distributed, including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, to name a few. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., the BS 102) may include components located in a single physical location or components located in various physical locations. In an embodiment in which a base station includes components located in various physical locations, the various components may each perform functions such that the various components collectively achieve similar functionality as a base station located in a single physical location. In some aspects, a base station that includes components located at different physical locations may be referred to as a split radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. Figure 2 illustrates and describes an example split base station architecture.

[0023]

[0039] Different BSs 102 in the wireless communication network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and 5G. For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) via a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0024]

[0040] The wireless communications network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where the frequencies may also be referred to as carriers, subcarriers, frequency channels, tones, or subbands. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 600 MHz to 6 GHz, which is often referred to (interchangeably) as "sub-6 GHz." Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 26 to 41 GHz, which is sometimes referred to (interchangeably) as "millimeter wave" ("mmW" or "mmWave"). Base stations (e.g., mmWave base stations such as BS 180) configured to communicate using mmWave / near-mmWave radio frequency bands may utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0025]

[0041] The communication link 120 between the BS 102 and, for example, the UE 104 may pass one or more carriers that may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and other MHz) and may be aggregated in various manners. The carriers may or may not be adjacent to each other. The allocation of carriers may also be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than UL).

[0026]

[0042] Communications using higher frequency bands may have higher path loss and shorter range compared to lower frequency communications. Thus, some base stations (e.g., 180 in FIG. 1) may utilize beamforming 182 with the UE 104 to improve path loss and range. For example, the BS 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182′. The UE 104 may receive beamformed signals from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit beamformed signals to the base station 180 in one or more transmit directions 182″. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182′. The base station 180 and the UE 104 can then perform beam training to determine the best receive and transmit directions for each of the BS 180 and the UE 104. In particular, the transmit and receive directions of the BS 180 may or may not be the same. Similarly, the transmit and receive directions of the UE 104 may or may not be the same.

[0027]

[0043] The wireless communication network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, for example, in the 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.

[0028]

[0044] Particular UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).

[0029]

[0045] The EPC 160 may include various functional components, including, in the illustrated example, a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0030]

[0046] Generally, user Internet Protocol (IP) packets are forwarded through a Serving Gateway 166, which itself is connected to a PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), Packet Switched (PS) streaming services, and / or other IP services.

[0031]

[0047] The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions and may be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN) and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to deliver MBMS traffic to BSs 102 that belong to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start / stop) and collecting eMBMS related charging information.

[0032]

[0048] The 5GC 190 may include various functional components, including an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196.

[0033]

[0049] The AMF 192 is a control node that handles signaling between the UE 104 and the 5GC 190. The AMF 192 provides, for example, quality of service (QoS), flow and session management.

[0034]

[0050] Internet Protocol (IP) packets are forwarded through UPF 195, which connects to IP services 197 and provides UE IP address allocation and other functions for 5GC 190. IP services 197 may include, for example, Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0035]

[0051] In various aspects, the network entities or network nodes may be implemented as aggregate base stations, as distributed base stations, as integrated access and backhaul (IAB) nodes, as relay nodes, as sidelink nodes, to name a few.

[0036]

[0052] 2 illustrates an exemplary split base station 200 architecture. The split base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with the core network 220 via a backhaul link or indirectly with the core network 220 via one or more split base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both). The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 240 simultaneously.

[0037]

[0053] Each of the units, i.e., CU 210, DU 230, RU 240, and quasi-RT RIC 225, non-RT RIC 215, and SMO framework 205, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, the units may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Furthermore, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit or transmit signals over a wireless transmission medium to one or more of the other units.

[0038]

[0054] In some aspects, the CU 210 may host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and the like. Each control function may implement an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 210 may be implemented to communicate with the DU 230, as necessary, for network control and signaling.

[0039]

[0055] The DU 230 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may correspond to a 3G Partnership Project (3GPP)-compliant 3GPP ... rdDepending at least in part on a functional division such as that defined by the Third Generation Partnership Project (3GPP), the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, the DU 230 may further host one or more lower PHY layers. Each layer (or module) may implement an interface configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0040]

[0056] The lower layer functions may be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DU 230 may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division such as a lower layer functional division. In such an architecture, the RU(s) 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU(s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0041]

[0057] The SMO framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, the CU 210, the DU 230, the RU 240, and the quasi-RT RIC 225. In some implementations, the SMO framework 205 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0042]

[0058] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the quasi-RT RIC 225 (e.g., via an A1 interface). The quasi-RT RIC 225 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and action via one or more CUs 210, one or more DUs 230, or both, and interfaces connecting the O-eNB to the quasi-RT RIC 225 (e.g., via an E2 interface).

[0043]

[0059] In some implementations, the non-RT RIC 215 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 225. Such information may be utilized by the quasi-RT RIC 225 or may be received at the SMO framework 205 or the non-RT RIC 215 from non-network data sources or from network functions. In some embodiments, the non-RT RIC 215 or the quasi-RT RIC 225 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 215 may employ the AI / ML models to monitor long-term trends and patterns regarding performance and take corrective action via the SMO framework 205 (e.g., reconfiguration via O1) or via the creation of RAN management policies (e.g., A1 policies).

[0044]

[0060] FIG. 3 illustrates an example aspect of the BS 102 and UE 104.

[0045]

[0061] Generally, the BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively 334), transceivers 332a-t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, the BS 102 can transmit and receive data between the BS 102 and the UE 104. The BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communications.

[0046]

[0062] Generally, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-r (collectively 352), transceivers 354a-r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 362) and wireless reception of data (e.g., data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0047]

[0063] For an example downlink transmission, the BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. In some examples, the data may be for a physical downlink shared channel (PDSCH).

[0048]

[0064] The transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0049]

[0065] A transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) in transceivers 332a-t. Each modulator in transceivers 332a-t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a-t may be transmitted via antennas 334a-t, respectively.

[0050]

[0066] To receive downlink transmissions, the UE 104 includes antennas 352a-352r, which can receive downlink signals from the BS 102 and provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in the transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

[0051]

[0067] A MIMO detector 356 may obtain received symbols from all demodulators in the transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols and provide decoded data for the UE 104 to a data sink 360 and provide decoded control information to the controller / processor 380.

[0052]

[0068] For an example uplink transmission, the UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for a PUSCH) from a data source 362 and control information (e.g., for a physical uplink control channel (PUCCH)) from a controller / processor 380. The transmit processor 364 may also generate reference symbols for a reference signal (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM, etc.), and transmitted to the BS 102.

[0053]

[0069] At the BS 102, the uplink signals from the UE 104 may be received by antennas 334a-t, processed by demodulators in transceivers 332a-t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information transmitted by the UE 104. The receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to a controller / processor 340.

[0054]

[0070] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0055]

[0071] A scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0056]

[0072] In various aspects, the BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data from the data source 312, the scheduler 344, the memory 342, the transmit processor 320, the controller / processor 340, the TX MIMO processor 330, the transceivers 332a-t, the antennas 334a-t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from the antennas 334a-t, the transceivers 332a-t, the RX MIMO detector 336, the controller / processor 340, the receive processor 338, the scheduler 344, the memory 342, and / or other aspects described herein.

[0057]

[0073] In various aspects, the UE 104 may similarly be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data from the data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antennas 352a-t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from the antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0058]

[0074] In some aspects, the processor may be configured to perform various operations, such as those associated with the methods described herein, to transmit (output) data to or receive (obtain) data from another interface configured to transmit or receive data, respectively.

[0059]

[0075] 4A, 4B, 4C, and 4D illustrate aspects of data structures for a wireless communication network, such as wireless communication network 100 of FIG.

[0060]

[0076] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe in a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of a DL channel in a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe in a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of a UL channel in a 5G subframe.

[0061]

[0077] A wireless communication system may utilize orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) on the uplink and downlink. Such a system may also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers (e.g., as shown in FIGS. 4B and 4D). Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and in the time domain with SC-FDM.

[0062]

[0078] The wireless communication frame structure may be frequency division duplex (FDD) where, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL. The wireless communication frame structure may also be time division duplex (TDD) where, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.

[0063]

[0079] In Figures 4A and 4C, the wireless communication frame structure is TDD, where D is DL, U is UL, and X is flexible for use between DL / UL. The UE may be configured with the slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). In the illustrated example, a 10 ms frame is divided into ten equally sized 1 ms subframes. Each subframe may include one or multiple time slots. In some examples, each slot may include 7 or 14 symbols depending on the slot configuration. A subframe may also include a minislot, which generally has fewer symbols than an entire slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0064]

[0080] In general, the number of slots in a subframe is based on the slot configuration and numerology. In slot configuration 0, the different numerologies (μ) 0-5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. In slot configuration 1, the different numerologies 0-2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. Subcarrier spacing and symbol length / duration are functions of numerology. Subcarrier spacing is 2 μ×15 kHz, where μ is a numerology from 0 to 5. Thus, numerology μ=0 has a subcarrier spacing of 15 kHz, and numerology μ=5 has a subcarrier spacing of 480 kHz. The symbol length / period is inversely proportional to the subcarrier spacing. Figures 4A, 4B, 4C, and 4D give an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol period is approximately 16.67 μs.

[0065]

[0081] A resource grid can be used to represent the frame structure, as shown in Figures 4A, 4B, 4C, and 4D. Each time slot contains resource blocks (RBs) (also called physical RBs (PRBs)), which span 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0066]

[0082] As shown in FIG. 4A, some of the REs carry reference (pilot) signals (RS) for UEs (e.g., UE 104 in FIG. 1 and FIG. 3). The RS may include demodulation RS (DMRS) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0067]

[0083] 4B shows an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs), each CCE containing 9 RE Groups (REGs), each REG containing 4 consecutive REs within one OFDM symbol.

[0068]

[0084] A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE (e.g., 104 in Figures 1 and 3) to determine subframe / symbol timing and physical layer identification information.

[0069]

[0085] A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identity and the timing of the radio frame.

[0070]

[0086] Based on the physical layer identity and the group number of the physical layer cell identity, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the above-mentioned DMRS. The physical broadcast channel (PBCH), which carries the master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0071]

[0087] As shown in FIG. 4C, some of the REs carry DMRS (denoted as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE may transmit DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE 104 may also transmit a sounding reference signal (SRS). The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb configuration, and the UE may transmit the SRS in one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0072]

[0088] 4D shows an example of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be arranged as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0073] Exemplary Reduction Capability (RedCap) UE

[0089] Various technologies may be the focus of current wireless communication standards. For example, Rel-15 and / or Rel-16 may focus on premium smartphones (e.g., enhanced mobile broadband (eMBB)) and other verticals such as ultra-reliable low latency communication (URLLC) and / or vehicle-to-everything (V2X) communications. In some wireless communication standards (e.g., Rel-17 and beyond), there may be a strong desire for new radio (NR) to be scalable and deployable in a more efficient and cost-effective manner. Thus, a new UE type (RedCap) with reduced capabilities is being introduced. RedCap UEs may exhibit relaxed peak throughput (e.g., 20 MHz) and lower latency and / or reliability requirements. Also, RedCap UEs may entail lower device cost (and complexity) and improved efficiency (e.g., power consumption, system overhead, and cost improvements) compared to high-end devices such as 5G NR Rel-15 / 16 high-end eMBB and URLCC devices (e.g., high-end smartphones). In some cases, a cell may enable access for a RedCap UE. The network may configure a separate initial UL BWP for the RedCap UE in a system information block (SIB) that may be used both during and after initial access. The RedCap UE may not be configured to support a BWP that is wider than the maximum bandwidth of the initial BWP for the RedCap UE. However, non-RedCap UEs that may share the initial UL BWP with the RedCap UE are allowed to exceed the maximum bandwidth of the initial BWP. The RedCap UE may switch to a non-initial BWP by using a BWP switching mechanism described in FIG. 8 below.

[0074]

[0090] In many use cases, the RedCap UE may be implemented in a device design with a more compact form factor. The RedCap UE may also support Frequency Range (FR) 1 and / or 2 bands for Frequency Division Duplex (FDD) and / or Time Division Duplex (TDD) communications. For F1, basic BWP operation with restrictions may be used as a starting point for RedCap UE capabilities. Alternatively, basic BWP operation without restrictions may be used as a starting point for RedCap UE capabilities. For FR1 in TDD, the center frequency may be the same for the initial DL and UL BWPs used during random access for the RedCap UE. The center frequency may be the same for non-initial DL and UL BWPs with the same BWP identifier (BWP ID) for the RedCap UE.

[0075]

[0091] Thus, some design objectives for an NR RedCap UE may include scalable resource allocation, coverage extension for DL ​​and / or UL, power conservation in all RRC states, and / or coexistence with NR Premium UEs.

[0076]

[0092] As shown in Figure 5, an NR-RedCap UE may be a smart wearable device, a sensor / camera, or any other device configured for relaxed Internet of Things (IoT) communications. Additionally, RedCap UE functions and / or capabilities may overlap with those of long term evolution (LTE) and / or fifth generation (5G) devices (e.g., premium 5G devices). For example, relaxed IoT device functions may overlap with URLLC device functions, smart wearable device functions may overlap with low power wide area (LPWA) massive machine type communication (mMTC) device functions, and / or sensor / camera functions may overlap with eMBB device functions.

[0077] Exemplary RACH Procedure

[0093] A random access channel (RACH) is so named because it refers to a wireless channel (medium) that may be shared by multiple UEs and that is used by the UE to (randomly) access the network for communication. For example, the RACH may be used to access the network for call setup and for data transmission. In some cases, the RACH may be used to initially access the network when the UE switches from an idle mode to an active mode of a radio resource control (RRC) connection or when handing over within an RRC connected mode. Moreover, the RACH may be used for downlink (DL) and / or uplink (UL) data arrival when the UE is in an RRC idle mode or an RRC inactive mode and when re-establishing a connection with the network.

[0078]

[0094] FIG. 6A is a timing (or "call flow") diagram 600A illustrating an example four-step RACH procedure according to certain aspects of the disclosure. A first message (MSG1) may be sent from the UE 104 to the BS 102 on a physical random access channel (PRACH). In this case, MSG1 may include only a RACH preamble. The BS 102 may respond with a random access response (RAR) message (MSG2), which may include an identifier (ID) of the RACH preamble, a timing advance (TA), an uplink grant, a cell radio network temporary identifier (C-RNTI), and a back-off indicator. MSG2 may include a PDCCH communication including control information for subsequent communication on the PDSCH, as shown. In response to MSG2, MSG3 is transmitted from the UE 104 to the BS 102 on a PUSCH. MSG3 may include one or more of an RRC connection request, a tracking area update request, a system information request, a positioning fix or signal request, or a scheduling request. BS 110 then responds with MSG4, which may include a contention resolution message.

[0079]

[0095] In some cases, to speed up access, a two-step RACH procedure may be supported. As the name suggests, the two-step RACH procedure effectively "folds" the four messages of the four-step RACH procedure into two messages.

[0080]

[0096] FIG. 6B is a call flow diagram 600B illustrating an example two-step RACH procedure according to certain aspects of the present disclosure. A first extended message (msgA) may be sent from the UE 104 to the BS 102. In certain aspects, msgA may include some or all of the information from MSG1 and MSG3 from the four-step RACH procedure, effectively combining MSG1 and MSG3. For example, msgA may include MSG1 and MSG3 multiplexed together, such as using one of time division multiplexing or frequency division multiplexing. In certain aspects, msgA includes a RACH preamble and a payload for random access. The msgA payload may include, for example, a UE-ID and other signaling information (e.g., a buffer status report (BSR)) or a scheduling request (SR). The BS 102 may respond with a random access response (RAR) message (msgB), which may effectively combine MSG2 and MSG4 described above. For example, msgB may include an ID of the RACH preamble, a timing advance (TA), a backoff indicator, a contention resolution message, a UL / DL grant, and a transmit power control (TPC) command.

[0081]

[0097] In a two-step RACH procedure, msgA may include a RACH preamble and a payload. In some cases, the RACH preamble and the payload may be sent in the msgA transmission occasion.

[0082]

[0098] A random access message (msgA) transmission occasion generally includes a msgA preamble occasion (for transmitting a preamble signal) and a msgA payload occasion for transmitting a PUSCH. A msgA preamble transmission generally involves the following: (1) Selection of a preamble sequence, and (2) Selection of a preamble occasion in the time / frequency domain (for transmitting a selected preamble sequence) A msgA payload transmission typically involves the following: (1) Construction of the random access message payload (DMRS / PUSCH), and (2) Selection of one or more PUSCH resource units (PRUs) in the time / frequency domain for transmitting this message (payload).

[0083]

[0099] In some cases, the UE monitors SSB transmissions, which are sent (by the gNB using different beams) and are associated with a finite set of time / frequency resources that define RACH occasions (ROs) and PRUs. Upon detecting an SSB, the UE may select an RO and one or more PRUs associated with that SSB for MSG1 / msgA transmission. In some cases, the RO associated with the detected SSB falls within the RedCap UE bandwidth, and the RedCap UE may utilize a separate initial UL BWP for RedCap (not expected to exceed the maximum RedCap UE bandwidth), which may include an RO for RedCap UEs. The RO may be dedicated to RedCap UEs or may be shared with non-RedCap UEs. The finite set of ROs and PRUs may help reduce monitoring overhead (blind decoding) by the base station.

[0084]

[0100] The two-step RACH procedure has several advantages, such as speed of access and the ability to send relatively small amounts of data without the overhead of a full four-step RACH procedure to establish a connection (when the four-step RACH message is larger than the payload).

[0085]

[0101] The two-step RACH procedure may work in any RRC state and any supported cell size. A network using the two-step RACH procedure may typically support contention-based random access (CBRA) transmission of messages (e.g., msgA) with a finite number of MCS levels within a finite range of payload sizes.

[0086]

[0102] After the UE selects an SSB (beam), there are one or more predefined ROs for that SS block with specific time and frequency offsets and directions (e.g., specific to the selected SSB). Figure 7 shows an example association (mapping) between SSBs and ROs.

[0087]

[0103] This SSB to RO association is used by the gNB to know which beam the UE has acquired / is using (commonly referred to as beam establishment). One SSB may be associated with one or multiple ROs, or two or more SSBs may be associated with one RO. The association is usually performed first in the frequency domain, then in the time domain within the RACH slot, and then in the time domain across the RACH slots (e.g. starting from a lower SSB index). The association period is usually defined as the minimum number of RACH configuration periods such that all (configured) SSB beams are mapped to a RO.

[0088] Overview of Dedicated RedCap BWP

[0104] Due to differences in capabilities, RedCap UEs (due to their lower bandwidth capabilities) and conventional (e.g., non-RedCap or legacy) UEs may be configured to operate in bandwidth portions (BWPs) with different characteristics. Table 800 in FIG. 8 summarizes some of the different characteristics. For example, a conventional non-RedCap initial downlink (DL) BWP may include an SSB, a RACH common search space (CSS), and a CORESET0. As shown in FIG. 8, a RedCap initial DL BWP may include, for example, a RACH CSS but may not include an SSB, a CORESET (e.g., CORESET0, CORESET for paging), and / or a system information block (SIB). In other cases, a RedCap UE may not include a RACH CSS but may include a CORESET (e.g., CORESET0). Similarly, a RedCap non-initial DL BWP may not include an SSB or system information and may not be able to access this information. Although operating without specific information may greatly reduce the complexity for a RedCap UE, a RedCap UE operating in these BWPs without access to the information (e.g., SSBs) cannot obtain the benefit of the information while operating on the BWP.

[0089]

[0105] As a result, RedCap UEs operating in these BWPs cannot obtain the benefits of SSB. However, aspects of the present disclosure may enable RedCap UEs to implement an extended timeline, which allows the RedCap UE to switch to a different BWP (e.g., to a non-RedCap initial DL BWP) during a RACH procedure to monitor for SSB. After detecting the SSB, the RedCap UE may then return (e.g., to the RedCap initial BWP) to resume the RACH procedure.

[0090]

[0106] Thus, the techniques presented herein can help address potential problems caused by the inability of a RedCap UE to measure and track the SSB during a RACH procedure. If the UE fails to receive the RAR after transmitting a RACH preamble and the UE is not allowed to monitor the SSB, potential problems may be caused because the UE must reselect the RACH resource using the same SSB during a RACH retransmission (despite the previous failure). In some cases, failure to track and measure the SSB during a RedCap BWP may result in the UE not having a CORESET set and a CSS set (e.g., for paging, small data transmission, random access, etc.) configured.

[0091]

[0107] In some cases, the UE may be able to increase the power ramping counter during RACH retransmissions but may not change the SSB, which may lead to UE congestion during RACH retransmissions, for example, when other UEs may reuse the same SSB for RACH transmissions.

[0092]

[0108] In general, a conventional RedCap UE cannot track SSBs from the time of the initial Msg1 transmission to the time the NW configures the UE with an active BWP (including non-cell defined SSBs) through RRC. As a result, the UE may not be able to properly receive and transmit messages during the RACH procedure.

[0093]

[0109] In FR1 and FR2, if a separate initial DL BWP is configured for random access rather than paging, a RedCap UE in idle / inactive mode may not expect that DL BWP to include SSB (e.g., cells defining SSB or CD-SSB), CORESET#0, or SIB transmissions. Therefore, it may be assumed that a RedCap UE performing random access in a separate DL BWP may not need to monitor paging in a BWP including CORESET#0.

[0094]

[0110] If the initial DL BWP is configured for paging, the RedCap UE may expect the DL BWP to include non-cell defined SSBs (NCD-SSBs) for the serving cell, rather than CORESET#0 or SIB. If the initial DL BWP configured with a separate SIB 0 includes the entire CORESET#0, the RedCap UE may use the bandwidth and location of CORESET#0 during initial access. In such a case, the NCD-SSB periodicity may not be required to be the same as the CD-SSB periodicity (although the NCD-SSB periodicity may be expected not to be smaller than the CD-SSB periodicity). If the separate initial DL BWP is configured to include the entire CORESET#0, the RedCap UE may expect the CD-SSB in this DL BWP. In some cases, the network may configure the SSB or MIB configured CORESET#0 or SIB1 to be in the initial DL BWP.

[0095] Aspects Related to RedCap Cell Selection / Reselection Procedure

[0111] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for performing various procedures by a UE that may be configured to operate in a bandwidth portion (BWP) that may be reserved for a particular type of UE, such as an initial downlink BWP reserved for reduced capacity (RedCap) UEs.

[0096]

[0112] As mentioned above, in both FR1 and FR2, a separate initial DL BWP may be configured for idle / inactive RedCap UEs via SIB. The configuration of this DL BWP may be according to the maximum UE bandwidth (BW) supported by the RedCap UE. Such a separate initial DL BWP may be configured by the network, for example, to mitigate potential resource fragmentation of the linked initial UL BWP or to offload DL traffic from MIB configured CORESET#0.

[0097]

[0113] If the RedCap-specific early DL BWP does not include the entire CORESET#0 configured by the MIB, a separate CORESET(s) and SS set(s) may be configured in the RedCap-specific early DL BWP for idle / inactive mode procedures. In such cases, SSBs may or may not be transmitted in the RedCap-specific early DL BWP. In some cases, both a common search space (CSS) set and a UE-specific (USS) set may be configured for inactive mode procedures. Such procedures may include configured grant small data transmission (CG-SDT), hybrid automatic repeat request (HARQ) retransmission of multicast and broadcast services (MBS), and mobile terminated SDG (MT-SDT) procedures.

[0098]

[0114] Aspects of the present disclosure provide mechanisms that may help support RedCap UEs and improve flexibility of RedCap UE procedures such as cell selection / reselection, subject to constraints on reduced UE complexity. The mechanisms may provide enhancements to RedCap UE cell selection and reselection procedures.

[0099]

[0115] In some cases, for initial cell selection on an NR frequency, a RedCap UE may scan a synchronization raster and search for a suitable cell of a selected public land mobile network (PLMN) or standalone non-public network (SNPN). The UE may measure CD-SSB and obtain MIB / SIB to find out whether the cell allows RedCap UEs to access. If the cell allows RedCap UEs to access, the RedCap UE may be provided with RedCap-specific cell selection criteria and a list of neighbor cells in the SIB (e.g., neighbor cells that also allow RedCap UE access).

[0100]

[0116] If an initial DL BWP is configured separately for RedCap UEs, this configuration information may also be indicated in the SIB. This configuration information may include, for example, the location, numerology, and BW of the BWP and CORESET / CSS set configured for idle mode procedures (e.g., random access, paging, broadcast / multicast). Figures 10-13 are examples of how the BWP and CORESET / CSS set may be configured within an operating (carrier) BW. The configuration information may also include the TX power, periodicity, and transmission pattern of DL RS broadcast / multicast (e.g., CD-SSB, NCD-SSB, or other DL RS) to RedCap UEs in the BWP.

[0101]

[0117] Depending on the UE capabilities and initial DL BWP configuration, RedCap UE intra / inter frequency cell selection / reselection may be based on measurements of one or more DL RSs received in idle / inactive state. These DL RSs may include, for example, one or a combination of CD-SSB, NCD-SSB transmitted in RedCap specific initial DL BWP, and other broadcast / multicast DL RSs (different from CD-SSB and NCD-SSB) transmitted in RedCap specific initial DL BWP that are quasi-co-located (QCLed) with CD-SSB or NCD-SSB. Examples of these other broadcast / multicast DL RSs include CSI-RS / TRS, DMRS for multicast / broadcast PDSCH, and scheduling PDCCH.

[0102]

[0118] Aspects of the present disclosure also provide various options for how a RedCap UE may determine resource mapping for CORESET#0.

[0103]

[0119] For example, on some frequency bands supporting a narrow channel BW of a UE, resource mapping for CORESET#0 (including SSB and CORESET#0 multiplexing pattern, number of RBs for CORESET#0, number of symbols for CORESET#0, and frequency offset between CORESET#0 and CD-SSB) may be mapped to one or more look-up tables (LUTs).

[0104]

[0120] In such a case, using a LUT-based mapping, the UE may determine the resource mapping for CORESET#0 by finding the frequency location and numerology of CD-SSB, and based on the numerology of CORESET#0 indicated by the CD-SSB MIB, the UE may find an index into the LUT for SSB / CORESET#0 multiplexing.

[0105]

[0121] In some cases, the index of the LUT may be obtained from the demodulation reference signal (DMRS) scrambling ID or the payload of the PBCH. For example, as shown in Figure 9A, in some cases, the index of the LUT may be indicated by a spare bit in the MIB payload. As shown in Figure 9B, the index of the LUT may also be indicated by a BCCH-BCH-message type indicator mapped to the MIB payload.

[0106]

[0122] In other cases, the index of the LUT may be obtained from the ssb-SubcarrierOffset (e.g., LSB, MSB, even / odd), the RRC message type indicator in the MIB (1 bit added to the MIB payload by higher layers), the half-frame index of the SSB burst (mapped to the 8-bit PHY payload of the PBCH), the DMRS position indicated by the MIB, or the system frame number (SFN) index.

[0107]

[0123] From the LUT, the UE may find an index for CORESET#0 resource mapping from the pdcch-ConfigSIB1 field in the MIB. The LUT may be any suitable LUT (such as, for example, a LUT defined by TS 38.213). For cell selection / reselection, the UE may need to decode the SIBs of the serving cell and neighboring cells. To decode the SIBs, the UE may need to find the CORESET#0 associated with the scheduling PDCCH of the SIB. After finding the SCS for the SS / PBCH block and CORESET#0 / PDCCH, the UE may need to determine which LUT should be used to look up the resource mapping for CORESET#0.

[0108]

[0124] Aspects of the present disclosure also provide various options for how a RedCap UE may perform Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ) measurements for idle / inactive mode procedures. The RSRP and RSRQ measurements may be based on various DL RSs configured in the RedCap-specific initial DL BWP.

[0109]

[0125] As shown in Figure 10, in some cases, the CD-SSB method is configured in an initial DL BWP 1005 that includes all of CORESET#0. As shown in Figure 11, in some cases, the CD-SSB method is configured in an initial DL BWP 1105 that includes only a portion of CORESET#0. As shown in Figure 12, in some cases, the CD-SSB method may be configured in a separate BWP that includes CORESET#0, while the initial DL BWP 1205 may be configured with NCD-SSB and a non-zero CORESET for RedCap UEs. As shown in Figure 13, in some cases, the initial DL BWP 1305 may be configured with other DL RSs (e.g., different from SSB).

[0110]

[0126] These SSBs and / or other DL RSs broadcast / multicast to RedCap UEs in a separate initial DL BWP may be used as QCL sources for DL ​​channels / signals as well as for spatial relationships of UL channels / signals.

[0111]

[0127] When SI acquisition, paging, and random access procedures for idle / inactive RedCap UEs are distributed across multiple DL BWPs (e.g., SI acquisition in CORESET#0, paging / RA in another separately configured initial DL BWP), RSRP / RSRQ measurements may be based on various options. According to the first option, RSRP / RSRQ measurements may be based on broadcast / multicast DL RS (CD-SSB, NCD-SSB, or other DL RS) transmitted in DL BWP configured with paging CSS set and QCL'd with paging PDCCH for idle / inactive UEs. According to the second option, RSRP / RSRQ measurements may be based on SSB (CD-SSB or NCD-SSB) QCL'd with paging PDCCH. According to the third option, RSRP / RSRQ measurements may be based on SSB (CD-SSB or NCD-SSB) used for RO selection. According to a fourth option, the RSRP / RSRQ measurements may be based on the SSBs (CD-SSB and / or NCD-SSB) used for RO selection and QCL'd with the paging PDCCH. According to a fifth option, the RSRP / RSRQ measurements may be based on a single RS type (e.g., only CD-SSB).

[0112]

[0128] When RSRP / RSRQ measurements are made in more than one DL BWP or based on more than one RS type, various parameters may be configured by the network and indicated to the RedCap UE in S1. Such parameters may include, for example, cell-specific filtering / weighting / combining parameters for multiple measurement identities, offsets applicable to RedCap (e.g., parameters Qrxlevminoffset_RedCap, Qqualminoffset_RedCap), compensation factors applicable to RedCap (Pcompensation_RedCap), and thresholds (Qrxlevmin_RedCap, Qqualmin_RedCap) are configured by the NW and indicated to the RedCap UE in SI.

[0113]

[0129] Aspects of the present disclosure also provide various options for how a RedCap UE may perform BWP switching for idle / inactive mode procedures running on two or more DL BWPs. Such options may be useful to support procedures such as on-demand requests for SI delivery, and on-demand PDCCH monitoring adaptation, with and without BWP switching.

[0114]

[0130] In some cases, after obtaining the configuration of separate early DL / UL BWPs, a RedCap UE may switch to a RedCap specific early DL / UL BWP to perform idle / inactive mode procedures, as shown in Figures 14 and 15. Such procedures may include requests for measurements, random access (ra-SearchSpace-RedCap), paging (pagingSearchSpace-RedCap), or on-demand SI (based on msg1 / msg3 / msgA / CG-PUSCH / PUCCH / SRS) for cell selection / reselection.

[0115]

[0131] Such procedures may also include Mobile Originated (MO) Small Data Transmission (SDT), or Mobile Terminated (MT) SDT, processing multicast / broadcast signaling, or positioning. Figure 16 shows an example of a DL BWP configuration that may support SDT in early BWP. This configuration may be suitable, for example, for eMBB RedCap UEs.

[0116]

[0132] In some cases, during each DRX cycle, an idle RedCap UE may monitor a paging occasion (PO) associated with a paging SS (pagingSearchSpace-RedCap) to receive RAN / CN initiated paging. In such a case, the RedCap UE has various options on what action to take upon receiving notification of an SI change applicable to the RedCap UE.

[0117]

[0133] For example, according to the first option, the RedCap UE can perform a BWP switch to a BWP containing CORESET#0 to retrieve SI updates / PWS, and switch back to the RedCap specific initial DL BWP after reacquiring the SI updates. This option can be applied, for example, to the DL BWP configurations shown in Figures 14 and 15.

[0118]

[0134] According to the second option, the RedCap UE may not need to perform a BWP switch and may initiate a RACH within a RedCap specific initial DL BWP to request an "on-demand broadcast / multicast of updated SI".

[0119]

[0135] Aspects of the present disclosure also provide various options for enhanced PDCCH monitoring. For example, PDCCH monitoring adaptation can be configured for a UE based on UE capabilities and UE assistance information (UAI).

[0120]

[0136] As used herein, PDCCH monitoring adaptation generally refers to adapting (changing) one or more PDCCH monitoring related parameters, e.g., to achieve a desired objective. For example, PDCCH monitoring parameters may be updated so that a RedCap UE monitors less frequently for PDCCH transmissions to achieve power savings. PDCCH monitoring adaptation may include, for example, updating one or more of the following: PDCCH monitoring periodicity, time offset of PDCCH monitoring window, duration of PDCCH monitoring window, time offset of PDCCH monitoring skipping window, or duration of PDCCH monitoring skipping window. In some cases, the UE may be configured for PDCCH monitoring adaptation (e.g., with a different set of parameters). In such cases, PDCCH monitoring may be activated via network signaling or automatically based on one or more conditions (e.g., when the UE switches from one BWP to another). In some cases, the network may adjust the transmission PDCCH based on the UE PDCCH monitoring adaptation. In other words, the network may send the PDCCH when the UE is monitoring a PDCCH transmission.

[0121]

[0137] Possibly, the UE may transmit a request for PDCCH monitoring adaptation when performing an idle mode procedure or an inactive mode procedure in one or more of the first DL BWP or the second DL BWP. Possibly, the request for PDCCH monitoring adaptation may be multiplexed with a UL transmission associated with a random access procedure (4-step RA or 2-step RA), a measurement report, a MO-SDT or a MT-SDT.

[0122]

[0138] In some cases, the UE may transmit a UAI for PDCCH monitoring adaptation when performing an idle mode procedure or an inactive mode procedure in the first and / or second DL BWP. The UAI may be multiplexed with UL transmissions associated with a random access procedure (4-step or 2-step RA), a measurement report, MO-SDT, or MT-SDT.

[0123]

[0139] After sending the request or UAI, the UE may monitor for an indication for PDCCH monitoring adaptation. In some cases, the indication for PDCCH monitoring adaptation may be sent in a DCI, MAC CE, or RRC message.

[0124]

[0140] During each discontinuous reception (DRX) cycle, the UE may monitor for indications for PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on the first DL BWP or the second DL BWP.

[0125]

[0141] After receiving the indication for PDCCH monitoring adaptation, the UE may update the PDCCH monitoring accordingly. For example, the UE may update one or more of the PDCCH monitoring periodicity, the time offset and duration of the PDCCH monitoring window, the time offset and duration of the PDCCH monitoring skipping window, the search space set configuration, or the CORESET configuration based on receiving the indication for PDCCH monitoring adaptation.

[0126] Exemplary Operation of User Equipment

[0142] FIG. 17 illustrates a method 1700 for wireless communication by a UE, such as the UE 104 of FIGS.

[0127]

[0143] Method 1700 begins with receiving, from a network entity, a configuration for a first DL BWP, a first CORESET configured on the first DL BWP, and one or more first SS sets within the first CORESET, at 1705. In some cases, the operations in this step may refer to or be performed by resource configuration circuitry such as that described with reference to FIG.

[0128]

[0144] Method 1700 then proceeds to step 1710, where it receives from a network entity a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets within the second CORESET. In some cases, the operations of this step may refer to or be performed by resource configuration circuitry such as that described with reference to FIG.

[0129]

[0145] Method 1700 then proceeds to step 1715, where signaling is received to configure the UE for PDCCH monitoring adaptation. In some cases, the operations of this step may refer to or be performed by PDCCH monitoring adaptation circuitry such as that described with reference to FIG.

[0130]

[0146] Method 1700 then proceeds to step 1720, where, while performing one or more idle or inactive mode procedures on at least one of the first DL BWP or the second DL BWP, monitor the PDCCH according to the PDCCH monitoring adaptation. In some cases, the operations of this step may refer to or be performed by PDCCH monitoring circuitry as described with reference to FIG.

[0131]

[0147] Various aspects relate to the method 1700, including the following aspects.

[0132]

[0148] In some aspects, the method 1700 further includes monitoring for an indication of PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during the DRX cycle.

[0133]

[0149] In some aspects, the method 1700 further includes receiving signaling indicating PDCCH monitoring adaptation on at least one of the first DL BWP or the second DL BWP as a result of the monitoring. In some aspects, the signaling indicating PDCCH monitoring adaptation is received via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof.

[0134]

[0150] In some aspects, the method 1700 further includes updating at least one of a PDCCH monitoring periodicity, a time offset of a PDCCH monitoring window, a duration of a PDCCH monitoring window, a time offset of a PDCCH monitoring skipping window, or a duration of a PDCCH monitoring skipping window based on the signaling.

[0135]

[0151] In some aspects, the PDCCH monitoring adaptation is activated when the UE switches from a first DL BWP to a second DL BWP or from the second DL BWP to the first DL BWP while in an idle or inactive mode.

[0136]

[0152] In some aspects, the total number of PDCCH decoding or channel estimation attempts of a UE within a preconfigured time span on the first DL BWP and the second DL BWP is limited by preconfigured boundaries, where the configuration of at least one of the time span or boundaries depends on at least one of the UE capabilities, the configuration of the first DL BWP, the configuration of the second DL BWP, the power saving configuration, or the coverage extension configuration.

[0137]

[0153] In some aspects, the method 1700 further includes updating at least one of an SS set or a CORESET configuration for PDCCH monitoring on at least one of the first DL BWP or the second DL BWP based on the signaling.

[0138]

[0154] In some aspects, the PDCCH monitoring adaptation is configured for the UE based on at least one of a UE capability indication or a UAI sent by the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP.

[0139]

[0155] In some aspects, the method 1700 further includes transmitting at least one of a request for PDCCH monitoring adaptation or a UAI when performing an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP.

[0140]

[0156] In some aspects, transmitting the request or UAI includes multiplexing the request or UAI with a UL transmission associated with at least one of a random access procedure, a measurement report, a mobile originated data transfer, or a mobile terminated data transfer.

[0141]

[0157] In one aspect, the method 1700, or any aspect related thereto, may be performed by an apparatus, such as a communications device 1900 of Figure 19, which includes various components operable, configured, or adapted to perform the method 1700. Communications device 1900 is described in further detail below.

[0142]

[0158] It should be noted that FIG. 17 is merely one example of a method, and that other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0143] Exemplary Operation of a Network Entity

[0159] FIG 18 illustrates an example method 1800 for wireless communication according to an aspect of the disclosure. In some aspects, a user equipment, such as the UE 104 of FIG 1 and FIG 3, or the processing system 1905 of FIG 19, may perform the method 1700. In some aspects, a base station, such as the BS 102 of FIG 1 and FIG 3, or the processing system 2005 of FIG 20, may perform the method 1800.

[0144]

[0160] FIG. 18 illustrates a method 1800 for wireless communication by a network entity, such as the BS 102 of FIGS. 1 and 3, or a separate base station as described with respect to FIG.

[0145]

[0161] The method 1800 begins with transmitting to the UE, at 1805, a configuration for a first DL BWP, a first CORESET configured on the first DL BWP, and one or more first SS sets in the first CORESET. In some cases, the operations in this step may refer to or be performed by UE configuration circuitry such as those described with reference to FIG.

[0146]

[0162] Method 1800 then proceeds to step 1810, where it transmits to the UE a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets in the second CORESET. In some cases, the operations of this step may refer to or be performed by UE configuration circuitry such as those described with reference to FIG. 20.

[0147]

[0163] Method 1800 then proceeds to step 1815, where it transmits signaling to configure the UE for PDCCH monitoring adaptation. In some cases, the operations of this step may refer to or be performed by PDCCH monitoring adaptation configuration circuitry such as that described with reference to FIG.

[0148]

[0164] Method 1800 then proceeds to step 1820, where the PDCCH is transmitted in accordance with PDCCH monitoring adaptation when participating with the UE in one or more idle or inactive mode procedures on at least one of the first DL BWP or the second DL BWP. In some cases, the operations of this step may refer to or be performed by PDCCH transmission circuitry as described with reference to FIG. 20.

[0149]

[0165] Various aspects relate to the method 1800, including the following aspects.

[0150]

[0166] In some aspects, the method 1800 further includes transmitting signaling indicating PDCCH monitoring adaptation upon performing one or more idle or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during the DRX cycle. In some aspects, the signaling indicating PDCCH monitoring adaptation is transmitted via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof.

[0151]

[0167] In some aspects, the PDCCH monitoring adaptation is activated when the UE switches from a first DL BWP to a second DL BWP or from the second DL BWP to the first DL BWP while in an idle or inactive mode.

[0152]

[0168] In some aspects, the total number of PDCCH decoding or channel estimation attempts of a UE within a preconfigured time span on the first DL BWP and the second DL BWP is limited by preconfigured boundaries, where the configuration of at least one of the time span or boundaries depends on at least one of the UE capabilities, the configuration of the first DL BWP, the configuration of the second DL BWP, the power saving configuration, or the coverage extension configuration.

[0153]

[0169] In some aspects, the method 1800 further includes updating at least one of an SS set or a CORESET configuration for transmitting a PDCCH on at least one of the first DL BWP or the second DL BWP based on the signaling.

[0154]

[0170] In some aspects, the PDCCH monitoring adaptation is configured for the UE based on at least one of a UE capability indication or a UAI received from the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP.

[0155]

[0171] In some aspects, the method 1800 further includes receiving, from the UE, at least one of a request or a UAI for PDCCH monitoring adaptation when the UE performs an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP, in some aspects the request or UAI is multiplexed with a UL transmission associated with at least one of a random access procedure, a measurement report, a mobile originated data transfer, or a mobile terminated data transfer.

[0156]

[0172] In one aspect, the method 1800, or any aspect related thereto, may be performed by an apparatus such as the communications device 2000 of Figure 20 that includes various components operable, configured, or adapted to perform the method 1800. The communications device 2000 is described in further detail below.

[0157]

[0173] It should be noted that FIG. 18 is merely one example of a method and that other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0158] Exemplary Communication Devices

[0174] 19 illustrates an aspect of an example communications device 1900. In some aspects, the communications device 1900 is user equipment, such as the UE 104 described above with respect to FIGS.

[0159]

[0175] Communications device 1900 includes a processing system 1905 coupled to a transceiver 1955 (e.g., a transmitter and / or a receiver). The transceiver 1955 is configured to transmit and receive signals for communications device 1900 via an antenna 1960, such as various signals as described herein. Processing system 1905 may be configured to perform processing functions for communications device 1900, including processing signals to be received and / or transmitted by communications device 1900.

[0160]

[0176] The processing system 1905 includes one or more processors 1910. In various aspects, the one or more processors 1910 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380 as described with respect to FIG. 3. The one or more processors 1910 are coupled to the computer-readable medium / memory 1930 via a bus 1950. In certain aspects, the computer-readable medium / memory 1930 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1910, cause the one or more processors 1910 to perform the method 1700 described with respect to FIG. 17, or any aspects related thereto. It should be noted that a reference to a processor performing a function of the communication device 1900 may include one or more processors 1910 performing that function of the communication device 1900.

[0161]

[0177] In the depicted example, the computer readable medium / memory 1930 stores code (e.g., executable instructions), such as a resource configuration code 1935, a PDCCH monitoring adaptation code 1940, and a PDCCH monitoring code 1945. Processing of the resource configuration code 1935, the PDCCH monitoring adaptation code 1940, and the PDCCH monitoring code 1945 may cause the communications device 1900 to perform the method 1700 described with respect to FIG.

[0162]

[0178] The one or more processors 1910 include circuitry configured to implement (e.g., execute) code stored in a computer-readable medium / memory 1930, including circuitry such as a resource configuration circuit 1915, a PDCCH monitoring adaptation circuit 1920, and a PDCCH monitoring circuit 1925. Processing by the resource configuration circuit 1915, the PDCCH monitoring adaptation circuit 1920, and the PDCCH monitoring circuit 1925 can cause the communications device 1900 to perform the method 1700 described with respect to FIG.

[0163]

[0179] Various components of the communications device 1900 may provide means for performing the method 1700 described with respect to Figure 17, or any aspect related thereto. For example, the means for transmitting, sending, or outputting for transmission may include the transceiver 354 and / or antenna(s) 352 of the UE 104 shown in Figure 3, and / or the transceiver 1955 and antenna 1960 of the communications device 1900 of Figure 19. The means for receiving or acquiring may include the transceiver 354 and / or antenna(s) 352 of the UE 104 shown in Figure 3, and / or the transceiver 1955 and antenna 1960 of the communications device 1900 of Figure 19.

[0164]

[0180] According to some aspects, the resource configuration circuit 1915 receives from the network entity a configuration for a first DL BWP, a first CORESET configured on the first DL BWP, and one or more first SS sets in the first CORESET. In some examples, the resource configuration circuit 1915 receives from the network entity a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets in the second CORESET.

[0165]

[0181] In accordance with some aspects, the PDCCH monitoring adaptation circuit 1920 receives signaling to configure the UE for PDCCH monitoring adaptation. In accordance with some aspects, the PDCCH monitoring circuit 1925 monitors the PDCCH in accordance with the PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP.

[0166]

[0182] In some examples, the PDCCH monitoring adaptation circuit 1920 monitors for an indication of PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during a DRX cycle. In some examples, the PDCCH monitoring adaptation circuit 1920 receives signaling indicating PDCCH monitoring adaptation on at least one of the first DL BWP or the second DL BWP as a result of the monitoring. In some aspects, the signaling indicating PDCCH monitoring adaptation is received via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof. In some examples, the PDCCH monitoring adaptation circuit 1920 updates at least one of the PDCCH monitoring periodicity, the time offset of the PDCCH monitoring window, the duration of the PDCCH monitoring window, the time offset of the PDCCH monitoring skipping window, or the duration of the PDCCH monitoring skipping window based on the signaling. In some aspects, the PDCCH monitoring adaptation is activated when the UE switches from a first DL BWP to a second DL BWP or from the second DL BWP to the first DL BWP while in an idle or inactive mode.

[0167]

[0183] In some aspects, the total number of PDCCH decoding or channel estimation attempts of the UE within a preconfigured time span on the first DL BWP and the second DL BWP is limited by a preconfigured boundary, and a configuration of at least one of the time span or boundary depends on at least one of the UE capabilities, the configuration of the first DL BWP, the configuration of the second DL BWP, the power saving configuration, or the coverage extension configuration. In some examples, the resource configuration circuit 1915 updates at least one of the SS set or CORESET configuration for PDCCH monitoring on at least one of the first DL BWP or the second DL BWP based on the signaling.

[0168]

[0184] In some aspects, the PDCCH monitoring adaptation is configured for the UE based on at least one of a UE capability indication or a UAI transmitted by the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP. In some examples, the PDCCH monitoring adaptation circuit 1920 transmits at least one of a request or a UAI for PDCCH monitoring adaptation upon performing an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP. In some aspects, transmitting the request or UAI includes multiplexing the request or UAI with a UL transmission associated with at least one of a random access procedure, a measurement report, a mobile originated data transfer, or a mobile terminated data transfer.

[0169]

[0185] 20 illustrates aspects of an exemplary communications device 2000. In some aspects, the communications device 2000 is a network entity such as the BS 102 described above with respect to FIGS.

[0170]

[0186] The communications device 2000 includes a processing system 2005 coupled to a transceiver 2055 (e.g., a transmitter and / or a receiver) and / or a network interface 2065. The transceiver 2055 is configured to transmit and receive signals for the communications device 2000 via an antenna 2060, such as various signals as described herein. The network interface 2065 is configured to obtain and transmit signals for the communications device 2000 via a communications link(s), such as a backhaul link, a midhaul link, and / or a fronthaul link as described herein, such as with respect to FIG. 2. The processing system 2005 may be configured to perform processing functions for the communications device 2000, including processing signals to be received and / or transmitted by the communications device 2000.

[0171]

[0187] The processing system 2005 includes one or more processors 2010. In various aspects, the one or more processors 2010 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340 as described with respect to FIG. 3. The one or more processors 2010 are coupled to the computer-readable medium / memory 2030 via a bus 2050. In certain aspects, the computer-readable medium / memory 2030 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 2010, cause the one or more processors 2010 to perform the method 1800 described with respect to FIG. 18, or any aspects related thereto. It should be noted that a reference to a processor of the communications device 2000 performing a function may include the one or more processors 2010 of the communications device 2000 performing that function.

[0172]

[0188] In the illustrated example, the computer readable medium / memory 2030 stores code (e.g., executable instructions), such as UE configuration code 2035, PDCCH monitoring adaptation configuration code 2040, and PDCCH transmission code 2045. Processing of the UE configuration code 2035, the PDCCH monitoring adaptation configuration code 2040, and the PDCCH transmission code 2045 may cause the communications device 2000 to perform the method 1800 described with respect to FIG.

[0173]

[0189] The one or more processors 2010 include circuitry configured to implement (e.g., execute) code stored in a computer-readable medium / memory 2030, including circuitry such as a UE configuration circuit 2015, a PDCCH monitoring adaptation configuration circuit 2020, and a PDCCH transmission circuit 2025. Processing by the UE configuration circuit 2015, the PDCCH monitoring adaptation configuration circuit 2020, and the PDCCH transmission circuit 2025 can cause the communications device 2000 to perform the method 1800 described with respect to FIG.

[0174]

[0190] Various components of the communications device 2000 may provide means for performing the method 1800 described with respect to Figure 18, or any aspect related thereto. The means for transmitting, sending, or outputting for transmission may include the transceiver 332 and / or antenna(s) 334 of the BS 102 shown in Figure 3, and / or the transceiver 2055 and antenna 2060 of the communications device 2000 of Figure 20. The means for receiving or acquiring may include the transceiver 332 and / or antenna(s) 334 of the BS 102 shown in Figure 3, and / or the transceiver 2055 and antenna 2060 of the communications device 2000 of Figure 20.

[0175]

[0191] According to some aspects, the UE configuration circuit 2015 transmits to the UE a configuration for a first DL BWP, a first CORESET configured on the first DL BWP, and one or more first SS sets in the first CORESET. In some examples, the UE configuration circuit 2015 transmits to the UE a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets in the second CORESET. According to some aspects, the PDCCH monitoring adaptation configuration circuit 2020 transmits signaling to configure the UE for PDCCH monitoring adaptation. According to some aspects, the PDCCH transmission circuit 2025 transmits a PDCCH in accordance with PDCCH monitoring adaptation when participating with the UE in one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP.

[0176]

[0192] In some examples, the PDCCH monitoring adaptation configuration circuit 2020 transmits signaling indicating PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during a DRX cycle. In some aspects, the signaling indicating PDCCH monitoring adaptation is transmitted via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof. In some aspects, the PDCCH monitoring adaptation is activated when the UE switches from the first DL BWP to the second DL BWP or from the second DL BWP to the first DL BWP while in an idle or inactive mode.

[0177]

[0193] In some aspects, the total number of PDCCH decoding or channel estimation attempts of the UE within a preconfigured time span on the first DL BWP and the second DL BWP is limited by a preconfigured boundary, and the configuration of at least one of the time span or boundary depends on at least one of the UE capability, the configuration of the first DL BWP, the configuration of the second DL BWP, the power saving configuration, or the coverage extension configuration. In some examples, the UE configuration circuit 2015 updates at least one of the SS set or CORESET configuration for transmitting the PDCCH on at least one of the first DL BWP or the second DL BWP based on the signaling. In some aspects, the PDCCH monitoring adaptation is configured for the UE based on at least one of the UE capability indication or UAI received from the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP. In some examples, the PDCCH monitoring adaptation configuration circuit 2020 receives at least one of a request or UAI for PDCCH monitoring adaptation from the UE when the UE is performing an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP. In some aspects, the request or UAI is multiplexed with a UL transmission associated with at least one of a random access procedure, a measurement report, a mobile originated data transfer, or a mobile terminated data transfer.

[0178] Example clauses

[0194] The following numbered clauses describe example implementations.

[0179]

[0195] Clause 1: A method for wireless communication by a UE, comprising: receiving, from a network entity, a configuration for a first DL BWP, a first CORESET configured on the first DL BWP, and one or more first SS sets in the first CORESET; receiving, from the network entity, a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets in the second CORESET; receiving signaling to configure the UE for PDCCH monitoring adaptation; and monitoring a PDCCH in accordance with the PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP.

[0180]

[0196] Clause 2: The method of clause 1, further comprising monitoring an indication of PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during a DRX cycle.

[0181]

[0197] Clause 3: The method of clause 1 or 2, further comprising receiving, as a result of the monitoring, signaling indicating PDCCH monitoring adaptation on at least one of the first DL BWP or the second DL BWP.

[0182]

[0198] Clause 4: The method of clause 3, wherein the signaling indicating PDCCH monitoring adaptation is received via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof.

[0183]

[0199] Clause 5: The method of clause 3, further comprising updating at least one of a PDCCH monitoring periodicity, a time offset of a PDCCH monitoring window, a duration of a PDCCH monitoring window, a time offset of a PDCCH monitoring skipping window, or a duration of a PDCCH monitoring skipping window based on the signaling.

[0184]

[0200] Clause 6: The method according to any one of clauses 1 to 5, wherein PDCCH monitoring adaptation is activated when the UE switches from a first DL BWP to a second DL BWP or switches from the second DL BWP to the first DL BWP while in an idle or inactive mode.

[0185]

[0201] Clause 7: The method according to any one of clauses 1 to 6, wherein the total number of PDCCH decoding or channel estimation attempts of the UE within a preconfigured time span on the first DL BWP and the second DL BWP is limited by preconfigured boundaries, and the configuration of at least one of the time spans or boundaries depends on at least one of the UE capabilities, the configuration of the first DL BWP, the configuration of the second DL BWP, the power saving configuration, or the coverage extension configuration.

[0186]

[0202] Clause 8: The method of any one of clauses 1 to 7, further comprising updating at least one of an SS set or a CORESET configuration for PDCCH monitoring on at least one of the first DL BWP or the second DL BWP based on the signaling.

[0187]

[0203] Clause 9: The method according to any one of clauses 1 to 8, wherein PDCCH monitoring adaptation is configured for the UE based on at least one of a UE capability indication or a UAI sent by the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP.

[0188]

[0204] Clause 10: The method of any one of clauses 1 to 9, further comprising sending at least one of a request for PDCCH monitoring adaptation or a UAI when performing an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP.

[0189]

[0205] Clause 11: The method of clause 10, wherein transmitting the request or UAI includes multiplexing the request or UAI with UL transmissions associated with at least one of a random access procedure, a measurement report, a mobile originated data transfer, or a mobile terminated data transfer.

[0190]

[0206] Clause 12: A method for wireless communication by a network entity, comprising: transmitting to a UE a configuration for a first DL BWP, a first CORESET configured on the first DL BWP, and one or more first SS sets within the first CORESET; transmitting to the UE a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets within the second CORESET; transmitting signaling to configure the UE for PDCCH monitoring adaptation; and transmitting a PDCCH in accordance with the PDCCH monitoring adaptation when participating with the UE in one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP.

[0191]

[0207] Clause 13: The method of clause 12, further comprising: transmitting signaling indicating PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during a DRX cycle.

[0192]

[0208] Clause 14: The method of clause 13, wherein the signaling indicating the PDCCH monitoring adaptation is sent via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof.

[0193]

[0209] Clause 15: The method according to any one of clauses 12 to 14, wherein PDCCH monitoring adaptation is activated when the UE switches from a first DL BWP to a second DL BWP or switches from the second DL BWP to the first DL BWP while in an idle or inactive mode.

[0194]

[0210] Clause 16: The method according to any one of clauses 12 to 15, wherein the total number of PDCCH decoding or channel estimation attempts of the UE within a preconfigured time span on the first DL BWP and the second DL BWP is limited by a preconfigured boundary, and the configuration of at least one of the time span or boundary depends on at least one of the UE capabilities, the configuration of the first DL BWP, the configuration of the second DL BWP, the power saving configuration, or the coverage extension configuration.

[0195]

[0211] Clause 17: The method of any one of clauses 12 to 16, further comprising updating at least one of an SS set or a CORESET configuration for transmitting a PDCCH on at least one of the first DL BWP or the second DL BWP based on the signaling.

[0196]

[0212] Clause 18: The method according to any one of clauses 12 to 17, wherein PDCCH monitoring adaptation is configured for the UE based on at least one of a UE capability indication or a UAI received from the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP.

[0197]

[0213] Clause 19: The method of any one of clauses 12 to 18, further comprising receiving from the UE at least one of a request for PDCCH monitoring adaptation or a UAI when the UE performs an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP.

[0198]

[0214] Clause 20: The method of clause 19, wherein the request or UAI is multiplexed with UL transmissions associated with at least one of a random access procedure, a measurement report, a mobile originated data transfer, or a mobile terminated data transfer.

[0199]

[0215] Clause 21: A processing system comprising a memory containing computer-executable instructions and one or more processors configured to execute the computer-executable instructions and cause the processing system to perform a method according to any one of clauses 1 to 20.

[0200]

[0216] Clause 22: A processing system comprising means for carrying out the method according to any one of clauses 1 to 20.

[0201]

[0217] Clause 23: A non-transitory computer-readable medium comprising computer-executable instructions that, when executed by one or more processors of a processing system, cause the processing system to perform the method of any one of clauses 1 to 20.

[0202]

[0218] Clause 24: A computer program product embodied on a computer-readable storage medium comprising code for performing the method according to any one of clauses 1 to 20.

[0203] Additional Considerations

[0219] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The embodiments described herein are not intended to limit the scope, applicability, or aspects described in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of the elements described without departing from the scope of the disclosure. Various embodiments may omit, substitute, or add various steps or components as appropriate. For example, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some embodiments may be combined in some other embodiments. For example, an apparatus may be implemented or a method may be performed using any number of the aspects described herein. Furthermore, the scope of the disclosure is intended to encompass apparatuses or methods that are implemented using other structures, functions, or structures and functions in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0204]

[0220] The various example logic blocks, modules, and circuits described in connection with this disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0205]

[0221] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, ccc, or any other order of a, b, c).

[0206]

[0222] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0207]

[0223] The methods disclosed herein include one or more actions for achieving the method. The actions of those methods may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Furthermore, various operations of the methods described above may be performed by any suitable means capable of performing the corresponding functions. Those means may include various hardware and / or software component(s) including, but not limited to, circuits, application specific integrated circuits (ASICs), or processors, and / or various hardware and / or software module(s).

[0208]

[0224] The following claims are not intended to be limited to the embodiments set forth herein, but are to be accorded the full scope consistent with the language of the claims. Within the claims, reference to an element by the singular is not intended to mean "one and only one" unless expressly stated as such, but rather "one or more." The term "several" refers to "one or more" unless expressly stated otherwise. Claim elements are not to be construed under the provisions of 35 U.S.C. 112(f) unless the element is expressly recited using the phrase "means for." All structural and functional equivalents of the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims.

Claims

1. 1. An apparatus for wireless communication in a user equipment (UE), comprising: a memory containing computer-executable instructions; and one or more processors for executing the computer-executable instructions and causing the apparatus to: receiving, from a network entity, a configuration for a first downlink (DL) bandwidth portion (BWP), a first control resource set (CORESET) configured on the first DL BWP, and one or more first search space (SS) sets within the first CORESET; receiving, from the network entity, a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets in the second CORESET; receiving signaling of a configuration for physical downlink control channel (PDCCH) monitoring adaptation; monitoring for an indication of PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during a discontinuous reception (DRX) cycle; receiving, as a result of the monitoring, signaling on at least one of the first DL BWP or the second DL BWP in accordance with the configuration to activate PDCCH monitoring adaptation; updating at least one of a PDCCH monitoring periodicity, a time offset of a PDCCH monitoring window, a duration of the PDCCH monitoring window, a time offset of a PDCCH monitoring skipping window, or a duration of the PDCCH monitoring skipping window based on the signaling activating PDCCH monitoring adaptation; causing a PDCCH to be monitored in accordance with the PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP; one or more processors configured to An apparatus comprising:

2. 2. The apparatus of claim 1, wherein the signaling indicating PDCCH monitoring adaptation is received via at least one of downlink control information (DCI), medium access control (MAC) control element (CE), radio resource control (RRC) signaling, or a combination thereof.

3. The one or more processors execute the computer-executable instructions and cause the device to: updating at least one of an SS set or a CORESET configuration for PDCCH monitoring on at least one of the first DL BWP or the second DL BWP based on the signaling; The apparatus of claim 1 , further configured to:

4. 2. The apparatus of claim 1, wherein the PDCCH monitoring adaptation is configured for the UE based on at least one of a UE capability indication or UE assistance information (UAI) sent by the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP.

5. The one or more processors execute the computer-executable instructions and cause the device to: causing at least one of a request for PDCCH monitoring adaptation or UE assistance information (UAI) to be transmitted when performing an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP; The apparatus of claim 1 , further configured to:

6. 6. The apparatus of claim 5, wherein transmitting the request or UAI includes multiplexing the request or UAI with an UL transmission associated with at least one of a random access procedure, a measurement report, a mobile-originated data transfer, or a mobile-terminated data transfer.

7. 1. An apparatus for wireless communication in a network entity, comprising: a memory containing computer-executable instructions; and one or more processors for executing the computer-executable instructions and causing the apparatus to: causing a user equipment (UE) to transmit a configuration for a first downlink (DL) bandwidth portion (BWP), a first control resource set (CORESET) configured on the first DL BWP, and one or more first search space (SS) sets within the first CORESET; causing the UE to transmit a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets in the second CORESET; causing the UE to transmit signaling to configure it for physical downlink control channel (PDCCH) monitoring adaptation; causing signaling indicating PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during a discontinuous reception (DRX) cycle; updating at least one of an SS set or a CORESET configuration for transmitting PDCCH on at least one of the first DL BWP or the second DL BWP based on the signaling indicating PDCCH monitoring adaptation; transmitting the PDCCH in accordance with the PDCCH monitoring adaptation when participating with the UE in one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP; one or more processors configured to An apparatus comprising:

8. 8. The apparatus of claim 7, wherein the signaling indicating PDCCH monitoring adaptation is transmitted via at least one of downlink control information (DCI), medium access control (MAC) control element (CE), radio resource control (RRC) signaling, or a combination thereof.

9. 8. The apparatus of claim 7, wherein PDCCH monitoring adaptation is activated when the UE switches from the first DL BWP to the second DL BWP or from the second DL BWP to the first DL BWP while in an idle or inactive mode.

10. 8. The apparatus of claim 7, wherein a total number of PDCCH decoding or channel estimation attempts of the UE within a preconfigured time span on the first DL BWP and the second DL BWP is limited by a preconfigured boundary, a configuration of at least one of the time span or the boundary depending on at least one of UE capability, a configuration of the first DL BWP, a configuration of the second DL BWP, a power saving configuration, or a coverage extension configuration.

11. 8. The apparatus of claim 7, wherein the PDCCH monitoring adaptation is configured for the UE based on at least one of a UE capability indication or a UE assistance information (UAI) received from the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP.

12. The one or more processors execute the computer-executable instructions and cause the device to: receiving, from the UE, at least one of a request for PDCCH monitoring adaptation or UE assistance information (UAI) when the UE performs an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP; It is further structured as follows:

8. The apparatus of claim 7, wherein the request or UAI is multiplexed with an UL transmission associated with at least one of a random access procedure, a measurement report, a mobile-originated data transfer, or a mobile-terminated data transfer.

13. 1. A method for wireless communication in a user equipment (UE), comprising: receiving, from a network entity, a configuration for a first downlink (DL) bandwidth portion (BWP), a first control resource set (CORESET) configured on the first DL BWP, and one or more first search space (SS) sets within the first CORESET; receiving, from the network entity, a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets in the second CORESET; receiving signaling to configure the UE for physical downlink control channel (PDCCH) monitoring adaptation; monitoring for an indication of PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during a discontinuous reception (DRX) cycle; receiving, as a result of the monitoring, signaling activating PDCCH monitoring adaptation on at least one of the first DL BWP or the second DL BWP in accordance with the configuration; and updating at least one of a PDCCH monitoring periodicity, a time offset of a PDCCH monitoring window, a duration of the PDCCH monitoring window, a time offset of a PDCCH monitoring skipping window, or a duration of the PDCCH monitoring skipping window based on the signaling activating PDCCH monitoring adaptation; monitoring a PDCCH in accordance with the PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP; A method comprising:

14. 1. A method for wireless communication in a network entity, comprising: transmitting, to a user equipment (UE), a configuration for a first downlink (DL) bandwidth portion (BWP), a first control resource set (CORESET) configured on the first DL BWP, and one or more first search space (SS) sets within the first CORESET; transmitting to the UE a configuration for a second downlink BWP, a second CORESET configured on the second DL BWP, and one or more second SS sets in the second CORESET; transmitting signaling to configure the UE for physical downlink control channel (PDCCH) monitoring adaptation; transmitting signaling indicating PDCCH monitoring adaptation when performing one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP during a discontinuous reception (DRX) cycle; updating at least one of an SS set or a CORESET configuration for transmitting PDCCH on at least one of the first DL BWP or the second DL BWP based on the signaling indicating PDCCH monitoring adaptation; transmitting a PDCCH in accordance with the PDCCH monitoring adaptation when participating with the UE in one or more idle mode procedures or inactive mode procedures on at least one of the first DL BWP or the second DL BWP; A method comprising:

15. A computer program comprising instructions: The instructions, when executed by one or more processors of an apparatus for wireless communication in a user equipment (UE), cause the one or more processors to perform the method of claim 13; 15. A computer program product, the instructions, when executed by one or more processors of an apparatus for wireless communication in a network entity, causing the one or more processors to perform the method of claim 14.

Images