Downlink control channel monitoring in multiple downlink bandwidth parts

Abstract

Methods, systems, and apparatus for wireless communication are described. A user equipment (UE) can receive one or more control messages from a network entity, indicating the following configuration: a first downlink bandwidth portion (BWP) associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP. At least a portion of this configuration may correspond to the capabilities of the UE. The UE can monitor the first set of resources when in the first operating mode and can monitor the second set of resources when in the second operating mode. The UE can receive system information updates or public warning system (PWS) notifications from the network entity via the second set of resources.

Description

Technical Field

[0001] This patent application claims the benefit of U.S. Patent Application No. 18,061,347, filed December 2, 2022, entitled "DOWNLINK CONTROL CHANNEL MONITORING IN MULTIPLE DOWNLINK BANDWIDTH PARTS" by LEI et al., which also claims the benefit of U.S. Provisional Patent Application No. 63 / 297,691, filed January 7, 2022, entitled "DOWNLINK CONTROL CHANNEL MONITORING IN MULTIPLE DOWNLINK BANDWIDTH PARTS". Both of these U.S. patent applications have been assigned to the assignee of this application and are expressly incorporated herein by reference.

[0002] The following text pertains to wireless communications, including downlink control channel monitoring in multiple downlink bandwidth portions (BWPs). Prior Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiplexing access systems include fourth-generation (4G) systems (e.g., Long Term Evolution (LTE), LTE-A Advanced (LTE-A), or LTE-A Pro) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiplexing access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication with multiple communication devices (which may otherwise be referred to as User Equipment (UE)). Components within a wireless communication system can be coupled to each other (e.g., operational ground, communication ground, functional ground, electronic ground, and / or electrical ground coupling).

[0004] Idle or inactive UEs can be configured to monitor resources in different bandwidth portions (BWPs). For example, an idle or inactive UE can switch from a first downlink BWP to a second downlink BWP, allowing the UE to monitor downlink transmissions in the second downlink BWP. However, in some cases, switching between downlink BWPs and monitoring a relatively large number of resources can lead to higher power consumption and a higher processing and management burden at the UE. Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting downlink control channel monitoring in multiple downlink bandwidth portions (BWPs). Generally, the described technology provides improved efficiency for downlink monitoring procedures at idle or inactive user equipment (UEs). The UE can receive one or more control messages from a network entity indicating a configuration of: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP. At least a portion of this configuration may correspond to the capabilities of the UE. The UE can monitor the first set of resources when in the first operating mode and can monitor the second set of resources when in the second operating mode. The UE can receive system information updates or Public Warning System (PWS) notifications from the network entity via the second set of resources. The technology described herein enables UEs (e.g., idle or inactive UEs) to perform downlink channel monitoring with reduced power consumption, higher processing efficiency, and other benefits.

[0006] A method for wireless communication at a UE is described. The method may include: receiving one or more control messages indicating a first configuration for a first downlink BWP and a second configuration for a second downlink BWP specific to a RedCap UE, wherein the first configuration identifies a first set of resources within the first downlink BWP, and the second configuration identifies a second set of resources within the second downlink BWP. The method may also include: monitoring the first set of resources within the first downlink BWP based on the first configuration, the radio resource control (RRC) state of the UE, and the capabilities of the UE. The method may also include: monitoring the second set of resources specific to a RedCap UE within the second downlink BWP based on the second configuration, the RRC state of the UE, and the capabilities of the UE.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and memory coupled to the at least one processor (e.g., operational ground, communication ground, functional ground, electronic ground, or electrical ground), the memory storing instructions executable (e.g., directly or indirectly) by the at least one processor to cause the UE to perform the following operations: receiving one or more control messages indicating a first configuration for a first downlink BWP and a second configuration specific to the RedCap UE for a second downlink BWP, wherein the first configuration identifies a first set of resources within the first downlink BWP, and the second configuration identifies a second set of resources within the second downlink BWP. These instructions may further be executed by the at least one processor to cause the UE to monitor the first set of resources within the first downlink BWP based on the first configuration, the UE's RRC state, and the UE's capabilities. These instructions may further be executed by the at least one processor to cause the UE to monitor the second set of resources specific to the RedCap UE within the second downlink BWP based on the second configuration, the UE's RRC state, and the UE's capabilities.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for receiving one or more control messages indicating a first configuration for a first downlink BWP and a second configuration specific to the RedCap UE for a second downlink BWP, the first configuration identifying a first set of resources within the first downlink BWP and the second configuration identifying a second set of resources within the second downlink BWP. The apparatus may also include: a unit for monitoring the first set of resources within the first downlink BWP based on the first configuration, the UE's RRC state, and the UE's capabilities. The apparatus may also include: a unit for monitoring the second set of resources specific to the RedCap UE within the second downlink BWP based on the second configuration, the UE's RRC state, and the UE's capabilities.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to: receive one or more control messages indicating a first configuration for a first downlink BWP and a second RedCap UE-specific configuration for a second downlink BWP, the first configuration identifying a first set of resources within the first downlink BWP and the second configuration identifying a second set of resources within the second downlink BWP. These instructions may further be executed by the at least one processor to monitor the first set of resources within the first downlink BWP based on the first configuration, the UE's RRC state, and the UE's capabilities. These instructions may further be executed by the at least one processor to monitor the second set of resources within the second downlink BWP, specific to the RedCap UE, based on the second configuration, the UE's RRC state, and the UE's capabilities.

[0010] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, units, or instructions for determining a first set of parameters for the first downlink BWP based on the first configuration, the first set of parameters including one or more of the following: the cyclic prefix, subcarrier spacing, number of resource blocks, or number of symbols of the control resource set (CORESET) within the first downlink BWP.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining a second set of parameters specific to the RedCap UE for the second downlink BWP based on the second configuration, the second set of parameters including one or more of the following: the bandwidth of the second downlink BWP, the first physical resource block (PRB), or the subcarrier spacing.

[0012] In some instances of the methods, apparatuses and nontransitory computer-readable media described herein, monitoring the first set of resources may include: an operation, feature, element or instruction for receiving at least one message of a paging operation via a common search space (CSS) within the first downlink BWP, based on the first configuration and the capabilities of the UE, wherein the first downlink BWP includes a CORESET having an index of zero (0).

[0013] In some instances of the methods, apparatuses and nontransitory computer-readable media described herein, monitoring the second set of resources may include: operations, features, elements or instructions for receiving one or more random access messages via the second set of resources specific to the RedCap UE within the second downlink BWP, based on the second configuration, the RRC state of the UE and the capability of the UE, wherein the second downlink BWP does not include a CORESET with an index of zero (0).

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include: operations, features, elements, or instructions for receiving downlink messages scheduled for transmission in a first system information block (SIB) within the first downlink BWP via one or more physical downlink control channel (PDCCH) resources within the first downlink BWP, wherein the first SIB indicates the second configuration of the second downlink BWP specific to the RedCap UE.

[0015] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, monitoring the first set of resources may include: receiving operations, features, units, or instructions of one or more cell-defined synchronization signal blocks (CD-SSBs) via the first set of resources within the first downlink BWP; and performing operations, features, units, or instructions of a cell selection procedure based on measurements of the one or more CD-SSBs.

[0016] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include: operations, features, units, or instructions for receiving an indication of a search space (SS) configured for downlink small data transmission (SDT) in the first downlink BWP or the second downlink BWP; and for monitoring the operations, features, units, or instructions of the SS for the downlink SDT according to the indication.

[0017] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include: receiving operations, features, elements, or instructions of the Master Information Block (MIB) of the first configuration of the first downlink BWP; and receiving operations, features, elements, or instructions of the SIB of the second configuration of the second downlink BWP.

[0018] Some examples of the methods, apparatuses and non-transitory computer-readable media described herein may also include: operations, features, elements or instructions for receiving one or more of the following via the first downlink BWP or the second downlink BWP specific to the RedCap UE: system information messages, paging operation messages, random access messages, SDT, broadcast messages, PWS notifications, or non-cell defined synchronization signal blocks (NCD-SSBs).

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include: operations, features, units, or instructions for receiving one or more of CD-SSB, system information messages, paging operation messages, or random access messages via the first set of resources within the first downlink BWP, based on the first configuration, the RRC state of the UE, and the capability of the UE.

[0020] Examples of methods, apparatuses, and nontransitory computer-readable media described herein: for transmitting one or more of the following operations, features, elements, or instructions via one or more resources within an uplink BWP configured for the UE: SDT, random access messages, UE mobility information, or requests for on-demand system information.

[0021] Examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include: operations, features, elements, or instructions for sending a request for on-demand system information via one or more resources within an uplink BWP configured for the UE; and operations, features, elements, or instructions for receiving the on-demand system information via the first set of resources within the first downlink BWP or the second set of resources within the second downlink BWP.

[0022] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the UE sends the request for on-demand system information according to a random access procedure.

[0023] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, the bandwidth of the second downlink BWP specific to the RedCap UE is less than or equal to the maximum downlink bandwidth supported by the UE.

[0024] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, the one or more control messages include MIB, SIB, RRC messages, or combinations thereof.

[0025] In some instances of the methods, apparatus, and non-transitory computer-readable media described herein, the first downlink BWP can be used to receive CD-SSB.

[0026] In some instances of the methods, apparatus, and non-transitory computer-readable media described herein, the UE may be a RedCap UE, and the RRC state of the UE may be an idle RRC state or an inactive RRC state.

[0027] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, the first downlink BWP includes a first set of CSS configured for a cell selector or cell reselector, and the second downlink BWP includes a second set of CSS configured for a random access procedure or paging operation.

[0028] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, the first downlink BWP includes one or more CSSs configured for system information retrieval or paging operations.

[0029] Some examples of the methods, apparatuses and non-transitory computer-readable media described herein may also include operations, features, units or instructions for determining the number of CORESETs in the second downlink BWP based on the number of CORESETs in the first downlink BWP, the sum of CORESETs in the other downlink BWPs of the UE, the threshold number of CORESETs supported by the UE, or a combination thereof.

[0030] Some examples of the methods, apparatuses and non-transitory computer-readable media described herein may also include operations, features, units or instructions for determining the number of SS sets in the second downlink BWP based on the number of SS sets in the first downlink BWP, the sum of SS sets in other downlink BWPs of the UE, the threshold number of SS sets supported by the UE, or a combination thereof.

[0031] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, units, or instructions for switching from the first downlink BWP to the second downlink BWP after switching from a first operating mode associated with the first downlink BWP to a second operating mode associated with the second downlink BWP.

[0032] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include: operations, features, units, or instructions for receiving system information that indicates at least one of the aggregation level (AL), monitoring period, or monitoring timing configuration for a RedCap UE-specific CSS set within the second downlink BWP.

[0033] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include: operations, features, elements, or instructions for receiving an SIB that indicates: a first downlink control information (DCI) size alignment for a PDCCH message scheduled in the SS set of the first downlink BWP, a second DCI size alignment for a PDCCH message scheduled in the SS set of the second downlink BWP, or operations, features, elements, or instructions for both.

[0034] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include operations, features, elements, or instructions for receiving an indication of the number of PRBs specific to the RedCap UE within the second downlink BWP, wherein the number of PRBs is based on the control channel element (CCE) AL of the CORESET within the second downlink BWP, the duration of the CORESET within the second downlink BWP, the total number of CORESETs within the second downlink BWP, the RRC state of the UE, or a combination thereof.

[0035] In some instances of the methods, apparatuses and non-transitory computer-readable media described herein, receiving the one or more control messages may include operations, features, units or instructions for receiving one or more of the following: system information messages, RRC messages, broadcast messages, or multicast messages indicating information such as: the CCE AL of the SS set within the second downlink BWP, the number of blind decoding candidates of the SS set within the second downlink BWP, or both.

[0036] A method for wireless communication at a network entity is described. The method may include: sending one or more control messages indicating a first configuration for a first downlink BWP and a second configuration specific to a RedCap UE for a second downlink BWP, the first configuration identifying a first set of resources within the first downlink BWP and the second configuration identifying a second set of resources within the second downlink BWP. The method may also include: sending a first downlink message to a RedCap UE via the first set of resources within the first downlink BWP according to the first configuration indicated by the one or more control messages. The method may also include: sending a second downlink message to a RedCap UE via the second set of resources specific to the RedCap UE within the second downlink BWP according to the second configuration indicated by the one or more control messages.

[0037] An apparatus for wireless communication at a network entity is described. The apparatus may include at least one processor and memory coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, or electrical ground) to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to perform the following operations: sending one or more control messages indicating a first configuration for a first downlink BWP and a second configuration specific to a RedCap UE for a second downlink BWP, the first configuration identifying a first set of resources within the first downlink BWP, and the second configuration identifying a second set of resources within the second downlink BWP. These instructions may further be executed by the at least one processor to cause the network entity to send a first downlink message to the RedCap UE via the first set of resources within the first downlink BWP according to the first configuration indicated by the one or more control messages. These instructions can be further executed by the at least one processor to cause the network entity to send a second downlink message to the RedCap UE via the second set of resources specific to the RedCap UE within the second downlink BWP, according to the second configuration indicated by the one or more control messages.

[0038] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a unit for transmitting one or more control messages indicating a first configuration for a first downlink BWP and a second configuration specific to a RedCap UE for a second downlink BWP, the first configuration identifying a first set of resources within the first downlink BWP and the second configuration identifying a second set of resources within the second downlink BWP. The apparatus may also include: a unit for transmitting a first downlink message to a RedCap UE via the first set of resources within the first downlink BWP according to the first configuration indicated by the one or more control messages. The apparatus may also include: a unit for transmitting a second downlink message to a RedCap UE via the second set of resources specific to a RedCap UE within the second downlink BWP according to the second configuration indicated by the one or more control messages.

[0039] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by at least one processor to perform the following operations: sending one or more control messages indicating a first configuration for a first downlink BWP and a second configuration specific to a RedCap UE for a second downlink BWP, the first configuration identifying a first set of resources within the first downlink BWP and the second configuration identifying a second set of resources within the second downlink BWP; sending a first downlink message to a RedCap UE via the first set of resources within the first downlink BWP according to the first configuration indicated by the one or more control messages; and sending a second downlink message to a RedCap UE via the second set of resources specific to the RedCap UE within the second downlink BWP according to the second configuration indicated by the one or more control messages.

[0040] In some instances of the methods, apparatuses and nontransitory computer-readable media described herein, sending the first downlink message may include: an operation, feature, element or instruction for sending at least one message of a paging operation to the RedCap UE via a CSS within the first downlink BWP according to the first configuration, wherein the first downlink BWP includes a CORESET having an index of zero (0).

[0041] A method for wireless communication at a UE is described. The method may include: receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; the UE, in the first operating mode, monitoring the first set of control resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and the UE, in the second operating mode, monitoring the second set of control resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0042] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and memory coupled to the at least one processor (e.g., operational ground, communication ground, functional ground, electronic ground, or electrical ground), the memory storing instructions executable by the at least one processor to cause the apparatus to perform the following operations: receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; the UE, in the first operating mode, monitoring the first set of control resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and the UE, in the second operating mode, monitoring the second set of control resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0043] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; a unit for the UE to monitor the first set of control resources within the first downlink BWP according to the configuration and based on the capabilities of the UE in the first operating mode; and a unit for the UE to monitor the second set of control resources within the second downlink BWP according to the configuration and based on the capabilities of the UE in the second operating mode.

[0044] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to perform the following operations: receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; the UE, in the first operating mode, monitoring the first set of control resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and the UE, in the second operating mode, monitoring the second set of control resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0045] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: monitoring the first set of control resources within the first downlink BWP by the UE in the first operating mode; receiving, via the first set of control resources, one or more control messages from the network entity instructing the configuration for the second downlink BWP and the second set of control resources within the second downlink BWP; and determining the number of control resources in the second downlink BWP based on the number of control resources within the first downlink BWP.

[0046] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining the number of control resources in the second downlink BWP based on the number of control resources in the first downlink BWP, the sum of control resources in different downlink BWPs of the UE, and a threshold number of control resources corresponding to the capabilities of the UE.

[0047] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining the number of SS sets in the second downlink BWP based on the number of SS sets in the first downlink BWP, the sum of SS sets in different downlink BWPs of the UE, and a threshold number of SS sets corresponding to the capabilities of the UE.

[0048] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include operations, features, units, or instructions for: receiving a control signal transmission indicating one or both of a first set of parameters associated with the first downlink BWP or a second set of parameters associated with the second downlink BWP, the first set of parameters including bandwidth, initial PRB position, digital scheme, or a combination thereof associated with the first downlink BWP, and the second set of parameters including bandwidth, initial PRB position, digital scheme, or a combination thereof associated with the second downlink BWP, wherein the first set of parameters may differ from the second set of parameters.

[0049] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include operations, features, units, or instructions for: receiving from the network entity an MIB indicating the configuration for the first downlink BWP, and receiving from the network entity one or more of an SIB, RRC message, multicast message, or broadcast message indicating the configuration for the second downlink BWP.

[0050] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, units, or instructions for performing a BWP handover procedure from the first downlink BWP to the second downlink BWP based on a transition from the first operating mode to the second operating mode, wherein monitoring the second set of control resources within the second downlink BWP may be based on the execution of the BWP handover procedure.

[0051] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for executing one or more procedures associated with the first operating mode or the second operating mode of the UE using the CORESET and SS set within the first downlink BWP or the CORESET and SS set within the second downlink BWP, the one or more procedures including a system information retrieval procedure, a system information update procedure, a mobility procedure, a paging operation, a random access procedure, a small data transfer procedure, an on-demand system information transfer request procedure, or a combination thereof.

[0052] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the first operating mode and the second operating mode correspond to the RRC idle state or RRC inactive state of the UE, and the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP include a set of CSS.

[0053] In some instances of the methods, apparatuses and nontransitory computer-readable media described herein, the first operating mode and the second operating mode correspond to the UE’s RRC inactive state or RRC connected state, and the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP include a UE-specific search space (USS) set, a CSS set, or both.

[0054] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the first downlink BWP and the second downlink BWP correspond to different frequency ranges.

[0055] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the first downlink BWP includes a first CSS configured for a cell selection procedure or cell reselection procedure for a UE in an RRC idle or RRC inactive state, and the second downlink BWP includes at least a second CSS configured for a random access procedure or paging operation for a UE in an RRC idle or RRC inactive state.

[0056] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the first downlink BWP includes one or more CSSs configured for system information retrieval procedures, system information update procedures, mobility procedures, or paging operations of a UE in an RRC idle or RRC inactive state.

[0057] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include operations, features, elements, or instructions for receiving an SIB based on the UE's capabilities, wherein the SIB indicates one or more of the AL, monitoring period, or monitoring timing configuration for the CSS set within the second downlink BWP.

[0058] Some examples of the methods, apparatuses and non-transitory computer-readable media described herein may also include operations, features, units or instructions for receiving CD-SSB, system information messages, paging operation messages, PEI messages, random access messages or combinations thereof from the network entity by the UE in the first operating mode via the first set of control resources within the first downlink BWP associated with the first operating mode of the UE in the first operating mode.

[0059] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include: operations, features, elements, or instructions for receiving an SIB from the network entity, the SIB indicating a first DCI size alignment of PDCCH messages in the SS set of the first downlink BWP, a second DCI size alignment of PDCCH messages in the SS set of the second downlink BWP, or both.

[0060] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, units, or instructions for receiving one or more of random access messages, system information messages, multicast messages, broadcast messages, paging operation messages, SDTs, or NCD-SSBs from the network entity via the second set of control resources within the second downlink BWP.

[0061] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the one or more control messages may include operations, features, units, or instructions for receiving control signal transmissions indicating the number of PRBs within the second downlink BWP, wherein the number of PRBs may be based on the CCE AL of the CORESET within the second downlink BWP, the duration of the CORESET within the second downlink BWP, the total number of CORESETs within the second downlink BWP, the RRC state of the UE, or a combination thereof.

[0062] In some instances of the methods, apparatuses and non-transitory computer-readable media described herein, receiving the one or more control messages may include operations, features, units or instructions for receiving one or more of the following: an operation, feature, unit or instruction indicating a CCE AL of an SS set within the second downlink BWP, the number of blind decoding candidates of an SS set within the second downlink BWP, or both of a system information message, RRC message, broadcast message or multicast message.

[0063] A method for wireless communication at a network entity is described. The method may include: sending one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to a capability of the UE; transmitting a first set of messages via the first set of control resources within the first downlink BWP according to the configuration and based on the capability of the UE; and transmitting a second set of messages via the second set of control resources within the second downlink BWP according to the configuration and based on the capability of the UE.

[0064] An apparatus for wireless communication at a network entity is described. The apparatus may include at least one processor and memory coupled to the at least one processor (e.g., operational ground, communication ground, functional ground, electronic ground, or electrical ground), the memory storing instructions executable by the at least one processor to cause the apparatus to perform the following operations: transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; transmitting a first set of messages via the first set of control resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and transmitting a second set of messages via the second set of control resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0065] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of a UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; a unit for transmitting a first set of messages via the first set of control resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and a unit for transmitting a second set of messages via the second set of control resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0066] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by at least one processor to: send one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of a UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; sending a first set of messages via the first set of control resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and sending a second set of messages via the second set of control resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0067] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: determining the number of control resources in the second downlink BWP based on the number of control resources in the first downlink BWP; and sending an indication to the UE of the number of control resources in the second downlink BWP.

[0068] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: determining the number of control resources in the second downlink BWP based on the number of control resources in the first downlink BWP and the sum of control resources in different downlink BWPs of the UE; and sending an indication to the UE of the number of control resources in the second downlink BWP.

[0069] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: determining the number of SS sets in the second downlink BWP based on the number of SS sets in the first downlink BWP, the sum of SS sets in different downlink BWPs of the UE, and a threshold number of SS sets related to the UE's ability to connect to the network entity; and sending an indication to the UE of the number of control resources in the second downlink BWP.

