REDUCED-CAPABILITY-SPECIFIC INITIAL BANDWIDTH PARTS

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may monitor a control channel configured within a reduced capability (RedCap)-specific initial downlink bandwidth part (BWP), wherein the UE is a RedCap UE operating in idle mode or inactive mode. The UE may receive at least one communication via the control channel. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for reduced-capability-specific initial bandwidth parts.

BACKGROUND

A wireless network may include one or more network nodes that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the network node to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the network node.

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include monitoring a control channel configured within a reduced capability (RedCap)-specific initial downlink bandwidth part (BWP), wherein the UE is a RedCap UE operating in idle mode or inactive mode. The method may include receiving at least one communication via the control channel.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting a first communication on a first control channel that corresponds to a non-RedCap-specific initial downlink BWP. The method may include transmitting a second communication on a second control channel that corresponds to a RedCap-specific initial downlink BWP.

Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to monitor a control channel configured within a RedCap-specific initial downlink BWP, wherein the UE is a RedCap UE operating in idle mode or inactive mode. The one or more processors may be configured to receive at least one communication via the control channel.

Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit a first communication on a first control channel configured within a non-RedCap-specific initial downlink BWP. The one or more processors may be configured to transmit a second communication on a second control channel configured within a RedCap-specific initial downlink BWP.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to monitor a control channel configured within a RedCap-specific initial downlink BWP, wherein the UE is a RedCap UE operating in idle mode or inactive mode. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive at least one communication via the control channel.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit a first communication on a first control channel configured within a non-RedCap-specific initial downlink BWP. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit a second communication on a second control channel configured within a RedCap-specific initial downlink BWP.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for monitoring a control channel configured within a RedCap-specific initial downlink BWP, wherein the UE is a RedCap UE operating in idle mode or inactive mode. The apparatus may include means for receiving at least one communication via the control channel.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a first communication on a first control channel configured within a non-RedCap-specific initial downlink BWP. The apparatus may include means for transmitting a second communication on a second control channel configured within a RedCap-specific initial downlink BWP.

DETAILED DESCRIPTION

FIG.1is a diagram illustrating an example of a wireless network100, in accordance with the present disclosure. The wireless network100may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network100may include one or more base stations110(shown as a BS110a,a BS110b,a BS110c,and a BS110d), a user equipment (UE)120or multiple UEs120(shown as a UE120a,a UE120b,a UE120c,a UE120d,and a UE120e), and/or other network entities. A base station110is an entity that communicates with UEs120. A base station110(sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and/or a transmission reception point (TRP). Each base station110may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a base station110and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.

As described herein, a network node, which also may be referred to as a “node” or a “wireless node,” may be a base station (e.g., base station110), a UE (e.g., UE120), a relay device, a network controller, an apparatus, a device, a computing system, one or more components of any of these, and/or another processing entity configured to perform one or more aspects of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station. A network node may be an aggregated base station and/or one or more components of a disaggregated base station. As an example, a first network node may be configured to communicate with a second network node or a third network node. The adjectives “first,” “second,” “third,” and so on are used for contextual distinction between two or more of the modified noun in connection with a discussion and are not meant to be absolute modifiers that apply only to a certain respective node throughout the entire document. For example, a network node may be referred to as a “first network node” in connection with one discussion and may be referred to as a “second network node” in connection with another discussion, or vice versa. Reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE being configured to receive information from a base station also discloses a first network node being configured to receive information from a second network node, “first network node” may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first one or more components, a first processing entity, or the like configured to receive the information from the second network; and “second network node” may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second one or more components, a second processing entity, or the like.

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may monitor a control channel configured within a reduced capability (RedCap)-specific initial downlink bandwidth part (BWP), wherein the UE is a RedCap UE operating in idle mode or inactive mode; and receive at least one communication via the control channel. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, a network node (e.g., the base station110) may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit a first communication on a first control channel configured within a non-RedCap-specific initial downlink BWP; and transmit a second communication on a second control channel configured within a RedCap-specific initial downlink BWP. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

FIG.2is a diagram illustrating an example200of a base station110in communication with a UE120in a wireless network100, in accordance with the present disclosure. The base station110may be equipped with a set of antennas234athrough234t,such as T antennas (T≥1). The UE120may be equipped with a set of antennas252athrough252r,such as R antennas (R≥1).

In some aspects, the UE includes means for monitoring a control channel configured within a RedCap-specific initial downlink BWP, wherein the UE is a RedCap UE operating in idle mode or inactive mode; and/or means for receiving at least one communication via the control channel. The means for the UE to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, the network node includes means for transmitting a first communication on a first control channel configured within a non-RedCap-specific initial downlink BWP; and/or means for transmitting a second communication on a second control channel configured within a RedCap-specific initial downlink BWP. The means for the network node to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

FIG.3is a diagram illustrating an example300of an O-RAN architecture, in accordance with the present disclosure. As shown inFIG.3, the O-RAN architecture may include a control unit (CU)310that communicates with a core network320via a backhaul link. Furthermore, the CU310may communicate with one or more DUs330via respective midhaul links. The DUs330may each communicate with one or more RUs340via respective fronthaul links, and the RUs340may each communicate with respective UEs120via radio frequency (RF) access links. The DUs330and the RUs340may also be referred to as O-RAN DUs (0-DUs)330and O-RAN RUs (O-RUs)340, respectively.

In some aspects, the DUs330and the RUs340may be implemented according to a functional split architecture in which functionality of a base station110(e.g., an eNB or a gNB) is provided by a DU330and one or more RUs340that communicate over a fronthaul link. Accordingly, as described herein, a base station110may include a DU330and one or more RUs340that may be co-located or geographically distributed. In some aspects, the DU330and the associated RU(s)340may communicate via a fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, to exchange non-real-time management information via an LLS management plane (LLS-M) interface, and/or to exchange user plane information via an LLS user plane (LLS-U) interface.

Accordingly, the DU330may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs340. For example, in some aspects, the DU330may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and/or modulation and demodulation) based at least in part on a lower layer functional split. Higher layer control functions, such as a packet data convergence protocol (PDCP), radio resource control (RRC), and/or service data adaptation protocol (SDAP), may be hosted by the CU310. The RU(s)340controlled by a DU330may correspond to logical nodes that host RF processing functions and low-PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and/or physical random access channel (PRACH) extraction and filtering) based at least in part on the lower layer functional split. Accordingly, in an O-RAN architecture, the RU(s)340handle all over the air (OTA) communication with a UE120, and real-time and non-real-time aspects of control and user plane communication with the RU(s)340are controlled by the corresponding DU330, which enables the DU(s)330and the CU310to be implemented in a cloud-based RAN architecture.

