Idle / Inactive Mode Procedure for Reduced Capability of User Equipment

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 No. 17 / 676,097, filed on February 18, 2022, which is assigned to the assignee of the present application and is expressly incorporated herein by reference in its entirety for all applicable purposes as if fully set forth herein.

Background Art

[0002] Field of the Disclosure

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

[0003] 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 can employ multiple access technologies that are capable of supporting communication with multiple users by sharing available wireless communication system resources with the users.

[0004]

[0004] Wireless communication systems have made significant technological advancements over the years, but challenges still remain. For example, complex and dynamic environments can still attenuate or interrupt signals between wireless transmitters and wireless receivers. Therefore, it is still desirable to improve the technical performance of wireless communication systems, including, for example, improving communication speed and data carrying capacity, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers while performing communication, improving the reliability of wireless communication, avoiding redundant transmission and / or reception and related 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, and increasing the number and types of wireless communication media available for use. Therefore, further improvements in wireless communication systems are needed to overcome the aforementioned technical challenges. [Overview of the project]

[0005]

[0005] One embodiment provides a method for wireless communication by a user device (UE), the method 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 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; receiving signaling that constitutes the UE for physical downlink control channel (PDCCH) monitoring adaptation; and monitoring the PDCCH in accordance with 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 embodiment provides a method for wireless communication by a network entity, the method 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 a 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 that constitutes the UE for PDCCH monitoring adaptation; and transmitting a PDCCH in accordance with PDCCH monitoring adaptation when the UE participates with 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 embodiments provide a device configured or otherwise adapted to operate to perform the methods described above and the methods described elsewhere in this specification; a non-temporary computer-readable medium having instructions, when executed by the processor of the device, to cause the device to perform the methods described above and the methods described elsewhere in this specification; a computer program product embodied on a computer-readable storage medium having code to perform the methods described above and the methods described elsewhere in this specification; and a device having means to perform the methods described above and the methods described elsewhere in this specification. For example, the device 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 accompanying drawings illustrate some features for illustrative purposes. [Brief explanation of the drawing]

[0009]

[0009] The accompanying drawings illustrate some features of various embodiments described herein and should not be considered to limit the scope of this disclosure. [Figure 1]

[0010] An exemplary wireless communication network is shown. [Figure 2]

[0011] This shows an exemplary isolated base station architecture. [Figure 3]

[0012] This shows exemplary configurations of a base station and exemplary user equipment. [Figure 4A]

[0013] This document illustrates various exemplary embodiments of data structures for wireless communication networks. [Figure 4B] This document illustrates various exemplary embodiments of data structures for wireless communication networks. [Figure 4C] This document illustrates various exemplary embodiments of data structures for wireless communication networks. [Figure 4D] This document illustrates various exemplary embodiments of data structures for wireless communication networks. [Figure 5]

[0014] This shows an example of a New Radio (NR) Red Cap User Equipment (UE). [Figure 6A]

[0015] A call flow diagram for a 4-step random access channel (RACH) procedure is shown. [Figure 6B] A call flow diagram for a two-step random access channel (RACH) procedure is shown. [Figure 7]

[0016] This provides an example of SSB's association with RACH occasions (ROs). [Figure 8]

[0017] Exemplary features for RedCap and non-RedCap bandwidth portions (BWP) are shown. [Figure 9A]

[0018] This disclosure provides options for lookup table (LUT)-based resource mapping according to the aspects described herein. [Figure 9B] This disclosure provides options for lookup table (LUT)-based resource mapping according to the aspects described herein. [Figure 10]

[0019] An example of a downlink reference signal (DL-RS) in a RedCap-specific initial downlink bandwidth part (DL-BWP) according to aspects of the present disclosure is shown. [Figure 11] An example of a downlink reference signal (DL-RS) in a RedCap-specific initial downlink bandwidth part (DL-BWP) according to aspects of the present disclosure is shown. [Figure 12] An example of a downlink reference signal (DL-RS) in a RedCap-specific initial downlink bandwidth part (DL-BWP) according to aspects of the present disclosure is shown. [Figure 13] An example of a downlink reference signal (DL-RS) in a RedCap-specific initial downlink bandwidth part (DL-BWP) according to aspects of the present disclosure is shown. [Figure 14]

[0020] An example of BWP switching according to aspects of the present disclosure is shown. [Figure 15] An example of BWP switching according to aspects of the present disclosure is shown. [Figure 16]

[0021] An example of bandwidth allocation according to aspects of the present disclosure is shown. [Figure 17]

[0022] A method for wireless communication is shown. [Figure 18]

[0023] A method for wireless communication is shown. [Figure 19]

[0024] Aspects of an exemplary communication device are shown. [Figure 20]

[0025] Aspects of an exemplary communication device are shown. DETAILED DESCRIPTION OF EMBODIMENTS

[0010]

[0026] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable media for performing various procedures by a user equipment (UE) that can be configured to operate in a bandwidth part (BWP) that can be reserved for a specific 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 specific purposes. For example, some UEs may be designed to be scalable and deployable in a more efficient and cost-effective way. These types of UEs may have reduced capabilities (RedCap) compared to conventional (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 Portions (BWPs), for RedCap UEs to perform specific functions, such as Random Access Channel (RACH) procedures. In some cases, a RedCap UE may have only a single radio (for example, to control costs), meaning that a RedCap UE may be able to operate on only one BWP at a time. However, this can present some challenges, as it may require the UE to retune its radio to receive specific types of signals used for particular purposes.

[0013]

[0029] For example, a network may configure RedCap UEs using a downlink BWP (DL BWP) that does not transmit certain signals (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 consist of certain DL signals, which can present challenges. For example, in some cases, synchronous 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 in order to detect the SSBs for various purposes. Since BWP switching consumes power and can increase the latency of certain procedures, managing procedures with different BWPs presents challenges.

[0014]

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

[0015] Deployment to wireless communication networks

[0031] The techniques and methods described herein can be used for a variety of wireless communication networks. While embodiments may be described herein using terms generally associated with 3G, 4G, and / or 5G wireless technologies, embodiments of this disclosure may also be applicable to other communication systems and standards not expressly mentioned herein.

[0016]

[0032] Figure 1 shows an example of a wireless communication network 100 in which embodiments described herein may be implemented.

[0017]

[0033] Generally, a wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). Network entities are generally communication devices and / or communication functions performed by communication devices. 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 example shown, 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] Figure 1 shows various exemplary UE104s, which more commonly include mobile phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE104s may also more commonly be called mobile devices, wireless devices, wireless communication devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, etc.

[0020]

[0036] BS102 communicates wirelessly with UE104 via communication link 120. The communication link 120 between BS102 and UE104 may include uplink (UL) transmissions (also referred to as reverse link) from UE104 to BS102, and / or downlink (DL) transmissions (also referred to as forward link) from BS102 to UE104. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various forms.

[0021]

[0037] BS102 may generally include NodeBs, enhanced NodeBs (eNBs), next-generation enhanced NodeBs (ng-eNBs), next-generation NodeBs (gNBs or gNodeBs), access points, base transceiver stations, radio base stations, radio transceivers, transceiver functions, transceiver points, etc. Each of BS102 may provide communication coverage to its respective geographical coverage area 110, which may sometimes be referred to as a cell and may overlap in some cases (for example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macrocell). BS may provide communication coverage to, for example, macrocells (covering relatively large geographical areas), picocells (covering relatively smaller geographical areas, such as sports stadiums), femtocells (covering relatively smaller geographical areas, such as homes), and / or other types of cells.

[0022]

[0038] Although BS102 is shown in various forms as a single communication device, BS102 can be implemented in various configurations. For example, one or more components of a base station, including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), radio units (RUs), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, can be distributed. In another example, various forms of a base station can be virtualized. More generally, a base station (e.g., BS102) can include components located in a single physical location or components located in various physical locations. In embodiments in which the base station includes components located in various physical locations, each of the various components can perform functions such that the various components collectively achieve similar functions to a base station located in a single physical location. In some embodiments, base stations including components located at various physical locations are sometimes referred to as isolated radio access network architectures, such as Open RAN (O-RAN) or Virtualized RAN (VRAN) architectures. Figure 2 illustrates and describes an exemplary isolated base station architecture.

[0023]

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

[0024]