[0070] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the one or more control messages may include operations, features, units, or instructions for: sending a control signal transmission indicating one or both of a first set of parameters associated with the first downlink BWP or a second set of parameters associated with the second downlink BWP, the first set of parameters including bandwidth, initial PRB position, digital scheme, or a combination thereof associated with the first downlink BWP, and the second set of parameters including bandwidth, initial PRB position, digital scheme, or a combination thereof associated with the second downlink BWP, wherein the first set of parameters may differ from the second set of parameters.

[0071] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the one or more control messages may include operations, features, elements, or instructions for: sending the UE an MIB indicating the configuration for the first downlink BWP, and sending the UE one or more of an SIB, a dedicated RRC message, a multicast message, or a broadcast message indicating the configuration for the second downlink BWP.

[0072] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the first operating mode and the second operating mode correspond to the RRC idle state or RRC inactive state of the UE, and the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP include a set of CSS.

[0073] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, the first operating mode and the second operating mode correspond to the RRC inactive state or the RRC connected state of the UE, and the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP include a USS set, a CSS set, or both.

[0074] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the first downlink BWP and the second downlink BWP correspond to different frequency ranges.

[0075] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the first downlink BWP includes a first CSS configured for a cell selection procedure or cell reselection procedure for a UE in an RRC idle or RRC inactive state, and the second downlink BWP includes at least a second CSS configured for a random access procedure or paging operation for a UE in an RRC idle or RRC inactive state.

[0076] In some instances of the methods, apparatuses, and non-transitory computer-readable media described herein, the first downlink BWP includes one or more CSSs configured for system information retrieval procedures, system information update procedures, mobility procedures, or paging operations of a UE in an RRC idle or RRC inactive state.

[0077] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the one or more control messages may include operations, features, elements, or instructions for sending an SIB based on the UE's capabilities, wherein the SIB indicates one or more of the AL, monitoring period, or monitoring timing configuration of the CSS set within the second downlink BWP.

[0078] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending CD-SSB, system information messages, paging operation messages, random access messages, or combinations thereof from the network entity via the first set of control resources within the first downlink BWP associated with the first operating mode of the UE.

[0079] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the one or more control messages may include: operations, features, units, or instructions for sending an SIB that indicates a first DCI size alignment of PDCCH messages in the SS set of the first downlink BWP, a second DCI size alignment of PDCCH messages in the SS set of the second downlink BWP, or both.

[0080] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, units, or instructions for transmitting one or more of random access messages, system information messages, multicast messages, broadcast messages, paging operation messages, SDTs, or NCD-SSBs via the second set of control resources within the second downlink BWP.

[0081] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the one or more control messages may include operations, features, units, or instructions for transmitting control signal transmissions indicating the number of PRBs within the second downlink BWP, wherein the number of PRBs may be based on the CCE AL of the CORESET within the second downlink BWP, the duration of the CORESET within the second downlink BWP, the total number of CORESETs within the second downlink BWP, the RRC state of the UE, or a combination thereof.

[0082] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the one or more control messages may include operations, features, units, or instructions for sending one or more of the following: an instruction for a CCE AL for a set of SS within the second downlink BWP, a number of blind decoding candidates for a set of SS within the second downlink BWP, or both of a system information message, an RRC message, a broadcast message, or a multicast message.

[0083] A method for wireless communication at a UE is described. The method may include: receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; the UE, in the first operating mode, receiving one or more messages via the first set of resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and the UE, in the second operating mode, receiving one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0084] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and memory coupled to the at least one processor (e.g., operational ground, communication ground, functional ground, electronic ground, or electrical ground), the memory storing instructions executable by the at least one processor to cause the apparatus to perform the following operations: receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; the UE, in the first operating mode, receiving one or more messages via the first set of resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and the UE, in the second operating mode, receiving one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0085] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; a unit for receiving one or more messages by the UE in the first operating mode, according to the configuration and based on the capabilities of the UE, via the first set of resources within the first downlink BWP; and a unit for receiving one or both of system information messages or PWS messages by the UE in the second operating mode, according to the configuration and based on the capabilities of the UE, via the second set of resources within the second downlink BWP.

[0086] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to perform the following operations: receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; the UE, in the first operating mode, receiving one or more messages via the first set of resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and the UE, in the second operating mode, receiving one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0087] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include: operations, features, units, or instructions for performing random access procedures with the network entity via a second set of resources within the second downlink BWP.

[0088] In some instances of the methods, apparatuses and nontransitory computer-readable media described herein, receiving one or both of the system information message and the PWS message may include: operations, features, units or instructions for receiving random access messages from the network entity via the second set of resources within the second downlink BWP according to the random access procedure, the random access message indicating one or both of the system information message and the PWS message.

[0089] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving one or both of the system information message and the PWS message may include: operations, features, units, or instructions for receiving random access messages from the network entity via the second set of resources within the second downlink BWP based on the identification that the second downlink BWP does not include a CSS configured for paging operations, the random access message indicating one or both of the system information message and the PWS message.

[0090] In some instances of the methods, apparatus, and nontransitory computer-readable media described herein, receiving one or both of the system information message and the PWS message may include: operations, features, units, or instructions for receiving a message of a paging operation from the network entity via the second set of resources within the second downlink BWP, based on the identification that the second downlink BWP includes a CSS configured for paging operations, the message of the paging operation indicating one or both of the system information message and the PWS message.

[0091] In some instances of the methods, apparatus, and nontransitory computer-readable media described herein, receiving one or both of the system information message and the PWS message may include: operations, features, units, or instructions for receiving a message of a paging operation from the network entity via the second set of resources within the second downlink BWP, the message of the paging operation being scheduled from the downlink SDT of the network entity, and monitoring the second set of resources within the second downlink BWP based on the message of the paging operation to obtain the downlink SDT from the network entity, the downlink SDT indicating one or both of the system information message and the PWS message.

[0092] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving one or both of the system information message or the PWS message may include operations, features, units, or instructions for: receiving a PDCCH transmission from the network entity via the second set of resources within the second downlink BWP, the PDCCH transmission being scheduled from a broadcast or multicast entity downlink shared channel (PDSCH) transmission of the network entity, and monitoring the second set of resources based on the PDCCH transmission to obtain the broadcast or multicast PDSCH transmission from the network entity, the broadcast or multicast PDSCH transmission indicating one or both of the system information message or the PWS message.

[0093] A method for wireless communication at a network entity is described. The method may include: sending one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of a UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to a capability of the UE; sending one or more messages via the first set of resources within the first downlink BWP according to the configuration and based on the capability of the UE; and sending one or both of a system information message or a PWS message via the second set of resources within the second downlink BWP according to the configuration and based on the capability of the UE.

[0094] An apparatus for wireless communication at a network entity is described. The apparatus may include at least one processor and memory coupled to the at least one processor (e.g., operational ground, communication ground, functional ground, electronic ground, or electrical ground), the memory storing instructions executable by the at least one processor to cause the apparatus to perform the following operations: transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of a UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; transmitting one or more messages via the first set of resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and transmitting one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0095] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; a unit for transmitting one or more messages via the first set of resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and a unit for transmitting one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0096] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by at least one processor to perform the following operations: sending one or more control messages, wherein the one or more control messages indicate a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE; sending one or more messages via the first set of resources within the first downlink BWP according to the configuration and based on the capabilities of the UE; and sending one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP according to the configuration and based on the capabilities of the UE.

[0097] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing random access procedures with the UE via a second set of resources within the second downlink BWP.

[0098] In some instances of the methods, apparatuses and nontransitory computer-readable media described herein, sending one or both of the system information message and the PWS message may include: an operation, feature, element or instruction for sending a random access message to the UE via the second set of resources within the second downlink BWP according to the random access procedure, the random access message indicating one or both of the system information message and the PWS message.

[0099] In some instances of the methods, apparatus, and nontransitory computer-readable media described herein, sending one or both of the system information message and the PWS message may include: an operation, feature, element, or instruction for sending a random access message to the UE via the second set of resources within the second downlink BWP based on the identification that the second downlink BWP does not include a CSS configured for paging operations, the random access message indicating one or both of the system information message and the PWS message.

[0100] In some instances of the methods, apparatus, and nontransitory computer-readable media described herein, sending one or both of the system information message and the PWS message may include: an operation, feature, element, or instruction for sending a paging operation message to the UE via the second set of resources within the second downlink BWP based on the identification that the second downlink BWP includes a CSS configured for paging operations, the paging operation message indicating one or both of the system information message and the PWS message.

[0101] In some instances of the methods, apparatus, and nontransitory computer-readable media described herein, transmitting one or both of the system information message and the PWS message may include: operations, features, elements, or instructions for transmitting a paging operation message to the UE via the second set of resources within the second downlink BWP, the paging operation message being scheduled from the downlink SDT of the network entity, and transmitting the downlink SDT via the second set of resources according to the paging operation message, the downlink SDT indicating one or both of the system information message and the PWS message.

[0102] In some instances of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting one or both of the system information message and the PWS message may include operations, features, elements, or instructions for: transmitting a PDCCH transmission to the UE via the second set of resources within the second downlink BWP, the PDCCH transmission being scheduled from a broadcast or multicast PDSCH transmission of the network entity; and, based on the PDCCH transmission, transmitting the broadcast or multicast PDSCH transmission via the second set of resources, the broadcast or multicast PDSCH transmission instructing one or both of the system information message and the PWS message. Simple Explanation of the Diagram

[0103] Figures 1 and 2 illustrate examples of wireless communication systems that support downlink control channel monitoring in multiple downlink bandwidth portions (BWPs) according to the contents of this case.

[0104] Figures 3A and 3B illustrate examples of resource graphs supporting downlink control channel monitoring in multiple downlink BWPs according to the various states described in this case.

[0105] Figures 4 and 5 illustrate examples of procedure flows supporting downlink control channel monitoring in multiple downlink BWPs, according to the various forms described in this case.

[0106] Figures 6 and 7 illustrate block diagrams of devices supporting downlink control channel monitoring in multiple downlink BWPs according to various aspects of this case.

[0107] Figure 8 is a block diagram illustrating a communication manager that supports downlink control channel monitoring in multiple downlink BWPs according to the various states described in this case.

[0108] Figure 9 illustrates a system including the device according to the contents of this case, which supports downlink control channel monitoring in multiple downlink BWPs.

[0109] Figures 10 and 11 illustrate block diagrams of devices supporting downlink control channel monitoring in multiple downlink BWPs according to various forms of the present case.

[0110] Figure 12 is a block diagram illustrating a communication manager that supports downlink control channel monitoring in multiple downlink BWPs according to various states of the present case.

[0111] Figure 13 illustrates a system including the device according to the contents of this case, which supports downlink control channel monitoring in multiple downlink BWPs.

[0112] Figures 14 to 19 illustrate flowcharts of methods for monitoring downlink control channels in multiple downlink BWPs, according to various illustrations of the content of this case. Implementation

[0113] Compared to other user equipment (UEs), a Reduced Capability (RedCap) UE can be associated with reduced processing power, longer battery life, and lower overall cost. Therefore, RedCap UEs are suitable for Internet of Things (IoT), Augmented Reality (AR), Virtual Reality (VR), and Vehicle-to-Everything (V2X) applications, among others. In some cases, RedCap UEs in idle or inactive mode can be configured to monitor a first downlink bandwidth portion (BWP) to obtain system information updates, paging messages (e.g., paging operation messages), or cell-defined (CD) synchronization signal blocks (SSBs) from network entities. RedCap UEs can also be configured with a second initial downlink BWP, which can be dedicated to RedCap UEs. RedCap UEs can monitor the second downlink BWP to obtain random access messages, paging messages, or non-cell-defined (NCD) SSBs from network entities.

[0114] However, if the first downlink BWP and the second downlink BWP correspond to different frequency bands, monitoring the first downlink BWP and the second downlink BWP may lead to increased power consumption and reduced processing efficiency for the RedCap UE. For example, even if the RedCap UE is not scheduled to receive any downlink transmissions from network entities on these resources, the RedCap UE still has to perform a relatively large amount of blind decoding operations on the resources within the first downlink BWP and the resources within the second downlink BWP (e.g., monitoring downlink channels to obtain notification and scheduling information).

[0115] To reduce the processing costs and power consumption associated with downlink monitoring procedures for idle or inactive RedCap UEs, the total number of control resources in the first and second downlink BWPs (e.g., the downlink BWP configured for RedCap UEs) can be limited to a threshold number of control resource sets (CORESETs) and a threshold number of search spaces (SSs). For example, a network entity can configure the first and second downlink BWPs such that the total number of CORESETs and SSs in both the first and second downlink BWPs is less than a threshold. In some instances, the total number of CORESETs and SSs in the first and second downlink BWPs can depend on the capabilities of non-RedCap UEs.

[0116] Network entities (e.g., base stations) can configure a first downlink BWP and a second downlink BWP for the RedCap UE via system information or Radio Resource Control (RRC) signals. After the network entity configures the first and second downlink BWPs for the RedCap UE, the RedCap UE can monitor both the first and second downlink BWPs based on information provided by the network entity. In some instances, the network entity can send system information updates or Public Warning System (PWS) notifications to the RedCap UE via resources within the second downlink BWP.

[0117] Various embodiments of the present invention can be implemented to achieve one or more of the following advantages. The described techniques can support higher processing efficiency and reduced power consumption at the RedCap UE, among other benefits. For example, the techniques described herein can reduce the number of control resources (e.g., CORESET, SS) monitored when the RedCap UE is configured to operate in idle or inactive mode, which can reduce the processing costs and power consumption associated with idle or inactive entity downlink control channel (PDCCH) monitoring activities performed by the RedCap UE. Specifically, the described techniques can reduce the number of blind decoding operations performed by the RedCap UE, which can enable the RedCap UE to perform idle or inactive mode operation with higher processing efficiency (e.g., using fewer processing resources) and reduced power consumption.

[0118] The various forms of the present invention are initially described within the context of wireless communication systems, resource diagrams, and program flows. The various forms of the present invention are further illustrated and described by means of, and with reference to, device diagrams, system diagrams, and flowcharts relating to downlink control channel monitoring in multiple downlink BWPs.

[0119] Figure 1 illustrates examples of a wireless communication system 100 supporting downlink control channel monitoring in multiple downlink BWPs according to various embodiments of the present invention. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some instances, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some instances, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0120] Base stations 105 can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or with different capabilities. Base stations 105 and UEs 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UEs 115 and base stations 105 can establish one or more communication links 125 on the coverage area 110. The coverage area 110 can be an example of a geographical area where base stations 105 and UEs 115 can support signal transmission according to one or more radio access technologies.

[0121] UE 115 may be distributed throughout the wireless communication system 100, and each UE 115 may be fixed or mobile. UE 115 may also be referred to as mobile device, wireless device, remote device, handheld device, or user equipment, or some other suitable term, wherein "device" may also be referred to as unit, station, terminal, or client. UE 115 can be a device such as: a cellular phone, a smartphone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, MP3 player, or video device), a camera, a gaming device, a navigation / positioning device (e.g., a GNSS (Global Navigation Satellite System) device based on, for example, GPS (Global Positioning System), BeiDou, GLONASS, or Galileo, or a terrestrial device), a tablet computer, a laptop, a laptop, a smartphone, a personal computer, a smart device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets), a drone, a robot / robotic device, a vehicle, vehicle equipment, an instrument (e.g., a parking meter, an electricity meter, a gas meter, a water meter), a monitor, a gas pump, a home appliance (e.g., a kitchen appliance, a washing machine, a dryer), a location tag, a medical / healthcare device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via wireless or wired media. In some instances, UE 115 can also represent a wireless area loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or MTC device that can be implemented in various items such as home appliances, drones, robots, vehicles, or meters.

[0122] In some instances, one or more components of the wireless communication system 100 may operate as, or be referred to as, a network node. As used herein, a network node may represent any entity, apparatus, device, or computing system of the UE 115, base station 105, core network 130 configured to perform any of the technologies described herein. For example, a network node may be UE 115. As another example, a network node may be base station 105. As yet another example, a first network node may be configured to communicate with a second or third network node. In one embodiment of this instance, the first network node may be UE 115, the second network node may be base station 105, and the third network node may be UE 115. In another embodiment of this instance, the first network node may be UE 115, the second network node may be base station 105, and the third network node may be base station 105. In other embodiments of this instance, the first, second, and third network nodes may be different. Similarly, references to UE 115, base station 105, device, equipment, or computing system may include disclosures of UE 115, base station 105, device, or computing system as network nodes. For example, disclosures that UE 115 is configured to receive information from base station 105 may also disclose that a first network node is configured to receive information from a second network node. In this example, according to the content of this application, the first network node may represent a first UE 115, first base station 105, first device, first equipment, or first computing system configured to receive information; and the second network node may represent a second UE 115, second base station 105, second device, second equipment, or second computing system.

[0123] Base station 105 can communicate with core network 130, communicate with each other, or perform both operations. For example, base station 105 can interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base stations 105 can communicate with each other directly (e.g., directly between base stations 105), indirectly (e.g., via core network 130), or both on backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some instances, backhaul link 120 can be or includes one or more radio links.

[0124] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art to which this invention pertains, as base station transceiver, radio base station, access point, radio transceiver, node B, evolved node B (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), home node B, home evolved node B, or other suitable terms.

[0125] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscription device, or some other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some instances, UE 115 may include or be referred to as a wireless area loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as home appliances, vehicles, instruments, etc.

[0126] The UE 115 described in this article can communicate with various types of devices, such as other UE 115s that can sometimes act as repeaters, as well as base stations 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc., as shown in Figure 1.

[0127] UE 115 and base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication links 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., BWP) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry capture signal transmissions (e.g., synchronization signals, system information), control signal transmissions coordinating operation for the carrier, user data, or other signal transmissions. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0128] In some instances (e.g., in a carrier aggregation configuration), carriers may also have acquisition signal passing or control signal passing that coordinates operation against other carriers. Carriers may be associated with frequency channels (e.g., Evolutionary Universal Mobile Telecommunications Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and can be positioned according to a channel grid for discovery by UE 115. Carriers can operate in standalone mode, where UE 115 can initiate acquisition and connection via a carrier, or carriers can operate in non-standalone mode, where different carriers (e.g., the same or different radio access technologies) are used to anchor connections.

[0129] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0130] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some instances, the carrier bandwidth can be referred to as the carrier or the "system bandwidth" of the wireless communication system 100. For example, the carrier bandwidth can be one of several determined bandwidths of a carrier for a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) can have hardware settings supporting communication on a specific carrier bandwidth, or can be configured to support communication on one carrier bandwidth in a set of carrier bandwidths. In some instances, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some instances, each served UE 115 can be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0131] The signal waveform transmitted on a carrier can consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Spread Spectrum OFDM (DFT-S-OFDM). In a system employing MCM, a resource element can include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for UE 115. Radio communication resources can represent a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity for communication with UE 115.

[0132] It can support one or more digital schemes (numerologies) for the carrier, wherein the digital schemes may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different digital schemes. In some instances, UE 115 can be configured with multiple BWPs. In some instances, a single BWP for a carrier can be active at a given time, and communication for UE 115 can be restricted to one or more active BWPs.

[0133] It can be in the basic unit of time (which can be, for example, referred to as...) The sampling period is seconds, where It can represent the maximum supported subcarrier spacing, and The time interval for base station 105 or UE 115 can be represented as a multiple of the maximum supported Discrete Fourier Transform (DFT) size. The time intervals of communication resources can be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified via a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0134] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some instances, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into several time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier interval. Each time slot may include several symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems, time slots may be further divided into multiple mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., (Number) sampling periods. The duration of a symbol period can depend on the subcarrier interval or the operating frequency band.

[0135] Subframes, time slots, mini-time slots, or symbols can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as transmission time intervals (TTIs). In some instances, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively or supplementarily, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., as a short pulse of a shortened TTI (sTTI)).

[0136] Physical channels can be multiplexed on a carrier using various techniques. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. A control region (e.g., CORESET) for a physical control channel can be defined by the number of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESET) can be configured for a group of UEs 115. For example, one or more UEs 115 can monitor or search for control regions for control information based on one or more SS sets, and each SS set can include one or more control channel candidates arranged in a cascaded manner in one or more aggregation levels (ALs). The AL for a control channel candidate can represent the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The SS set may include a common search space (CSS) set configured to send control information to multiple UEs 115 and a USS set configured to send control information to a specific UE 115.

[0137] Each base station 105 may provide communication coverage via one or more cells (e.g., macrocells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., on a carrier) to communicate with base station 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others). In some instances, a cell may also represent a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of base station 105), the range of cells can vary from small areas (e.g., structures, subsets of structures) to large areas. For example, a cell may be or include buildings, subsets of buildings, or external space between or overlapping geographic coverage areas 110, etc.

[0138] Macrocells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 115 with a service subscription to a network provider supporting the macrocell. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed) frequency bands as macrocells. Small cells can provide unrestricted access to UE 115 with a service subscription to a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a residence or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0139] In some instances, a carrier can support multiple cells and can be configured with different cells based on different protocol types that provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0140] In some instances, base station 105 may be mobile, and therefore provide communication coverage for mobile geographic coverage areas 110. In some instances, different geographic coverage areas 110 associated with different technologies may overlap, but different geographic coverage areas 110 may be supported by the same base station 105. In other instances, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographic coverage areas 110.