In some aspects, a network node may serve different UEs of different categories and/or different UEs that support different capabilities. For example, the network node may serve a first category of UEs that have a less advanced capability (e.g., a lower capability and/or a reduced capability) and a second category of UEs that have a more advanced capability (e.g., a higher capability). A UE of the first category may have a reduced feature set compared to UEs of the second category and may be referred to as a reduced-capability (RedCap) UE (which may be interchangeably referred to as a reduced-capacity UE, also having the acronym “RedCap”), a low tier UE, and/or an NR-Lite UE, among other examples. A UE of the second category may be an ultra-reliable low-latency communication (URLLC) device and/or an enhanced mobile broadband (eMBB) device and may have an advanced feature set compared to RedCap UEs. RedCap UEs may include wearable devices, IoT devices, sensors, cameras, and/or the like that are associated with a limited bandwidth, power capacity, and/or transmission range, among other examples. A UE of the second category may be referred to as a baseline UE, a high tier UE, an NR UE, and/or a premium UE, among other examples. In some aspects, a RedCap UE may have capabilities that satisfy requirements of a first wireless communication standard but not a second wireless communication standard, while a UE of the second category may have capabilities that satisfy requirements of the second wireless communication standard (and also the first wireless communication standard, in some cases).

For example, a RedCap UE of the first category may support a lower maximum MCS than a UE of the second category (e.g., quadrature phase shift keying (QPSK) or the like as compared to 256-quadrature amplitude modulation (QAM) or the like), may support a lower maximum transmit power than a UE of the second category, may have a less advanced beamforming capability than a UE of the second category (e.g., may not be capable of forming as many beams as a UE of the second category), may require a longer processing time than a UE of the second category, may include less hardware than a UE of the second category (e.g., fewer antennas, fewer transmit antennas, and/or fewer receive antennas), and/or may not be capable of communicating on as wide of a maximum BWP as a UE of the second category, among other examples. In some instances, the bandwidth, power capacity, computational capability, and/or transmission range of a RedCap UE may be limited or reduced relative to an eMBB UE (which may be referred to herein, interchangeably, as a “non-RedCap eMBB UE”). Similarly, a BWP, control channel, search space set, and/or bandwidth or other feature that is specific to, or otherwise dedicated for use with or by, a RedCap UE may be referred to as “RedCap-specific.” A BWP, control channel, search space set, and/or bandwidth or other feature that is specific to, otherwise dedicated for use with or by, a non-RedCap UE, and/or is not RedCap-specific, may be referred to as “Non-RedCap-specific.”

In some cases, idle mode and/or inactive mode procedures (e.g., initial access, paging, synchronization, and/or system information broadcasting, among other examples) can be performed by a network node and a UE in an initial downlink BWP. In some cases, because a RedCap UE may not have the capability to receive transmissions across the entire initial downlink BWP, the UE may miss communications, which may affect the ability of the UE to perform idle mode and/or inactive mode procedures, thereby negatively impacting network and/or device performance.

Aspects of techniques and apparatuses described herein facilitate providing for idle mode and/or inactive mode procedures for RedCap UEs use RedCap-specific initial downlink BWPs. In some aspects, a RedCap UE may monitor a control channel configured within a RedCap-specific initial downlink BWP. The RedCap UE may be operating in idle mode or inactive mode and may receive at least one communication via the control channel. As a result, aspects may facilitate enabling RedCap UEs to perform idle mode and/or inactive mode procedures using a RedCap-specific initial downlink BWP. Accordingly, some aspects of the disclosure may facilitate reducing the incidents of missed communications, thereby having a positive impact on network and/or device performance.

FIG.4is a diagram illustrating an example400associated with RedCap-specific initial downlink BWPs, in accordance with the present disclosure. As shown inFIG.4, a RedCap UE405and a network node410may communicate with one another. The network node410may communicate with a non-RedCap UE415as well. In some aspects, any number of RedCap UEs and/or non-RedCap UEs may communicate with the network node.