[0040] A wireless communication network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some embodiments, the subdivision is provided based on wavelength and frequency, where frequency may also be called carrier, subcarrier, frequency channel, tone, or subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as encompassing 600 MHz to 6 GHz, which is often (interchangeably) referred to as "sub-6 GHz". Similarly, 3GPP currently defines Frequency Range 2 (FR2) as encompassing 26 to 41 GHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mm wave"). A base station configured to communicate using the mm wave / near-mm wave radio frequency band (e.g., a mm wave base station such as BS180) may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0025]

[0041] The communication link 120 between BS102 and, for example, UE104, may have one or more carriers with different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or not. Carrier allocation may be asymmetrical with respect to DL and UL (e.g., DL may be allocated more or fewer carriers than UL).

[0026]

[0042] Communications using higher frequency bands may have higher path loss and shorter range compared to lower frequency communications. Therefore, some base stations (e.g., 180 in Figure 1) can utilize beamforming with UE104 to improve path loss and range. For example, BS180 and UE104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS180 can transmit a beamformed signal to UE104 in one or more transmit directions 182'. UE104 can receive a beamformed signal from base station 180 in one or more receive directions 182''. UE104 can also transmit a beamformed signal to base station 180 in one or more transmit directions 182''. BS180 can also receive a beamformed signal from UE104 in one or more receive directions 182'. Next, base station 180 and UE104 can perform beam training to determine the best receiving and transmitting directions for BS180 and UE104, respectively. In particular, the transmitting and receiving directions for BS180 may be the same or different. Similarly, the transmitting and receiving directions for UE104 may be the same or different.

[0027]

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

[0028]

[0044] Certain UE104s can communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 can 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] EPC160 may include various functional components, including, in the example shown, a Mobility Management Entity (MME) 162, another MME 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. MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE 104 and EPC160. Generally, MME 162 provides bearer and connection management.

[0030]

[0046] Generally, user Internet Protocol (IP) packets are forwarded through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address assignment and other functions. The PDN gateway 172 and BM-SC170 are connected to IP service 176, which can include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) streaming services, and / or other IP services.

[0031]

[0047] The BM-SC170 may provide functions for MBMS user service provisioning and distribution. The BM-SC170 can function as an entry point for content provider MBMS transmissions and may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to BS102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0032]

[0048] The 5GC190 may include various functional components, including an Access and Mobility Management Function (AMF)192, other AMFs193, a Session Management Function (SMF)194, and a User Plane Function (UPF)195. The AMF192 may communicate with Unified Data Management (UDM)196.

[0033]

[0049] AMF192 is a control node that handles signaling between UE104 and 5GC190. AMF192 provides, for example, quality of service (QoS) flow and session management.

[0034]

[0050] Internet Protocol (IP) packets are forwarded via UPF195, which connects to IP service 197 and provides UE IP address assignment and other functions for 5GC190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0035]

[0051] In various forms, a network entity or network node can be implemented as, to name a few, an aggregate base station, a distributed base station, an integrated access and backhaul (IAB) node, a relay node, or a sidelink node.

[0036]

[0052] Figure 2 shows an exemplary architecture of a separate base station 200. The architecture of the separate base station 200 may include one or more central units (CUs) 210 that can communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 via one or more separate base station units (such as a quasi-real-time (quasi-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 CUs 210 can communicate with one or more distributed units (DUs) 230 via their respective midhaul links, such as an F1 interface. The DUs 230 can communicate with one or more radio units (RUs) 240 via their respective fronthaul links. The RUs 240 can communicate with their respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE104 can be serviced simultaneously by multiple RU240s.

[0037]

[0053] Each of the units, namely CU210, DU230, RU240, and the quasi-RT RIC225, non-RT RIC215, and SMO framework 205, includes, or may 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 communication interface of a unit, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit 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, those units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit or receive signals over a wireless transmission medium to one or more of the other units.

[0038]

[0054] In some embodiments, the CU210 can host one or more higher-layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptive Protocol (SDAP), etc. Each control function may implement an interface configured to communicate signals with other control functions hosted by the CU210. The CU210 may be configured to handle user plane functions (i.e., central unit-user plane (CU-User Plane, CU-UP)), control plane functions (i.e., central unit-control plane (CU-Control Plane, CU-CP)), or a combination thereof. In some implementations, the CU210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. The CU210 may be implemented to communicate with the DU230 as needed for network control and signaling.

[0039]

[0055] The DU230 can correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU240s. In some embodiments, the DU230 is used in the Third Generation Partnership Project (3 rdDepending at least partially in accordance with the functional divisions defined by the Generation Partnership Project (3GPP), the DU230 may host one or more of the following: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules related to forward error correction (FEC) coding and decoding, scrambling, modulation and demodulation). In some embodiments, the DU230 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 DU230, or with control functions hosted by the CU210.

[0040]

[0056] Lower-layer functions can be implemented by one or more RU240s. In some deployments, RU240s controlled by DU230s can 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, at least partially based on functional partitioning such as lower-layer functional partitioning. In such architectures, one or more RU240s may be implemented to handle over-the-air (OTA) communication with one or more UE104s. In some implementations, real-time and non-real-time modes of control and user-plane communication with the RU240s may be controlled by the corresponding DU230s. In some scenarios, this configuration can enable the DU230s and CU210s to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0041]

[0057] The SMO framework 205 can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements that can be managed via operational and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 290) and perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU210, DU230, RU240, and the quasi-RT RIC225. In some implementations, the SMO framework 205 can communicate with hardware embodiments of the 4G RAN, such as the Open eNB (O-eNB) 211, via the O1 interface. In addition, in some implementations, the SMO framework 205 can communicate directly with one or more RU240s via the O1 interface. The SMO framework 205 can also include non-RT RIC215s configured to support the functionality of the SMO framework 205.

[0042]

[0058] Non-RT RIC215 can be configured to include logical 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 updating, or policy-based guidance for applications / features in quasi-RT RIC225. Non-RT RIC215 may be coupled to quasi-RT RIC225 or communicate with quasi-RT RIC225 (e.g., via the A1 interface). Quasi-RT RIC225 can be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources via data acquisition and actions via an interface connecting one or more CU210s, one or more DU230s, or both, and the O-eNB to quasi-RT RIC225 (e.g., via the E2 interface).

[0043]

[0059] In some implementations, the non-RT RIC215 may receive parameter or external enrichment information from an external server to generate an AI / ML model to be deployed to the quasi-RT RIC225. Such information may be utilized by the quasi-RT RIC225 and may be received in the SMO framework 205 or the non-RT RIC215 from a non-network data source or from a network function. In some embodiments, the non-RT RIC215 or quasi-RT RIC225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC215 may monitor long-term trends and patterns in performance and employ an AI / ML model to take corrective action via the SMO framework 205 (e.g., reconfiguration via O1) or by creating a RAN management policy (e.g., an A1 policy).

[0044]

[0060] Figure 3 shows exemplary embodiments of BS102 and UE104.

[0045]

[0061] In general, BS102 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 embodiments enabling wireless transmission of data (e.g., data source 312) and other embodiments enabling wireless reception of data (e.g., data sink 339). For example, BS102 can send and receive data between BS102 and UE104. BS102 includes a controller / processor 340 which can be configured to implement various functions related to wireless communication described herein.

[0046]

[0062] Generally, the UE104 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 embodiments enabling wireless transmission of data (e.g., data source 362) and other embodiments enabling wireless reception of data (e.g., data sink 360). The UE104 includes a controller / processor 380 which can be configured to implement various functions related to wireless communication as described herein.

[0047]

[0063] In an exemplary downlink transmission, BS102 includes a transmitting processor 320 that can receive data from data source 312 and control information from controller / processor 340. The control information may be for a physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical HARQ indicator channel (PHICH), physical downlink control channel (PDCCH), 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 can process data and control information (e.g., encoding and symbol mapping) to obtain data symbols and control symbols, respectively. The transmit processor 320 can also generate reference symbols for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS), among others.

[0049]

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

[0050]

[0066] To receive downlink transmissions, UE104 includes antennas 352a-352r, which can receive downlink signals from BS102 and provide the received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r may adjust (e.g., filter, amplify, downconvert, and digitize) its respective received signal to obtain an input sample. Each demodulator may further process the input sample to obtain a received symbol.