[0141] Some UE 115s (e.g., MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated machine-to-machine communication (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can represent data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some instances, M2M communication or MTC can include communication from a device that integrates sensors or meters to measure or capture information and relay that information to a central server or application that can utilize that information or present it to humans interacting with the application. Some UE 115s can be designed to collect information or enable automated machine behavior. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing. In one instance, the techniques disclosed herein are applicable to MTC or IoT UE 115s. MTC or IoT UE 115 may include MTC / enhanced MTC (eMTC, also known as Category (CAT)-M, CAT M1) UE, NB-IoT (also known as CAT NB1) UE 115, and other types of UE 115. eMTC and NB-IoT represent future technologies that can be developed from these technologies or can be based on these technologies. For example, eMTC may include FeMTC (Further eMTC), eFeMTC (Enhanced Further eMTC), and mMTC (Massive MTC), while NB-IoT may include eNB-IoT (Enhanced NB-IoT) and FeNB-IoT (Further Enhanced NB-IoT).

[0142] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via either transmission or reception, rather than simultaneous transmission and reception). In some instances, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communication, when operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks) within a carrier, within a carrier's guard band, or outside a carrier.

[0143] Wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communications and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include service prioritization, and such services may be used for public safety or general business applications. The terms ultra-reliable, low-latency, and ultra-reliable low latency are used interchangeably herein.

[0144] In some instances, UE 115 can communicate directly with other UE 115s on a device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). One or more UE 115s utilizing D2D communication can be within the geographic coverage area 110 of base station 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some instances, multiple groups of UE 115s communicating via D2D communication can employ a one-to-many (1:M) system, where each UE 115 sends to each other UE 115 in the group. In some instances, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UE 115s without involving base station 105.

[0145] In some systems, the D2D communication link can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some instances, vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. Vehicles can send signals to transmit information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some instances, vehicles in a V2X system can communicate with roadside infrastructure (such as roadside units), or use vehicle-to-network (V2N) communication to communicate with the network via one or more network nodes (e.g., base station 105), or both.

[0146] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an Evolved Packet Core (EPC) or a 5G Core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), an Access and Mobility Management Function Unit (AMF)) managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), a Packet Data Network (PDN) Gateway (P-GW), or a User Plane Function (UPF)) routing packets to or interconnecting with external networks. The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with core network 130. User IP packets can be transmitted via user plane entities, which can provide IP address allocation and other functions. User plane entities can connect to one or more network service providers' IP services 150. IP service 150 may include access to the Internet, intranet, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0147] Some network devices (e.g., base station 105) may include sub-components such as access network entity 140, which may be an instance of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 via one or more other access network transport entities 145 (which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP)). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio headends and ANCs) or incorporated into a single network device (e.g., base station 105).

[0148] Wireless communication system 100 can operate using one or more frequency bands (typically in the range of 300 MHz to 300 GHz). The region from 300 MHz to 3 GHz is generally referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves may be sufficient to penetrate structures for macrocells to provide service to UE 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the lower 300 MHz portion of the spectrum, such as the High Frequency (HF) or Extreme High Frequency (VHF) bands, UHF wave transmission can be associated with smaller antennas and shorter distances (e.g., less than 100 km).

[0149] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some instances, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding device can be smaller and more closely spaced compared to UHF antennas. In some instances, this can facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may suffer even greater atmospheric attenuation and shorter distances. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary depending on the country or regulatory authority.

[0150] Wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 can employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in unlicensed radio frequency spectrum bands, devices (such as base station 105 and UE 115) can employ carrier sensing for collision detection and avoidance. In some instances, operation in unlicensed frequency bands can be based on carrier aggregation configurations that combine component carriers operating in licensed frequency bands (e.g., LAA). Operation in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.

[0151] Base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at antenna elements, such as an antenna tower. In some instances, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with several rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, antenna panels may support radio frequency beamforming for signals transmitted via antenna ports.

[0152] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique can be called spatial multiplexing. For example, a transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same coded characters) or different data streams (e.g., different coded characters). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0153] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105, UE 115) to form or guide an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating relative to a specific orientation of the antenna array experience constructive interference, while others experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with the transmitting or receiving device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0154] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet fragmentation and reassembly for transmission over logical channels. The Media Access Control (MAC) layer can perform prioritization and multiplexing from logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between the UE 115 and the base station 105 or core network 130. At the physical layer, transport channels can be mapped to physical channels.

[0155] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correct data reception on communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal and noise conditions). In some instances, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0156] Compared to other eMBB and URLLC devices, RedCap UE 115 can have lower cost and lower complexity. For example, RedCap UE 115 can have reduced bandwidth capabilities or a reduced minimum number of receive branches. Complementarily or alternatively, RedCap UE 115 can be configured to have a lower maximum number of downlink MIMO layers, a lower maximum modulation order, or reduced duplex operation capabilities. For example, the maximum bandwidth of RedCap UE 115 in frequency range 1 (FR1) can be 20 MHz during and after initial access, and the minimum bandwidth of RedCap UE 115 in frequency range 2 (FR2) can be 100 MHz during and after initial access. In some cases, RedCap UE 115 may or may not support carrier aggregation and dual connectivity. RedCap UE 115 can support standalone mode or single connectivity operating in a single frequency band at a time.

[0157] For frequency bands where other UE 115s are equipped with at least two receive antenna ports, the minimum number of receive branches supported by the RedCap UE 115 can be set to 1. However, some RedCap UE 115s may support two receive branches in these frequency bands. For frequency bands where other UE 115s are equipped with at least four receive antenna ports (e.g., different from vehicle UE 115s with two receive branches), the minimum number of receive branches supported by the RedCap UE 115 can also be set to 1. However, some RedCap UE 115s may also support two receive branches in these frequency bands. In some cases, base station 105 may be able to determine the number of receive branches supported by UE 115.

[0158] A RedCap UE 115 with one receive branch can support one downlink MIMO layer. Similarly, a RedCap UE 115 with two receive branches can support two downlink MIMO layers. For the FR1 RedCap UE 115, support for 256QAM in the downlink is optional (e.g., not mandatory). Some RedCap UE 115s can support half-duplex or Frequency Division Duplex (FDD) Type A communication. Other RedCap UE 115s can also support full-duplex FDD and Time Division Duplex (TDD).

[0159] Examples of RedCap UE 115 can include wearable devices, connected industrial equipment, and smart city devices. Wearable devices can include smartwatches, AR or VR glasses, or eHealth and medical monitoring devices, etc. Wearable devices can have high downlink reference rates (e.g., 5-50 Mbps downlink and 2-5 Mbps uplink), peak downlink rates of 150 Mbps, and peak uplink data rates of 50 Mbps. Wearable devices can have latency and reliability constraints that typically correspond to those used by eMBB. Wearable devices typically have battery life lasting several days (e.g., up to one or two weeks).

[0160] Connected industrial devices can include pressure sensors, humidity sensors, motion sensors, thermal sensors, accelerometers, and actuators, among others. These devices can feature high uplink reference rates (e.g., 2 Mbps), latency of less than 100 ms (e.g., 5-10 ms for safety-related sensors), approximately 99.99% reliability, and at least several years of battery life. Smart city devices can be used for video surveillance. These devices can feature high uplink reference rates (e.g., 2-4 Mbps for budget devices, 7.5-25 Mbps for high-end devices), latency of less than 500 ms, and relatively high reliability (e.g., between 99% and 99.9%). The reduced complexity of RedCap devices allows for more compact device designs. RedCap devices can support all TDD and FDD frequency bands configured for 5G NR.

[0161] The wireless communication system 100 can support SSB transmission in the initial downlink BWP. In FR1, the RedCap UE 115 can be configured with a first downlink BWP, which includes resources allocated for CD-SSB reception and all CORESET#0 (e.g., the default initial downlink BWP for non-RedCap UEs). The RedCap UE 115 can also be configured with a second downlink BWP (e.g., separate from the first downlink BWP). If the second downlink BWP is configured for random access but not for paging in idle or inactive modes, the RedCap UE 115 may not expect the second downlink BWP to include resources allocated for SSB reception, CORESET#0, or resources allocated for System Information Block (SIB) reception.

[0162] For example, if RedCap UE 115 performs random access in the second downlink BWP, RedCap UE 115 may not be configured to monitor paging messages in the first downlink BWP, which includes CORESET#0. If the second downlink BWP is configured for paging, RedCap UE 115 may expect the second downlink BWP to include resources allocated for receiving NCD-SSBs from the RedCap UE's serving cell, but may not expect the second downlink BWP to include CORESET#0 or resources allocated for SIB reception. For example, if the second downlink BWP (e.g., the initial downlink BWP for a separate, SIB-configured RedCap UE) includes all CORESET#0s, RedCap UE 115 may use the bandwidth and location of CORESET#0 in the downlink during initial access.

[0163] The period of the NCD-SSB in the second downlink BWP can be the same as or different from the period of the CD-SSB in the first downlink BWP. However, the period of the NCD-SSB can be no less than the period of the CD-SSB. If the second downlink BWP (e.g., a separate initially configured downlink BWP) is configured to include all CORESET#0, then RedCap UE 115 can expect to receive CD-SSBs in the second downlink BWP. In some instances, the network entity can decide to configure SSB resources, CORESET#0 configured in the Master Information Block (MIB), or SIB1 resources such that these resources are located within the second downlink BWP. For some SSB and CORESET#0 multiplexing modes, if the second downlink BWP (e.g., a separate initially configured downlink BWP) is configured to include all CORESET#0, then RedCap UE 115 can expect to receive CD-SSBs in the second downlink BWP.

[0164] The wireless communication system 100 can support higher processing efficiency and reduced power consumption, among other benefits, in the RedCap UE 115. For example, the techniques described herein can reduce the number of control resources (e.g., CORESET, SS) monitored when the RedCap UE 115 is configured to operate in idle or inactive mode. This can reduce the processing costs and power consumption associated with the idle or inactive entity downlink control channel (PDCCH) monitoring activity performed by the RedCap UE 115. Specifically, the described techniques can reduce the number of blind decoding operations performed by the RedCap UE 115, enabling the RedCap UE 115 to perform idle or inactive mode operation with higher processing efficiency (e.g., using fewer processing resources) and reduced power consumption.

[0165] Figure 2 illustrates an example of a wireless communication system 200 supporting downlink control channel monitoring in multiple downlink BWPs according to various forms of the present invention. In some instances, the wireless communication system 200 may implement various forms of the wireless communication system 100, or may be implemented by various forms of the wireless communication system 100. For example, the wireless communication device 200 may include a base station 105-a and a UE 115-a, which may be examples of the corresponding devices described with reference to Figure 1. The base station 105-a (e.g., a network entity) and the UE 115-a (e.g., a RedCap UE) may communicate within a geographic coverage area 110-a, which may be an example of a geographic coverage area 110 described with reference to Figure 1. In the wireless communication system 200, the UE 115-a may switch between a first downlink BWP and a second BWP while performing various idle or inactive mode operations.

[0166] In FR1 and FR2, a separate initial downlink BWP can be configured (e.g., via SIB) for idle or inactive RedCap UEs. This separate initial downlink BWP may be limited by the maximum bandwidth supported by the RedCap UE. The CORESET#0 configured for CD-SSB resources and MIB may or may not be located within this separate initial downlink BWP configured for the RedCap UE. If the RedCap-specific initial downlink BWP does not include the entire CORESET#0 configured by the MIB, a separate common CORESET and SS set can be configured within the RedCap-specific initial downlink BWP. For cell search and system information retrieval, idle or inactive RedCap UEs can monitor the CORESET#0 and CSS sets for SIB1 and other system information (OSI). Common CORESET and SS sets for other idle or inactive mode procedures can be configured within the RedCap-specific initial downlink BWP or within the bandwidth of CORESET#0.

[0167] Depending on the various rules specified for non-RedCap UEs, each downlink can be provided via higher-layer signaling, where P ≦ 3 CORESET if no coresetPoolIndex is provided, or if a coresetPoolIndex is provided and the coresetPoolIndex value is the same for all CORESETs; if no coresetPoolIndex is provided for the first CORESET, or if a coresetPoolIndex is provided and the coresetPoolIndex value of the first CORESET is 0 and the coresetPoolIndex value of the second CORESET is 1, and S ≦ 10 search space sets (determined based on the correlation between the SS set index and the CORESET index), then P ≦ 5 CORESETs.

[0168] Unlike the initial downlink BWP configured for non-RedCap UEs using SIB1, the RedCap-specific initial downlink BWP configured via SIB may not include CORESET#0. Therefore, the CORESET and SS set configuration rules can be modified for idle or inactive RedCap UEs. To achieve a proper balance between reduced UE complexity and coexistence between different UE types, the described technique provides an improved PDCCH monitoring procedure for RedCap UEs in idle or inactive modes, where the RedCap UE in idle or inactive mode is configured to switch between CORESET#0 and the RedCap-specific initial downlink BWP to perform various idle or inactive mode procedures.