As shown by reference number420, the RedCap UE405may monitor a control channel corresponding to a RedCap-specific initial downlink BWP. The RedCap UE405may be operating in idle mode or inactive mode. As shown by reference number425, the RedCap UE405may receive at least one communication via the control channel. As shown by reference number430, which depicts frequency resources associated with a non-RedCap-specific initial downlink BWP435(e.g., a default initial downlink BWP) and a RedCap-specific initial downlink BWP440, the RedCap-specific initial downlink BWP440may have a narrower bandwidth than the non-RedCap-specific initial downlink BWP. In some aspects, the RedCap-specific initial downlink BWP440may be, or include, a RedCap specific initial downlink BWP and/or a RedCap-specific initial uplink BWP. Similarly, the non-RedCap-specific initial downlink BWP435may be, or include, a non-RedCap-specific initial downlink BWP and/or a non-RedCap-specific initial uplink BWP.

In some aspects, the control channel may include a paging control channel (PCCH). The RedCap UE405may monitor the PCCH periodically. The RedCap UE405may monitor the control channel (e.g., the PCCH) by monitoring a common search space (CSS) configured within the RedCap-specific initial downlink BWP440. The PCCH may be provided over the CSS, which may correspond to a control resource set (CORESET) #0445. In some aspects, as shown, the network node410may transmit, and the RedCap UE405may receive, a non-cell-defining synchronization signal block (SSB)450corresponding to the RedCap-specific initial downlink BWP. In some aspects, the RedCap-specific initial downlink BWP also may include one or more CSSs455of Type-0, Type-1, Type-2, and/or Type-3.

In some aspects, a broadcast control channel (BCCH) may be configured within the non-RedCap-specific initial downlink BWP435and/or the RedCap-specific initial downlink BWP440. For example, in some aspects, the BCCH may not be configured in the RedCap-specific initial downlink BWP440. In those cases, as shown by reference number460, the RedCap UE405may switch to the non-RedCap-specific initial downlink BWP435. For example, the RedCap UE405may switch to the non-RedCap-specific initial downlink BWP435to receive system information (SI). In some aspects, whenever there is an SI update, or the RedCap UE405requests on-demand SI (ODSI), the RedCap UE405may switch its active BWP to the non-RedCap-specific initial downlink BWP435to obtain SI. The SI may be transmitted using a system information block (SIB) and/or an SSB. A SIB may include an specified first SIB (e.g., a SIB1) and/or a master information block (MIB), among other examples. In some aspects, the bandwidth of the BCCH may be less than a maximum bandwidth that the RedCap UE405is capable of receiving.

In some aspects, the network node410may transmit, and the RedCap UE405may receive, the MIB and/or SSB over a BCCH configured within the RedCap-specific initial downlink BWP440. For example, the network node410may use a Type-0 CSS455to transmit the MIB and/or SSB. In some aspects, the network node410may duplicate the BCCH of the non-RedCap-Specific initial downlink BWP435in the RedCap-specific initial downlink BWP440. For example, in some aspects, the network node410may periodically transmit a MIB and an SIB1in the RedCap-specific initial downlink BWP440, as it does in the non-RedCap-Specific initial downlink BWP435. In some aspects, whenever ODSI is requested, regardless of whether this request is sent by a non-RedCap UE415in a non-RedCap-Specific initial downlink BWP435or by the RedCap UE in a RedCap-specific downlink BWP440, and/or if there is an SI update, the network node410may transmit the ODSI over a BCCH in both the non-RedCap-Specific initial downlink BWP435and the RedCap-specific downlink BWP440.

In some aspects, the network node410may separate BCCH operations in the non-RedCap-Specific initial downlink BWP435from BCCH operations in the RedCap-specific initial downlink BWP. For example, in some aspects, the network node410may transmit a MIB and a SIB (e.g., SIB1) periodically in both the non-RedCap-Specific initial downlink BWP435and the RedCap-specific initial downlink BWP440. In the non-RedCap-Specific initial downlink BWP435, the network node410and non-RedCap UE415may apply legacy procedures for SI delivery, including ODSI. If a change to SI is not applicable to any RedCap UEs405, the network node410may not transmit SIBs that indicate the changed SI in the RedCap-specific initial downlink BWP440, but may transmit the SIBs only in the non-RedCap-Specific initial downlink BWP435. Similarly, if the non-RedCap UE415transmits a request for ODSI, the network node410may transmit a responding SIB in the non-RedCap-Specific initial downlink BWP435, but not in the RedCap-specific initial downlink BWP440.

In some aspects, when there is an SI update and the update is only relevant to RedCap UEs405, the network node410may send a RedCap-specific short message in the RedCap-specific initial downlink BWP440to notify only the RedCap UEs405about the change. RedCap UEs405may also acquire new SI via the RedCap-specific initial downlink BWP440. For example, the network node410may transmit, and the RedCap UE405may receive, a RedCap-specific short message that indicates a RedCap-specific SI update.

In some aspects, the RedCap UE405may request ODSI via a random access channel (RACH) procedure in the RedCap-specific initial downlink BWP440. The RedCap UE405may transmit, and the network node410may receive, via a RACH procedure corresponding to the RedCap-specific initial downlink BWP, a request for ODSI. For example, in some aspects, the RedCap UE405may transmit the request via a PRACH transmission. The network node410may respond to the request by transmitting ODSI in the RedCap-specific initial downlink BWP440, but not in the non-RedCap-Specific initial downlink BWP435. In some aspects, the network node410may transmit, and the RedCap UE405may receive, an SIB corresponding to the RedCap-specific initial downlink BWP440, where the SIB is associated with one or more RedCap-specific transmission parameters. The RedCap-specific transmission parameters may be different than transmission parameters used in the non-RedCap-Specific initial downlink BWP435and may be configured to better support the reduced receiving capabilities of the RedCap UEs405. For example, the transmission parameters may include transmission power, bandwidth, and/or MCS, among other examples.