[0051]

[0067] The MIMO detector 356 can acquire received symbols from all demodulators in the transceivers 354a to 354r, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiving processor 358 can process the detected symbols (e.g., demodulate, deinterleave, and decode), provide the decoded data for UE104 to the data sink 360, and provide the decoded control information to the controller / processor 380.

[0052]

[0068] With respect to exemplary uplink transmission, UE104 further includes a transmit processor 364 capable of receiving and processing data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for physical uplink control channel, PUCCH). The transmit processor 364 can also generate reference symbols for reference signals (e.g., for sounding reference signal, SRS). Symbols from the transmit processor 364 may, where applicable, be precoded by TX MIMO processor 366, further processed by modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS102.

[0053]

[0069] In BS102, the uplink signal from UE104 is received by antennas 334a-334t, processed by demodulators in transceivers 332a-332t, detected by MIMO detector 336 where applicable, and further processed by receiving processor 338 to obtain the decoded data and control information transmitted by UE104. The receiving processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340.

[0054]

[0070] Memories 342 and 382 may store data and program code for BS102 and UE104, respectively.

[0055]

[0071] The scheduler 344 can schedule the UE for data transmission on the downlink and / or uplink.

[0056]

[0072] In various embodiments, BS102 can 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 that output data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceiver 332a-t, antenna 334a-t, and / or other embodiments described herein. Similarly, “receiving” may refer to various mechanisms that retrieve data, such as obtaining data from antenna 334a-t, transceiver 332a-t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other embodiments described herein.

[0057]

[0073] In various embodiments, UE104 can also 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 that output data, such as outputting data from data source 362, memory 382, ​​transmitting processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antennas 352a-t, and / or other embodiments described herein. Similarly, “receiving” may refer to various mechanisms that acquire data, such as acquiring data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receiving processor 358, memory 382, ​​and / or other embodiments described herein.

[0058]

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

[0059]

[0075] Figures 4A, 4B, 4C, and 4D illustrate embodiments of data structures for wireless communication networks, such as the wireless communication network 100 in Figure 1.

[0060]

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

[0061]

[0077] Wireless communication systems can utilize orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP) on the uplink and downlink. Such systems can also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) divide the system bandwidth into multiple orthogonal subcarriers (for example, as shown in Figures 4B and 4D). Each subcarrier can be modulated with data. The modulation symbol can be transmitted using OFDM in the frequency domain and using SC-FDM in the time domain.

[0062]

[0078] A wireless communication frame structure can be frequency division duplex (FDD), where for a given set of subcarriers, the subframes within that set are dedicated to either DL or UL. A wireless communication frame structure can also be time division duplex (TDD), where for a given set of subcarriers, the subframes within that set are dedicated to 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 can be configured in 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 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may contain one or more time slots. In some examples, each slot may contain 7 or 14 symbols depending on the slot configuration. Subframes may also contain minislots, generally with fewer symbols than the entire slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0064]

[0080] Generally, the number of slots within a subframe depends on the slot configuration and numerology. In slot configuration 0, different numerologies (μ) 0-5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. In slot configuration 1, different numerologies 0-2 allow for 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2 μ slots / subframe. Subcarrier spacing and symbol length / duration are features of the numerology. Subcarrier spacing is 2 μIt may also be equal to ×15kHz, where μ is numerology 0 to 5. Thus, numerology μ=0 has a subcarrier interval of 15kHz, and numerology μ=5 has a subcarrier interval of 480kHz. The symbol length / duration is inversely proportional to the subcarrier interval. Figures 4A, 4B, 4C, and 4D give examples of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25ms, the subcarrier interval is 60kHz, and the symbol duration is approximately 16.67μs.

[0065]

[0081] As shown in Figures 4A, 4B, 4C, and 4D, a resource grid can be used to represent the frame structure. Each time slot contains a resource block (RB) (also called Physical RBs, PRBs) spanning 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 Figure 4A, some of the REs carry reference (pilot) signals (RS) for the UE (e.g., UE104 in Figures 1 and 3). RS may include demodulated RS (DMRS) and channel state information reference signals (CSI-RS) for channel estimation in the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0067]

[0083] Figure 4B shows an example of various DL channels within a frame subframe. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE containing nine RE groups (REGs), and each REG containing four consecutive REs within a single OFDM symbol.

[0068]

[0084] A primary synchronization signal (PSS) may be present within symbol 2 of a specific 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 within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identification information and the timing of the radio frame.

[0070]

[0086] Based on the physical layer identification information and the group number of the physical layer cell identification information, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DMRS described above. The physical broadcast channel (PBCH) carrying 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 through the PBCH such as system information blocks (SIBs), and paging messages.

[0071]

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

[0072]

[0088] Figure 4D shows an example of various UL channels within a frame subframe. In one configuration, the PUCCHs may be arranged as shown. The PUCCHs carry 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 PUCCHs carry 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 can 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), as well as other verticals such as ultra-reliable low latency communication (URLLC) and / or vehicle-to-everything (V2X) communication. In some wireless communication standards (e.g., Rel-17 and later), there may be a strong demand for new radio (NR) to be scalable and deployable in a more efficient and cost-effective way. Thus, a new UE type with reduced capabilities (RedCap) has been introduced. RedCap UEs may offer relaxed peak throughput (e.g., 20MHz), as well as lower latency and / or reliability requirements. Furthermore, RedCap UEs may offer lower device costs (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 eMBBs 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 can be used both during and after initial access. A RedCap UE may not be configured to support a BWP 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 a RedCap UE are permitted to exceed the maximum bandwidth of the initial BWP. A RedCap UE may switch to a non-initial BWP by using the BWP switching mechanism described in Figure 8 below.

[0074]

[0090] In many use cases, RedCap UE can be implemented in device designs with a more compact form factor. RedCap UE can also support frequency range (FR) 1 and / or 2 bands for frequency division duplex (FDD) and / or time division duplex (TDD) communication. For F1, restricted basic BWP operation can be used as the starting point for RedCap UE capabilities. Alternatively, unrestricted basic BWP operation can be used as the starting point for RedCap UE capabilities. For FR1 in TDD, the center frequency may be the same for initial DL and UL BWPs used during random access for RedCap UE. The center frequency may be the same for non-initial DL and UL BWPs having the same BWP identifier (BWP ID) for RedCap UE.

[0075]

[0091] Therefore, some design objectives of the NR RedCap UE may include scalable resource allocation, coverage expansion for DL ​​and / or UL, power savings in all RRC states, and / or coexistence with NR Premium UEs.

[0076]

[0092] As shown in Figure 5, the NR-RedCap UE can be a smart wearable device, a sensor / camera, or any other device configured for relaxed Internet of Things (IoT) communication. Furthermore, the 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, the functions of a relaxed IoT device may overlap with those of a URLLC device, the functions of a smart wearable device may overlap with those of a low-power wide-area (LPWA) massive machine-type communication (mMTC) device, and / or the functions of a sensor / camera may overlap with those of an eMBB device.

[0077] Example RACH procedure

[0093] A Random Access Channel (RACH) is so named because it refers to a wireless channel (medium) that can be shared by multiple UEs and is used by UEs to access a network (randomly) for communication. For example, a RACH may be used to access the network for call setup and data transmission. In some cases, a RACH may be used for initial access to the network when a UE switches from idle mode to active mode of a Radio Resource Control (RRC) connection, or when performing a handover within an RRC connection mode. Furthermore, a RACH may be used for incoming downlink (DL) and / or uplink (UL) data when a UE is in RRC idle mode or RRC inactive mode, and when re-establishing a connection with the network.

[0078]

[0094] Figure 6A is a timing (or “call flow”) figure 600A illustrating an exemplary four-step RACH procedure according to a particular aspect of the present disclosure. A first message (MSG1) may be sent from UE104 to BS102 over a physical random access channel (PRACH). In this case, MSG1 may consist only of the RACH preamble. BS102 may respond with a random access response (RAR) message (MSG2), which may include the identifier (ID), timing advance (TA), uplink grant, cell radio network temporary identifier (C-RNTI), and backoff indicator of the RACH preamble. MSG2 may include a PDCCH communication containing control information for subsequent communications on the PDSCH, as shown. In response to MSG2, MSG3 is sent from UE104 to BS102 over the PUSCH. MSG3 may include one or more of the following: an RRC connection request, a tracking area update request, a system information request, a positioning fix or positioning signal request, or a scheduling request. Next, BS110 responds with MSG4, which may include a conflict resolution message.

[0079]

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

[0080]

[0096] Figure 6B is a call flow diagram 600B illustrating an exemplary two-step RACH procedure according to a particular aspect of the present disclosure. A first extended message (msgA) may be sent from UE 104 to BS 102. In a particular aspect, msgA may include some or all of the information from MSG1 and MSG3 from a 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 a particular aspect, msgA may include a RACH preamble for random access and a payload. 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). BS 102 may respond with a random access response (RAR) message (msgB) which may effectively combine MSG2 and MSG4 as described above. For example, msgB may include the ID of the RACH preamble, timing advance (TA), backoff indicator, conflict resolution message, UL / DL grant, and transmit power control (TPC) command.