[0169] The wireless communication system 200 can support CORESET and SS set configurations, which improve the efficiency of downlink channel monitoring for idle or inactive RedCap UEs. For idle or inactive RedCap UEs configured with a separate initial downlink BWP (e.g., different from the downlink BWP including CORESET#0), the bandwidth of the separate initial downlink BWP can be no less than 6*Q physical resource blocks (PRBs), wherein the component symbol scheme of the separate initial downlink BWP can be configured separately from the component symbol scheme used for CORESET#0. The variable Q can be defined via Equation 1 shown below, where This indicates the total number of CORESETs configured in the individual initial downlink BWP of the RedCap UE. (1)

[0170] For RedCap UEs that are in an idle state, This includes the number of CORESETs associated with the CSS collection. For RedCap UEs that are inactive, This includes the number of CORESETs associated with the CSS set and the UE-specific search space (USS) set. The CORESET and SS sets associated with the idle or inactive mode procedure can be configured jointly in CORESET#0 and in the separate initial downlink BWP for RedCap UEs.

[0171] Examples of idle or inactive mode procedures include SIB1 or OSI capture, on-demand transmission of RedCap specific system information, paging operations, Early Paging Indication (PEI) reception, mobility procedures, random access procedures (e.g., Type 1 or Type 2 random access procedures), small uplink data transmissions based on configuration authorization or according to random access procedures (e.g., Type 1 or Type 2 random access procedures), or small downlink data transmissions triggered by paging messages, multicast messages, or broadcast messages, etc. PEI can be an example of a PDCCH message that can provide UE power savings during paging operations. As described herein, mobility procedures can include cell-level mobility procedures (e.g., cell selection, cell reselection, handover) and TRP-level or beam-level mobility procedures.

[0172] The CORESET and SS sets for idle mode and inactive mode procedures can be configured within the same downlink BWP or distributed across different downlink BWPs. For example, the random access CSS for idle RedCap UEs can be configured in the RedCap-specific initial downlink BWP, while the random access CSS for inactive RedCap UEs can be configured in CORESET#0. Additionally or alternatively, the CSS set for system information retrieval or paging reception for idle or inactive UEs can be configured in CORESET#0.

[0173] In the MIB configuration, CORESET#0 (for example, , ) and the separate initial downlink BWP configured by SIB (e.g., , The total number of CORESET and SS sets configured in the configuration can be capped by P0 and S0, where P0 and S0 correspond to the total number of CORESET and SS sets configured in the downlink BWP of a non-RedCap UE. Specifically, this can be achieved according to the inequality... + The total number of CORESETs in CORESET#0 and the individual initial downlink BWP can be determined by the inequality. + This determines the total number of SS sets in CORESET#0 and the individual initial downlink BWP.

[0174] The control channel element (CCE) aggregation level (AL) and the number of blind decoding candidates for the SS set configured in the RedCap-specific initial downlink BWP can be explicitly provided to the RedCap UE via system information (e.g., for idle and inactive RedCap UEs) or RRC signal delivery (e.g., for inactive RedCap UEs). The AL of the CSS set configured in the individual initial downlink BWP can be less than the maximum value (e.g., 4, the minimum AL for the CSS set configured by SIB1 within CORESET#0). The downlink control information (DCI) size alignment transmitted in the PDCCH of the SS set in CORESET#0 and the individual initial downlink BWP can be enabled or disabled via SIB.

[0175] In the example of Figure 2, base station 105-a can send one or more control messages 205 to UE 115-a. These control messages can indicate the following configuration: a first downlink BWP associated with a first operating mode of UE 115-a, a second downlink BWP associated with a second operating mode of UE 115-a, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP. In some instances, base station 105-a can send one or more control messages 205-a to UE 115-a via the first set of resources within the first downlink BWP. Alternatively or supplementarily, base station 105-a can send one or more control messages 205-b to UE 115-a via the second set of resources within the second downlink BWP.

[0176] Base station 105-a can also send SSB 210 to UE 115-a via the first set of resources within the first downlink BWP and the second set of resources within the second downlink BWP. For example, base station 105-a can send CD-SSB 210-a to UE 115-a via the first set of resources within the first downlink BWP (e.g., when UE 115-a is in the first operating mode), and can send NCD-SSB 210-b to UE 115-a via the second set of resources within the second downlink BWP (e.g., when UE 115-a is in the second operating mode). For example, if UE 115-a switches from the first operating mode to the second operating mode, UE 115-a can perform a BWP handover procedure from the first downlink BWP to the second downlink BWP.

[0177] In some instances, UE 115-a can receive PWS notification 215 from base station 105-a via a second set of resources within the second downlink BWP. Similarly, UE 115-a can receive system information update 220 from base station 105-a via a second set of resources within the second downlink BWP. Base station 105-a can instruct PWS notification 215 or system information update 220 via random access messages (e.g., msgB or msg4), paging messages, paging-triggered downlink small data transmission (SDT), or PDCCH-triggered multicast or broadcast entity downlink shared channel (PDSCH) transmissions, etc.

[0178] The wireless communication system 200 can support higher processing efficiency and reduced power consumption, among other benefits, at the UE 115-a (e.g., a RedCap UE). For example, the techniques described herein can reduce the number of control resources (e.g., CORESET, SS) monitored when the UE 115-a is configured to operate in an idle or inactive mode, which can reduce the processing costs and power consumption associated with the idle or inactive entity downlink control channel (PDCCH) monitoring activity performed by the UE 115-a. Specifically, the described techniques can reduce the number of blind decoding operations performed by the UE 115-a, which can enable the UE 115-a to perform idle or inactive mode operation with higher processing efficiency (e.g., using fewer processing resources) and reduced power consumption.

[0179] Figures 3A and 3B illustrate examples of resource diagrams 300 and 301 supporting downlink control channel monitoring in multiple downlink BWPs according to various forms of the present invention. Resource diagrams 300 and 301 can implement various forms of wireless communication system 100 or wireless communication system 200, or can be implemented by various forms of wireless communication system 100 or wireless communication system 200. For example, resource diagrams 300 and 301 can implement UE 115 (e.g., RedCap UE) or base station 105 (e.g., network entity), or can be implemented by UE 115 (e.g., RedCap UE) or base station 105 (e.g., network entity), wherein UE 115 (e.g., RedCap UE) or base station 105 (e.g., network entity) can be examples of the corresponding devices described with reference to Figures 1 and 2. In resource diagrams 300 and 301, RedCap UEs in idle or inactive mode can switch between the first downlink BWP and the second downlink BWP to monitor downlink messages from network entities.

[0180] Resource diagrams 300 and 301 can support system information updates and PWS notifications for idle and inactive RedCap UEs. For idle or inactive RedCap UEs performing random access procedures in a separate initial downlink BWP, if no paging CSS is configured within the separate initial downlink BWP, PWS notifications and system information updates for the RedCap UE can be indicated via msg4 (e.g., in a type 1 random access procedure) or msgB (e.g., in a type 2 random access procedure). However, if a paging CSS is configured within the separate initial downlink BWP for idle and inactive RedCap UEs, PWS notifications and system information updates for the RedCap UE can be indicated via paging messages (e.g., SMS or paging messages). Alternatively or supplementarily, PWS notifications or system information updates can be delivered within the separate initial downlink BWP via paging-triggered downlink small data transmissions. PWS notifications and system information updates can also be delivered via broadcast or multicast PDSCH transmissions scheduled in conjunction with searchSpaceBroadcast (which is configured within a separate initial downlink BWP).

[0181] In the example of Figure 3A, an idle RedCap UE can reside on the serving cell's CORESET#0 to receive CD-SSB, system information, paging messages, or a combination thereof. Therefore, an idle RedCap UE can switch to a separate initial downlink BWP to perform random access or initiate a transfer to connected mode. An idle RedCap UE performing random access in a separate initial BWP before establishing an RRC connection with a network entity can avoid monitoring paging messages in CORESET#0. System information updates and PWS notifications for the RedCap UE can be delivered via msg4 or msgB transmissions scheduled in the RedCap-specific initial downlink BWP.

[0182] An idle RedCap UE can be configured to monitor the first downlink BWP of CD-SSB 305. The first downlink BWP may include CORESET#0 310, and one or more CORESETs and CSSs 315 configured for system information retrieval and system information update procedures. For example, the idle RedCap UE may receive SIB1 or OSI from network entities via one or more CORESETs and CSSs 315. In some instances, the idle RedCap UE may perform a BWP handover procedure from the first downlink BWP to the second downlink BWP based on a transition from a first operating mode to a second operating mode. The second downlink BWP may include one or more CORESETs and CSSs 320 configured for initial access, an initial downlink BWP 325 configured for the RedCap UE, one or more entity uplink shared channel (PUCCH) resources 330, an initial uplink BWP 335, and one or more random access channel (RACH) timings 340.

[0183] In the example of Figure 3B, an idle or inactive RedCap UE can receive CD-SSB and system information in CORESET#0. An idle or inactive RedCap UE can also receive NCD-SSB and monitor paging messages in a separate initial downlink BWP. Instructions for system information updates or PWS notifications can be delivered to the idle or inactive RedCap UE via paging messages or SMS. Alternatively or supplementarily, system information updates and PWS notifications can be delivered to the idle or inactive RedCap UE via downlink small data transmissions triggered by paging messages. An idle or inactive RedCap UE can also receive system information updates and PWS notifications via one or more broadcast transmissions, multicast transmissions, PDCCH transmissions, or PDSCH transmissions associated with searchSpaceBroadcast, which can be configured in a separate initial downlink BWP.

[0184] Idle or inactive RedCap UEs can be configured to monitor the first downlink BWP of CD-SSB 345. The first downlink BWP may include CORESET#0 350, and one or more CORESETs and CSS 355s configured for system information retrieval and system information update procedures. For example, an idle or inactive RedCap UE may receive SIB1 or OSI from a network entity via one or more CORESETs and CSS 355s. In some instances, an idle or inactive RedCap UE may perform a BWP handover procedure from the first downlink BWP to the second downlink BWP based on a transition from a first operating mode to a second operating mode. Idle or inactive RedCap UEs can be configured to monitor the second downlink BWP for NCD-SSB 360. The second downlink BWP may include one or more CORESETs and CSS 365s configured for paging and multicast broadcast services (MBS), an initial downlink BWP 370 configured for RedCap UEs, one or more PUCCH resources 375, and an initial uplink BWP 380.

[0185] Resource diagrams 300 and 301 can support higher processing efficiency and reduced power consumption at the RedCap UE, among other benefits. For example, the techniques described herein can reduce the number of control resources (e.g., CORESET, SS) that the RedCap UE is configured to monitor during idle or inactive mode operation, which can reduce the processing costs and power consumption associated with idle or inactive entity downlink control channel (PDCCH) monitoring activities performed by the RedCap UE. Specifically, the described techniques can reduce the number of blind decoding operations performed by the RedCap UE, which can enable the RedCap UE to perform idle or inactive mode operation with higher processing efficiency (e.g., using fewer processing resources) and reduced power consumption.

[0186] Figure 4 illustrates an example of a procedure flow 400 supporting downlink control channel monitoring in multiple downlink BWPs according to various forms of the present invention. Procedure flow 400 can implement various forms of wireless communication system 100 or wireless communication system 200, or can be implemented by various forms of wireless communication system 100 or wireless communication system 200. For example, procedure flow 400 may include base station 105-b (e.g., a network entity) and UE 115-b (e.g., a RedCap UE), wherein base station 105-b and UE 115-b may be instances of the corresponding devices described with reference to Figures 1 and 2. In the following description of procedure flow 400, operations between base station 105-b and UE 115-b may be performed in a different order or at different times than shown. Supplementally or alternatively, some operations may be omitted from procedure flow 400, and other operations may be added to procedure flow 400. In the example of Figure 4, UE 115-b (e.g., an idle or inactive RedCap UE) can be configured to monitor the first downlink BWP and the second downlink BWP in response to downlink messages from base station 105-b.

[0187] At 405, UE 115-b can receive from base station 105-b one or more control messages indicating configurations for: a first downlink BWP associated with a first operating mode of UE 115-b, a second downlink BWP associated with a second operating mode of UE 115-b, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP. For example, UE 115-b can receive a MIB indicating configurations for the first downlink BWP and the first set of control resources. Similarly, UE 115-b can receive an SIB, a dedicated RRC message, a multicast message, or a broadcast message indicating configurations for the second downlink BWP and the second set of control resources. In some instances, the first downlink BWP and the second downlink BWP may correspond to different frequency ranges (e.g., within the carrier bandwidth).

[0188] At least a portion of this configuration may correspond to the capabilities or operating modes of UE 115-b. In some instances, both the first and second operating modes of UE 115-b may correspond to the same RRC state. For example, the first and second operating modes of UE 115-b may correspond to the RRC idle state (RRC_IDLE) or the RRC inactive state (RRC-INACTIVE) of UE 115-b. In such instances, the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP may include CSS and may exclude other SSs. In other instances, the first and second operating modes of UE 115-b may correspond to the RRC inactive state (RRC_INACTIVE) or the RRC connected state (RRC_CONNECTED) of UE 115-b. In such instances, the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP may include CSS, USS, or both.

[0189] The one or more control messages may also indicate one or both of a first set of parameters associated with the first downlink BWP or a second set of parameters associated with the second downlink BWP. The first set of parameters may include bandwidth, initial PRB location, digital scheme, or a combination thereof associated with the first downlink BWP, while the second set of parameters may include bandwidth, initial PRB location, digital scheme, or a combination thereof associated with the second downlink BWP. In some instances, the first set of parameters may differ from the second set of parameters. Supplementally or alternatively, the one or more control messages may indicate the number of PRBs within the second downlink BWP, which may be based on the CCE AL of the CORESET within the second downlink BWP, the duration of the CORESET within the second downlink BWP, the total number of CORRESETs within the second downlink BWP, the RRC status of UE 115-b, or a combination thereof. The one or more control messages may also include system information messages, RRC messages, broadcast messages, or multicast messages, which indicate the CCE AL of the SS set within the second downlink BWP, the number of blind decoding candidates for the SS set within the second downlink BWP, or both.

[0190] At 410, UE 115-b can determine the number of control resources (e.g., CORESET, SS) in the second downlink BWP based on the number of control resources in the first downlink BWP, the sum of control resources in different downlink BWPs of UE 115-b, and a threshold number of control resources related to the capabilities of UE 115-b. In some instances, the first downlink BWP may include a first CSS configured for cell selection or cell reselection procedures for UEs in RRC idle or RRC inactive states. The first downlink BWP may also include one or more CSSs configured for system information retrieval procedures, system information update procedures, mobility procedures, or paging reception procedures for UEs in RRC idle or RRC inactive states. Supplementally or alternatively, the second downlink BWP may include a second CSS configured for random access procedures or paging reception procedures for UEs in RRC idle or RRC inactive states.

[0191] At 415, when UE 115-b is in the first operating mode, UE 115-b can monitor the first set of control resources within the first downlink BWP. UE 115-b can monitor the first set of control resources according to its configuration and capabilities. In some instances, UE 115-b can use CORESET and SS within the first downlink BWP to execute one or more procedures associated with UE 115-b's first operating mode. For example, UE 115-b can use the first set of control resources within the first downlink BWP to execute one or more of the following: system information update procedure, mobility procedure, paging reception procedure (also known as paging operation), random access procedure, small data transmission procedure, or on-demand system information transmission request procedure.

[0192] At 420, UE 115-b can receive one or more messages from base station 105-b via a first set of control resources within the first downlink BWP. For example, UE 115-b can receive an SIB based on its capabilities, which indicates one or more of the AL, monitoring period, or monitoring timing configuration of the CSS set within the second downlink BWP. Alternatively or supplementarily, UE 115-b (when in a first operating mode) can receive CD-SSB, system information messages, paging messages, PEI messages, random access messages, or combinations thereof from base station 105-b via a first set of control resources within the first downlink BWP associated with UE 115-b's first operating mode. UE 115-b can also receive an SIB indicating a first DCI size alignment for PDCCH messages in the SS for the first downlink BWP, a second DCI size alignment for PDCCH information in the SS for the second downlink BWP, or both.

[0193] At 425, UE 115-b can perform a BWP handover procedure from the first downlink BWP to the second BWP based on the transition from the first operating mode to the second operating mode. At 430, when UE 115-b is in the second operating mode, UE 115-b can monitor a second set of control resources within the second downlink BWP. UE 115-b can monitor the second set of control resources according to its configuration and capabilities. In some instances, UE 115-b can use CORESET and SS within the second downlink BWP to perform one or more procedures associated with UE 115-b's second operating mode. For example, UE 115-b can use the second set of control resources within the second downlink BWP to perform one or more of the following procedures: system information update procedure, mobility procedure, paging reception procedure, random access procedure, small data transmission procedure, or on-demand system information transmission request procedure.

[0194] At 435, UE 115-b can receive one or more messages from base station 105-b via the second set of control resources within the second downlink BWP. For example, UE 115-b can receive one or more of the following from base station 105-b via the second set of control resources within the second downlink BWP: random access messages, system information messages, multicast messages, broadcast messages, paging messages, SDT (e.g., uplink or downlink), or NCD-SSB. As described with reference to Figure 5, UE 115-b can also receive system information updates or PWS notifications from base station 105-b via the second set of control resources within the second downlink BWP.

[0195] Procedure flow 400 can support higher processing efficiency and reduced power consumption for UE 115-b (e.g., RedCap UE), among other benefits. For example, the techniques described herein can reduce the number of control resources (e.g., CORESET, SS) that UE 115-b is configured to monitor during idle or inactive mode operation, which can reduce the processing costs and power consumption associated with idle or inactive entity downlink control channel (PDCCH) monitoring activities performed by UE 115-b. Specifically, the described techniques can reduce the number of blind decoding operations performed by UE 115-b, which can enable UE 115-b to perform idle or inactive mode operation with higher processing efficiency (e.g., using fewer processing resources) and reduced power consumption.

[0196] Figure 5 illustrates an example of a procedure flow 500 supporting downlink control channel monitoring in multiple downlink BWPs according to various forms of the present invention. Procedure flow 500 can implement various forms of wireless communication system 100 or wireless communication system 200, or can be implemented by various forms of wireless communication system 100 or wireless communication system 200. For example, procedure flow 500 may include base station 105-c (e.g., network entity) and UE 115-c (e.g., RedCap UE), which may be instances of the corresponding devices described with reference to Figures 1 and 2. In the following description of procedure flow 500, operations between base station 105-c and UE 115-c may be performed in a different order or at different times than shown. Supplementally or alternatively, some operations may be omitted from procedure flow 500, and other operations may be added to procedure flow 500. In the example in Figure 5, UE 115-c can receive system information updates or PWS notifications from base station 105-c via resources in the downlink BWP configured for idle or inactive RedCap UEs.

[0197] At point 505, UE 115-c can receive one or more control messages from base station 105-c. These control messages may indicate configurations for a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP. At least a portion of this configuration may correspond to the capabilities of UE 115-c. At point 510, when UE 115-c is in the first operating mode, UE 115-c can monitor the first set of resources within the first downlink BWP. UE 115-c can monitor the first set of resources based on the configuration (indicated by one or more control messages) and based on the capabilities of UE 115-c. At point 515, UE 115-c can receive one or more messages from base station 105-c via the first set of resources within the first downlink BWP. UE 115-c can receive one or more messages based on the configuration and based on the capabilities of UE 115-c.

[0198] At 520, UE 115-c can perform a BWP handover procedure from the first downlink BWP to the second downlink BWP based on the transition from the first operating mode to the second operating mode. In some instances, the first and second operating modes can correspond to the same RRC state. For example, the first and second operating modes can correspond to an RRC idle state (e.g., RRC_IDLE) or an RRC inactive state (RRC_INACTIVE). In other words, UE 115-c can switch between different operating modes while maintaining the same RRC state. These different operating modes can be associated with different downlink BWPs. At 525, UE 115-c can monitor a second set of resources within the second downlink BWP (e.g., when UE 115-c is in the second operating mode). UE 115-c can monitor the second set of resources within the second downlink BWP based on its configuration and capabilities.

[0199] In some instances, UE 115-c can perform a random access procedure with base station 105-c at point 530 (when in the second operating mode). UE 115-c can perform the random access procedure via a second set of resources within the second downlink BWP. At point 535, UE 115-c can receive system information updates from base station 105-c via the second set of resources within the second downlink BWP. At point 540, UE 115-c can receive PWS notifications from base station 105-c via the second set of resources within the second downlink BWP. In some instances, UE 115-c can receive system information updates or PWS notifications via random access messages (e.g., msgB or msg4), wherein base station 105-c can send the random access message during the random access procedure (e.g., via the second set of resources within the second downlink BWP).

[0200] If, for example, the second downlink BWP does not include a CSS configured for paging operations, base station 105-c can send system information updates or PWS notifications via random access messages. If the second downlink BWP does include a CSS configured for paging operations, base station 105-c can indicate system information updates or PWS notifications via paging messages. In other instances, base station 105-c can indicate system information updates or PWS notifications via a paging-triggered SDT. For example, base station 105-c can send (e.g., via a second set of resources within the second downlink BWP) a paging message scheduling downlink SDTs from base station 105-c. Base station 105-c can send downlink SDTs based on the paging message and can include system information updates or PWS notifications in the downlink SDTs. Similarly, base station 105-c can send PDCCH messages scheduling broadcast or multicast PDSCH messages from base station 105-c (e.g., via a second set of resources within the second downlink BWP). Base station 105-c can send broadcast or multicast PDSCH messages based on PDCCH messages, and can include system information updates or PWS notifications in broadcast or multicast PDSCH messages.

[0201] Procedure flow 500 can support greater processing efficiency and reduced power consumption at UE 115-c (e.g., RedCap UE), among other benefits. For example, the techniques described herein can reduce the number of control resources (e.g., CORESET, SS) monitored when UE 115-c is configured to operate in idle or inactive mode, which can reduce the processing costs and power consumption associated with idle or inactive entity downlink control channel (PDCCH) monitoring activities performed by UE 115-c. Specifically, the described techniques can reduce the number of blind decoding operations performed by UE 115-c, which can enable UE 115-c to perform idle or inactive mode operation with higher processing efficiency (e.g., using fewer processing resources) and reduced power consumption.

[0202] Figure 6 illustrates a block diagram 600 of a device 605 supporting downlink control channel monitoring in multiple downlink BWPs according to various configurations of this document. Device 605 may be an example of some configurations of a UE 115 (e.g., a RedCap UE) as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0203] Receiver 610 may provide a unit for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to downlink control channel monitoring in multiple downlink BWPs). The information may be transmitted to other components of the device 605. Receiver 610 may employ a single antenna or a group of multiple antennas.

[0204] Transmitter 615 can provide a unit for transmitting signals generated by other components of transmitting device 605. For example, transmitter 615 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to downlink control channel monitoring in multiple downlink BWPs). In some instances, transmitter 615 can be co-located with receiver 610 in a transceiver module. Transmitter 615 can utilize a single antenna or a group of multiple antennas.

[0205] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be instances of units for performing various states of downlink control channel monitoring in the multiple downlink BWPs described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more functions described herein.

[0206] In some instances, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., using communication management circuitry). This hardware may include at least one processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof, configured to or otherwise support units for performing the functions described herein. In some instances, at least one processor and memory coupled to at least one processor (e.g., operational ground, communication ground, functional ground, electronic ground, and / or electrical ground) may be configured to perform one or more functions described herein (e.g., via instructions stored in memory executed by at least one processor).

[0207] Additionally or alternatively, in some instances, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof or components may be implemented using hardware, software (e.g., executed by at least one processor), or any combination thereof. If implemented using software executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations thereof or components may be performed by a general-purpose processor, DSP, central processing unit (CPU), graphics processing unit (GPU), ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., units configured or otherwise supported for performing the functions described herein).

[0208] In some instances, the communication manager 620 may be configured to use, or otherwise coordinate with, receiver 610, transmitter 615, or both, to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 620 may receive information from receiver 610, send information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to receive information, send information, or perform various other operations as described herein.

[0209] According to the examples disclosed herein, the communication manager 620 can support wireless communication at device 605. For example, the communication manager 620 can be configured or otherwise support: a unit for receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of device 605, a second downlink BWP associated with a second operating mode of device 605, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of device 605. The communication manager 620 can be configured or otherwise support: a unit for device 605 in the first operating mode to monitor the first set of control resources within the first downlink BWP, according to the configuration and based on the capabilities of device 605. The communication manager 620 can be configured or otherwise support: a unit for device 605 in the second operating mode to monitor the second set of control resources within the second downlink BWP, according to the configuration and based on the capabilities of device 605.

[0210] Additionally or alternatively, the communication manager 620 may support wireless communication at device 605 according to the examples disclosed herein. For example, the communication manager 620 may be configured or otherwise support: a unit for receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of device 605, a second downlink BWP associated with a second operating mode of device 605, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of this configuration corresponds to the capabilities of device 605. The communication manager 620 may also be configured or otherwise support: a unit for receiving one or more messages by device 605 in the first operating mode, according to the configuration and based on the capabilities of device 605, via the first set of resources within the first downlink BWP. The communication manager 620 can be configured or otherwise supported as a unit for receiving one or both of system information messages or PWS messages via a second set of resources within the second downlink BWP, as configured and based on the capabilities of the device 605 in the second operating mode.

[0211] By including or configuring the communication manager 620 according to the examples described herein, device 605 (e.g., at least one processor whose control or other means (e.g., operational ground, communication ground, functional ground, electronic ground, and / or electrical ground) is coupled to receiver 610, transmitter 615, communication manager 620, or a combination thereof) can support techniques for reducing processing and power consumption. For example, the techniques described herein can improve processing efficiency and power consumption associated with downlink channel monitoring at device 605 by reducing the number of resources that device 605 is configured to monitor in idle or inactive modes.

[0212] Figure 7 illustrates a block diagram 700 of a device 705 supporting downlink control channel monitoring in multiple downlink BWPs according to various configurations of this document. Device 705 may be an example of some configuration of device 605 as described herein or UE 115 (e.g., RedCap UE). Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0213] Receiver 710 may provide a unit for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to downlink control channel monitoring in multiple downlink BWPs). The information may be transmitted to other components of device 705. Receiver 710 may employ a single antenna or a group of multiple antennas.

[0214] Transmitter 715 may provide a unit for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to downlink control channel monitoring in multiple downlink BWPs). In some instances, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may employ a single antenna or a group of multiple antennas.

[0215] Device 705 or its various components may be instances of units used to perform various states of downlink control channel monitoring in a plurality of downlink BWPs as described herein. For example, communication manager 720 may include control message receiver 725, first downlink BWP monitoring component 730, second downlink BWP monitoring component 735, message receiving component 740, or any combination thereof. Communication manager 720 may be instances of various states of communication manager 620 as described herein. In some instances, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise coordinate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 720 may receive information from receiver 710, send information to transmitter 715, or be integrated with receiver 710, transmitter 715, or both to receive information, send information, or perform various other operations as described herein.

[0216] According to the examples disclosed herein, the communication manager 720 can support wireless communication at device 705. For example, the control message receiver 725 can be configured or otherwise supported to: receive one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of device 705, a second downlink BWP associated with a second operating mode of device 705, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of this configuration corresponds to the capabilities of device 705. The first downlink BWP monitoring component 730 can be configured or otherwise supported to: monitor the first set of control resources within the first downlink BWP according to the configuration and based on the capabilities of device 705 in the first operating mode of device 705. The second downlink BWP monitoring component 735 can be configured or otherwise supported to: monitor the second set of control resources within the second downlink BWP according to the configuration and based on the capabilities of device 705 in the second operating mode of device 705.

[0217] Additionally or alternatively, the communication manager 720 may support wireless communication at device 705 according to the examples disclosed herein. For example, the control message receiver 725 may be configured or otherwise supported for receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for a first downlink BWP associated with a first operating mode of device 705, a second downlink BWP associated with a second operating mode of device 705, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of device 705. The message receiving component 740 may be configured or otherwise supported for receiving one or more messages by device 705 in the first operating mode, according to the configuration and based on the capabilities of device 705, via the first set of resources within the first downlink BWP. The message receiving component 740 may be configured or otherwise supported as a unit for receiving one or both of system information messages or PWS messages via a second set of resources within a second downlink BWP, as configured and based on the capabilities of the device 705 in a second operating mode.

[0218] Figure 8 illustrates a block diagram 800 of a communication manager 820 supporting downlink control channel monitoring in multiple downlink BWPs according to various configurations described herein. The communication manager 820 may be an instance of a communication manager 620, communication manager 720, or some configuration of both as described herein. The communication manager 820, or its various components, may be instances of units for performing various configurations of downlink control channel monitoring in multiple downlink BWPs as described herein. For example, the communication manager 820 may include a control message receiver 825, a first downlink BWP monitoring component 830, a second downlink BWP monitoring component 835, a message receiving component 840, a resource determination component 845, a BWP switching component 850, a program execution component 855, an operating mode component 860, a control resource component 865, a random access execution component 870, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0219] According to the examples disclosed herein, the communication manager 820 can support wireless communication at the UE (e.g., a RedCap UE). For example, the control message receiver 825 can be configured or otherwise supported to include a unit for receiving one or more control messages from a network entity, the control messages indicating a configuration for a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of this configuration corresponds to the capabilities of the UE. The first downlink BWP monitoring unit 830 can be configured or otherwise supported to include a unit for the UE to monitor the first set of control resources within the first downlink BWP, according to the configuration and based on the capabilities of the UE, in the first operating mode. The second downlink BWP monitoring unit 835 can be configured or otherwise supported to include a unit for the UE to monitor the second set of control resources within the second downlink BWP, according to the configuration and based on the capabilities of the UE, in the second operating mode.

[0220] In some instances, the first downlink BWP monitoring component 830 may be configured or otherwise supported for monitoring a first set of control resources within the first downlink BWP by the UE in a first operating mode. In some instances, the control message receiver 825 may be configured or otherwise supported for receiving, via the first set of control resources, one or more control messages from a network entity instructing on the configuration of the second downlink BWP and a second set of control resources within the second downlink BWP. In some instances, the resource determination component 845 may be configured or otherwise supported for determining the number of control resources in the second downlink BWP based on the number of control resources in the first downlink BWP.

[0221] In some instances, the resource determination component 845 may be configured or otherwise supported to determine the number of control resources in the second downlink BWP based on the number of control resources in the first downlink BWP, the sum of control resources in different downlink BWPs of the UE, and a threshold number of control resources corresponding to the UE's capabilities.

[0222] In some instances, the resource determination component 845 may be configured or otherwise supported to determine the number of SS sets in the second downlink BWP based on the number of SS sets in the first downlink BWP, the sum of SS sets in different downlink BWPs of the UE, and a threshold number of SS sets corresponding to the UE's capabilities.

[0223] In some instances, to support receiving one or more control messages, the control message receiver 825 may be configured or otherwise support: receiving a control signal transmission indicating one or both of a first set of parameters associated with a first downlink BWP or a second set of parameters associated with a second downlink BWP, the first set of parameters including bandwidth, initial PRB position, digital scheme or combination thereof associated with the first downlink BWP, and the second set of parameters including bandwidth, initial PRB position, digital scheme or combination thereof associated with the second downlink BWP, wherein the first set of parameters differs from the second set of parameters.