In some aspects, the network node410may transmit SI updates to the RedCap UE405using dedicated signaling (UE-specific signaling). When there is an SI update and the update is relevant to RedCap UEs405, the network node410may transmit the updated SIB(s) (e.g., including MIB and/or SIB1) to RRC connected RedCap UEs405via their respective physical downlink shared channels (PDSCHs) by dedicated signaling. For example, in some aspects, the RedCap UE405may perform, via the RedCap-specific initial downlink BWP440, an initial access procedure to enter an RRC connected state. The network node410may transmit, and the RedCap UE405may receive, a UE-specific signal corresponding to a PDSCH associated with the RedCap UE405. The UE-specific signal may include an updated SIB.

In some aspects, the network node410may indicate in an SIB (e.g., an SIB1) in the non-RedCap-Specific initial downlink BWP435which mode RedCap UEs405should use to obtain SI. For example, the network node410may transmit, and the RedCap UE405may receive, an SIB corresponding to the non-RedCap-Specific initial downlink BWP435. The SIB may indicate a mode that the UE is to use to obtain SI.

In some aspects, radio resource management (RRM) measurements performed by the RedCap UE405associated with serving cells and/or neighbor cells may be based on SSBs transmitted in the RedCap-specific initial downlink BWP440, and not SSBs transmitted in the non-RedCap-Specific initial downlink BWP435. For example, in some aspects, the network node410may transmit, and the RedCap UE405may receive, at least one SSB corresponding to the RedCap-specific initial downlink BWP440. The RedCap UE405may obtain one or more RRM measurements based at least in part on the at least one SSB. Cell barring indications and unified access control (UAC) indications may be transmitted in the non-RedCap-Specific initial downlink BWP435. For example, the RedCap UE405may switch to the non-RedCap-Specific initial downlink BWP435and may receive, from the network node410, at least one of a cell barring indication or a UAC indication via the non-RedCap-Specific initial downlink BWP435.

As shown by reference number470, in some aspects, the RedCap-specific initial downlink BWP440may include only a random access search space (“ra-searchspace”)475. For example, in some aspects, the RedCap UE405may monitor a random access search space475configured within the RedCap-specific initial downlink BWP440, where the RedCap-specific initial downlink BWP440contains only one search space — the random access search space475. As a result, the RedCap UE405may still camp in the non-RedCap-Specific initial downlink BWP435to perform most of the idle-mode procedures (e.g., except RACH messages subsequent to the PRACH message). For example, the RedCap UE405may receive cell barring and UAC indications in an SIB1transmitted in the non-RedCap-Specific initial downlink BWP435. The RedCap UE405may monitor SI and paging channels in the non-RedCap-Specific initial downlink BWP435, and/or the RedCap UE405may perform RRM measurements on a cell-defining SSB465transmitted within the non-RedCap-Specific initial downlink BWP435.

When the RedCap UE405performs a RACH procedure, the RedCap UE405may first switch to the RedCap-specific initial downlink BWP440. For example, the RedCap UE405may transmit RACH messages (e.g., Msg1, MsgA, and/or Msg3) in a RedCap-specific initial downlink BWP and may receive RACH messages (e.g., Msg2, Msg B, and/or Msg4) in the random access search space475configured in the RedCap-specific initial downlink BWP440. For example, in some aspects, the RedCap UE405may switch from the non-RedCap-Specific initial downlink BWP435to the RedCap-specific initial downlink BWP440and may perform a RACH procedure corresponding to the RedCap-specific initial downlink BWP440.

As shown by reference number480, in some aspects, the RedCap-specific initial downlink BWP440may share a CORESET #0and/or SSBs with the non-RedCap-Specific initial downlink BWP435. Similarly, the RedCap-specific BWP440may share the same PRACH as the non-RedCap-Specific initial downlink BWP435. In some aspects, for example, the RedCap-specific initial downlink BWP440shares a CSS with the non-RedCap-Specific initial downlink BWP435.

FIG.5is a diagram illustrating an example process500performed, for example, by a UE, in accordance with the present disclosure. Example process500is an example where the UE (e.g., UE120) performs operations associated with RedCap-specific initial downlink BWPs.

As shown inFIG.5, in some aspects, process500may include monitoring a control channel configured within a RedCap-specific initial downlink BWP, wherein the UE is a RedCap UE operating in idle mode or inactive mode (block510). For example, the UE (e.g., using communication manager140and/or reception component702, depicted inFIG.7) may monitor a control channel corresponding to a RedCap-specific initial downlink BWP, wherein the UE is a RedCap UE operating in idle mode or inactive mode, as described above.

As further shown inFIG.5, in some aspects, process500may include receiving at least one communication via the control channel (block520). For example, the UE (e.g., using communication manager140and/or reception component702, depicted inFIG.7) may receive at least one communication via the control channel, as described above.

In a first aspect, the control channel comprises a PCCH. In a second aspect, alone or in combination with the first aspect, monitoring the control channel comprises monitoring a CSS configured within the RedCap-specific initial downlink BWP. In a third aspect, alone or in combination with one or more of the first and second aspects, process500includes receiving a non-cell-defining SSB corresponding to the RedCap-specific initial downlink BWP.