[0081]

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

[0082]

[0098] Random access message (msgA) transmission occasions generally include an msgA preamble occasion (for transmitting a preamble signal) and an msgA payload occasion (for transmitting a PUSCH). An msgA preamble transmission generally involves the following: (1) Selection of preamble sequence, and (2) Selection of preamble occasions in the time / frequency domain (for transmitting the selected preamble sequence) Sending a msgA payload generally involves the following: (1) Construction of random access message payloads (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 that are sent (by gNB using different beams) and associated with a finite set of time / frequency resources that define RACH occasions (ROs) and PRUs. Upon detecting an SSB, the UE may select the ROs and one or more PRUs associated with that SSB for MSG1 / msgA transmissions. In some cases, the ROs associated with a detected SSB may fall within the RedCap UE bandwidth, and the RedCap UE may utilize a separate initial UL BWP for RedCap (which is not expected to exceed the maximum RedCap UE bandwidth), which may include ROs for the RedCap UE. ROs may be exclusive to RedCap UEs or may be shared with non-RedCap UEs. A finite set of ROs and PRUs can help reduce monitoring overhead (blind decoding) by the base station.

[0084]

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

[0085]

[0101] The two-step RACH procedure can operate in any RRC state and any supported cell size. Networks using the two-step RACH procedure can typically support competition-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 exists one or more predefined ROs for that SS block, each having a specific time and frequency offset and direction (for example, specific to the selected SSB). Figure 7 shows an exemplary association (mapping) between the SSB and ROs.

[0087]

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

[0088] Overview of the dedicated RedCap BWP

[0104] Due to differences in capabilities, RedCap UEs and conventional (e.g., non-RedCap or legacy) UEs (due to their lower bandwidth capabilities) may be configured to operate in bandwidth sections (BWPs) with different characteristics. Table 800 in Figure 8 summarizes some of these differences. For example, a conventional non-RedCap initial downlink (DL) BWP may include the SSB, the RACH Common Search Space (CSS), and CORESET0. As shown in Figure 8, a RedCap initial DL BWP may include, for example, the RACH CSS, but may not include the SSB, CORESET (e.g., CORESET0, CORESET for paging), and / or the System Information Block (SIB). In other cases, a RedCap UE may not include the RACH CSS, but may include a CORESET (e.g., CORESET0). Similarly, a RedCap non-initial DL BWP may not include the SSB or system information, and may not be able to access this information. While operating without specific information can significantly reduce the complexity of a RedCap UE, a RedCap UE operating on these BWPs without access to information (e.g., SSBs) cannot benefit from that information while running on the BWP.

[0089]

[0105] As a result, RedCap UEs operating in these BWPs cannot benefit from SSBs. However, aspects of this disclosure may enable RedCap UEs to implement extended timelines, thereby enabling RedCap UEs to switch to a different BWP (e.g., a non-RedCap initial DL BWP) during the RACH procedure to monitor for SSBs. After detecting an SSB, RedCap UEs can then return (e.g., to the RedCap initial BWP) to resume the RACH procedure.

[0090]

[0106] Therefore, the techniques presented herein may help address potential problems caused by the RedCap UE's inability to measure and track the SSB during the RACH procedure. If the UE fails to receive the RAR after sending the RACH preamble and is not permitted to monitor the SSB, potential problems can arise because the UE must re-select the RACH resource using the same SSB during RACH retransmission (despite the previous failure). In some cases, the failure to track and measure the SSB during RedCap BWP may result in the UE not configuring CORESET sets and CSS sets (for example, for paging, small data transmissions, random access, etc.).

[0091]

[0107] In some cases, a UE may be able to increment its power ramping counter during RACH retransmission, but it cannot change the SSB. This can lead to UE congestion during RACH retransmission, for example, when other UEs may reuse the same SSB for RACH transmission.

[0092]

[0108] Generally, conventional RedCap UEs cannot track SSBs from the time of initial Msg1 transmission until the time the network configures the UE using active BWPs (including non-cell-defined SSBs) via 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 separate initial DL BWPs are configured for random access rather than paging, a RedCap UE in idle / inactive mode may not expect that the DL BWP to include an SSB (e.g., a cell defining SSB or CD-SSB), CORESET#0, or SIB transmission. Therefore, a RedCap UE performing random access in a separate DL BWP may assume that it does not need to monitor paging in a BWP containing CORESET#0.

[0094]

[0110] If the initial DL BWP is configured for paging, the RedCap UE may expect the DL BWP to contain non-cell-defined SSBs (NCD-SSBs) for serving cells, rather than CORESET#0 or SIBs. If the initial DL BWP, configured with a separate SIB 0, contains 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 need to be the same as that of the CD-SSB (however, the NCD-SSB periodicity may be expected not to be smaller than that of the CD-SSB). If a separate initial DL BWP is configured to contain the entire CORESET#0, the RedCap UE may expect a CD-SSB in this DL BWP. In some cases, the network may be configured to have an SSB or MIB-configured CORESET#0 or SIB1 within the initial DL BWP.

[0095] Aspects related to the RedCap cell selection / reselection procedure

[0111] Aspects of this disclosure provide apparatus, methods, processing systems, and computer-readable media for performing various procedures by a UE that can 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 a reduced-capacity (RedCap) UE.

[0096]

[0112] As described above, in both FR1 and FR2, a separate initial DL BWP may be configured via SIB for idle / inactive RedCap UEs. The configuration of this DL BWP may depend on 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 initial DL BWP does not include the entire CORESET#0 configured by the MIB, separate CORESETs and SS sets may be configured in the RedCap-specific initial DL BWP for idle / inactive mode procedures. In such cases, the SSB may or may not be transmitted in the RedCap-specific initial DL BWP. In some cases, both the Common Search Space (CSS) set and the UE-Specific (USS) set may be configured for inactive mode procedures. Such procedures may include configured Grant Small Data Transmission (CG-SDT), Hybrid Automatic Retransmission Request (HARQ) retransmissions for multicast and broadcast services (MBS), and Mobile Incoming Data Data (MT-SDT) procedures.

[0098]

[0114] Aspects of this disclosure may help support RedCap UE and provide a mechanism that may help improve the flexibility of RedCap UE procedures such as cell selection / reselection, in accordance with the limitations on reduced UE complexity. The mechanism may provide extensions to RedCap UE cell selection and reselection procedures.

[0099]

[0115] In some cases, for initial cell selection on the NR frequency, the RedCap UE may scan the synchronization raster and search for suitable cells in the selected Public Land Mobile Network (PLMN) or Standalone Non-Public Network (SNPN). The UE may measure the CD-SSB and obtain the MIB / SIB to determine whether the cell allows the RedCap UE to access it. If the cell allows the RedCap UE to access it, the RedCap UE may provide the RedCap-specific cell selection criteria and a list of neighboring cells in the SIB (e.g., neighboring cells that also allow RedCap UE access).

[0100]

[0116] If the initial DL BWP is configured separately for the RedCap UE, this configuration information may also be shown in the SIB. This configuration information may include, for example, the location, numerology, and BW of the BWP and CORESET / CSS sets configured for idle mode procedures (e.g., random access, paging, broadcast / multicast). Figures 10–13 show examples of how the BWP and CORESET / CSS sets may be configured within the operational (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 the RedCap UE within the BWP.

[0101]

[0117] Depending on the UE capabilities and initial DL BWP configuration, intra / interfrequency cell selection / reselection of a RedCap UE may be based on measurements of one or more DL RSs received in an idle / inactive state. These DL RSs may include, for example, CD-SSB, NCD-SSB transmitted in the RedCap-specific initial DL BWP, and one or a combination thereof of other broadcast / multicast DL RSs (different from CD-SSB and NCD-SSB) transmitted in the RedCap-specific initial DL BWP that are pseudo-collated (QCL) 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 this disclosure also provide various options regarding how RedCap UE may determine resource mapping for CORESET#0.

[0103]

[0119] For example, on several frequency bands supporting the UE's narrow channel BW, the resource mapping for CORESET#0 (including the SSB and CORESET#0 multiplexing patterns, the number of RBs for CORESET#0, the number of symbols for CORESET#0, and the frequency offset between CORESET#0 and CD-SSB) can be mapped to one or more lookup tables (LUTs).

[0104]

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

[0105]

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

[0106]

[0122] In other cases, the LUT index may be obtained from the ssb-SubcarrierOffset (e.g., LSB, MSB, even / odd), the MIB's RRC message type indicator (a single bit added to the MIB payload by the upper layer), 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 the CORESET#0 resource mapping in the pdcch-ConfigSIB1 field in the MIB. The LUT can be any suitable LUT (such as the LUT specified by TS 38.213). For cell selection / reselection, the UE may need to decode the SIBs of the serving cell and adjacent 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 SS / PBCH blocks and the SCS for 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 this disclosure also provide various options for how the RedCap UE may perform reference signal received power (RSRP) and reference signal received quality (RSRQ) for idle / inactive mode procedures. RSRP and RSRQ measurements may be based on various DL RS 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 using NCD-SSB and a non-zero CORESET for RedCap UE. As shown in Figure 13, in some cases the initial DL BWP 1305 may be configured using other DL RS (e.g., different from SSB).

[0110]

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

[0111]

[0127] When the 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), the RSRP / RSRQ metric can be based on various options. According to the first option, the RSRP / RSRQ metric can be based on a broadcast / multicast DL RS (CD-SSB, NCD-SSB, or other DL RS) transmitted in the DL BWP, configured with a paging CSS set and QCLed with a paging PDCCH for idle / inactive UEs. According to the second option, the RSRP / RSRQ metric can be based on an SSB (CD-SSB or NCD-SSB) QCLed with a paging PDCCH. According to the third option, the RSRP / RSRQ metric can be based on an SSB (CD-SSB or NCD-SSB) used for RO selection. According to the fourth option, the RSRP / RSRQ measurement may be based on the RO selection and paging PDCCH and QCL-treated SSB (CD-SSB and / or NCD-SSB). According to the fifth option, the RSRP / RSRQ measurement may be based on a single RS type (e.g., CD-SSB only).

[0112]

[0128] When RSRP / RSRQ measurements are performed in two or more DL BWPs or based on two or more RS types, various parameters may be configured by the network and shown to the RedCap UE in S1. Such parameters may include, for example, cell-specific filtering / weighting / joining parameters for multiple measurement identification information, RedCap-applicable offsets (e.g., parameters Qrxlevminoffset_RedCap, Qqualminoffset_RedCap), RedCap-applicable compensation coefficients (Pcompensation_RedCap), and thresholds (Qrxlevmin_RedCap, Qqualmin_RedCap) configured by the network and shown to the RedCap UE in SI.

[0113]

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

[0114]

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

[0115]

[0131] Such procedures may also include mobile outgoing (MO) small data transmission (SDT) or mobile incoming (MT) SDT, processing multicast / broadcast signaling, or positioning. Figure 16 shows an example of a DL BWP configuration that can support SDT in the initial BWP. This configuration may be suitable, for example, for the eMBB RedCap UE.

[0116]

[0132] In some cases, during each DRX cycle, an idle RedCap UE may monitor the paging occasion (PO) associated with the paging SS (pagingSearchSpace-RedCap) to receive RAN / CN start paging. In such cases, the RedCap UE has various options for what action to take when it receives 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 the SI update / PWS, and after reacquiring the SI update, switch back to the RedCap-specific initial DL BWP. This option can be applied, for example, to the DL BWP configuration shown in Figures 14 and 15.

[0118]

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

[0119]

[0135] Aspects of this disclosure also provide various options for enhanced PDCCH monitoring. For example, PDCCH monitoring adaptations may 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 (modifying) one or more PDCCH monitoring-related parameters to achieve a desired objective, for example. For example, PDCCH monitoring parameters may be updated so that a RedCap UE does not monitor PDCCH transmissions more frequently in order to achieve power savings. PDCCH monitoring adaptation may include updating one or more of the following: PDCCH monitoring periodicity, PDCCH monitoring window time offset, PDCCH monitoring window duration, PDCCH monitoring skipping window time offset, or PDCCH monitoring skipping window duration. In some cases, a UE may be configured for PDCCH monitoring adaptation (for example, 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 (for example, when the UE switches from one BWP to another). In some cases, the network may adjust the transmitted PDCCH based on the UE PDCCH monitoring adaptation. In other words, the network can send a PDCCH when the UE is monitoring for PDCCH transmissions.

[0121]

[0137] In some cases, the UE may send 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. In some cases, the request for PDCCH monitoring adaptation may be multiplexed using a random access procedure (4-step RA or 2-step RA), measurement report, or UL transmission associated with MO-SDT or 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 using UL transmissions associated with random access procedures (4-step or 2-step RA), measurement reports, MO-SDT, or MT-SDT.

[0123]

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

[0124]

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

[0125]

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

[0126] Example operation of user equipment

[0142] Figure 17 shows a method 1700 for wireless communication by a UE, such as UE104 in Figures 1 and 3.

[0127]

[0143] Method 1700 begins in 1705 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. In some cases, the operation of this step may refer to or be performed by a resource configuration circuit as described with reference to Figure 19.

[0128]

[0144] Method 1700 then proceeds to step 1710, where it 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 within the second CORESET. In some cases, the operation of this step may refer to or be performed by a resource configuration circuit as described with reference to Figure 19.

[0129]

[0145] Method 1700 then proceeds to step 1715, where it receives signaling that constitutes the UE for PDCCH monitoring adaptation. In some cases, the operation of this step may refer to or be performed by a PDCCH monitoring adaptation circuit, such as the one described with reference to Figure 19.

[0130]

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

[0131]

[0147] Various embodiments relate to Method 1700, including the following embodiments.

[0132]

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

[0133]

[0149] In some embodiments, method 1700 further includes receiving signaling indicating PDCCH monitoring adaptation on at least one of a first DL BWP or a second DL BWP as a result of monitoring. In some embodiments, 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 embodiments, method 1700 further includes updating at least one of the following based on signaling: PDCCH monitoring periodicity, PDCCH monitoring window time offset, PDCCH monitoring window duration, PDCCH monitoring skipping window time offset, or PDCCH monitoring skipping window duration.

[0135]

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

[0136]

[0152] In some embodiments, the total number of PDCCH decoding or channel estimation attempts of a UE within a pre-configured time span on a first DL BWP and a second DL BWP is limited by a pre-configured boundary, where 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, a power saving configuration, or a coverage extension configuration.

[0137]

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

[0138]

[0154] In some embodiments, the PDCCH monitoring adaptation is configured for the UE based on at least one of the UE capability instructions or UAI transmitted 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 embodiments, method 1700 further includes sending at least one of a PDCCH monitoring adaptation request or 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 embodiments, transmitting a request or UAI involves multiplexing the request or UAI with a UL transmission associated with at least one of the following: a random access procedure, measurement reporting, mobile outgoing data transfer, or mobile incoming data transfer.

[0141]

[0157] In one embodiment, Method 1700, or any embodiment relating thereto, may be carried out by a device such as the communication device 1900 of Figure 19, which includes various components configured or adapted to operate in order to perform Method 1700. The communication device 1900 will be described in more detail below.

[0142]

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

[0143] Exemplary behavior of network entities

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

[0144]

[0160] Figure 18 shows a method 1800 for wireless communication by a network entity, such as BS102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2.

[0145]

[0161] Method 1800 begins in 1805 by transmitting 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 within the first CORESET. In some cases, the operation of this step may refer to or be performed by a UE configuration circuit as described with reference to Figure 20.

[0146]

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

[0147]

[0163] Method 1800 then proceeds to step 1815, where it transmits signaling that constitutes the UE for PDCCH monitoring adaptation. In some cases, the operation of this step may refer to or be performed by a PDCCH monitoring adaptation configuration circuit, such as the one described with reference to Figure 20.

[0148]

[0164] Method 1800 then proceeds to step 1820, where, when the UE participates in one or more idle-mode or inactive-mode procedures on at least one of the first DL BWP or the second DL BWP, it transmits a PDCCH according to the PDCCH monitoring adaptation. In some cases, the operation of this step may refer to or be performed by a PDCCH transmitting circuit as described with reference to Figure 20.

[0149]

[0165] Various embodiments relate to Method 1800, including the following embodiments.

[0150]

[0166] In some embodiments, method 1800 further includes transmitting a signaling indicating PDCCH monitoring adaptation when performing one or more idle-mode or inactive-mode procedures on at least one of the first DL BWP or the second DL BWP during a DRX cycle. In some embodiments, 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 embodiments, PDCCH monitoring adaptation is activated when the UE switches from a first DL BWP to a second DL BWP, or from a second DL BWP to a first DL BWP, while the UE is in idle or inactive mode.

[0152]

[0168] In some embodiments, the total number of PDCCH decoding or channel estimation attempts of a UE within a pre-configured time span on a first DL BWP and a second DL BWP is limited by a pre-configured boundary, where 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, a power saving configuration, or a coverage extension configuration.

[0153]

[0169] In some embodiments, method 1800 further includes updating at least one of SS sets or CORESET configurations for transmitting a PDCCH on at least one of a first DL BWP or a second DL BWP based on signaling.

[0154]

[0170] In some embodiments, the PDCCH monitoring adaptation is configured for the UE based on at least one of the UE capability instructions 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.

[0155]

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

[0156]

[0172] In one embodiment, Method 1800, or any embodiment relating thereto, may be carried out by a device such as the communication device 2000 of Figure 20, which includes various components configured or adapted to operate in order to perform Method 1800. The communication device 2000 will be described in more detail below.

[0157]

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

[0158] Exemplary communication devices

[0174] Figure 19 shows an exemplary embodiment of the communication device 1900. In some embodiments, the communication device 1900 is a user device such as the UE104 described in relation to Figures 1 and 3.

[0159]

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

[0160]

[0176] The processing system 1905 includes one or more processors 1910. In various embodiments, one or more processors 1910 may represent one or more of the receiving processor 358, transmitting processor 364, TX MIMO processor 366, and / or controller / processor 380, as described with respect to Figure 3. One or more processors 1910 are coupled to computer-readable medium / memory 1930 via bus 1950. In certain embodiments, computer-readable medium / memory 1930 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1910, cause one or more processors 1910 to execute method 1700 as described with respect to Figure 17, or any related embodiments thereof. Note that references to processors performing the functions of the communication device 1900 may include one or more processors 1910 that perform those functions of the communication device 1900.

[0161]

[0177] In the illustrated example, the computer-readable medium / memory 1930 stores codes (e.g., executable instructions) such as resource configuration code 1935, PDCCH monitoring adaptation code 1940, and PDCCH monitoring code 1945. Processing of resource configuration code 1935, PDCCH monitoring adaptation code 1940, and PDCCH monitoring code 1945 causes the communication device 1900 to execute the method 1700 described with respect to Figure 17, or any related aspect thereof.

[0162]

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

[0163]

[0179] Various components of the communication device 1900 can provide means for performing the method 1700 described with respect to Figure 17, or any related aspect thereof. For example, 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 communication device 1900 shown in Figure 19. 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 communication device 1900 shown in Figure 19.

[0164]

[0180] In some embodiments, 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 within 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 within the second CORESET.

[0165]

[0181] In some embodiments, the PDCCH monitoring adaptation circuit 1920 receives signaling that constitutes the UE for PDCCH monitoring adaptation. In some embodiments, the PDCCH monitoring circuit 1925 monitors the PDCCH in accordance with 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 adaptive circuit 1920 monitors for PDCCH monitoring adaptive instructions when executing one or more idle-mode 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 adaptive circuit 1920 receives signaling indicating PDCCH monitoring adaptive on at least one of the first DL BWP or the second DL BWP as a result of monitoring. In some embodiments, the signaling indicating PDCCH monitoring adaptive is received via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof. In some examples, the PDCCH monitoring adaptive circuit 1920 updates at least one of the PDCCH monitoring periodicity, PDCCH monitoring window time offset, PDCCH monitoring window duration, PDCCH monitoring skipping window time offset, or PDCCH monitoring skipping window duration based on the signaling. In some embodiments, PDCCH monitoring adaptation is activated when the UE switches from a first DL BWP to a second DL BWP, or from a second DL BWP to a first DL BWP, while the UE is in idle or inactive mode.

[0167]

[0183] In some embodiments, the total number of PDCCH decoding or channel estimation attempts of the UE within a pre-configured time span on the first DL BWP and the second DL BWP is limited by a pre-configured boundary, 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 expansion configuration. In some examples, the resource configuration circuit 1915 updates at least one of the SS set or CORESET configurations for PDCCH monitoring on at least one of the first DL BWP or the second DL BWP based on signaling.

[0168]

[0184] In some embodiments, PDCCH monitoring adaptation is configured for the UE based on at least one of UE capability instructions or UAIs 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 the requests or UAIs for PDCCH monitoring adaptation 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. In some embodiments, transmitting a request or UAI involves multiplexing the request or UAI with a UL transmission associated with at least one of a random access procedure, measurement report, mobile outgoing data transfer, or mobile incoming data transfer.

[0169]

[0185] Figure 20 shows an exemplary embodiment of the communication device 2000. In some embodiments, the communication device 2000 is a network entity such as BS 102 described above with respect to Figures 1 and 3.

[0170]

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

[0171]

[0187] The processing system 2005 includes one or more processors 2010. In various embodiments, one or more processors 2010 may represent one or more of the receiving processor 338, transmitting processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to Figure 3. One or more processors 2010 are coupled to computer-readable medium / memory 2030 via bus 2050. In certain embodiments, computer-readable medium / memory 2030 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 2010, cause one or more processors 2010 to execute method 1800 as described with respect to Figure 18, or any related embodiments thereof. Note that references to processors of communication devices 2000 that perform functions may include one or more processors 2010 of the communication devices 2000 that perform those functions.

[0172]

[0188] In the illustrated example, the computer-readable medium / memory 2030 stores codes (e.g., executable instructions) such as the UE configuration code 2035, the PDCCH monitoring adaptive configuration code 2040, and the PDCCH transmission code 2045. Processing the UE configuration code 2035, the PDCCH monitoring adaptive configuration code 2040, and the PDCCH transmission code 2045 can cause the communication device 2000 to execute the method 1800 described with respect to Figure 18, or any related aspect thereof.

[0173]

[0189] One or more processors 2010 include circuits configured to implement (e.g., execute) code stored in computer-readable medium / memory 2030, including circuits such as a UE configuration circuit 2015, a PDCCH monitoring adaptive configuration circuit 2020, and a PDCCH transmission circuit 2025. Processing by the UE configuration circuit 2015, the PDCCH monitoring adaptive configuration circuit 2020, and the PDCCH transmission circuit 2025 can cause the communication device 2000 to perform the method 1800 described with respect to Figure 18, or any related aspect thereof.

[0174]

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

[0175]

[0191] In some embodiments, 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 within 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 within the second CORESET. In some embodiments, the PDCCH monitoring adaptive configuration circuit 2020 transmits signaling that configures the UE for PDCCH monitoring adaptive. In some embodiments, the PDCCH transmitting circuit 2025 transmits the PDCCH according to PDCCH monitoring adaptive 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 embodiments, the PDCCH monitoring adaptive configuration circuit 2020 transmits signaling indicating PDCCH monitoring adaptive when executing one or more idle-mode or inactive-mode procedures on at least one of the first DL BWP or the second DL BWP during a DRX cycle. In some embodiments, the signaling indicating PDCCH monitoring adaptive is transmitted via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof. In some embodiments, PDCCH monitoring adaptive 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 idle or inactive mode.

[0177]

[0193] In some embodiments, the total number of PDCCH decoding or channel estimation attempts of the UE within a pre-configured time span on the first DL BWP and the second DL BWP is limited by a pre-configured boundary, where at least one of the time spans or boundary configurations 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 configurations for transmitting PDCCH on at least one of the first DL BWP or the second DL BWP based on signaling. In some embodiments, the PDCCH monitoring adaptation is configured for the UE based on at least one of the UE capability instructions 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 adaptive configuration circuit 2020 receives at least one 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 embodiments, the request or UAI is multiplexed with a UL transmission associated with at least one of a random access procedure, measurement report, mobile outgoing data transfer, or mobile incoming data transfer.

[0178] Exemplary clause

[0194] Implementation examples are described in the following numbered clauses.

[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 within the first CORESET; receiving 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; receiving signaling that constitutes the UE for PDCCH monitoring adaptation; and monitoring the PDCCH in accordance with 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 according to Clause 1, further comprising monitoring PDCCH monitoring adaptation instructions 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 according to Clause 1 or 2, further comprising receiving, as a result of 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 according to Clause 3, wherein 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 according to Clause 3, further comprising updating at least one of the following based on signaling: PDCCH monitoring periodicity, PDCCH monitoring window time offset, PDCCH monitoring window duration, PDCCH monitoring skipping window time offset, or PDCCH monitoring skipping window duration.

[0184]

[0200] Clause 6: The method described in any one of Clauses 1 to 5, 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 the UE is in 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 a UE within a pre-configured time span on the first DL BWP and the second DL BWP is limited by a pre-configured 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.

[0186]

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

[0187]

[0203] Clause 9: The method of any one of Clauses 1 to 8, wherein the PDCCH monitoring adaptation is configured for the UE based on at least one of the UE capability instructions or UAI transmitted 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 PDCCH monitoring adaptation request or 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 the transmission of a request or UAI is multiplexed with a UL transmission associated with at least one of the following: a random access procedure, measurement report, mobile outgoing data transfer, or mobile incoming 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 a 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 that constitutes the UE for PDCCH monitoring adaptation; and transmitting a PDCCH in accordance with PDCCH monitoring adaptation when the UE participates with 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 according to Clause 12, further comprising transmitting a 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 signaling indicating PDCCH monitoring adaptation is transmitted via at least one of DCI, MAC-CE, RRC signaling, or a combination thereof.

[0193]

[0209] Clause 15: The method described in any one of Clauses 12 to 14, 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 the UE is in 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 pre-configured time span on the first DL BWP and the second DL BWP is limited by a pre-configured 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 described in any one of Clauses 12 to 16, further comprising updating at least one of the SS set or CORESET configurations for transmitting a PDCCH on at least one of the first DL BWP or the second DL BWP based on signaling.

[0196]

[0212] Clause 18: The method of any one of Clauses 12 to 17, wherein the PDCCH monitoring adaptation is configured for the UE based on at least one of the UE capability instructions 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.

[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 PDCCH monitoring adaptation request or a UAI 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.

[0198]

[0214] Clause 20: The method of Clause 19, wherein the request or UAI is multiplexed with a UL transmission associated with at least one of the following: random access procedures, measurement reports, mobile outgoing data transfers, or mobile incoming data transfers.

[0199]

[0215] Clause 21: A processing system comprising: memory containing computer executable instructions; and one or more processors that execute computer executable instructions and are configured to cause the processing system to perform the method described in any one of Clauses 1 to 20.

[0200]

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

[0201]

[0217] Clause 23: A non-temporary computer-readable medium containing a computer-executable instruction, wherein, when the computer-executable instruction is executed by one or more processors of a processing system, the processing system causes the processing system to perform the method described in 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 methods described in any one of Clauses 1 through 20.

[0203] Additional considerations

[0219] The foregoing description is provided so that any person skilled in the art can practice the various embodiments described herein. The embodiments described herein do not limit the scope, applicability, or embodiments described in the claims. Various modifications to these embodiments will be readily apparent to a person skilled in the art, and the general principles defined herein may also be applied to other embodiments. For example, changes may be made to the function and arrangement of the elements described without departing from the scope of the disclosure. Various embodiments may omit, replace, or add various procedures or components as needed. For example, the methods described may be performed in an order different from the order described, and various actions may be added, omitted, or combined. Also, features described in some embodiments may be combined in some other embodiments. For example, an apparatus can be implemented or a method can be performed using any number of embodiments described herein. Furthermore, the scope of the disclosure is intended to include apparatus or methods that are implemented using other structures, functions, or structures and functions in addition to, or other than, the various embodiments 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 the claims.

[0204]

[0220] The various exemplary logic blocks, modules, and circuits described in this disclosure may be implemented or run using general-purpose processors, digital signal processors (DSPs), ASICs, field-programmable gate arrays (FPGAs) or other programmable logic devices (PLDs), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., 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] Where used herein, the phrase “at least one of” in an enumeration of items refers to any combination of those items that contains a single member. For 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 multiple identical elements (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 range of actions. For example, “determining” may include calculating, calculating, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or other data structure), and confirming. It may also include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and resolving, selecting, choosing, and establishing.

[0207]

[0223] The methods disclosed herein include one or more actions for achieving the method. The actions of those methods can be interchanged with one another without departing from the claims. In other words, unless a particular order of actions is specified, the order and / or use of any particular action can be modified without departing from the claims. Furthermore, the various operations of the methods described above may be performed by any preferred means capable of performing the corresponding function. These means may include, but are not limited to, various hardware components and / or software components, and / or various hardware modules and / or software modules.

[0208]

[0224] The following claims are not intended to be limited to the embodiments shown herein, but rather the full scope consistent with the language of the claims should be recognized. Within the claims, a singular reference to an element is intended to mean "one or more" rather than "one and only" unless explicitly stated otherwise. Unless otherwise specified, the term "several" means "one or more." Claim elements should not be construed under Section 112(f) of the U.S. Patent Act unless the element is explicitly described using the phrase "means for." All structural and functional equivalents of the elements in various embodiments described throughout this disclosure, whether known to those skilled in the art or to become known thereafter, are expressly incorporated by reference herein and intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, whether such disclosure is expressly enumerated in the claims or not. The invention described in the original claims of this application is listed below. [C1] A device for wireless communication in a user device (UE), comprising a memory containing computer executable instructions, and one or more processors that execute the computer executable instructions and the device, The network entity receives 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. The network entity receives 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. To receive signaling for configuration adaptation of the Physical Downlink Control Channel (PDCCH), 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, the PDCCH is monitored according to the PDCCH monitoring adaptation. One or more processors configured as follows: A device equipped with the following features. [C2] The one or more processors execute the computer executable instructions and the device, During a discontinuous receive (DRX) cycle, 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, the PDCCH monitoring adaptation instruction is monitored. The apparatus described in C1, further configured as follows. [C3] The apparatus according to C1, wherein one or more processors are further configured to execute the computer executable instructions and cause the apparatus to receive, as a result of the monitoring, a signaling that activates PDCCH monitoring adaptation on at least one of the first DL BWP or the second DL BWP, in accordance with the configuration. [C4] The apparatus according to C3, wherein the signaling indicating PDCCH monitoring adaptation is received via at least one of downlink control information (DCI), media access control (MAC) control elements (CE), radio resource control (RRC) signaling, or a combination thereof. [C5] The apparatus according to C1, wherein the PDCCH monitoring adaptation according to the configuration 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 the UE is in idle or inactive mode. [C6] The one or more processors execute the computer executable instructions and the device, Based on the signaling, update at least one of the following: PDCCH monitoring periodicity, PDCCH monitoring window time offset, PDCCH monitoring window duration, PDCCH monitoring skipping window time offset, or PDCCH monitoring skipping window duration. The apparatus described in C3, further configured as follows. [C7] The one or more processors execute the computer executable instructions and the device, Based on the signaling, update at least one of the S-set or CORESET configurations for PDCCH monitoring on at least one of the first DL BWP or the second DL BWP. The apparatus described in C1, further configured as follows. [C8] The apparatus according to C1, wherein the PDCCH monitoring adaptation is configured for the UE based on at least one of UE capability instructions or UE assistance information (UAI) transmitted by the UE in a UL BWP linked to at least one of the first DL BWP or the second DL BWP. [C9] The one or more processors execute the computer executable instructions and the device, 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 system causes at least one of the following to be transmitted: a request for PDCCH monitoring adaptation or UE assistance information (UAI). The apparatus described in C1, further configured as follows. [C10] The apparatus according to C9, wherein 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, measurement report, mobile outgoing data transfer, or mobile incoming data transfer. [C11] A device for wireless communication in a network entity, comprising a memory containing computer executable instructions, and one or more processors that execute the computer executable instructions and the device, The user equipment (UE) is instructed 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. The UE is instructed 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 within the second CORESET. To enable monitoring and adaptation of the physical downlink control channel (PDCCH), the signaling constituting the UE is transmitted. When the UE participates 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, the PDCCH is transmitted in accordance with the PDCCH monitoring adaptation. One or more processors configured as follows: A device equipped with the following features. [C12] The one or more processors execute the computer executable instructions and the device, During a discontinuous receive (DRX) cycle, when performing one or more idle-mode or inactive-mode procedures on at least one of the first DL BWP or the second DL BWP, a signaling indicating PDCCH monitoring adaptation is transmitted. The apparatus described in C11, further configured as follows. [C13] The apparatus according to C12, wherein the signaling indicating PDCCH monitoring adaptation is transmitted via at least one of downlink control information (DCI), media access control (MAC) control elements (CE), radio resource control (RRC) signaling, or a combination thereof. [C14] The apparatus according to C11, 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 the UE is in idle or inactive mode. [C15] The apparatus according to C12, wherein the total number of PDCCH decoding or channel estimation attempts of the UE within a pre-configured time span on the first DL BWP and the second DL BWP is limited by a pre-configured boundary, and the configuration of the time span or the boundary depends on at least one of the UE capabilities, the configuration of the first DL BWP, the configuration of the second DL BWP, a power saving configuration, or a coverage expansion configuration. [C16] The one or more processors execute the computer executable instructions and the device, Based on the signaling, update at least one of the SS set or CORESET configuration for transmitting PDCCH on at least one of the first DL BWP or the second DL BWP. The apparatus described in C12, further configured as follows. [C17] The apparatus according to C12, wherein the PDCCH monitoring adaptation is configured for the UE based on at least one of UE capability instructions or 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. [C18] The one or more processors execute the computer executable instructions and the device, The UE receives at least one of the following when it performs an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP: a request for PDCCH monitoring adaptation or UE assistance information (UAI). The apparatus described in C12, further configured as follows. [C19] The apparatus according to C18, wherein the request or UAI is multiplexed with a UL transmission associated with at least one of a random access procedure, measurement report, mobile outgoing data transfer, or mobile incoming data transfer. [C20] A method for wireless communication in user equipment (UE), 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 aforementioned network entity the configuration for the second downlink BWP, the second CORESET configured on the second DL BWP, and one or more second SS sets within the second CORESET, To receive the signaling constituting the UE for monitoring adaptation of the physical downlink control channel (PDCCH), 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, the PDCCH is monitored in accordance with the PDCCH monitoring adaptation, Methods that include... [C21] A method for wireless communication in a network entity, Transmitting to the 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, The UE transmits 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 the signaling that constitutes the UE for monitoring adaptation of the physical downlink control channel (PDCCH), When the UE participates 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, it transmits a PDCCH in accordance with the PDCCH monitoring adaptation, Methods that include...

Claims

1. A device for wireless communication in user equipment (UE), comprising a memory containing computer executable instructions, and one or more processors that execute the computer executable instructions and the device, The network entity receives 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. The network entity receives 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. To receive signaling for the configuration of the Physical Downlink Control Channel (PDCCH) monitoring adaptation, During a discontinuous reception (DRX) cycle, 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, the PDCCH monitoring adaptation instruction is monitored. As a result of the monitoring, according to the configuration, a signaling to activate PDCCH monitoring adaptation is received on at least one of the first DL BWP or the second DL BWP, Based on the signaling that activates PDCCH monitoring adaptation, update at least one of the following: PDCCH monitoring periodicity, PDCCH monitoring window time offset, PDCCH monitoring window duration, PDCCH monitoring skipping window time offset, or PDCCH monitoring skipping window duration. 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, the PDCCH is monitored according to the PDCCH monitoring adaptation. One or more processors configured as such, A device equipped with the following features.

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

3. The one or more processors execute the computer executable instructions and the device, Based on the signaling, update at least one of the SS sets or CORESET configurations for PDCCH monitoring on at least one of the first DL BWP or the second DL BWP. The apparatus according to claim 1, further configured as follows.

4. The apparatus according to claim 1, wherein the PDCCH monitoring adaptation is configured for the UE based on at least one of UE capability instructions or UE support information (UAI) transmitted 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 the device, 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, at least one of a request for PDCCH monitoring adaptation or UE support information (UAI) is transmitted. The apparatus according to claim 1, further configured as follows.

6. The apparatus according to claim 5, wherein 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, measurement report, mobile outgoing data transfer, or mobile incoming data transfer.

7. A device for wireless communication in a network entity, comprising a memory containing computer executable instructions, and one or more processors that execute the computer executable instructions and the device, The user equipment (UE) is instructed 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. The UE is instructed 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 within the second coreset. To enable monitoring and adaptation of the physical downlink control channel (PDCCH), the signaling constituting the UE is transmitted. During a discontinuous receive (DRX) cycle, 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 signaling indicating PDCCH monitoring adaptation is transmitted. Based on the signaling indicating PDCCH monitoring adaptation, update at least one of the SS sets or CORESET configurations for transmitting PDCCH on at least one of the first DL BWP or the second DL BWP. When the UE participates 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, the PDCCH is transmitted in accordance with the PDCCH monitoring adaptation. One or more processors configured as such, A device equipped with the following features.

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

9. The apparatus according to 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 the UE is in idle or inactive mode.

10. The apparatus according to claim 7, wherein the total number of PDCCH decoding or channel estimation attempts of the UE within a pre-configured time span on the first DL BWP and the second DL BWP is limited by a pre-configured boundary, and the configuration of at least one of the time span or the boundary depends on at least one of the UE capability, the configuration of the first DL BWP, the configuration of the second DL BWP, a power saving configuration, or a coverage expansion configuration.

11. The apparatus according to claim 7, wherein the PDCCH monitoring adaptation is configured for the UE based on at least one of UE capability instructions or UE support 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 the device, The UE receives at least one of the following when it performs an idle mode procedure or an inactive mode procedure in at least one of the first DL BWP or the second DL BWP: a request for PDCCH monitoring adaptation or UE support information (UAI). It is further structured in the following way: The apparatus according to claim 7, wherein the request or UAI is multiplexed with a UL transmission associated with at least one of a random access procedure, measurement report, mobile outgoing data transfer, or mobile incoming data transfer.

13. A method for wireless communication in user equipment (UE), 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 aforementioned 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, To receive the signaling constituting the UE for monitoring and adaptation of the physical downlink control channel (PDCCH), During a discontinuous reception (DRX) cycle, 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, the PDCCH monitoring adaptation instruction is monitored, As a result of the monitoring, a signaling to activate PDCCH monitoring adaptation is received on at least one of the first DL BWP or the second DL BWP, according to the configuration. Based on the signaling that activates PDCCH monitoring adaptation, update at least one of the following: PDCCH monitoring periodicity, PDCCH monitoring window time offset, PDCCH monitoring window duration, PDCCH monitoring skipping window time offset, or PDCCH monitoring skipping window duration. 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, the PDCCH is monitored in accordance with the PDCCH monitoring adaptation, Methods that include...

14. A method for wireless communication in a network entity, Transmitting to the 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, To transmit 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 that constitutes the UE for monitoring adaptation of the physical downlink control channel (PDCCH), During a discontinuous receive (DRX) cycle, 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 signaling indicating PDCCH monitoring adaptation is transmitted. Based on the signaling indicating PDCCH monitoring adaptation, update at least one of the SS sets or CORESET configurations for transmitting PDCCH on at least one of the first DL BWP or the second DL BWP, 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, the PDCCH is transmitted in accordance with the PDCCH monitoring adaptation, Methods that include...

15. A computer program including instructions, When the instruction is executed by one or more processors of a device for wireless communication in a user device (UE), the one or more processors are instructed to perform the method according to claim 13. A computer program that, when the instruction is executed by one or more processors of a device for wireless communication in a network entity, causes the one or more processors to perform the method according to claim 14.

Images