[0224] In some instances, to support receiving the one or more control messages, the control message receiver 825 may be configured or otherwise supported for receiving, from a network entity, a main information block indicating the configuration for the first downlink BWP. In some instances, to support receiving the one or more control messages, the control message receiver 825 may be configured or otherwise supported for receiving, from a network entity, one or more of an SIB, a dedicated RRC message, a multicast message, or a broadcast message indicating the configuration for the second downlink BWP.

[0225] In some instances, the BWP switching unit 850 may be configured or otherwise supported as a unit for executing a BWP switching procedure from a first downlink BWP to a second downlink BWP based on a transition from a first operating mode to a second operating mode, wherein monitoring a second set of control resources within the second downlink BWP is based on executing the BWP switching procedure.

[0226] In some instances, the program execution unit 855 may be configured or otherwise supported to execute one or more programs associated with a first operating mode or a second operating mode of the UE, using the CORESET and SS set within a first downlink BWP or using the CORESET and SS set within a second downlink BWP, the one or more programs including a system information retrieval program, a system information update program, a mobility program, a paging operation, a random access program, a small data transmission program, an on-demand system information transmission request program, or a combination thereof.

[0227] In some instances, the first operating mode and the second operating mode correspond to the UE's RRC idle state or RRC inactive state. In some instances, the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP include a set of CSS.

[0228] In some instances, the first operating mode and the second operating mode correspond to the UE's RRC inactive state or RRC connected state. In some instances, the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP include a USS set, a CSS set, or both. In some instances, the first downlink BWP and the second downlink BWP correspond to different frequency ranges.

[0229] In some instances, the first downlink BWP includes a first CSS configured for cell selection or cell reselection procedures for a UE in an RRC idle or RRC inactive state. In some instances, the second downlink BWP includes at least a second CSS configured for random access procedures or paging operations for a UE in an RRC idle or RRC inactive state.

[0230] In some instances, the first downlink BWP includes one or more CSSs configured for system information retrieval procedures, system information update procedures, mobility procedures, or paging operations of a UE in an RRC idle or RRC inactive state.

[0231] In some instances, to support receiving one or more control messages, the control message receiver 825 may be configured or otherwise supported for receiving an SIB based on the UE's capabilities, wherein the SIB indicates one or more of the AL, monitoring period, or monitoring timing configuration of the CSS set within the second downlink BWP.

[0232] In some instances, the message receiving unit 840 may be configured or otherwise supported for receiving CD-SSB, system information messages, paging messages, PEI messages, random access messages, or combinations thereof from a network entity via a first set of control resources within a first downlink BWP associated with the first operating mode of the UE in a first operating mode.

[0233] In some instances, to support the reception of one or more control messages, the message receiving unit 840 may be configured or otherwise support: a unit for receiving an SIB from a network entity, the SIB indicating a first DCI size alignment of PDCCH messages in the SS set of a first downlink BWP, a second DCI size alignment of PDCCH messages in the SS set of a second downlink BWP, or both.

[0234] In some instances, the message receiving component 840 may be configured or otherwise supported for receiving one or more of the following from network entities via a second set of control resources within the second downlink BWP: random access messages, system information messages, multicast messages, broadcast messages, paging messages, SDT, or NCD-SSB.

[0235] In some instances, to support receiving one or more control messages, the control message receiver 825 may be configured or otherwise supported for receiving a control signal transmission indicating the number of PRBs within the second downlink BWP, wherein the number of PRBs is based on the CCE AL of the CORESET within the second downlink BWP, the duration of the CORESET within the second downlink BWP, the total number of CORESETs within the second downlink BWP, the RRC state of the UE, or a combination thereof.

[0236] In some instances, to support receiving one or more control messages, the control message receiver 825 may be configured or otherwise supported to receive one or more of the following: a CCE AL indicating the set of SS within the second downlink BWP, the number of blind decoding candidates for the set of SS within the second downlink BWP, or both; a system information message; an RRC message; a broadcast message; or a multicast message.

[0237] Additionally or alternatively, the communication manager 820 may support wireless communication at the UE according to the examples disclosed herein. In some instances, the control message receiver 825 may be configured or otherwise supported for receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE. The message receiving unit 840 may be configured or otherwise supported for receiving one or more messages by the UE in the first operating mode, according to the configuration and based on the capabilities of the UE, via the first set of resources within the first downlink BWP. In some instances, the message receiving unit 840 may be configured or otherwise supported for receiving one or both of system information messages or PWS messages by the UE in the second operating mode, according to the configuration and based on the capabilities of the UE, via the second set of resources within the second downlink BWP.

[0238] In some instances, the random access execution unit 870 may be configured or otherwise supported as a unit for performing random access procedures with network entities via a second set of resources within the second downlink BWP.

[0239] In some instances, to support receiving one or both of system information messages or PWS messages, the message receiving unit 840 may be configured or otherwise supported to: receive random access messages from a network entity via a second set of resources within a second downlink BWP according to a random access procedure, the random access messages indicating one or both of system information messages or PWS messages.

[0240] In some instances, to support receiving one or both of system information messages or PWS messages, the message receiving unit 840 may be configured or otherwise support: a unit for receiving random access messages from a network entity via a second set of resources within the second downlink BWP based on the identification that the second downlink BWP does not include a CSS configured for paging operations, the random access messages indicating one or both of system information messages or PWS messages.

[0241] In some instances, to support receiving one or both of system information messages or PWS messages, the message receiving unit 840 may be configured or otherwise support: a unit for receiving paging messages from a network entity via a second set of resources within the second downlink BWP based on the identification that the second downlink BWP includes a CSS configured for paging operations, the paging message indicating one or both of system information messages or PWS messages.

[0242] In some instances, to support receiving one or both of system information messages or PWS messages, the message receiving unit 840 may be configured or otherwise supported for receiving paging messages from a network entity via a second set of resources within the second downlink BWP, the paging messages being scheduled from the network entity's downlink SDT. In some instances, to support receiving one or both of system information messages or PWS messages, the second downlink BWP monitoring unit 835 may be configured or otherwise supported for monitoring a second set of resources within the second downlink BWP based on paging messages to obtain a downlink SDT from the network entity, the downlink SDT indicating one or both of system information messages or PWS messages.

[0243] In some instances, to support receiving one or both of system information messages or PWS messages, the control message receiver 825 may be configured or otherwise supported for receiving PDCCH transmissions from network entities via a second set of resources within the second downlink BWP, the PDCCH transmissions being scheduled from broadcast or multicast PDSCH transmissions from the network entities. In some instances, to support receiving one or both of system information messages or PWS messages, the second downlink BWP monitoring component 835 may be configured or otherwise supported for monitoring the second set of resources based on PDCCH transmissions to obtain broadcast or multicast PDSCH transmissions from network entities, the broadcast or multicast PDSCH transmissions indicating one or both of system information messages or PWS messages.

[0244] Figure 9 illustrates a system 900 including device 905 according to various embodiments of the present invention, which supports downlink control channel monitoring in multiple downlink BWPs. Device 905 may be an instance of device 605, device 705, or UE 115 (e.g., RedCap UE) as described herein, or a component including device 605, device 705, or UE 115. Device 905 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 905 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, memory 930, code 935, and a processor 940. These components may be electrically communicated via one or more buses (e.g., bus 945) or otherwise coupled (e.g., operating ground, communication ground, functional ground, electronic ground and / or electrical ground).

[0245] I / O controller 910 can manage input and output signals to device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize operating systems such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, I / O controller 910 can represent, or interact with, a modem, keyboard, mouse, touchscreen, or similar device. In some cases, I / O controller 910 can be implemented as part of a processor (e.g., processor 940). In some cases, a user can interact with device 905 via I / O controller 910 or via hardware controlled by I / O controller 910.

[0246] In some cases, the device 905 may include a single antenna 925. However, in other cases, the device 905 may have more than one antenna 925, which are capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link, as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, providing modulated packets to one or more antennas 925 for transmission, and demodulating packets received from one or more antennas 925. The transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof, as described herein.

[0247] Memory 930 may include random access memory (RAM) and read-only memory (ROM). Memory 930 may store computer-readable, computer-executable code 935, including instructions that, when executed by processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, code 935 may not be executed directly by processor 940, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some specific cases, memory 930 may include a basic I / O system (BIOS) that controls basic hardware or software operations (e.g., interaction with peripheral components or devices).

[0248] Processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, GPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, individual gate or transistor logic units, individual hardware components, or any combination thereof). In some cases, processor 940 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 940. Processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting downlink control channel monitoring in multiple downlink BWPs). For example, device 905 or components of device 905 may include processor 940 and memory 930 coupled to processor 940 (e.g., operational ground, communication ground, functional ground, electronic ground, and / or electrical ground), processor 940 and processor 930 being configured to perform the various functions described herein.

[0249] According to the examples disclosed herein, the communication manager 920 can support wireless communication at device 905. For example, the communication manager 920 can be configured or otherwise support: a unit for receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of device 905, a second downlink BWP associated with a second operating mode of device 905, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of device 905. The communication manager 920 can be configured or otherwise support: a unit for device 905 in the first operating mode to monitor the first set of control resources within the first downlink BWP, according to the configuration and based on the capabilities of device 905. The communication manager 920 can be configured or otherwise support: a unit for device 905 in the second operating mode to monitor the second set of control resources within the second downlink BWP, according to the configuration and based on the capabilities of device 905.

[0250] Additionally or alternatively, the communication manager 920 may support wireless communication at the device 905 according to the examples disclosed herein. For example, the communication manager 920 may be configured or otherwise support: a unit for receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the device 905, a second downlink BWP associated with a second operating mode of the device 905, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of this configuration corresponds to the capabilities of the device 905. The communication manager 920 may also be configured or otherwise support: a unit for receiving one or more messages by the device 905 in the first operating mode, according to the configuration and based on the capabilities of the device 905, via the first set of resources within the first downlink BWP. The communication manager 920 can be configured or otherwise supported as a unit for receiving one or both of system information messages or PWS messages via a second set of resources within the second downlink BWP, as configured and based on the capabilities of the device 905 in the second operating mode.

[0251] By including or configuring the communication manager 920 according to the examples described herein, device 905 (e.g., RedCap UE) can support techniques for improving downlink channel monitoring. For example, if device 905 is configured to monitor different downlink BWPs when operating in an idle or inactive state, the techniques described herein can provide a way to reduce the total number of CORESETs and SSs in different downlink BWPs. As a result, device 905 can monitor fewer control resources, which allows device 905 to perform downlink channel monitoring with lower processing management overhead and reduced power consumption, among other benefits.

[0252] In some instances, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using transceiver 915, one or more antennas 925, or any combination thereof, or otherwise coordinated with transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is shown as a separate component, in some instances, one or more functions described with reference to the communication manager 920 may be supported or performed by processor 940, memory 930, code 935, or any combination thereof. For example, code 935 may include instructions executable by processor 940 to cause device 905 to perform various states of downlink control channel monitoring in the multiple downlink BWPs described herein, or processor 940 and memory 930 may be otherwise configured to perform or support such operations.

[0253] Figure 10 illustrates a block diagram 1000 of a device 1005 supporting downlink control channel monitoring in multiple downlink BWPs according to various configurations described herein. Device 1005 may be an example of some configurations of a base station 105 (e.g., a network entity) as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0254] Receiver 1010 may provide a unit for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to downlink control channel monitoring in multiple downlink BWPs). The information may be transmitted to other components of the device 1005. Receiver 1010 may employ a single antenna or a group of multiple antennas.

[0255] Transmitter 1015 may provide a unit for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to downlink control channel monitoring in multiple downlink BWPs). In some instances, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may employ a single antenna or a group of multiple antennas.

[0256] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be instances of units for performing various states of downlink control channel monitoring in the multiple downlink BWPs described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more functions described herein.

[0257] In some instances, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented using hardware (e.g., communication management circuitry). This hardware may include at least one processor, DSP, ASIC, FPGA, or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof, configured or otherwise supporting units for performing the functions described herein. In some instances, at least one processor and memory coupled to at least one processor (e.g., operational ground, communication ground, functional ground, electronic ground, and / or electrical ground) may be configured to perform one or more functions described herein (e.g., via instructions stored in memory executed by at least one processor).

[0258] Additionally or alternatively, in some instances, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented using hardware, software (e.g., executed by at least one processor), or any combination thereof. If implemented using software executed by at least one processor, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, GPU, ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., units configured or otherwise supported for performing the functions described herein).

[0259] In some instances, the communication manager 1020 may be configured to use, or otherwise coordinate with, receiver 1010, transmitter 1015, or both, to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 1020 may receive information from receiver 1010, send information to transmitter 1015, or combine with receiver 1010, transmitter 1015, or both to receive information, send information, or perform various other operations described herein.

[0260] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at device 1005. For example, the communication manager 1020 can be configured or otherwise support: a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE. The communication manager 1020 can be configured or otherwise support: a unit for transmitting a first set of messages via the first set of control resources within the first downlink BWP, based on the configuration and the capabilities of the UE. The communication manager 1020 can be configured or otherwise support: a unit for transmitting a second set of messages via the second set of control resources within the second downlink BWP, based on the configuration and the capabilities of the UE.

[0261] Additionally or alternatively, the communication manager 1020 may support wireless communication at device 1005 according to the examples disclosed herein. For example, the communication manager 1020 may be configured or otherwise support: a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE. The communication manager 1020 may be configured or otherwise support: a unit for transmitting one or more messages via the first set of resources within the first downlink BWP, depending on the configuration and based on the capabilities of the UE. The communication manager 1020 may be configured or otherwise support: a unit for transmitting one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP, depending on the configuration and based on the capabilities of the UE.

[0262] By including or configuring the communication manager 1020 according to the examples described herein, device 1005 (e.g., at least one processor whose control or other means (e.g., operational ground, communication ground, functional ground, electronic ground, and / or electrical ground) is coupled to receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof) can support techniques for reducing processing and power consumption. For example, the techniques described herein can support constraints on the total number of CORESETs and SSs in the various downlink BWPs configured for device 1005. Constraining the total number of control resources in these downlink BWPs can improve communication efficiency between device 1005 and idle or inactive RedCap UEs associated with device 1005.

[0263] Figure 11 illustrates a block diagram 1100 of a device 1105 supporting downlink control channel monitoring in multiple downlink BWPs according to various configurations of this document. Device 1105 may be an example of some configuration of device 1005 as described herein or base station 105 (e.g., a network entity). Device 1105 may include receiver 1110, transmitter 1115, and communication manager 1120. Device 1105 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0264] Receiver 1110 may provide a unit for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to downlink control channel monitoring in multiple downlink BWPs). The information may be transmitted to other components of the device 1105. Receiver 1110 may employ a single antenna or a group of multiple antennas.

[0265] Transmitter 1115 may provide a unit for transmitting signals generated by other components of device 1105. For example, transmitter 1115 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to downlink control channel monitoring in multiple downlink BWPs). In some instances, transmitter 1115 may be co-located with receiver 1110 in a transceiver module. Transmitter 1115 may employ a single antenna or a group of multiple antennas.

[0266] Device 1105 or its various components may be instances of units used to perform various states of downlink control channel monitoring in the multiple downlink BWPs described herein. For example, communication manager 1120 may include control message transmitter 1125, first downlink BWP transmission component 1130, second downlink BWP transmission component 1135, or any combination thereof. Communication manager 1120 may be instances of various states of communication manager 1120 as described herein. In some instances, communication manager 1120 or its various components may be configured to use receiver 1110, transmitter 1115, or both, or otherwise coordinate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 1120 may receive information from receiver 1110, send information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to receive information, send information, or perform various other operations described herein.

[0267] According to the examples disclosed herein, the communication manager 1120 can support wireless communication at the device 1105. For example, the control message transmitter 1125 can be configured or otherwise supported to include a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of this configuration corresponds to the capabilities of the UE. The first downlink BWP transmission unit 1130 can be configured or otherwise supported to include a unit for transmitting a first set of messages via the first set of control resources within the first downlink BWP, based on the configuration and the capabilities of the UE. The second downlink BWP transmission unit 1135 can be configured or otherwise supported to include a unit for transmitting a second set of messages via the second set of control resources within the second downlink BWP, based on the configuration and the capabilities of the UE.

[0268] Alternatively or supplementally, the communication manager 1120 may support wireless communication at device 1105 according to the examples disclosed herein. The control message transmitter 1125 may be configured or otherwise support: a unit for transmitting one or more control messages, wherein the one or more control messages indicate a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE. The first downlink BWP transmission unit 1130 may be configured or otherwise support: a unit for transmitting one or more messages via the first set of resources within the first downlink BWP, depending on the configuration and based on the capabilities of the UE. The second downlink BWP transmission unit 1135 may be configured or otherwise support: a unit for transmitting one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP, depending on the configuration and based on the capabilities of the UE.

[0269] Figure 12 illustrates a block diagram 1200 of a communication manager 1220 supporting downlink control channel monitoring in multiple downlink BWPs according to various configurations described herein. The communication manager 1220 may be an instance of a configuration of the communication manager 1020, communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be instances of units for performing various configurations of downlink control channel monitoring in multiple downlink BWPs as described herein. For example, the communication manager 1220 may include a control message transmitter 1225, a first downlink BWP transmission component 1230, a second downlink BWP transmission component 1235, a resource determination component 1240, an operation mode component 1245, a resource control component 1250, a message transmission component 1255, a random access component 1260, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0270] According to the examples disclosed herein, the communication manager 1220 can support wireless communication at a network entity. For example, the control message transmitter 1225 can be configured or otherwise supported to: a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of this configuration corresponds to the capabilities of the UE. The first downlink BWP transmission unit 1230 can be configured or otherwise supported to: a unit for transmitting a first set of messages via the first set of control resources within the first downlink BWP, based on the configuration and the capabilities of the UE. The second downlink BWP transmission unit 1235 can be configured or otherwise supported to: a unit for transmitting a second set of messages via the second set of control resources within the second downlink BWP, based on the configuration and the capabilities of the UE.

[0271] In some instances, the resource determination component 1240 may be configured or otherwise supported for determining the number of control resources in the second downlink BWP based on the number of control resources in the first downlink BWP. In some instances, the control message transmitter 1225 may be configured or otherwise supported for sending an indication to the UE of the number of control resources in the second downlink BWP.

[0272] In some instances, the resource determination component 1240 may be configured or otherwise supported for determining the number of control resources in the second downlink BWP based on the number of control resources in the first downlink BWP and the sum of control resources in the different downlink BWPs of the UE. In some instances, the control message transmitter 1225 may be configured or otherwise supported for sending an indication of the number of control resources in the second downlink BWP to the UE.

[0273] In some instances, the resource determination component 1240 may be configured or otherwise supported to determine the number of SS sets in the second downlink BWP based on the number of SS sets in the first downlink BWP, the sum of SS sets in different downlink BWPs of the UE, and a threshold number of SS sets related to the UE's ability to connect to network entities. In some instances, the control message transmitter 1225 may be configured or otherwise supported to send an indication to the UE regarding the amount of control resources in the second downlink BWP.

[0274] In some instances, to support the transmission of one or more control messages, the control message transmitter 1225 may be configured or otherwise support: a unit for transmitting control signal transmissions indicating one or both of a first set of parameters associated with a first downlink BWP or a second set of parameters associated with a second downlink BWP, the first set of parameters including bandwidth, initial PRB position, digital scheme or combination thereof associated with the first downlink BWP, and the second set of parameters including bandwidth, initial PRB position, digital scheme or combination thereof associated with the second downlink BWP, wherein the first set of parameters differs from the second set of parameters.

[0275] In some instances, to support the transmission of one or more control messages, the control message transmitter 1225 may be configured or otherwise supported to: transmit to the UE a MIB indicating the configuration for the first downlink BWP. In some instances, to support the transmission of one or more control messages, the control message transmitter 1225 may be configured or otherwise supported to: transmit to the UE one or more of an SIB, a dedicated RRC message, a multicast message, or a broadcast message indicating the configuration for the second downlink BWP.

[0276] In some instances, the first operating mode and the second operating mode correspond to the UE's RRC idle state or RRC inactive state. In some instances, the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP include a set of CSS.

[0277] In some instances, the first operating mode and the second operating mode correspond to the UE's RRC inactive state or RRC connected state. In some instances, the first set of control resources within the first downlink BWP and the second set of control resources within the second downlink BWP include a USS set, a CSS set, or both. In some instances, the first downlink BWP and the second downlink BWP correspond to different frequency ranges.

[0278] In some instances, the first downlink BWP includes a first CSS configured for cell selection or cell reselection procedures for a UE in an RRC idle or RRC inactive state. In some instances, the second downlink BWP includes at least a second CSS configured for random access procedures or paging operations for a UE in an RRC idle or RRC inactive state.

[0279] In some instances, the first downlink BWP includes one or more CSSs that are configured for system information retrieval procedures, system information update procedures, mobility procedures, or paging operations of a UE in an RRC idle or RRC inactive state.

[0280] In some instances, to support the transmission of one or more control messages, the control message transmitter 1225 may be configured or otherwise supported to: transmit an SIB based on the UE's capabilities, wherein the SIB indicates one or more of the AL, monitoring period, or monitoring timing configuration of the CSS set within the second downlink BWP.

[0281] In some instances, the message transmission component 1255 may be configured or otherwise supported for transmitting CD-SSB, system information messages, paging messages, PEI messages, random access messages, or combinations thereof from a network entity via a first set of control resources within a first downlink BWP associated with a first operating mode of the UE.

[0282] In some instances, to support the transmission of one or more control messages, the message transmission unit 1255 may be configured or otherwise support: a unit for transmitting an SIB indicating a first DCI size alignment of PDCCH messages in the SS set of a first downlink BWP, a second DCI size alignment of PDCCH messages in the SS set of a second downlink BWP, or both.