In a fourth aspect, alone or in combination with one or more of the first through second aspects, process500includes switching to a non-RedCap-Specific initial downlink BWP and monitoring a BCCH configured within the non-RedCap-Specific initial downlink BWP, wherein the BCCH corresponds to a bandwidth that is less than or equal to a maximum bandwidth capability of the UE. In a fifth aspect, alone or in combination with the fourth aspect, process500includes receiving system information via the BCCH.

In a sixth aspect, alone or in combination with one or more of the first through second aspects, the control channel comprises a BCCH configured within the RedCap-specific initial downlink BWP. In a seventh aspect, alone or in combination with the sixth aspect, process500includes receiving, via the BCCH, at least one of a master information block or a system information block.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process500includes receiving a RedCap-specific short message that indicates a RedCap-specific system information update. In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process500includes transmitting, via a random access channel procedure corresponding to the RedCap-specific initial downlink BWP, a request for on-demand system information.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process500includes performing, via the RedCap-specific initial downlink BWP, an initial access procedure to enter an RRC connected state and receiving a UE-specific signal corresponding to a PDSCH associated with the UE, wherein the UE-specific signal includes an updated SIB.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process500includes receiving an SIB corresponding to a non-RedCap-Specific initial downlink BWP, wherein the SIB indicates a mode that the UE is to use to obtain system information. In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, process500includes receiving an SIB corresponding to the RedCap-specific initial downlink BWP, wherein the SIB is associated with one or more RedCap-specific transmission parameters.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process500includes receiving at least one SSB corresponding to the RedCap-specific initial downlink BWP and obtaining one or more RRM measurements based at least in part on the at least one SSB. In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process500includes switching to a non-RedCap-Specific initial downlink BWP, and receiving at least one of a cell barring indication or a unified access control indication via the non-RedCap-Specific initial downlink BWP.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, monitoring the control channel comprises monitoring a random access search space configured within the RedCap-specific initial downlink BWP. In a sixteenth aspect, alone or in combination with the fifteenth aspect, the RedCap-specific initial downlink BWP contains only one search space, the one search space comprising the random access search space. In a seventeenth aspect, alone or in combination with one or more of the fifteenth through sixteenth aspects, process500includes switching from a non-RedCap-Specific initial downlink BWP to the RedCap-specific initial downlink BWP, and performing a RACH procedure corresponding to the RedCap-specific initial downlink BWP.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the RedCap-specific initial downlink BWP shares a common search space with a non-RedCap-Specific initial downlink BWP. In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the RedCap-specific initial downlink BWP shares a synchronization signal block with a non-RedCap-Specific initial downlink BWP. In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the RedCap-specific initial downlink BWP shares a physical random access channel with a non-RedCap-Specific initial downlink BWP.

FIG.6is a diagram illustrating an example process600performed, for example, by a network node, in accordance with the present disclosure. Example process600is an example where the network node (e.g., network node410) performs operations associated with RedCap-specific initial downlink BWPs.

As shown inFIG.6, in some aspects, process600may include transmitting a first communication on a first control channel configured within a non-RedCap-Specific initial downlink BWP (block610). For example, the network node (e.g., using communication manager150and/or transmission component804, depicted inFIG.8) may transmit a first communication on a first control channel configured within a default initial downlink BWP, as described above.

As further shown inFIG.6, in some aspects, process600may include transmitting a second communication on a second control channel configured within a RedCap-specific initial downlink BWP (block620). For example, the network node (e.g., using communication manager150and/or transmission component804, depicted inFIG.8) may transmit a second communication on a second control channel configured within a RedCap-specific initial downlink BWP, as described above.

In a first aspect, the second control channel comprises a PCCH. In a second aspect, alone or in combination with the first aspect, the second control channel includes a CSS. In a third aspect, alone or in combination with one or more of the first and second aspects, the second communication comprises an SSB. In a fourth aspect, alone or in combination with one or more of the first through third aspects, the second communication comprises an SSB (e.g., a cell-defining SSB or a non-cell-defining SSB).

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the first control channel comprises a BCCH, wherein the BCCH corresponds to a bandwidth that is less than or equal to a maximum bandwidth capability of a RedCap UE. In a sixth aspect, alone or in combination with the fifth aspect, the first communication comprises SI. In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the first control channel comprises a first instance of a BCCH, and the second control channel comprises a second instance of the BCCH. In an eighth aspect, alone or in combination with the seventh aspect, the first communication comprises a first instance of at least one of a MIB or SIB, and the second communication comprises a second instance of the at least one of the MIB or the SIB.

In a ninth aspect, alone or in combination with one or more of the first through sixth aspects, the first control channel comprises a first BCCH, and the second control channel comprises a second BCCH that is different than the first BCCH. In a tenth aspect, alone or in combination with the ninth aspect, process600includes determining that a change in SI is not applicable to any RedCap UE, transmitting an SIB on the first control channel, wherein the SIB indicates the change in the system information, and refraining from transmitting an SIB on the second control channel based at least in part on determining that the change in the system information is not applicable to any RedCap UE. In an eleventh aspect, alone or in combination with one or more of the ninth through tenth aspects, process600includes receiving, via the non-RedCap-Specific initial downlink BWP, a request for ODSI from a UE, transmitting, via the default initial downlink BWP, an SIB that indicates the ODSI, and refraining from transmitting an SIB indicating the ODSI via the RedCap-specific initial downlink BWP based at least in part on not receiving a request for the ODSI from a RedCap UE.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, process600includes transmitting a RedCap-specific short message that indicates a RedCap-specific SI update. In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process600includes receiving, via a RACH procedure corresponding to the RedCap-specific initial downlink BWP, a request for ODSI from a RedCap UE, transmitting, via the RedCap-specific initial downlink BWP, an SIB that indicates the ODSI, and refraining from transmitting an SIB indicating the ODSI via the non-RedCap-Specific initial downlink BWP based at least in part on not receiving a request for the ODSI from a non-RedCap UE.