[0283] In some instances, the message transmission component 1255 may be configured or otherwise supported for transmitting one or more of the following: random access messages, system information messages, multicast messages, broadcast messages, paging messages, SDT, or NCD-SSB via a second set of control resources within the second downlink BWP.

[0284] In some instances, to support the transmission of one or more control messages, the control message transmitter 1225 may be configured or otherwise support: a unit for transmitting control signal transmission indicating the number of PRBs within the second downlink BWP, wherein the number of PRBs is based on the CCE AL of the CORESET within the second downlink BWP, the duration of the CORESET within the second downlink BWP, the total number of CORESETs within the second downlink BWP, the RRC state of the UE, or a combination thereof.

[0285] In some instances, to support the transmission of one or more control messages, the control message transmitter 1225 may be configured or otherwise supported to transmit one or more of the following: a CCE AL indicating the number of blind decoding candidates for the SS set within the second downlink BWP, or both, a system information message, an RRC message, a broadcast message, or a multicast message.

[0286] Additionally or alternatively, the communication manager 1220 may support wireless communication at a network entity according to the examples disclosed herein. In some instances, the control message transmitter 1225 may be configured or otherwise supported to: a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE. In some instances, the first downlink BWP transmission unit 1230 may be configured or otherwise supported to: a unit for transmitting one or more messages via the first set of resources within the first downlink BWP, depending on the configuration and based on the capabilities of the UE. In some instances, the second downlink BWP transmission unit 1235 may be configured or otherwise supported to: a unit for transmitting one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP, depending on the configuration and based on the capabilities of the UE.

[0287] In some instances, the random access component 1260 may be configured or otherwise supported as a unit for performing random access procedures with the UE via a second set of resources within the second downlink BWP.

[0288] In some instances, in order to support the transmission of one or both of system information messages or PWS messages, the second downlink BWP transmission unit 1235 may be configured or otherwise support: a unit for transmitting random access messages to the UE via a second set of resources within the second downlink BWP according to a random access procedure, the random access messages indicating one or both of system information messages or PWS messages.

[0289] In some instances, to support the transmission of one or both of system information messages or PWS messages, the second downlink BWP transmission unit 1235 may be configured or otherwise support: a unit for transmitting a random access message to the UE via a second set of resources within the second downlink BWP based on the identification that the second downlink BWP does not include a CSS configured for paging operations, the random access message indicating one or both of system information messages or PWS messages.

[0290] In some instances, to support the transmission of one or both of system information messages or PWS messages, the second downlink BWP transmission unit 1235 may be configured or otherwise support: a unit for transmitting a paging message to the UE via a second set of resources within the second downlink BWP based on the identification that the second downlink BWP includes a CSS configured for paging operations, the paging message indicating one or both of system information messages or PWS messages.

[0291] In some instances, to support the transmission of one or both of system information messages or PWS messages, the second downlink BWP transmission component 1235 may be configured or otherwise support: a unit for transmitting a paging message to the UE via a second set of resources within the second downlink BWP, the paging message being scheduled from the downlink SDT of the network entity. In some instances, to support the transmission of one or both of system information messages or PWS messages, the second downlink BWP transmission component 1235 may be configured or otherwise support: a unit for transmitting a downlink SDT via a second set of resources based on the paging message, the downlink SDT indicating one or both of system information messages or PWS messages.

[0292] In some instances, to support the transmission of one or both of system information messages or PWS messages, the second downlink BWP transmission component 1235 may be configured or otherwise support: a unit for transmitting PDCCH transmissions to the UE via a second set of resources within the second downlink BWP, the PDCCH transmissions being scheduled from broadcast or multicast PDSCH transmissions of network entities. In some instances, to support the transmission of one or both of system information messages or PWS messages, the second downlink BWP transmission component 1235 may be configured or otherwise support: a unit for transmitting broadcast or multicast PDSCH transmissions via a second set of resources based on PDCCH transmissions, wherein the broadcast or multicast PDSCH transmissions indicate one or both of system information messages or PWS messages.

[0293] Figure 13 illustrates a system 1300 including device 1305 according to various embodiments of the present invention. Device 1305 supports downlink control channel monitoring in multiple downlink BWPs. Device 1305 may be an instance of device 1005, device 1105, or base station 105 (e.g., a network entity) as described herein, or a component including device 1005, device 1105, or base station 105. Device 1305 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as communication manager 1320, network communication manager 1310, transceiver 1315, antenna 1325, memory 1330, code 1335, processor 1340, and inter-station communication manager 1345. These components may be electrically communicated via one or more buses (e.g., bus 1350) or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, and / or electrical ground).

[0294] The network communication manager 1310 can manage communication with the core network 130 (e.g., via one or more wired backhaul links). For example, the network communication manager 1310 can manage the transmission of data communications to client devices (e.g., one or more UEs 115).

[0295] In some cases, device 1305 may include a single antenna 1325. However, in other cases, device 1305 may have more than one antenna 1325, which are capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 1315 may communicate bidirectionally via one or more antennas 1325, a wired link, or a wireless link, as described herein. For example, transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1315 may also include a modem for modulating packets to provide modulated packets to one or more antennas 1325 for transmission, and for demodulating packets received from one or more antennas 1325. Transceiver 1315, or transceiver 1315 and one or more antennas 1325, may be an example of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or components thereof, as described herein.

[0296] Memory 1330 may include RAM and ROM. Memory 1330 may store computer-readable, computer-executable code 1335 containing instructions that, when executed by processor 1340, cause device 1305 to perform the various functions described herein. Code 1335 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, code 1335 may not be directly executed by processor 1340, but may enable the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1330 may include a BIOS, which controls basic hardware or software operations (e.g., interaction with peripheral components or devices).

[0297] Processor 1340 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, GPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, decoupled gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, processor 1340 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks supporting downlink control channel monitoring in multiple downlink BWPs). For example, device 1305 or components of device 1305 may include processor 1340 and memory 1330, the memory 1330 being coupled to or coupled to processor 1340 (e.g., operative ground, communication ground, functional ground, electronic ground and / or electrical ground), processor 1340 and processor 1330 being configured to perform the various functions described herein.

[0298] Inter-site communication manager 1345 can manage communication with other base stations 105 and may include a controller or scheduler for coordinating communication with UE 115 with other base stations 105. For example, inter-site communication manager 1345 can coordinate the scheduling of transmissions to UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some instances, inter-site communication manager 1345 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0299] According to the examples disclosed herein, the communication manager 1320 can support wireless communication at device 1305. For example, the communication manager 1320 can be configured or otherwise support: a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of control resources within the first downlink BWP, and a second set of control resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE. The communication manager 1320 can be configured or otherwise support: a unit for transmitting a first set of messages via the first set of control resources within the first downlink BWP, based on the configuration and the capabilities of the UE. The communication manager 1320 can be configured or otherwise support: a unit for transmitting a second set of messages via the second set of control resources within the second downlink BWP, based on the configuration and the capabilities of the UE.

[0300] Additionally or alternatively, the communication manager 1320 may support wireless communication at device 1305 according to the examples disclosed herein. For example, the communication manager 1320 may be configured or otherwise support: a unit for transmitting one or more control messages indicating a configuration for: a first downlink BWP associated with a first operating mode of the UE, a second downlink BWP associated with a second operating mode of the UE, a first set of resources within the first downlink BWP, and a second set of resources within the second downlink BWP, wherein at least a portion of the configuration corresponds to the capabilities of the UE. The communication manager 1320 may be configured or otherwise support: a unit for transmitting one or more messages via the first set of resources within the first downlink BWP, depending on the configuration and based on the capabilities of the UE. The communication manager 1320 may be configured or otherwise support: a unit for transmitting one or both of system information messages or PWS messages via the second set of resources within the second downlink BWP, depending on the configuration and based on the capabilities of the UE.

[0301] By including or configuring the communication manager 1320 according to the examples described herein, device 1305 can support techniques for improving idle or inactive mode programs at device 1305. For example, the techniques described herein can improve the efficiency (e.g., processing efficiency, power efficiency) of paging programs, system information retrieval programs, system information update programs, SDT programs, or MBS programs executed by device 1305.

[0302] In some instances, the communication manager 1320 may be configured to use, or otherwise coordinate with, transceiver 1315, one or more antennas 1325, or any combination thereof, to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1320 is shown as a separate component, in some instances, one or more functions described with reference to the communication manager 1320 may be supported or performed by processor 1340, memory 1330, code 1335, or any combination thereof. For example, code 1335 may include instructions executable by processor 1340 to cause device 1305 to perform various states of downlink control channel monitoring in the multiple downlink BWPs described herein, or processor 1340 and memory 1330 may be otherwise configured to perform or support such operations.

[0303] Figure 14 illustrates a flowchart of a method 1400 supporting downlink control channel monitoring in multiple downlink BWPs, according to various embodiments of the present invention. The operation of method 1400 can be implemented by a UE (e.g., a RedCap UE) or its components as described herein. For example, the operation of method 1400 can be performed by a UE 115 as described with reference to Figures 1 through 9. In some instances, the UE can execute a set of instructions to control the functional units of the UE to perform the described functions. Alternatively or supplementarily, the UE can use dedicated hardware to perform various embodiments of the described functions.

[0304] At 1405, the method may include receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink bandwidth portion associated with a first operating mode of the UE, a second downlink bandwidth portion associated with a second operating mode of the UE, a first set of control resources within the first downlink bandwidth portion, and a second set of control resources within the second downlink bandwidth portion, wherein at least a portion of the configuration corresponds to the capabilities of the UE. The operation of 1405 may be performed according to examples as disclosed herein. In some examples, the mode of operation of 1405 may be performed by a control message receiver 825 as described with reference to FIG8.

[0305] At 1410, the method may include: monitoring a first set of control resources within a first downlink bandwidth portion by the UE in a first operating mode, based on configuration and at least in part on the UE's capabilities. The operation of 1410 may be performed according to examples disclosed herein. In some instances, the operation of 1410 may be performed by a first downlink BWP monitoring component 830 as described with reference to FIG8.

[0306] At 1415, the method may include: monitoring a second set of control resources within a second downlink bandwidth portion by the UE in a second operating mode, based on configuration and at least in part on the UE's capabilities. The operation at 1415 may be performed according to examples disclosed herein. In some instances, the operation at 1415 may be performed by a second downlink BWP monitoring component 835 as described with reference to FIG8.

[0307] Figure 15 illustrates a flowchart of a method 1500 for supporting downlink control channel monitoring in multiple downlink BWPs, according to various embodiments of the present invention. The operation of method 1500 can be implemented by a network entity or its components as described herein. For example, the operation of method 1500 can be performed by a base station 105 as described with reference to Figures 1-5 and Figures 10-13. In some instances, the network entity can execute a set of instructions to control the functional units of the network entity to perform the described functions. Alternatively or supplementarily, the network entity can use dedicated hardware to perform various embodiments of the described functions.

[0308] At 1505, the method may include sending one or more control messages indicating a configuration for: a first downlink bandwidth portion associated with a first operating mode of the UE, a second downlink bandwidth portion associated with a second operating mode of the UE, a first set of control resources within the first downlink bandwidth portion, and a second set of control resources within the second downlink bandwidth portion, wherein at least a portion of the configuration corresponds to the capabilities of the UE. Operation 1505 may be performed according to examples disclosed herein. In some examples, the mode of operation of 1505 may be performed by a control message transmitter 1225 as described with reference to FIG12.

[0309] At 1510, the method may include: transmitting a first set of messages via a first set of control resources within a first downlink bandwidth portion, based on the configuration and at least in part on the capabilities of the UE. The operation of 1510 may be performed according to examples disclosed herein. In some instances, the operation of 1510 may be performed by a first downlink BWP transmission component 1230 as described with reference to FIG12.

[0310] At 1515, the method may include: transmitting a second set of messages via a second set of control resources within a second downlink bandwidth portion, based on the configuration and at least in part on the capabilities of the UE. The operation of 1515 may be performed according to examples disclosed herein. In some instances, the operation of 1515 may be performed by a second downlink BWP transmission component 1235 as described with reference to FIG12.

[0311] Figure 16 illustrates a flowchart of a method 1600 supporting downlink control channel monitoring in multiple downlink BWPs, according to various embodiments of the present invention. Operation of method 1600 can be implemented by a UE (e.g., a RedCap UE) or its components as described herein. For example, operation of method 1600 can be performed by a UE 115 as described with reference to Figures 1 through 9. In some instances, the UE can execute a set of instructions to control the functional units of the UE to perform the described functions. Alternatively or supplementarily, the UE can use dedicated hardware to perform various embodiments of the described functions.

[0312] At 1605, the method may include receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink bandwidth portion associated with a first operating mode of the UE, a second downlink bandwidth portion associated with a second operating mode of the UE, a first set of resources within the first downlink bandwidth portion, and a second set of resources within the second downlink bandwidth portion, wherein at least a portion of the configuration corresponds to the capabilities of the UE. The operation at 1605 may be performed according to examples as disclosed herein. In some examples, the operation at 1605 may be performed by a control message receiver 825 as described with reference to FIG8.

[0313] At 1610, the method may include: receiving one or more messages by the UE in a first operating mode, according to the configuration and at least in part based on the UE's capabilities, via a first set of resources within a first downlink bandwidth portion. The operation of 1610 may be performed according to examples as disclosed herein. In some instances, the operation of 1610 may be performed by a message receiving unit 840 as described with reference to FIG8.

[0314] At 1615, the method may include: receiving, in a second operating mode, one or both of a system information message or a public warning system message via a second set of resources within a second downlink bandwidth portion, according to the configuration and at least in part based on the capabilities of the UE. The operation at 1615 may be performed according to examples as disclosed herein. In some instances, the operation at 1615 may be performed by a message receiving unit 840 as described with reference to FIG8.

[0315] Figure 17 illustrates a flowchart of a method 1700 for monitoring downlink control channels in multiple downlink BWPs, according to various embodiments of the present invention. The operation of method 1700 can be implemented by a network entity or its components as described herein. For example, the operation of method 1700 can be performed by a base station 105 as described with reference to Figures 1-5 and Figures 10-13. In some instances, the network entity can execute a set of instructions to control the functional units of the network entity to perform the described functions. Alternatively or supplementarily, the network entity can use dedicated hardware to perform various embodiments of the described functions.

[0316] At 1705, the method may include sending one or more control messages indicating a configuration for: a first downlink bandwidth portion associated with a first operating mode of the UE, a second downlink bandwidth portion associated with a second operating mode of the UE, a first set of control resources within the first downlink bandwidth portion, and a second set of control resources within the second downlink bandwidth portion, wherein at least a portion of the configuration corresponds to the capabilities of the UE. Operation 1705 may be performed according to examples as disclosed herein. In some examples, the mode of operation of 1705 may be performed by a control message transmitter 1225 as described with reference to FIG12.

[0317] At 1710, the method may include: transmitting one or more messages via a first set of resources within a first downlink bandwidth portion, based on the configuration and at least in part on the capabilities of the UE. The operation of 1710 may be performed according to examples disclosed herein. In some instances, the operation of 1710 may be performed by a first downlink BWP transmission component 1230 as described with reference to FIG12.

[0318] At 1715, the method may include: transmitting one or both of a system information message or a public warning system message via a second set of resources within the second downlink bandwidth portion, based on the configuration and at least in part on the capabilities of the UE. The operation of 1715 may be performed according to examples disclosed herein. In some instances, the operation of 1715 may be performed by a second downlink BWP transmission component 1235 as described with reference to FIG12.

[0319] Figure 18 illustrates a flowchart of a method 1800 for monitoring downlink control channels in multiple downlink BWPs, according to various embodiments of the present invention. The operation of method 1800 can be implemented by a UE or its components as described herein. For example, the operation of method 1800 can be performed by a UE 115 as described with reference to Figures 1 through 6. In some instances, the UE can execute a set of instructions to control the functional units of the UE to perform the described functions. Alternatively or supplementarily, the UE can use dedicated hardware to perform various embodiments of the described functions.

[0320] At 1805, the method may include: receiving one or more control messages indicating a first configuration for a first downlink bandwidth portion and a second configuration for a second downlink bandwidth portion specific to a reduced-capability UE, wherein the first configuration identifies a first set of resources within the first downlink bandwidth portion, and the second configuration identifies a second set of resources within the second downlink bandwidth portion. The operation at 1805 may be performed according to examples as disclosed herein. In some examples, the operation at 1805 may be performed by a control message receiver 825 as described with reference to FIG8.

[0321] At 1810, the method may include: monitoring a first set of resources within a first downlink bandwidth portion based on a first configuration, the radio resource control state of the UE, and the capabilities of the UE. The operation at 1810 may be performed according to examples disclosed herein. In some instances, the operation at 1810 may be performed by a first downlink BWP monitoring component 830 as described with reference to FIG8.

[0322] At 1815, the method may include: monitoring a second set of resources within a second downlink bandwidth portion specific to a degraded UE, based on a second configuration, the UE's radio resource control state, and the UE's capabilities. The operation at 1815 may be performed according to examples disclosed herein. In some instances, the operation at 1815 may be performed by a second downlink BWP monitoring component 835 as described with reference to FIG8.

[0323] Figure 19 illustrates a flowchart of a method 1900 for supporting downlink control channel monitoring in multiple downlink BWPs, according to various embodiments of the present invention. The operation of method 1900 can be implemented by a network entity or its components as described herein. For example, the operation of method 1900 can be performed by an access network entity 140 as described with reference to Figures 1-2 and Figures 7-10. In some instances, the network entity can execute an instruction set to control the functional units of the network entity to perform the described functions. Alternatively or supplementarily, the network entity can use dedicated hardware to perform various embodiments of the described functions.

[0324] At 1905, the method may include: sending one or more control messages indicating a first configuration for a first downlink bandwidth portion and a second configuration for a second downlink bandwidth portion specific to a reduced-capability UE, wherein the first configuration identifies a first set of resources within the first downlink bandwidth portion and the second configuration identifies a second set of resources within the second downlink bandwidth portion. The operation at 1905 may be performed according to examples as disclosed herein. In some examples, the operation at 1905 may be performed by a control message transmitter 1225 as described with reference to FIG12.

[0325] At 1910, the method may include: transmitting a first downlink message to a degraded UE via a first set of resources within a first downlink bandwidth portion, according to a first configuration indicated by one or more control messages. The operation at 1910 may be performed according to examples disclosed herein. In some instances, the operation at 1910 may be performed by a first downlink BWP transmission component 1230 as described with reference to FIG12.

[0326] At 1915, the method may include: transmitting a second downlink message to the degraded UE via a second set of resources within a second downlink bandwidth portion specific to the degraded UE, according to a second configuration indicated by one or more control messages. The operation at 1915 may be performed according to examples disclosed herein. In some instances, the operation at 1915 may be performed by a second downlink BWP transmission component 1235 as described with reference to FIG12.

[0327] The following provides an overview of the various aspects of this case:

[0328] Sample 1: A method for wireless communication at a UE, comprising: receiving one or more control messages indicating a first configuration for a first downlink bandwidth portion and a second configuration for a second downlink bandwidth portion specific to a degraded UE, wherein the first configuration identifies a first set of resources within the first downlink bandwidth portion and the second configuration identifies a second set of resources within the second downlink bandwidth portion; monitoring the first set of resources within the first downlink bandwidth portion based on the first configuration, a radio resource control state of the UE, and the capabilities of the UE; and monitoring the second set of resources within the second downlink bandwidth portion specific to a degraded UE based on the second configuration, the radio resource control state of the UE, and the capabilities of the UE.

[0329] State 2: The method according to State 1 also includes: determining a first set of parameters for the first downlink bandwidth portion based at least in part on the first configuration, the first set of parameters including one or more of the following: the cyclic prefix of the control resource set within the first downlink bandwidth portion, the subcarrier spacing, the number of resource blocks, or the number of symbols; and determining a second set of parameters for the second downlink bandwidth portion specific to the reduced-capability UE based at least in part on the second configuration, the second set of parameters including one or more of the following: the bandwidth for the second downlink bandwidth portion, the first physical resource block, or the subcarrier spacing.

[0330] State 3: The method according to any one of states 1 to 2, wherein monitoring the first set of resources includes: receiving at least one message of a paging operation via a common search space within the first downlink bandwidth portion, based on the first configuration and the capabilities of the UE, wherein the first downlink bandwidth portion includes a set of control resources with an index of zero (0).

[0331] State 4: The method according to any one of states 1 to 3, wherein in order to monitor the second set of resources, it includes: receiving one or more random access messages via the second set of resources in the second downlink bandwidth portion of the UE specific to the de-capable UE, based on the second configuration, the radio resource control state of the UE and the capability of the UE, wherein the second downlink bandwidth portion does not include a control resource set having an index of zero (0).

[0332] State 5: The method according to any one of States 1 to 4 also includes: receiving a downlink message that schedules the transmission of a first system information block within the first downlink bandwidth via one or more entity downlink control channel resources within the first downlink bandwidth, wherein the first system information block indicates the second configuration of the second downlink bandwidth specific to the degraded UE.

[0333] State 6: The method according to any one of states 1 to 5, wherein monitoring the first set of resources includes: receiving one or more cell-defined synchronization signal blocks via the first set of resources within the first downlink bandwidth portion; and performing a cell selection procedure based at least in part on measurements of the one or more cell-defined synchronization signal blocks.

[0334] State 7: The method according to any one of states 1 to 6, wherein receiving the one or more control messages includes: receiving an indication of a search space configured for downlink small data transmission in the first downlink bandwidth portion or the second downlink bandwidth portion; and, according to the indication, monitoring the search space for downlink small data transmission.

[0335] State 8: The method according to any one of states 1 to 7, wherein receiving the one or more control messages includes: receiving a master information block indicating the first configuration of the first downlink bandwidth portion; and receiving a system information block indicating the second configuration of the second downlink bandwidth portion.