In a fourteenth aspect, alone or in combination with one or more of the first through eleventh aspects, process600includes performing, via the RedCap-specific initial downlink BWP, an initial access procedure to connect to a UE, and transmitting a UE-specific signal corresponding to a PDSCH associated with the UE, wherein the UE-specific signal includes an updated SIB.

In a fifteenth aspect, alone or in combination with one or more of the first through eleventh aspects, process600includes transmitting an SIB corresponding to a non-RedCap-Specific initial downlink BWPc, wherein the SIB indicates a mode that a UE is to use to obtain SI.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the second communication comprises an SIB associated with one or more RedCap-specific transmission parameters. In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, transmitting the second communication comprises transmitting the second communication to a RedCap UE, and transmitting the first communication comprises transmitting the first communication to the RedCap UE after the RedCap UE has switched to the non-RedCap-Specific initial downlink BWP, wherein the first communication comprises at least one of a cell barring indication or a UAC indication.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the second control channel comprises a random access search space. In a nineteenth aspect, alone or in combination with the eighteenth aspect, the RedCap-specific initial downlink BWP contains only one search space, the one search space comprising the random access search space.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the RedCap-specific initial downlink BWP shares a common search space with a non-RedCap-Specific initial downlink BWP. In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the RedCap-specific initial downlink BWP shares a synchronization signal block with a non-RedCap-Specific initial downlink BWP. In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, the RedCap-specific initial downlink BWP shares a physical random access channel with a non-RedCap-Specific initial downlink BWP.

FIG.7is a diagram of an example apparatus700for wireless communication. The apparatus700may be a UE, or a UE may include the apparatus700. In some aspects, the apparatus700includes a reception component702and a transmission component704, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus700may communicate with another apparatus706(such as a UE, a network node, or another wireless communication device) using the reception component702and the transmission component704. As further shown, the apparatus700may include the communication manager140.

The transmission component704may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus706. In some aspects, one or more other components of the apparatus700may generate communications and may provide the generated communications to the transmission component704for transmission to the apparatus706. In some aspects, the transmission component704may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus706. In some aspects, the transmission component704may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection withFIG.2. In some aspects, the transmission component704may be co-located with the reception component702in a transceiver.

The communication manager140and/or the reception component702may monitor a control channel configured within a RedCap-specific initial downlink BWP, wherein the UE is a RedCap UE operating in idle mode or inactive mode. The reception component702may receive at least one communication via the control channel. In some aspects, the communication manager140may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection withFIG.2. In some aspects, the communication manager140may include the reception component702and/or the transmission component704.

The reception component702may receive an SSB corresponding to the RedCap-specific initial downlink BWP. The communication manager140and/or the reception component702may switch to a non-RedCap-Specific initial downlink BWP. The communication manager140and/or the reception component702may monitor a BCCH corresponding to the non-RedCap-Specific initial downlink BWP, wherein the BCCH corresponds to a bandwidth that is less than or equal to a maximum bandwidth capability of the UE. The reception component702may receive system information via the BCCH. The reception component702may receive, via the BCCH, at least one of an MIB or an SIB.

The reception component702may receive a RedCap-specific short message that indicates a RedCap-specific SI update. The transmission component704may transmit, via a RACH procedure corresponding to the RedCap-specific initial downlink BWP, a request for ODSI. The communication manager140, the reception component702, and/or the transmission component704may perform, via the RedCap-specific initial downlink BWP, an initial access procedure to enter an RRC connected state.

The reception component702may receive a UE-specific signal corresponding to a PDSCH associated with the UE, wherein the UE-specific signal includes an updated SIB. The reception component702may receive an SIB corresponding to a non-RedCap-Specific initial downlink BWP, wherein the SIB indicates a mode that the UE is to use to obtain SI. The reception component702may receive an SIB corresponding to the RedCap-specific initial downlink BWP, wherein the SIB is associated with one or more RedCap-specific transmission parameters.

The reception component702may receive at least one SSB corresponding to the RedCap-specific initial downlink BWP. The communication manager140and/or the reception component702may obtain one or more RRM measurements based at least in part on the at least one SSB.

The communication manager140, the reception component702, and/or the transmission component704may switch to a non-RedCap-Specific initial downlink BWPc. The reception component702may receive at least one of a cell barring indication or a UAC indication via the non-RedCap-Specific initial downlink BWP. The communication manager140, the reception component702, and/or the transmission component704may switch from a non-RedCap-Specific initial downlink BWP to the RedCap-specific initial downlink BWP. The communication manager140, the reception component702, and/or the transmission component704may perform a RACH procedure corresponding to the RedCap-specific initial downlink BWP.

The number and arrangement of components shown inFIG.7are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG.7. Furthermore, two or more components shown inFIG.7may be implemented within a single component, or a single component shown inFIG.7may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown inFIG.7may perform one or more functions described as being performed by another set of components shown inFIG.7.