[0336] State 9: The method according to any one of States 1 to 8 also includes: receiving one or more of the following via the first downlink bandwidth portion or the second downlink bandwidth portion specific to the degraded UE: a set of control resources or a set of search spaces: system information messages, paging operation messages, random access messages, small data transmissions, broadcast messages, public warning system notifications, or non-cell-defined synchronization signal blocks.

[0337] State 10: The method according to any one of states 1 to 9 also includes: receiving one or more of the following via the first set of resources within the first downlink bandwidth portion, including a cell-defined synchronization signal block, a system information message, a paging operation message, or a random access message, based on the first configuration, the radio resource control state of the UE, and the capability of the UE.

[0338] State 11: The method according to any one of states 1 to 10 also includes: transmitting one or more of small data transmissions, random access messages, UE mobility information, or requests for on-demand system information via one or more resources within an uplink bandwidth portion configured for the UE.

[0339] State 12: The method according to any one of states 1 to 11 also includes: sending a request for on-demand system information via one or more resources within an uplink bandwidth portion configured for the UE; and receiving the on-demand system information via the first set of resources within the first downlink bandwidth portion or the second set of resources within the second downlink bandwidth portion.

[0340] State 13: According to the method of State 12, wherein the UE sends the request for on-demand system information according to the random access procedure.

[0341] State 14: The method according to any one of states 1 to 13, wherein the bandwidth of the second downlink bandwidth portion specific to the reduced capability UE is less than or equal to the maximum downlink bandwidth supported by the UE.

[0342] State 15: The method according to any one of states 1 to 14, wherein the one or more control messages include a master information block, a system information block, a radio resource control message, or a combination thereof.

[0343] State 16: The method according to any one of states 1 to 15, wherein the first downlink bandwidth portion is used to receive a cell-defined synchronization signal block.

[0344] State 17: The method according to any one of states 1 to 16, wherein the UE is a de-capable UE; and the radio resource control state of the UE includes an idle radio resource control state or an inactive radio resource control state.

[0345] State 18: The method according to any one of states 1 to 17, wherein the first downlink bandwidth portion includes a first set of common search spaces configured for a cell selection procedure or a cell reselection procedure; and the second downlink bandwidth portion includes a second set of common search spaces configured for a random access procedure or a paging operation.

[0346] State 19: The method according to any one of states 1 to 18, wherein the first downlink bandwidth portion includes one or more common search spaces configured for system information retrieval or paging operations.

[0347] State 20: The method according to any one of states 1 to 19 also includes: determining the number of control resource sets in the second downlink bandwidth portion based at least in part on the number of control resource sets in the first downlink bandwidth portion, the sum of control resource sets in other downlink bandwidth portions of the UE, the threshold number of control resource sets supported by the UE, or a combination thereof.

[0348] State 21: The method according to any one of states 1 to 20 also includes: determining the number of search space sets in the second downlink bandwidth portion based at least in part on the number of search space sets in the first downlink bandwidth portion, the sum of search space sets in other downlink bandwidth portions of the UE, the threshold number of search space sets supported by the UE, or a combination thereof.

[0349] State 22: The method according to any one of states 1 to 21 also includes: switching from the first downlink bandwidth portion to the second downlink bandwidth portion after switching from a first operating mode associated with the first downlink bandwidth portion to a second operating mode associated with the second downlink bandwidth portion.

[0350] State 23: The method according to any one of states 1 to 22, wherein receiving the one or more control messages includes: receiving system information indicating at least one of the aggregation level, monitoring period, or monitoring timing configuration for a common search space set within the second downlink bandwidth portion specific to the degraded UE.

[0351] State 24: The method according to any one of states 1 to 23, wherein receiving the one or more control messages includes: receiving a system information block, the system information block indicating: a first downlink control information size alignment of physical downlink control channel messages scheduled in the search space set of the first downlink bandwidth portion, a second downlink control information size alignment of physical downlink control channel messages scheduled in the search space set of the second downlink bandwidth portion, or both.

[0352] State 25: The method according to any one of states 1 to 24, wherein receiving the one or more control messages includes: receiving an indication of the number of physical resource blocks within the second downlink bandwidth portion specific to the degraded UE, wherein the number of physical resource blocks is based at least in part on the control channel element aggregation level of the control resource set within the second downlink bandwidth portion, the duration of the control resource set within the second downlink bandwidth portion, the total number of control resource sets within the second downlink bandwidth portion, the radio resource control state of the UE, or a combination thereof.

[0353] State 26: The method according to any one of states 1 to 25, wherein receiving the one or more control messages includes: receiving one or more of the following: a system information message, a radio resource control message, a broadcast message, or a multicast message indicating: the control channel element aggregation level of the search space set within the second downlink bandwidth portion, the number of blind decoding candidates of the search space set within the second downlink bandwidth portion, or both.

[0354] 27. A method for wireless communication at a network entity, comprising: transmitting one or more control messages, the one or more control messages indicating a first configuration for a first downlink bandwidth portion and a second configuration for a second downlink bandwidth portion specific to a degraded UE, the first configuration identifying a first set of resources within the first downlink bandwidth portion, the second configuration identifying a second set of resources within the second downlink bandwidth portion; transmitting a first downlink message to a degraded UE via the first set of resources within the first downlink bandwidth portion according to the first configuration indicated by the one or more control messages; and transmitting a second downlink message to a degraded UE via the second set of resources within the second downlink bandwidth portion specific to the degraded UE according to the second configuration indicated by the one or more control messages.

[0355] State 28: According to the method of State 27, sending the first downlink message includes: according to the first configuration, sending at least one message of a paging operation to the degraded UE via a common search space within the first downlink bandwidth portion, wherein the first downlink bandwidth portion includes a control resource set having an index of zero (0).

[0356] Sample 29: An apparatus for wireless communication at a UE, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to perform the method according to any one of Samples 1 to 26.

[0357] State 30: An apparatus for wireless communication at a UE, comprising: at least one unit for performing the method according to any one of states 1 to 26.

[0358] Format 31: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by at least one processor to perform the method according to any one of Formats 1 to 26.

[0359] Sample 32: An apparatus for wireless communication at a network entity, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to perform the method according to any one of Samples 27 to 28.

[0360] Sample 33: An apparatus for wireless communication at a network entity, comprising: at least one unit for performing the method according to any one of Samples 27 to 28.

[0361] Sample 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code including instructions executable by at least one processor to perform the method according to any one of Samples 27 to 28.

[0362] Sample 35: A method for wireless communication at a UE, comprising: receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink bandwidth portion associated with a first operating mode of the UE, a second downlink bandwidth portion associated with a second operating mode of the UE, a first set of control resources within the first downlink bandwidth portion, and a second set of control resources within the second downlink bandwidth portion, wherein at least a portion of the configuration corresponds to a capability of the UE; the UE, in the first operating mode, monitoring the first set of control resources within the first downlink bandwidth portion according to the configuration and at least in part based on the capability of the UE; and the UE, in the second operating mode, monitoring the second set of control resources within the second downlink bandwidth portion according to the configuration and at least in part based on the capability of the UE.

[0363] Version 36: The method according to version 35 also includes: the UE monitoring the first set of control resources in the first downlink bandwidth in the first operating mode; receiving, via the first set of control resources, one or more control messages from the network entity indicating the configuration for the second downlink bandwidth and the second set of control resources in the second downlink bandwidth; and determining the number of control resources in the second downlink bandwidth based at least in part on the number of control resources in the first downlink bandwidth.

[0364] Version 37: The method according to any one of versions 35 to 36 also includes: determining the number of control resources in the second downlink bandwidth portion based at least in part on the number of control resources in the first downlink bandwidth portion, the sum of control resources in different downlink bandwidth portions of the UE, and a threshold number of control resources corresponding to the capabilities of the UE.

[0365] Version 38: The method according to any one of versions 35 to 37 also includes: determining the number of search space sets in the second downlink bandwidth portion based at least in part on the number of search space sets in the first downlink bandwidth portion, the sum of search space sets in different downlink bandwidth portions of the UE, and a threshold number of search space sets corresponding to the capabilities of the UE.

[0366] State 39: The method according to any one of States 35 to 38, wherein receiving the one or more control messages includes: receiving a control signal transmission indicating one or both of a first set of parameters associated with the first downlink bandwidth portion or a second set of parameters associated with the second downlink bandwidth portion, the first set of parameters including bandwidth associated with the first downlink bandwidth portion, initial physical resource block location, digital scheme or a combination thereof, and the second set of parameters including bandwidth associated with the second downlink bandwidth portion, initial physical resource block location, digital scheme or a combination thereof, wherein the first set of parameters is different from the second set of parameters.

[0367] State 40: The method according to any one of states 35 to 39, wherein receiving the one or more control messages includes: receiving from the network entity a main information block indicating the configuration for the first downlink bandwidth portion; and receiving from the network entity one or more of a system information block, a dedicated radio resource control message, a multicast message, or a broadcast message indicating the configuration for the second downlink bandwidth portion.

[0368] State 41: The method according to any one of states 35 to 40 also includes: performing a bandwidth portion handover procedure from the first downlink bandwidth portion to the second downlink bandwidth portion based at least in part on the transition from the first operating mode to the second operating mode, wherein monitoring the second set of control resources within the second downlink bandwidth portion is based at least in part on the execution of the bandwidth portion handover procedure.

[0369] State 42: The method according to any one of states 35 to 41 also includes: using the control resource set and search space set within the first downlink bandwidth portion or using the control resource set and search space set within the second downlink bandwidth portion to execute one or more procedures associated with the first operating mode or the second operating mode of the UE, the one or more procedures including a system information retrieval procedure, a system information update procedure, a mobility procedure, a paging operation, a random access procedure, a small data transmission procedure, an on-demand system information transmission request procedure, or a combination thereof.

[0370] State 43: The method according to any one of states 35 to 42, wherein the first operating mode and the second operating mode correspond to the radio resource control idle state or radio resource control inactive state of the UE; and, the first set of control resources in the first downlink bandwidth portion and the second set of control resources in the second downlink bandwidth portion include a common search space set.

[0371] State 44: The method according to any one of states 35 to 42, wherein the first operating mode and the second operating mode correspond to the radio resource control inactive state or radio resource control connected state of the UE; and, the first set of control resources in the first downlink bandwidth portion and the second set of control resources in the second downlink bandwidth portion include a UE-specific search space set, a common search space set, or both.

[0372] State 45: The method according to any one of states 35 to 44, wherein the first downlink bandwidth portion and the second downlink bandwidth portion correspond to different frequency ranges.

[0373] State 46: The method according to any one of states 35 to 45, wherein the first downlink bandwidth portion includes a first common search space configured for a cell selection procedure or cell reselection procedure of a UE in a radio resource control idle state or a radio resource control inactive state; and the second downlink bandwidth portion includes at least a second common search space configured for a random access procedure or paging operation of a UE in a radio resource control idle state or a radio resource control inactive state.

[0374] State 47: The method according to any one of states 35 to 46, wherein the first downlink bandwidth portion includes one or more common search spaces configured for system information retrieval procedures, system information update procedures, mobility procedures, or paging operations of a UE in a radio resource control idle state or radio resource control inactive state.

[0375] State 48: The method according to any one of states 35 to 47, wherein receiving the one or more control messages includes: receiving a system information block based on the UE's capability, the system information block indicating the aggregation level, monitoring period, or monitoring timing configuration of the common search space set within the second downlink bandwidth portion.

[0376] State 49: The method according to any one of states 35 to 48 also includes: the UE receiving, in the first operating mode, a cell-defined synchronization signal block, system information message, paging operation message, random access message, or a combination thereof from the network entity via the first set of control resources within the first downlink bandwidth portion associated with the first operating mode of the UE.

[0377] State 50: The method according to any one of states 35 to 49, wherein receiving the one or more control messages includes: receiving a system information block from the network entity, the system information block indicating a first downlink control information size alignment for entity downlink control channel messages in the search space set of the first downlink bandwidth portion, a second downlink control information size alignment for entity downlink control channel messages in the search space set of the second downlink bandwidth portion, or both.

[0378] State 51: The method according to any one of states 35 to 50 also includes: receiving one or more of random access messages, system information messages, multicast messages, broadcast messages, paging operation messages, small data transmissions, or non-cell-defined synchronization signal blocks from the network entity via the second set of control resources within the second downlink bandwidth portion.

[0379] State 52: The method according to any one of states 35 to 51, wherein receiving the one or more control messages includes: receiving a control signal transmission indicating the number of physical resource blocks within the second downlink bandwidth portion, wherein the number of physical resource blocks is at least partially based on the control channel element aggregation level of the control resource set within the second downlink bandwidth portion, the duration of the control resource set within the second downlink bandwidth portion, the total number of control resource sets within the second downlink bandwidth portion, the radio resource control state of the UE, or a combination thereof.

[0380] State 53: The method according to any one of states 35 to 52, wherein receiving the one or more control messages includes receiving one or more of the following: a system information message indicating a control channel element aggregation level for a search space set within the second downlink bandwidth portion, the number of blind decoding candidates for the search space set within the second downlink bandwidth portion, or both, a radio resource control message, a broadcast message, or a multicast message.

[0381] Sample 54: A method for wireless communication at a network entity, comprising: transmitting one or more control messages, the one or more control messages indicating a configuration for: a first downlink bandwidth portion associated with a first operating mode of the UE, a second downlink bandwidth portion associated with a second operating mode of the UE, a first set of control resources within the first downlink bandwidth portion, and a second set of control resources within the second downlink bandwidth portion, wherein at least a portion of the configuration corresponds to a capability of the UE; transmitting a first set of messages via the first set of control resources within the first downlink bandwidth portion according to the configuration and at least in part based on the capability of the UE; and transmitting a second set of messages via the second set of control resources within the second downlink bandwidth portion according to the configuration and at least in part based on the capability of the UE.

[0382] State 55: The method according to State 54 also includes: determining the number of control resources in the second downlink bandwidth portion based at least in part on the number of control resources in the first downlink bandwidth portion; and sending an indication to the UE regarding the number of control resources in the second downlink bandwidth portion.

[0383] State 56: The method according to any one of states 54 to 55 also includes: determining the number of control resources in the second downlink bandwidth portion based at least in part on the number of control resources in the first downlink bandwidth portion and the sum of control resources in different downlink bandwidth portions of the UE; and sending an indication to the UE of the number of control resources in the second downlink bandwidth portion.

[0384] Version 57: The method according to any one of versions 54 to 56 also includes: determining the number of search space sets in the second downlink bandwidth portion based at least in part on the number of search space sets in the first downlink bandwidth portion, the sum of search space sets in different downlink bandwidth portions of the UE, and a threshold number of search space sets related to the UE's ability to connect to the network entity; and sending an indication to the UE regarding the number of control resources in the second downlink bandwidth portion.

[0385] Format 58: The method according to any one of formats 54 to 57, wherein sending the one or more control messages includes: sending a control signal transmission indicating one or both of a first set of parameters related to the first downlink bandwidth portion or a second set of parameters related to the second downlink bandwidth portion, the first set of parameters including bandwidth associated with the first downlink bandwidth portion, initial physical resource block location, digital scheme or a combination thereof, and the second set of parameters including bandwidth associated with the second downlink bandwidth portion, initial physical resource block location, digital scheme or a combination thereof, wherein the first set of parameters is different from the second set of parameters.

[0386] State 59: The method according to any one of states 54 to 58, wherein sending the one or more control messages includes: sending a master information block to the UE indicating the configuration for the first downlink bandwidth portion; and sending the UE a system information block, a dedicated radio resource control message, a multicast message, or a broadcast message indicating the configuration for the second downlink bandwidth portion.

[0387] State 60: The method according to any one of states 54 to 59, wherein the first operating mode and the second operating mode correspond to the radio resource control idle state or radio resource control inactive state of the UE; and, the first set of control resources in the first downlink bandwidth portion and the second set of control resources in the second downlink bandwidth portion include a common search space set.

[0388] State 61: The method according to any one of states 54 to 59, wherein the first operating mode and the second operating mode correspond to the radio resource control inactive state or radio resource control connected state of the UE; and, the first set of control resources in the first downlink bandwidth portion and the second set of control resources in the second downlink bandwidth portion include a UE-specific search space set, a common search space set, or both.

[0389] State 62: The method according to any one of states 54 to 61, wherein the first downlink bandwidth portion and the second downlink bandwidth portion correspond to different frequency ranges.

[0390] State 63: The method according to any one of states 54 to 62, wherein the first downlink bandwidth portion includes a first common search space configured for a cell selection procedure or cell reselection procedure of a UE in a radio resource control idle state or a radio resource control inactive state; and the second downlink bandwidth portion includes at least a second common search space configured for a random access procedure or paging operation of a UE in a radio resource control idle state or a radio resource control inactive state.

[0391] State 64: The method according to any one of states 54 to 63, wherein the first downlink bandwidth portion includes one or more common search spaces configured for system information retrieval procedures, system information update procedures, mobility procedures, or paging operations of a UE in a radio resource control idle state or radio resource control inactive state.

[0392] State 65: The method according to any one of states 54 to 64, wherein sending the one or more control messages includes: sending a system information block at least in part based on the capabilities of the UE, the system information block indicating one or more of an aggregation level, monitoring period, or monitoring timing configuration for a common search space set within the second downlink bandwidth portion.

[0393] State 66: The method according to any one of states 54 to 65 also includes: transmitting from the network entity a cell-defined synchronization signal block, system information message, paging operation message, random access message, or a combination thereof via the first set of control resources within the first downlink bandwidth portion associated with the first operating mode of the UE.

[0394] State 67: The method according to any one of states 54 to 66, wherein sending the one or more control messages includes: sending a system information block, the system information block indicating a first downlink control information size alignment for entity downlink control channel messages in the search space set of the first downlink bandwidth portion, a second downlink control information size alignment for entity downlink control channel messages in the search space set of the second downlink bandwidth portion, or both.

[0395] State 68: The method according to any one of states 54 to 67 also includes: transmitting one or more of random access messages, system information messages, multicast messages, broadcast messages, paging operation messages, small data transmissions, or non-cell-defined synchronization signal blocks via the second set of control resources within the second downlink bandwidth portion.

[0396] State 69: The method according to any one of states 54 to 68, wherein sending the one or more control messages includes: sending a control signal transmission indicating the number of physical resource blocks within the second downlink bandwidth portion, wherein the number of physical resource blocks is at least partially based on the control channel element aggregation level of the control resource set within the second downlink bandwidth portion, the duration of the control resource set within the second downlink bandwidth portion, the total number of control resource sets within the second downlink bandwidth portion, the radio resource control state of the UE, or a combination thereof.

[0397] State 70: The method according to any one of states 54 to 69, wherein sending the one or more control messages includes sending one or more of the following: a control channel element aggregation level indicating the search space set within the second downlink bandwidth portion, the number of blind decoding candidates for the search space set within the second downlink bandwidth portion, or both, a system information message, a radio resource control message, a broadcast message, or a multicast message.

[0398] Sample 71: A method for wireless communication at a UE, comprising: receiving one or more control messages from a network entity, the one or more control messages indicating a configuration for: a first downlink bandwidth portion associated with a first operating mode of the UE, a second downlink bandwidth portion associated with a second operating mode of the UE, a first set of resources within the first downlink bandwidth portion, and a second set of resources within the second downlink bandwidth portion, wherein at least a portion of the configuration corresponds to a capability of the UE; the UE, in the first operating mode, receiving one or more messages via the first set of resources within the first downlink bandwidth portion according to the configuration and at least in part based on the capability of the UE; and the UE, in the second operating mode, receiving one or both of a system information message or a public warning system message via the second set of resources within the second downlink bandwidth portion according to the configuration and at least in part based on the capability of the UE.

[0399] State 72: The method according to State 71 also includes: performing a random access procedure with the network entity via a second set of resources within the second downlink bandwidth portion.

[0400] Version 73: According to the method of version 72, receiving one or both of the system information message or the public warning system message includes: receiving a random access message from the network entity via the second set of resources within the second downlink bandwidth portion, according to the random access procedure, the random access message indicating one or both of the system information message or the public warning system message.

[0401] State 74: The method according to any one of states 71 to 73, wherein receiving one or both of the system information message or the public warning system message comprises: receiving, at least in part, a random access message from the network entity via the second set of resources within the second downlink bandwidth portion, based on the identification that the second downlink bandwidth portion does not include a public search space configured for paging operations, the random access message indicating one or both of the system information message or the public warning system message.

[0402] Version 75: According to the method of Version 71, receiving one or both of the system information message or the public warning system message includes: at least in part based on identifying that the second downlink bandwidth portion includes a public search space configured for paging operations, receiving a paging operation message from the network entity via the second set of resources within the second downlink bandwidth portion, the paging operation message indicating one or both of the system information message or the public warning system message.

[0403] Version 76: According to the method of Version 71, receiving one or both of the system information message or the public warning system message includes: receiving a paging operation message from the network entity via the second set of resources within the second downlink bandwidth portion, the paging operation message being scheduled from the downlink small data transmission of the network entity; and monitoring the second set of resources within the second downlink bandwidth portion based on the paging operation message to obtain the downlink small data transmission from the network entity, the downlink small data transmission indicating one or both of the system information message or the public warning system message.

[0404] Version 77: According to the method of Version 71, receiving one or both of the system information message or the public warning system message includes: receiving entity downlink control channel transmission from the network entity via the second set of resources within the second downlink bandwidth portion, the entity downlink control channel transmission scheduling broadcast or multicast entity downlink shared channel transmission from the network entity; and monitoring the second set of resources based on the entity downlink control channel transmission to obtain the broadcast or multicast entity downlink shared channel transmission from the network entity, the broadcast or multicast entity downlink shared channel transmission indicating one or both of the system information message or the public warning system message.