The transmission component804may transmit a first communication on a first control channel configured within a non-RedCap-Specific initial downlink BWP. The transmission component804may transmit a second communication on a second control channel configured within a RedCap-specific initial downlink BWP.

The communication manager150may determine that a change in SI is not applicable to any RedCap UE. The transmission component804may transmit an SIB on the first control channel, wherein the SIB indicates the change in the SI. The transmission component804may refrain from transmitting an SIB on the second control channel based at least in part on determining that the change in the SI is not applicable to any RedCap UE. In some aspects, the communication manager150may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described in connection withFIG.2. In some aspects, the communication manager150may include the reception component802and/or the transmission component804.

The reception component802may receive, via the non-RedCap-Specific initial downlink BWP, a request for ODSI from a UE. The transmission component804may transmit, via the non-RedCap-Specific initial downlink BWP, an SIB that indicates the ODSI. The transmission component804may refrain from transmitting an SIB indicating the ODSI via the RedCap-specific initial downlink BWP based at least in part on not receiving a request for the ODSI via the RedCap-specific initial downlink BWP.

The transmission component804may transmit a RedCap-specific short message that indicates a RedCap-specific SI update. The reception component802may receive, via a RACH procedure corresponding to the RedCap-specific initial downlink BWP, a request for ODSI from a RedCap UE. The transmission component804may transmit, via the RedCap-specific initial downlink BWP, an SIB that indicates the ODSI. The transmission component804may refrain from transmitting an SIB indicating the ODSI via the non-RedCap-Specific initial downlink BWP based at least in part on not receiving a request for the ODSI from a non-RedCap UE.

The communication manager150, the reception component802, and/or the transmission component804may perform, via the RedCap-specific initial downlink BWP, an initial access procedure to connect to a UE. The transmission component804may transmit a UE-specific signal corresponding to a PDSCH associated with the UE, wherein the UE-specific signal includes an updated SIB. The transmission component804may transmit an SIB corresponding to a non-RedCap-Specific initial downlink BWP, wherein the non-RedCap-Specific initial downlink BWP is not RedCap-specific, wherein the SIB indicates a mode that a user equipment is to use to obtain SI.

Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: monitoring a control channel configured within a reduced capability (RedCap)-specific initial downlink bandwidth part (BWP), wherein the UE is a RedCap UE operating in idle mode or inactive mode; and receiving at least one communication via the control channel.

Aspect 2: The method of Aspect 1, wherein the control channel comprises a paging control channel (PCCH).

Aspect 3: The method of either of Aspects 1 or 2, wherein monitoring the control channel comprises monitoring a common search space configured within the RedCap-specific initial downlink BWP.

Aspect 4: The method of any of Aspects 1-3, further comprising receiving synchronization signal block corresponding to the RedCap-specific initial downlink BWP.

Aspect 5: The method of any of Aspects 1-4, further comprising: switching to a non-RedCap-specific initial downlink BWP; and monitoring a broadcast control channel (BCCH) corresponding to the non-RedCap-specific initial downlink BWP, wherein the BCCH corresponds to a bandwidth that is less than or equal to a maximum bandwidth capability of the UE.

Aspect 6: The method of Aspect 5, further comprising receiving system information via the BCCH.

Aspect 7: The method of any of Aspects 1-6, wherein the control channel comprises a broadcast control channel (BCCH) corresponding to the RedCap-specific initial downlink BWP.

Aspect 8: The method of Aspect 7, further comprising receiving, via the BCCH, a system information block.

Aspect 9: The method of any of Aspects 1-8, further comprising receiving a RedCap-UE-specific short message that indicates a RedCap-specific system information update.

Aspect 10: The method of any of Aspects 1-9, further comprising transmitting, via a random access channel procedure corresponding to the RedCap-specific initial downlink BWP, a request for on-demand system information.

Aspect 11: The method of any of Aspects 1-10, further comprising: performing, via the RedCap-specific initial downlink BWP, an initial access procedure to enter a radio resource control connected state; and receiving a UE-specific signal corresponding to a physical downlink shared channel associated with the UE, wherein the UE-specific signal includes an updated system information block.

Aspect 12: The method of any of Aspects 1-11, further comprising receiving a system information block (SIB) corresponding to a non-RedCap-specific initial downlink BWP, wherein the SIB indicates a mode that the UE is to use to obtain system information.

Aspect 13: The method of any of Aspects 1-12, further comprising receiving a system information block (SIB) corresponding to the RedCap-specific initial downlink BWP, wherein the SIB is associated with one or more RedCap-specific transmission parameters.

Aspect 14: The method of any of Aspects 1-13, further comprising: receiving at least one synchronization signal block (SSB) corresponding to the RedCap-specific initial downlink BWP; and obtaining one or more radio resource management measurements based at least in part on the at least one SSB.

Aspect 15: The method of any of Aspects 1-14, further comprising: switching to a non-RedCap-specific initial downlink BWP; and receiving at least one of a cell barring indication or a unified access control indication via the non-RedCap-specific initial downlink BWP.

Aspect 16: The method of any of Aspects 1-15, wherein monitoring the control channel comprises monitoring a random access search space configured within the RedCap-specific initial downlink BWP.

Aspect 17: The method of Aspect 16, wherein the RedCap-specific initial downlink BWP contains only one search space, the one search space comprising the random access search space.

Aspect 18: The method of either of Aspects 16 or 17, further comprising: switching from a non-RedCap-specific initial downlink BWP to the RedCap-specific initial downlink BWP; and performing a random access channel (RACH) procedure corresponding to the RedCap-specific initial downlink BWP.