[0405] Sample 78: A method for wireless communication at a network entity, comprising: transmitting one or more control messages, the one or more control messages indicating a configuration for: a first downlink bandwidth portion associated with a first operating mode of a UE, a second downlink bandwidth portion associated with a second operating mode of the UE, a first set of resources within the first downlink bandwidth portion, and a second set of resources within the second downlink bandwidth portion, wherein at least a portion of the configuration corresponds to a capability of the UE; transmitting one or more messages via the first set of resources within the first downlink bandwidth portion according to the configuration and at least in part based on the capability of the UE; and transmitting one or both of a system information message or a public warning system message via the second set of resources within the second downlink bandwidth portion according to the configuration and at least in part based on the capability of the UE.

[0406] State 79: The method according to State 78 also includes: performing a random access procedure with the UE via a second set of resources within the second downlink bandwidth portion.

[0407] State 80: According to the method of State 79, sending one or both of the system information message or the public warning system message includes: according to the random access procedure, sending a random access message to the UE via the second set of resources within the second downlink bandwidth portion, the random access message indicating one or both of the system information message or the public warning system message.

[0408] State 81: The method according to any one of states 78 to 80, wherein sending one or both of the system information message or the public warning system message comprises: at least in part based on identifying that the second downlink bandwidth portion does not include a public search space configured for paging operations, sending a random access message to the UE via the second set of resources within the second downlink bandwidth portion, the random access message indicating one or both of the system information message or the public warning system message.

[0409] Version 82: According to the method of Version 78, sending one or both of the system information message and the public warning system message includes: at least in part based on identifying that the second downlink bandwidth portion includes a public search space configured for paging operations, sending a paging operation message to the UE via the second set of resources within the second downlink bandwidth portion, the paging operation message indicating one or both of the system information message and the public warning system message.

[0410] Version 83: According to the method of Version 78, sending one or both of the system information message and the public warning system message includes: sending a paging operation message to the UE via the second set of resources within the second downlink bandwidth portion, the paging operation message being scheduled from the downlink small data transmission of the network entity; and, according to the paging operation message, sending the downlink small data transmission via the second set of resources, the downlink small data transmission indicating one or both of the system information message and the public warning system message.

[0411] Version 84: According to the method of Version 78, sending one or both of the system information message and the public warning system message includes: sending an entity downlink control channel transmission to the UE via the second set of resources within the second downlink bandwidth portion, the entity downlink control channel transmission being scheduled from a broadcast or multicast entity downlink shared channel transmission of the network entity; and, according to the entity downlink control channel transmission, sending the broadcast or multicast entity downlink shared channel transmission via the second set of resources, the broadcast or multicast entity downlink shared channel transmission indicating one or both of the system information message and the public warning system message.

[0412] Sample 85: An apparatus for wireless communication at a UE, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to perform the method according to any one of Samples 35 to 53.

[0413] State 86: An apparatus for wireless communication at a UE, comprising: at least one unit for performing the method according to any one of states 35 to 53.

[0414] Sample 87: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by at least one processor to perform the method according to any one of Samples 35 to 53.

[0415] Sample 88: An apparatus for wireless communication at a network entity, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to perform the method according to any one of Samples 54 to 70.

[0416] Sample 89: An apparatus for wireless communication at a network entity, comprising: at least one unit for performing the method according to any one of Samples 54 to 70.

[0417] Sample 90: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code including instructions executable by at least one processor to perform the method according to any one of Samples 54 to 70.

[0418] Sample 91: An apparatus for wireless communication at a UE, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to perform the method according to any one of Samples 71 to 77.

[0419] State 92: An apparatus for wireless communication at a UE, comprising: at least one unit for performing the method according to any one of states 71 to 77.

[0420] Sample 93: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by at least one processor to perform the method according to any one of Samples 71 to 77.

[0421] Sample 94: An apparatus for wireless communication at a network entity, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to perform the method according to any one of Samples 78 to 84.

[0422] Sample 95: An apparatus for wireless communication at a network entity, comprising: at least one unit for performing the method according to any one of Samples 78 to 84.

[0423] Sample 96: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code including instructions executable by at least one processor to perform the method according to any one of Samples 78 to 84.

[0424] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, variants from two or more methods can be combined.

[0425] While various forms of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the technologies described herein apply beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described technologies can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein (including future systems and radio technologies).

[0426] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0427] The various illustrative blocks and components described in connection with this disclosure can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, GPU, FPGA or other programmable logic device, individual gate or transistor logic, individual hardware component, 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 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, a combination of one or more microprocessors with a DSP core, or any other such configuration).

[0428] The functionality described herein can be implemented using hardware, software executed by at least one processor, or any combination thereof. Software should be interpreted broadly as instructions, instruction sets, code, code fragments, program code, program, subprogram, software module, application, software application, software suite, commonality, subcommonality, object, executable file, executable thread, program, or function, whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms. If implemented using software executed by at least one processor, the functionality can be stored as one or more instructions or code on or transmitted via a computer-readable medium. Other examples and implementations are within the scope of this document and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software, hardware, hardwired, or any combination of these items executed by at least one processor. Features implementing the functionality can also be located at various physical locations, including being distributed such that different parts of the functionality are implemented at different physical locations.

[0429] Computer-readable media includes both non-transitory computer storage media and communication media, with communication media including any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media can be any available media that can be accessed by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electronically erasable programmable ROM (EEPROM), flash memory, phase-change memory, compressed optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to carry or store desired units of program code in the form of instructions or data structures, and any other non-transitory media that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, magnetic disks and optical disks include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where magnetic disks typically copy data magnetically, while optical discs use lasers to optically copy data. The combination of the above is also included within the scope of computer-readable media.

[0430] As used herein (including in a request), the word "or" as used in a list of entries (e.g., a list of entries ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (e.g., A and B and C). Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, without departing from the scope of this document, an instance step described as "based on condition A" could be based on both condition A and condition B. In other words, as used herein, the phrase "based on" should be interpreted in the same way as the phrase "at least partially based on". As used herein, when the term "and / or" is used in a list of two or more entries, it means using any one of the listed entries, or any combination of two or more of the listed entries. For example, if a composite is described as containing components A, B and / or C, then the composite may contain only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B and C.

[0431] The terms "decision," "judgment," "identification," or "recognition" encompass a wide range of actions. Therefore, "decision" or "identification" can include calculation, operation, processing, deduction, research, querying (e.g., via a lookup table, database, or other data structure), or assertion. Furthermore, "decision" or "identification" can also include receiving (e.g., receiving information or signal transmissions, such as receiving signal transmissions used for decision-making or signal transmissions used for identification) or accessing (e.g., accessing data in memory or accessing signals). Additionally, "decision" or "identification" can also include parsing, selecting, choosing, creating, and other similar actions.

[0432] In the accompanying drawings, similar parts or features have the same element symbols. Furthermore, parts of the same type can be distinguished by adding a dashed line after the element symbol and a second mark to differentiate similar parts. If only the first element symbol is used in the specification, the description applies to any similar part having the same first element symbol, regardless of any subsequent element symbols.

[0433] This document describes exemplary configurations with reference to the accompanying drawings, but these do not represent all possible instances, nor all instances falling within the scope of protection of the claims. As used herein, the term "exemplary" means "used as an example, illustration, or description," but does not imply "better" or "more advantageous" than other instances. Specific details are included to provide a thorough understanding of the described techniques. However, these techniques can be implemented without using these specific details. In some instances, well-known structures and devices are illustrated in block diagram form to avoid obscuring the concepts of the described instances.

[0434] The above description is intended to enable anyone skilled in the art to implement or use the content of this invention. Various modifications to the content of this invention will be apparent to those skilled in the art, and the overall principles defined herein can be applied to other variations without departing from the scope of protection of this invention. Therefore, the content of this invention is not limited to the examples and designs described herein, but is consistent with the broadest scope of the principles and novel features disclosed herein.

[0435] 100: Wireless Communication System 105: Base 105-a: Base station 105-b: Base Station 105-c: Base Station 110: Geographical coverage area 110-a: Geographical coverage area 115:UE 115-a:UE 115-b:UE 115-c:UE 120: Backload Link 125: Communication Link 130: Core Network 135: Device-to-device (D2D) communication link 140: Access to network entities 145: Access to network transmission entities 150: IP Service 200: Wireless Communication System 205-a: Control Messages 205-b: Control Messages 210-a:CD-SSB 210-b:NCD-SSB 215: PWS Notification 220: System Information Update 300: Resource Image 301: Resource Image 305:CD-SSB 310:CORESET#0 315:CSS 320:CSS 325: Initial Downlink BWP 330: Entity Uplink Shared Channel (PUCCH) Resource 335: Initial Uplink BWP 340: Random Access Channel (RACH) Timing 345:CD-SSB 350:CORESET#0 355: CORESET and CSS 360:NCD-SSB 365: CORESET and CSS 370: Initial Downlink BWP 375:PUCCH Resources 380: Initial Uplink BWP 400: Program Flow 405: Procedure 410: Program 415: Program 420: Program 425: Program 430: Program 435: Program 500: Program Flow 505: Procedure 510: Program 515: Program 520: Program 525: Program 530: Program 535: Program 540: Program 600: Block Diagram 605: Equipment 610: Receiver 615: Launcher 620: Communication Manager 700: Block Diagram 705: Equipment 710: Receiver 715: Launcher 720: Communication Manager 725: Control Message Receiver 730: First downlink BWP monitoring component 735: Second Downlink BWP Monitoring Component 740: Message receiving component 800: Block Diagram 820: Communication Manager 825: Control Message Receiver 830: First downlink BWP monitoring component 835: Second Downlink BWP Monitoring Component 840: Message Receiving Component 845: Resources determine components 850: BWP Switching Component 855: Program Execution Unit 860: Operation Mode Component 865: Control Resource Component 870: Random Access Execution Unit 900: System 905: Equipment 910: Input / Output (I / O) Controller 915: Transceiver 920: Communication Manager 925: Antenna 930: Memory 935: Code 940: Processor 945: Busbar 1000: Block Diagram 1005: Equipment 1010: Receiver 1015: Launcher 1020: Communication Manager 1100: Block Diagram 1105: Equipment 1110: Receiver 1115: Transmitter 1120: Communication Manager 1125: Control Message Transmitter 1130: First downlink BWP transmission component 1135: Second downlink BWP transmission component 1200: Block Diagram 1220: Communication Manager 1225: Control Message Transmitter 1230: First downlink BWP transmission component 1235: Second downlink BWP transmission component 1240: Resources determine components 1245: Operation Mode Component 1250: Control Resource Component 1255: Message transmission component 1260: Random Access Component 1300: System 1305: Equipment 1310: Network Communication Manager 1315: Transceiver 1320: Communication Manager 1325: Antenna 1330: Memory 1335: Code 1340: Processor 1345: Inter-station Communication Manager 1350: Busbar 1400: Method 1405: Square 1410: Square 1415: Square 1500: Method 1505: Square 1510: Square 1515: Square 1600: Method 1605: Square 1610: Square 1615: Square 1700: Method 1705: Square 1710: Square 1715: Square 1800: Method 1805: Square 1810: Square 1815: Square 1900: Method 1905: Square 1910: Square 1915: Square

[0436] Domestic storage information (please note in order of storage institution, date, and number) none Overseas storage information (please note in the order of storage country, institution, date, and number) none

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: At least one processor; and memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to perform the following operations: receiving one or more control messages indicating a first configuration for a first downlink bandwidth portion and a second configuration for a second downlink bandwidth portion specific to a degraded UE, the first configuration identifying a first set of resources within the first downlink bandwidth portion and the second configuration identifying a second set of resources within the second downlink bandwidth portion; monitoring the first set of resources within the first downlink bandwidth portion based on the first configuration, a radio resource control state of the UE, and a capability of the UE; switching from the first downlink bandwidth portion to the second downlink bandwidth portion after transitioning from a first operating mode associated with the first downlink bandwidth portion to a second operating mode associated with the second downlink bandwidth portion; and monitoring the second set of resources within the second downlink bandwidth portion specific to a degraded UE based on the second configuration, the radio resource control state of the UE, and the capability of the UE.

2. The apparatus according to claim 1, wherein the instructions may further be executed by the at least one processor to cause the UE to: determine, at least in part based on the first configuration, a first set of parameters for the first downlink bandwidth portion, the first set of parameters including one or more of the following: a cyclic prefix of a control resource set within the first downlink bandwidth portion, a primary carrier spacing, a number of resource blocks, or a number of symbols; and determine, at least in part based on the second configuration, a second set of parameters for the second downlink bandwidth portion specific to a degraded UE, the second set of parameters including one or more of the following: a bandwidth of the second downlink bandwidth portion, a first physical resource block, or a primary carrier spacing.

3. The apparatus according to claim 1, wherein, in order to monitor the first set of resources, the instructions can be executed by the at least one processor to enable the UE to: receive at least one message of a paging operation via a common search space within the first downlink bandwidth portion, according to the first configuration and the capability of the UE, wherein the first downlink bandwidth portion includes a control resource set having an index of zero (0).

4. The apparatus according to claim 1, wherein, in order to monitor the second set of resources, the instructions may be executed by the at least one processor to cause the UE to: receive one or more random access messages via the second set of resources within the second downlink bandwidth portion of the de-capable UE, depending on the second configuration, the radio resource control state of the UE and the capability of the UE, wherein the second downlink bandwidth portion does not include a control resource set having an index of zero (0).

5. The apparatus according to claim 1, wherein the instructions may further be executed by the at least one processor to cause the UE to: receive, via one or more physical downlink control channel resources within the first downlink bandwidth portion, a downlink message that schedules the transmission of a first system information block within the first downlink bandwidth portion, wherein the first system information block indicates the second configuration of the second downlink bandwidth portion specific to the degraded UE.

6. The apparatus according to claim 1, wherein, in order to monitor the first set of resources, the instructions can be executed by the at least one processor to cause the UE to: receive one or more cell-defined synchronization signal blocks via the first set of resources within the first downlink bandwidth portion; and perform a cell selection procedure based at least in part on a measurement of the one or more cell-defined synchronization signal blocks.

7. The apparatus according to claim 1, wherein, in order to receive the one or more control messages, the instructions may be executed by the at least one processor to cause the UE to: receive an indication of a search space configured for downlink small data transmissions in the first downlink bandwidth portion or the second downlink bandwidth portion; and monitor the search space for downlink small data transmissions according to the indication.

8. The apparatus according to claim 1, wherein, in order to receive the one or more control messages, the instructions may be executed by the at least one processor to cause the UE to: receive a main information block indicating the first configuration of the first downlink bandwidth portion; and receive a system information block indicating the second configuration of the second downlink bandwidth portion.

9. The apparatus according to claim 1, wherein the instructions may further be executed by the at least one processor to cause the UE to: receive one or more of the following via the first downlink bandwidth portion or the second downlink bandwidth portion specific to the degraded UE: a system information message, a paging operation message, a random access message, a small data transmission, a broadcast message, a public warning system notification, or a non-cell-defined synchronization signal block.

10. The apparatus according to claim 1, wherein the instructions may be further executed by the at least one processor to cause the UE to: receive one or more of a cell-defined synchronization signal block, a system information message, a paging operation message, or a random access message via the first set of resources within the first downlink bandwidth portion, based on the first configuration, the radio resource control state of the UE, and the capability of the UE.

11. The apparatus according to claim 1, wherein the instructions may be further executed by the at least one processor to cause the UE to: transmit one or more of the following via one or more resources within an uplink bandwidth portion configured for the UE: a small data transmission, a random access message, UE mobility information, or a request for on-demand system information.

12. The apparatus according to claim 1, wherein the instructions may be further executed by the at least one processor to enable the UE to: transmit a request for on-demand system information via one or more resources within an uplink bandwidth portion configured for the UE; and receive the on-demand system information via the first set of resources within the first downlink bandwidth portion or the second set of resources within the second downlink bandwidth portion.

13. The apparatus according to request item 12, wherein the UE sends the request for on-demand system information according to a random access procedure.

14. The apparatus according to claim 1, wherein the second downlink bandwidth portion specific to the degraded capability UE has a bandwidth less than or equal to a maximum downlink bandwidth supported by the UE.

15. The apparatus according to claim 1, wherein the one or more control messages include a main information block, a system information block, a radio resource control message, or a combination thereof.

16. The apparatus according to claim 1, wherein the first downlink bandwidth portion is used to receive a cell-defined synchronization signal block.

17. The apparatus according to claim 1, wherein: The UE is a de-capacitated UE; and the radio resource control state of the UE includes an idle radio resource control state or an inactive radio resource control state.

18. The apparatus according to claim 1, wherein: The first downlink bandwidth portion includes a first set of common search spaces configured for cell selection procedures or cell reselection procedures; and the second downlink bandwidth portion includes a second set of common search spaces configured for random access procedures or paging operations.

19. The apparatus according to claim 1, wherein: The first downlink bandwidth portion includes one or more common search spaces configured for system information retrieval or paging operations.

20. The apparatus according to claim 1, wherein the instructions may further be executed by the at least one processor to cause the UE to: determine a number of control resource sets in the second downlink bandwidth portion based at least in part on a number of control resource sets in the first downlink bandwidth portion, a sum of control resource sets in other downlink bandwidth portions of the UE, a threshold number of control resource sets supported by the UE, or a combination thereof.

21. The apparatus according to claim 1, wherein the instructions may further be executed by the at least one processor to cause the UE to: determine a number of search space sets in the second downlink bandwidth portion based at least in part on a number of search space sets in the first downlink bandwidth portion, a sum of search space sets in other downlink bandwidth portions of the UE, a threshold number of search space sets supported by the UE, or a combination thereof.

22. The apparatus according to claim 1, wherein, in order to receive the one or more control messages, the instructions may be executed by the at least one processor to cause the UE to: receive system information indicating at least one of an aggregation level, a monitoring periodicity, or a monitoring timing configuration for a common search space set within the second downlink bandwidth portion specific to the degraded UE.

23. The apparatus according to claim 1, wherein, in order to receive the one or more control messages, the instructions may be executed by the at least one processor to cause the UE to: receive a system information block, the system information block indicating: a first downlink control information size alignment of physical downlink control channel messages centrally scheduled in the search space of the first downlink bandwidth portion, a second downlink control information size alignment of physical downlink control channel messages centrally scheduled in the search space of the second downlink bandwidth portion, or both.

24. The apparatus according to claim 1, wherein, in order to receive the one or more control messages, the instructions may be executed by the at least one processor to cause the UE to: receive an indication of a number of physical resource blocks within the second downlink bandwidth portion specific to the degraded UE, wherein the number of physical resource blocks is at least partially based on a control channel element aggregation level of a control resource set within the second downlink bandwidth portion, a duration of a control resource set within the second downlink bandwidth portion, a total number of control resource sets within the second downlink bandwidth portion, the radio resource control state of the UE, or a combination thereof.

25. The apparatus according to claim 1, wherein, in order to receive the one or more control messages, the instructions may be executed by the at least one processor to cause the UE to: receive one or more of the following: a system information message, a radio resource control message, a broadcast message, or a multicast message indicating: a control channel element aggregation level of a search space set within the second downlink bandwidth portion, a number of blind decoding candidates of the search space set within the second downlink bandwidth portion, or both.

26. An apparatus for wireless communication at a network entity, comprising: At least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to perform the following operations: sending one or more control messages indicating a first configuration for a first downlink bandwidth portion and a second configuration for a second downlink bandwidth portion specific to a degraded UE, wherein the first configuration identifies a first set of resources within the first downlink bandwidth portion and the second configuration identifies a second set of resources within the second downlink bandwidth portion; According to the first configuration indicated by the one or more control messages, a first downlink message is sent to a degraded UE via the first set of resources within the first downlink bandwidth portion; and based on the degraded UE switching from the first downlink bandwidth portion to the second downlink bandwidth portion after switching from a first operating mode associated with the first downlink bandwidth portion to a second operating mode associated with the second downlink bandwidth portion, the network entity sends a second downlink message to the degraded UE via the second set of resources within the second downlink bandwidth portion specific to the degraded UE according to the second configuration indicated by the one or more control messages.

27. The apparatus according to claim 26, wherein, in order to transmit the first downlink message via the first set of resources, the instructions may be executed by the at least one processor to cause the network entity to: transmit at least one message of a paging operation to the degraded UE via a common search space within the first downlink bandwidth portion, according to the first configuration, wherein the first downlink bandwidth portion includes a control resource set having an index of zero (0).

28. A method for wireless communication at a user equipment (UE), comprising the following steps: The system receives one or more control messages indicating a first configuration for a first downlink bandwidth portion and a second configuration for a second downlink bandwidth portion specific to a degraded UE, wherein the first configuration identifies a first set of resources within the first downlink bandwidth portion and the second configuration identifies a second set of resources within the second downlink bandwidth portion; monitors the first set of resources within the first downlink bandwidth portion based on the first configuration, a radio resource control state of the UE, and a capability of the UE; switches from the first downlink bandwidth portion to the second downlink bandwidth portion after transitioning from a first operating mode associated with the first downlink bandwidth portion to a second operating mode associated with the second downlink bandwidth portion; and monitors the second set of resources within the second downlink bandwidth portion specific to the degraded UE based on the second configuration, the radio resource control state of the UE, and the capability of the UE.

29. A method for wireless communication at a network entity, comprising the following steps: Sending one or more control messages, the one or more control messages indicating a first configuration for a first downlink bandwidth portion and a second configuration for a second downlink bandwidth portion specific to a degraded UE, wherein the first configuration identifies a first set of resources within the first downlink bandwidth portion and the second configuration identifies a second set of resources within the second downlink bandwidth portion; sending a first downlink message to a degraded UE via the first set of resources within the first downlink bandwidth portion according to the first configuration indicated by the one or more control messages; and switching from the first downlink bandwidth portion to the second downlink bandwidth portion based on the degraded UE switching from a first operating mode associated with the first downlink bandwidth portion to a second operating mode associated with the second downlink bandwidth portion, the method sending a second downlink message to the degraded UE via the second set of resources within the second downlink bandwidth portion specific to the degraded UE according to the second configuration indicated by the one or more control messages.

Images