Aspect 19: The method of any of Aspects 1-18, wherein the RedCap-specific initial downlink BWP shares a common search space with a non-RedCap-specific initial downlink BWP.

Aspect 20: The method of any of Aspects 1-19, wherein the RedCap-specific initial downlink BWP shares asynchronization signal block with a non-RedCap-specific initial downlink BWP.

Aspect 21: The method of any of Aspects 1-20, wherein the RedCap-specific initial downlink BWP shares a physical random access channel with a non-RedCap-specific initial downlink BWP.

Aspect 22: A method of wireless communication performed by a network node, comprising: transmitting a first communication on a first control channel configured within a non-RedCap-specific initial downlink bandwidth part (BWP); and transmitting a second communication on a second control channel configured within a reduced capability (RedCap)-specific initial downlink BWP.

Aspect 23: The method of Aspect 22, wherein the second control channel comprises a paging control channel (PCCH).

Aspect 24: The method of either of Aspects 22 or 23, wherein the second control channel includes a common search space.

Aspect 25: The method of any of Aspects 22-24, wherein the second communication comprises a synchronization signal block.

Aspect 26: The method of any of Aspects 22-25, wherein the second communication comprises a synchronization signal block.

Aspect 27: The method of any of Aspects 22-26, wherein the first control channel comprises a broadcast control channel (BCCH), wherein the BCCH corresponds to a bandwidth that is less than or equal to a maximum bandwidth capability of a RedCap user equipment (UE).

Aspect 28: The method of Aspect 27, wherein the first communication comprises system information.

Aspect 29: The method of any of Aspects 22-28, wherein the first control channel comprises a first instance of a broadcast control channel (BCCH), and wherein the second control channel comprises a second instance of the BCCH.

Aspect 30: The method of Aspect 29, wherein the first communication comprises a first instance of a system information block (SIB), and wherein the second communication comprises a second instance of the SIB.

Aspect 31: The method of any of Aspects 22-30, wherein the first control channel comprises a first broadcast control channel (BCCH), and wherein the second control channel comprises a second BCCH that is different than the first BCCH.

Aspect 32: The method of Aspect 31, further comprising: determining that a change in system information is not applicable to any RedCap user equipment (UE); transmitting a system information block (SIB) on the first control channel, wherein the SIB indicates the change in the system information; and refraining from transmitting an SIB on the second control channel based at least in part on determining that the change in the system information is not applicable to any RedCap UE.

Aspect 33: The method of either of Aspects 31 or 32, further comprising: receiving, via the non-RedCap-specific initial downlink BWP, a request for on-demand system information (ODSI) from a user equipment (UE); transmitting, via the non-RedCap-specific initial downlink BWP, a system information block (SIB) that indicates the ODSI; and refraining from transmitting an SIB indicating the ODSI via the RedCap-specific initial downlink BWP based at least in part on not receiving a request for the ODSI from a RedCap UE.

Aspect 34: The method of any of Aspects 22-33, further comprising transmitting a RedCap-specific short message that indicates a RedCap-specific system information update.

Aspect 35: The method of any of Aspects 22-34, further comprising: receiving, via a random access channel procedure corresponding to the RedCap-specific initial downlink BWP, a request for on-demand system information (ODSI) from a RedCap user equipment; transmitting, via the RedCap-specific initial downlink BWP, a system information block (SIB) that indicates the ODSI; and refraining from transmitting an SIB indicating the ODSI via the default initial downlink BWP based at least in part on not receiving a request for the ODSI from a non-RedCap UE.

Aspect 36: The method of any of Aspects 22-35, further comprising: performing, via the RedCap-specific initial downlink BWP, an initial access procedure to connect to a user equipment (UE); and transmitting a UE-specific signal corresponding to a physical downlink shared channel associated with the UE, wherein the UE-specific signal includes an updated system information block.

Aspect 37: The method of any of Aspects 22-36, further comprising transmitting a system information block (SIB) corresponding to the non-RedCap-specific initial downlink BWP, wherein the SIB indicates a mode that a user equipment is to use to obtain system information.

Aspect 38: The method of any of Aspects 22-37, wherein the second communication comprises a system information block (SIB) associated with one or more RedCap-specific transmission parameters.

Aspect 39: The method of any of Aspects 22-38, wherein transmitting the second communication comprises transmitting the second communication to a RedCap user equipment (UE), and wherein transmitting the first communication comprises transmitting the first communication to the RedCap UE after the RedCap UE has switched to the non-RedCap-specific initial downlink BWP, wherein the first communication comprises at least one of a cell barring indication or a unified access control indication.

Aspect 40: The method of any of Aspects 22-39, wherein the second control channel comprises a random access search space.

Aspect 41: The method of Aspect 40, wherein the RedCap-specific initial downlink BWP contains only one search space, the one search space comprising the random access search space.

Aspect 42: The method of any of Aspects 22-41, wherein the RedCap-specific initial downlink BWP shares a common search space with the non-RedCap-specific initial downlink BWP.

Aspect 43: The method of any of Aspects 22-42, wherein the RedCap-specific initial downlink BWP shares a synchronization signal block with the non-RedCap-specific initial downlink BWP.

Aspect 44: The method of any of Aspects 22-43, wherein the RedCap-specific initial downlink BWP shares a physical random access channel with the non-RedCap-specific initial downlink BWP.