TECHNIQUES TO FACILITATE PRIORITY RULES FOR MEASUREMENTS BASED ON CELL-DEFINING SSBS AND/OR NON-CELL-DEFINING SSBS

Apparatus, methods, and computer-readable media for facilitating priority rules for measurements based on CD-SSBs and/or NCD-SSBs are disclosed herein. An example method for wireless communication at a UE includes indicating a UE capability to a network. The example method also includes receiving a configuration for a measurement object and a DL BWP, the configuration indicating that the DL BWP includes a CD-SSB, includes an NCD-SSB, or that an SSB is absent. The configuration for the measurement object and the DL BWP may be based at least on one or more of a duplex mode type, a frequency range, a type of the DL BWP, or the UE capability.

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems utilizing cell-defining (CD) synchronization signal blocks (SSBs) and non-cell-defining (NCD) SSBs.

INTRODUCTION

BRIEF SUMMARY

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication. An apparatus may include a user equipment (UE). The example apparatus may indicate a UE capability to a network. The example apparatus may also receive a configuration for a measurement object and a downlink (DL) bandwidth part (BWP) in system information or a radio resource control (RRC) message, the configuration indicating that the DL BWP includes a cell-defining synchronization signal block (CD-SSB), includes a non-CD-SSB (NCD-SSB), or that an SSB is absent. The configuration for the measurement object and the DL BWP may be based at least on one or more of a duplex mode type, a frequency range, a type of the DL BWP, or the UE capability.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication. An apparatus may include a network entity, such as a base station or a component of a base station. The example apparatus may receive an indication of a UE capability of at least one UE. The example apparatus may also configure serving cell measurement and one or more DL BWPs, a configuration for each DL BWP being based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

DETAILED DESCRIPTION

Aspects disclosed herein provide techniques for different SSB transmission in the initial/non-initial downlink BWP of different UE types (e.g., a reduced capability UE or a non-reduced capability UE) when a cell allows different UE types to access the cell. That is, when a cell supports reduced capability UE and non-reduced capability UE co-existence, different SSB transmissions in the initial/non-initial downlink BWP of the different UE type may be supported. Additionally, aspects disclosed herein provide priority rules for SSB-based measurements (e.g., for random access channel occasion (RO) selection, time/frequency tracking, link recovery, radio resource management (RRM) measurements, radio link monitoring (RLM) measurements, beam failure detection (BFD) measurements, and other tasks).

FIG.1is a diagram100illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs (e.g., a CU110) that can communicate directly with a core network120via a backhaul link, or indirectly with the core network120through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC125) via an E2 link, or a Non-Real Time (Non-RT) RIC115associated with a Service Management and Orchestration (SMO) Framework (e.g., an SMO Framework105), or both). A CU110may communicate with one or more DUs (e.g., a DU130) via respective midhaul links, such as an F1 interface. The DU130may communicate with one or more RUs (e.g., an RU140) via respective fronthaul links. The RU140may communicate with respective UEs (e.g., a UE104) via one or more radio frequency (RF) access links. In some implementations, the UE104may be simultaneously served by multiple RUs.

Each of the units, i.e., the CUs (e.g., a CU110), the DUs (e.g., a DU130), the RUs (e.g., an RU140), as well as the Near-RT RICs (e.g., the Near-RT RIC125), the Non-RT RICs (e.g., the Non-RT RIC115), and the SMO Framework105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

Lower-layer functionality can be implemented by one or more RUs. In some deployments, an RU140, controlled by a DU130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU140can be implemented to handle over the air (OTA) communication with one or more UEs (e.g., the UE104). In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU140can be controlled by a corresponding DU. In some scenarios, this configuration can enable the DU(s) and the CU110to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework105may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework105may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework105may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud)190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs, DUs, RUs and Near-RT RICs. In some implementations, the SMO Framework105can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB)111, via an O1 interface. Additionally, in some implementations, the SMO Framework105can communicate directly with one or more RUs via an O1 interface. The SMO Framework105also may include a Non-RT RIC115configured to support functionality of the SMO Framework105.

The wireless communications system may further include a Wi-Fi AP150in communication with a UE104(also referred to as Wi-Fi stations (STAs)) via communication link154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UE104/Wi-Fi AP150may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

Referring again toFIG.1, in certain aspects, a device in communication with a base station, such as a UE104in communication with a network entity, such as a base station102or a component of a base station (e.g., a CU110, a DU130, and/or an RU140), may be configured to manage one or more aspects of wireless communication. For example, the UE104may include a prioritization component198configured to facilitate applying priority rules for measurements based on CD-SSBs and/or NCD-SSBs.

In certain aspects, the prioritization component198may be configured to indicate a UE capability to a network. The example prioritization component198may also be configured to receive a configuration for a measurement object and a DL BWP in system information or an RRC message, the configuration indicating that the DL BWP includes a CD-SSB, includes an NCD-SS, or that an SSB is absent. The configuration for the measurement object and the DL BWP may be based at least on one or more of a duplex mode type, a frequency range, a type of the DL BWP, or the UE capability.

In another configuration, a network entity, such as a base station102or a component of a base station (e.g., a CU110, a DU130, and/or an RU140), may be configured to manage or more aspects of wireless communication. For example, the base station102may include a configuration component199configured to facilitate applying priority rules for measurements based on CD-SSBs and/or NCD-SSBs.

In certain aspects, the configuration component199may be configured to receive an indication of a UE capability of at least one UE. The example configuration component199may also be configured to configure serving cell measurement and one or more DL BWPs, a configuration for each DL BWP being based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G-advanced, 6G, LTE, LTE-A, CDMA, GSM, and other wireless technologies.

FIG.3is a block diagram that illustrates an example of a first wireless device that is configured to exchange wireless communication with a second wireless device. In the illustrated example ofFIG.3, the first wireless device may include a base station310, the second wireless device may include a UE350, and the base station310may be in communication with the UE350in an access network. As shown inFIG.3, the base station310includes a transmit processor (TX processor316), a transmitter318Tx, a receiver318Rx, antennas320, a receive processor (RX processor370), a channel estimator374, a controller/processor375, and memory376. The example UE350includes antennas352, a transmitter354Tx, a receiver354Rx, an RX processor356, a channel estimator358, a controller/processor359, memory360, and a TX processor368. In other examples, the base station310and/or the UE350may include additional or alternative components.

Channel estimates derived by the channel estimator358from a reference signal or feedback transmitted by the base station310may be used by the TX processor368to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor368may be provided to different antenna of the antennas352via separate transmitters (e.g., the transmitter354Tx). Each transmitter354Tx may modulate an RF carrier with a respective spatial stream for transmission.

Wireless communication systems, such as NR communication systems, may support higher capability devices and reduced capability devices. Among others, examples of higher capability devices include premium smartphones, V2X devices, URLLC devices, eMBB devices, etc. Examples of reduced capability (RedCap) devices may include, among others, wearables (e.g., such as smart watches, augmented reality glasses, virtual reality glasses, health and medical monitoring devices, etc.), industrial wireless sensor networks (IWSN) (e.g., such as pressure sensors, humidity sensors, motion sensors, thermal sensors, accelerometers, actuators, etc.), surveillance cameras, low-end smartphones, etc. A reduced capability device may be referred to as an NR light device, a low-tier device, a lower tier device, etc.

A reduced capability UE may communicate based on various types of wireless communication. For example, smart wearables may transmit or receive communication based on low power wide area (LPWA)/mMTC, IoT devices may transmit or receive communication based on URLLC, sensors/cameras may transmit or receive communication based on eMBB, etc. In some examples, a reduced capability UE may have an uplink transmission power that is less than that of a higher capability UE. For example, a reduced capability UE may have an uplink transmission power of at least 10 dB less than that of a higher capability UE. As another example, a reduced capability UE may have reduced transmission bandwidth or reception bandwidth than other UEs. For instance, a reduced capability UE may have an operational bandwidth between 5 MHz and 20 MHz for both transmission and reception, in contrast to higher capability UEs that may have a bandwidth of up to 100 MHz. As an example, a reduced capability UE may have a maximum bandwidth of 20 MHz during and after initial access in FR1, and may have a maximum bandwidth of 100 MHz during and after initial access in FR2.

As a further example, a reduced capability UE may have a reduced number of reception antennas in comparison to other UEs. For frequency bands where a UE is equipped with at least two antennas, a minimum number of reception branches for a reduced capability UE may be 1, and may also include support for 2 reception branches. For frequency bands where a higher capability UE is equipped with four reception antenna ports, a minimum number of 1 reception branches may be supported, for example, with additional support for 2 reception branches for a reduced capability UE. In some aspects, a base station may know the number of reception branches at the UE. A reduced capability UE may have only a single receive antenna and may experience a lower equivalent receive signal to noise ratio (SNR) in comparison to higher capability UEs that may have multiple antennas. A reduced capability UE with 1 reception branch may support 1 downlink MIMO layer. A reduced capability UE with two reception branches may support two downlink MIMO layers. A maximum modulation order of 256 QAM may be supported in the downlink for an FR1 reduced capability UE. In some aspects, a reduced capability UE may support a half-duplex frequency division duplex (HD-FDD) type A duplex operation. A reduced capability UE may support a full-duplex FDD (FD-FDD) operation or a full-duplex time division duplex (FD-TDD) operation. Reduced capability UEs may additionally, or alternatively, have reduced computational complexity than other UEs.

As an example, a wearable may have a downlink heavy data rate, for example, of 5-50 Mbps on downlink compared to a rate of 2-5 Mbps on uplink, with peak rates of 150 Mbps on DL and 50 Mbps on UL. The latency and reliability may be based on eMBB. The battery life of the wearable may be intended to last for multiple days, for example, 1-2 weeks in one example. An industrial sensor may have uplink heavy data rates, for example, of around 2 Mbps, a latency of less than 100 ms with a smaller latency (e.g., 5-10 ms) for safety related sensors, a reliability of 99.9%, and may have a battery life that is intended to last for one or more years. A video surveillance device may have uplink heavy traffic, for example, with data rates of 2-4 Mbps for some traffic and 7.5-25 Mbps for higher priority traffic. The video surveillance device may have a latency of less than 500 ms with a reliability of 99%-99.9%.

It may be helpful for communication to be scalable and deployable in a more efficient and cost-effective way. For example, it may be possible to relax or reduce peak throughput, latency, and/or reliability requirements for the reduced capability devices. In some examples, reductions in power consumption, complexity, production cost, and/or reductions in system overhead may be prioritized. As an example, industrial sensors may have an acceptable latency up to approximately 100 ms. In some safety related applications, the latency of industrial wireless sensors may be acceptable up to 10 ms or up to 5 ms. The data rate may be lower and may include more uplink traffic than downlink traffic. As another example, video surveillance devices may have an acceptable latency up to approximately 500 ms.

Carrier bandwidth may span a contiguous set of PRBs, for example, from common resources blocks for a given numerology on a given carrier. A base station may configure one or more BWPs that have a smaller bandwidth span than the carrier bandwidth. One or more of the BWPs may be configured for downlink communication, and may be referred to as a DL BWP.

FIG.4illustrates a resource diagram400showing multiple BWPs (e.g., a BWP1, a BWP2, and a BWP3) configured within a frequency span of a carrier bandwidth402. One DL BWP may be active at a time, and the UE may not be expected to receive PDSCH, PDCCH, CSI-RS, or tracking RS (TRS) outside of an active BWP without a measurement gap or BWP switching gap. Each DL BWP may include at least one control resource set (CORESET). InFIG.4, the BWPs may be DL BWPs and are illustrated as having a CORESET within the BWP. In other examples, the BWP may be an UL BWP and may not include a CORESET configuration. One or more of the BWPs may be configured for uplink communication, and may be referred to as an uplink (UL) BWP. One UL BWP may be active at a time for the UE, and the UE may not transmit PUSCH or PUCCH outside of the active BWP. The use of a BWP may reduce the bandwidth monitored by the UE and/or used for transmissions, which may help the UE to save battery power.

A CORESET corresponds to a set of physical resources in time and frequency that a UE uses to monitor for PDCCH/DCI. Each CORESET comprises one or more resource blocks in the frequency domain and one or more symbols in the time domain. As an example, a CORESET might comprise multiple RBs in the frequency domain and 1, 2, or 3 contiguous symbols in the time domain. A Resource Element (RE) is a unit indicating one subcarrier in frequency over a single symbol in time. A Control Channel Element (CCE) includes Resource Element Groups (REGs), e.g., 6 REGs, in which an REG may correspond to one RB (e.g., 12 REs) during one OFDM symbol. REGs within a CORESET may be numbered in increasing order in a time-first manner, starting with 0 for the first OFDM symbol and the lowest-numbered resource block in the control resource set. A UE can be configured with multiple CORESETs, each CORESET being associated with a CCE-to-REG mapping. A search space may comprise a set of CCEs, for example, at different aggregation levels. For example, the search space may indicate a number of candidates to be decoded, e.g., in which the UE performs decoding. A CORESET may comprise multiple search space sets.

In some aspects, UEs having different levels of capabilities, such as reduced capability UEs and non-reduced (or higher) capability UEs, may share an initial DL BWP (e.g., BWP1) and CORESET #0(e.g., a CORESET404) for initial access. The UEs may monitor the resources of the CORESET404to receive system information that enables the UEs to perform initial access, for example. A cell-defining SSB (CD-SSB) may be transmitted within a bandwidth supported by the reduced capability UEs. As an example, the BWP1may be an initial DL BWP, e.g., which may be configured for both, reduced capability UEs and higher capability UEs. The UEs may be configured with a different BWP as an active DL BWP, e.g., after performing initial access. For example, inFIG.4, the BWP2may be configured for lower capability UEs, and the higher capability UEs may be configured with the active DL BWP3.FIG.4illustrates that the BWP1may include an SSB408.

A network may output one or more synchronization signal blocks (SSBs) to a UE, and the UE may process (e.g., decode) the SSBs in order to obtain system information and begin communications with the network. An SSB may include synchronization signals, such as a PSS, a PBCH, and an SSS, which may be referred to as acquisition signals. The SSB may occupy resources in the time domain and/or the frequency domain. The PSS, the PBCH, and the SSS may each occupy different sets of symbols and subcarriers of the SSB.

A cell that provides access to a reduced capability UE may configure a separate initial BWP for the reduced capability UE.FIG.5illustrate an example diagram500showing an initial downlink BWP510that may be configured within a carrier bandwidth502of a serving cell for reduced capability UEs to receive a CD-SSB, SI, paging information, etc. In some aspects, the initial downlink BWP510may be configured with resources for a CD-SSB512, a CORESET #0(e.g., a CORESET514), and a CORESET or a common search space (CSS) (e.g., resources516) for the UE to receive SIB1, other system information (OSI), or paging information. An idle or inactive reduced capability UE may camp on the initial downlink BWP510, e.g., on the CORESET514of the serving cell to receive the CD-SSB, SI, and/or paging information. The idle or inactive reduced capability UE may switch to a separate BWP to perform random access, small data transfer (SDT), or to initiate a transfer to a connected mode.

The reduced capability UE may receive a configuration for an initial BWP pair including an initial RedCap downlink BWP520and an initial RedCap uplink BWP530for random access or SDT. The initial RedCap downlink BWP520may include resources522configured for a CORESET or CSS for initial access by the reduced capability UE. The initial RedCap uplink BWP530may include PUCCH resources and may include a random access channel occasion (e.g., an RO532), for example. The network may assume that an idle or inactive reduced capability UE that performs random access in the separate initial BWP (e.g., transmitting a random access message in the initial RedCap uplink BWP530and/or monitoring for a downlink response in the initial RedCap downlink BWP520) does not monitor for paging in the CORESET514.

In some aspects, the separate initial BWP (e.g., the initial RedCap downlink BWP520) for the reduced capability UEs may include a CD-SSB, and particular CORESET resources, such as CORESET #0resources. In other aspects, the initial RedCap downlink BWP520for the reduced capability UEs may not include a CD-SSB (e.g., being configured without resources for a CD-SSB, not including a CD-SSB, etc., which may be referred to as an SSB-less BWP), and particular CORESET resources, such as resources for a CORESET #0, or the CORESET for the reception of SIB1, OSI, or paging information. In the illustrated example ofFIG.5, the initial RedCap downlink BWP520does not include a CD-SSB or a CORESET #0, for example, for random access.

In some aspects in FR1, for a separate initial DL BWP (e.g., such as the initial RedCap downlink BWP520) that does not include the CD-SSB and the CORESET #0(e.g., does not include an entire CORESET #0), the initial RedCap downlink BWP520may be configured for random access and not for paging in idle/inactive mode. The initial RedCap downlink BWP520may not contain SSB, CORESET #0, or SIB resources. For example, the network may assume that the reduced capability UE that is performing random access in the initial RedCap downlink BWP520does not monitor paging in a BWP containing the CORESET514(e.g., does not monitor paging in the initial downlink BWP510). If a BWP is configured for paging, the reduced capability UE may expect the BWP to contain a non-cell-defining SSB (NCD-SSB) for the serving cell, but may not expect the BWP to include a CORESET #0/SIB. For an RRC-configured active DL BWP configured for the UE in a connected mode, and if the active DL BWP does not include the CD-SSB and the entire CORESET #0, the reduced capability UE may expect the active DL BWP to include an NCD-SSB for the serving cell, e.g., but not a CORESET #0/SIB. In some aspects, the reduced capability UE may indicate a capability in which the UE does not use an NCD-SSB. For example, the reduced capability UE may optionally support relevant operation for wireless communication based on a reference signal, such as CSI-RS, and may report the capability to the network.

If the network configures a separate initial/RRC configured DL BWP for the reduced capability UE to contain the entire CORESET #0, the reduced capability UE may expect the separate initial BWP to include a CD-SSB. The network may choose to configure an SSB or a MIB-configured CORESET #0or SIB1 to be within the respective DL BWP. If a separate SIB-configured initial DL BWP for the reduced capability UE contains the entire CORESET #0, the reduced capability UE may use the bandwidth and location of the CORESET #0for downlink reception during initial access. An NCD-SSB periodicity may be different than a periodicity of a CD-SSB. In some aspects, a periodicity of an NCD-SSB may not be less than a periodicity of a CD-SSB.

In some aspects in FR2, a separate initial DL BWP (e.g., the initial RedCap downlink BWP520) that does not include a CD-SSB and the entire CORESET #0) may be configured for random access and not for paging in an idle/inactive mode. The initial RedCap downlink BWP520may not contain SSB, CORESET #0, or SIB resources. For example, the network may assume that the reduced capability UE that is performing random access in the initial RedCap downlink BWP520does not monitor paging in a BWP containing the CORESET514(e.g., does not monitor paging in the initial downlink BWP510). If the initial RedCap downlink BWP is configured for paging, the reduced capability UE may expect the initial RedCap downlink BWP to contain an NCD-SSB for the serving cell, but not CORESET #0or SIB resources.

For an RRC-configured active DL BWP configured for the UE in a connected mode, and if the active DL BWP does not include the CD-SSB and an entire CORESET #0, the reduced capability UE may expect the active DL BWP to include an NCD-SSB for the serving cell, e.g., but not a CORESET #0/SIB. In some aspects, the reduced capability UE may indicate a capability in which the UE does not use an NCD-SSB. For example, the reduced capability UE may optionally support relevant operation for wireless communication based on a reference signal, such as CSI-RS, and may report the capability to the network.

For an SSB and CORESET #0multiplexing pattern1, if a separate initial DL BWP is configured via RRC to contain the entire CORESET #0, the reduced capability UE may expect the separate initial DL BWP to include a CD-SSB. The network may choose to configure an SSB or a MIB-configured CORESET #0or SIB1 to be within the respective DL BWP. If a separate SIB-configured initial DL BWP for the reduced capability UE contains the entire CORESET #0, the reduced capability UE may use the bandwidth and location of the CORESET #0in for downlink reception during initial access. An NCD-SSB periodicity may be different than a periodicity of a CD-SSB. In some aspects, a periodicity of an NCD-SSB may not be less than a periodicity of a CD-SSB.

As described earlier, an SSB includes primary synchronization signals (PSS), secondary synchronization signals (SSS), and PBCH. The possible time locations of SSBs within a half-frame may be determined by sub-carrier spacing and the periodicity of the half-frames transmitting SSBs may be configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions, for example, using different beams and spanning the coverage area of a cell.

System information includes minimum system information and other system information. The other system information may include all SIBs not included in the minimum system information. The minimum system information includes basic information for initial access and information for acquiring any other system information. For example, minimum system information may include a master information block (MIB) and a system information block1(SIB1). The MIB may include cell barred status information and physical layer information of the cell to facilitate receiving further system information, for example, a CORESET #0configuration. The SIB1 may define the scheduling of other system information blocks and may contain information for initial access. The SIB1 may also be referred to as remaining minimum system information (RMSI). The MIB may be carried on the PBCH of the SSB and provide the UE with parameters (e.g., a CORESET #0configuration) for monitoring of PDCCH for scheduling PDSCH that carries the SIB1.

Within the frequency span of a carrier, one or more SSBs may be transmitted. The physical cell identity (PCI) of SSBs transmitted in different frequency locations may or may not be unique. For example, different SSBs in the frequency domain may have different PCIs. However, when an SSB is associated with RMSI (e.g., a SIB1), the SSB is referred to as a cell-defining SSB (CD-SSB). A primary cell (PCell) is associated to a CD-SSB located on the synchronization raster. Frequencies may be configured to be on the synchronization raster if they are also identifiable with a global synchronization channel number (GSCN).

In some examples, a MIB may indicate that the SSB is not associated with RMSI (e.g., there is no associated SIB1). When an SSB is not associated with RMSI, the SSB may be referred to as a non-cell-defining SSB (NCD-SSB). While a CD-SSB is transmitted on the synchronization raster, an NCD-SSB may be transmitted on or off the synchronization raster. A UE may determine whether an SSB is a CD-SSB or an NCD-SSB based on the MIB of the SSB.FIG.6illustrates an example MIB message600, as presented herein. The MIB message600may be transmitted from the network to a UE. The example MIB message600includes different fields, including an SSB subcarrier offset field602, which may be referred to as a “ssb-SubcarrierOffset” field or by any other name. The SSB subcarrier offset field602corresponds to an SSB-type indicator (KSSB) that signals the frequency domain offset between SSB and the overall resource block grid in number of subcarriers. For example, in FR1, the KSSBmay be a 5-bit value, and in FR2, the KSSBmay be a 4-bit value. Referring to FR1, when the value of the KSSBis greater than or equal to 0 and less than 24 (e.g., 0≤KSSB<24), the UE may determine that the SSB is a CD-SSB, and when the value of the KSSBis greater than or equal to 24 and less than 32 (e.g., 24≤KSSB<32), the UE may determine that the SSB is an NCD-SSB. With respect to FR2, when the value of the KSSBis greater than or equal to 0 and less than 12 (e.g., 0≤KSSB<12), the UE may determine that the SSB is a CD-SSB, and when the value of the KSSBis greater than or equal to 12 and less than 16 (e.g., 12≤KSSB<16), the UE may determine that the SSB is an NCD-SSB.

As shown inFIG.6, the SSB subcarrier offset field602is an integer between 0 and 15 and, thus, may be represented by four bits. However, the value of the KSSBfor FR1 may be between 0 and 31, which corresponds to five bits. Thus, the UE may use 1-bit of the L1 portion of the PBCH payload for the fifth bit of the KSSB. For example, the PBCH payload of an SSB may include 32 bits of which 24 bits are allocated to the MIB payload and 8 bits are allocated to the L1 payload.

The example MIB message600also includes a PDCCH SIB1 configuration field604, which may be referred to as a “pdcch-ConfigSIB1” field or by any other name. The PDCCH SIB1 configuration field604may determine a common CORESET, a common search space, and PDCCH parameters. If the SSB subcarrier offset field602indicates that SIB1 is absent, the PDCCH SIB1 configuration field604may indicate the frequency positions where the UE may find an SSB with SIB1 or the frequency range where the network does not provide an SSB with SIB1. Thus, when the SSB is a CD-SSB, the PDCCH SIB1 configuration field604points to valid configurations for CORESET #0and a type0 PDCCH CSS set, which may be referred to as a “Type0-PDCCH CSS set” or by another name. When the SSB is an NCD-SSB, the SSB (e.g., the PDCCH SIB1 configuration field604) does not point to a valid configuration for CORESET #0and the type0 PDCCH CSS set.

In some aspects, a UE may use an NCD-SSB for serving cell and non-serving cell measurements for all RRC modes (e.g., idle, inactive, and/or connected). The UE may use the measurements to facilitate with one or more of radio resource measurement (RRM), radio link monitoring (RLM), beam failure detection (BFD), link recovery, RO selection, mobility, time/frequency tracking, and automatic gain control (AGC).

In FR1 and FR2, initial and non-initial BWPs for reduced capability UEs may be configured by the network via system information and/or RRC signaling. The initial/non-initial BWPs may be configured subject to the maximum bandwidth supported by the reduced capability UEs. Depending on the functionalities of reduced capability UE-specific initial/non-initial downlink BWPs, the downlink BWPs of a reduced capability UE may have a configuration for an SSB. For example, the SSB configuration may indicate that a CD-SSB is transmitted by the serving cell, may indicate that an NCD-SSB is transmitted by the serving cell, or may indicate that no SSB is transmitted by the serving cell (e.g., that an SSB is absent).

On a cell that supports both reduced capability UEs and non-reduced capability UEs (e.g., higher capability UEs) to access, the CD-SSB and the NCD-SSB of the serving cell may provide different roles. For example, for cell selection/reselection, a UE (e.g., a reduced capability UE or a non-reduced capability UE) searches for a CD-SSB and decodes the included system information. A reduced capability UE may use either the CD-SSB or the NCD-SSB of the serving cell to perform RO selection, time/frequency tracking, link recovery, RRM measurements, RLM measurements, BFD measurements, and other tasks.

Aspects disclosed herein provide techniques for different SSB transmission in the initial/non-initial downlink BWP of different UE types (e.g., a reduced capability UE or a non-reduced capability UE) when a cell supports different UE types to access the cell. That is, when a cell supports co-existence between reduced capability UEs and non-reduced capability UEs, different SSB transmissions in the initial/non-initial downlink BWP of the different UE type may be supported. Additionally, aspects disclosed herein provide priority rules for SSB-based measurements (e.g., for RO selection, time/frequency tracking, link recovery, RRM measurements, RLM measurements, BFD measurements, and other tasks).

In some aspects, the SSB transmission in a downlink BWP of a reduced capability UE may be based on UE capability, deployment (e.g., duplex mode and/or frequency range, such as FR1 or FR2), and co-existence needs. With respect to the initial downlink BWP, the reduced capability UE may be configured with a CD-SSB being transmitted by the serving cell, an NCD-SSB being transmitted by the serving cell, or no SSB being transmitted (e.g., an SSB is absent). Additionally, with respect to the non-initial downlink BWP, the reduced capability UE may be configured with a CD-SSB being transmitted by the serving cell, an NCD-SSB being transmitted by the serving cell, or no SSB being transmitted by the serving cell.

FIG.7illustrates example diagrams showing SSB transmissions with respect to initial downlink BWPs and non-initial downlink BWPs that may be configured within a carrier bandwidth of a serving cell for a reduced capability UE, as presented herein. In an example first diagram700, a cell may have a carrier bandwidth702. A reduced capability UE may be configured with an initial downlink BWP704and a non-initial downlink BWP706. As shown in the first diagram700, the reduced capability UE may receive a CD-SSB708within the initial downlink BWP704. The CD-SSB708may also configure a CORESET #0710within the initial downlink BWP704. The first diagram700also illustrates that the reduced capability UE may receive an NCD-SSB712within the non-initial downlink BWP706.

In the illustrated example ofFIG.7, if the downlink BWP includes only a CD-SSB, a reduced capability UE is not expected to measure an NCD-SSB outside the active downlink BWP, for example, for RRM, RLM, BFD, link recovery, a tracking loop, and/or AGC. For example, in the first diagram700, the initial downlink BWP704includes the CD-SSB708and no NCD-SSB. In such scenarios, a reduced capability UE may be configured to not measure the NCD-SSB712outside the initial downlink BWP704.

In an example second diagram720, a cell may have a carrier bandwidth722. A reduced capability UE may be configured with an initial downlink BWP724and a non-initial downlink BWP726. As shown in the second diagram720, the reduced capability UE may receive an NCD-SSB728within the non-initial downlink BWP726. The reduced capability UE may also receive a CD-SSB730outside the initial downlink BWP724and the non-initial downlink BWP726. For example, the reduced capability UE may receive the CD-SSB730in a third BWP732. The CD-SSB730may also configure a CORESET #0734within the third BWP732.

In an example third diagram740, a cell may have a carrier bandwidth742. A reduced capability UE may be configured with an initial downlink BWP744and a non-initial downlink BWP746. As shown in the third diagram740, the reduced capability UE may receive a CD-SSB748within the non-initial downlink BWP746. The CD-SSB748may also configure a CORESET #0750within the non-initial downlink BWP746. The third diagram740also illustrates that the reduced capability UE may receive an NCD-SSB752within the initial downlink BWP744.

In an example fourth diagram760, a cell may have a carrier bandwidth762. A reduced capability UE may be configured with an initial downlink BWP764and a non-initial downlink BWP766. As shown in the fourth diagram760, the reduced capability UE may not receive an SSB in the initial downlink BWP764and also may not receive an SSB in the non-initial downlink BWP766. However, similar to the example second diagram720, the reduced capability UE may receive a CD-SSB768in a third BWP770. The CD-SSB768may also configure a CORESET #0772within the third BWP770.

As shown in the example diagrams ofFIG.7, for a reduced capability UE, the initial downlink BWP may include a CD-SSB (e.g., as shown in the first diagram700), may include an NCD-SSB (e.g., as shown in the third diagram740), or may include no SSB (e.g., as shown in the second diagram720and the fourth diagram760). Additionally, for the reduced capability UE, the non-initial downlink BWP may include a CD-SSB (e.g., as shown in the third diagram740), may include an NCD-SSB (e.g., as shown in the first diagram700and the second diagram720), or may include no SSB (e.g., as shown in the fourth diagram760).

It may be appreciated that other examples may include additional or alternate combinations of a CD-SSB, an NCD-SSB, and no SSB within an initial downlink BWP and a non-initial downlink BWP for a reduced capability UE.

In some aspects, the SSB transmission in a downlink BWP of a non-reduced capability UE (e.g., a higher capability UE) may be based on the bandwidth of a SIB1-configured initial downlink BWP. With respect to the initial downlink BWP, the non-reduced capability UE may be configured with a CD-SSB being transmitted by the serving cell, or a CD-SSB and an NCD-SSB being transmitted by the serving cell. Additionally, with respect to the non-initial downlink BWP, the non-reduced capability UE may be configured with a CD-SSB being transmitted by the serving cell, an NCD-SSB being transmitted by the serving cell, a CD-SSB and an NCD-SSB being transmitted by the serving cell, or no SSB being transmitted by the serving cell. For example, the non-reduced capability UE may have the capability to operate in a bandwidth as wide as the carrier bandwidth. In such examples, the non-reduced capability UE may have the capability to receive a CD-SSB and an NCD-SSB within an initial/non-initial downlink BWP.

FIG.8illustrates example diagrams showing SSB transmissions with respect to initial downlink BWPs and non-initial downlink BWPs that may be configured within a carrier bandwidth of a serving cell for a non-reduced capability UE, as presented herein. In an example first diagram800, a cell may have a carrier bandwidth802. A non-reduced capability UE may be configured with an initial downlink BWP804and a non-initial downlink BWP806. The initial downlink BWP804may be configured by SIB1 and/or by RRC signaling. In the example first diagram800, the initial downlink BWP804and the non-initial downlink BWP806overlap in frequency resources. The non-reduced capability UE may receive a CD-SSB808within the initial downlink BWP804. The CD-SSB808may also configure a CORESET #0810. The first diagram800also illustrates that the non-reduced capability UE may receive an NCD-SSB812within the non-initial downlink BWP806. In the example first diagram800, the non-initial downlink BWP806overlaps with the CD-SSB808and the NCD-SSB812.

In an example second diagram820, a cell may have a carrier bandwidth822. A non-reduced capability UE may be configured with an initial downlink BWP824and a non-initial downlink BWP826. The initial downlink BWP824may be configured by SIB1 and/or by RRC signaling. As shown in the second diagram820, the non-reduced capability UE may receive a CD-SSB828within the initial downlink BWP824. The CD-SSB828may also configure a CORESET #0830. As shown in the second diagram820, the non-initial downlink BWP826may partially overlap with the initial downlink BWP824. Additionally, the non-reduced capability UE may receive an NCD-SSB832within the non-initial downlink BWP826.

In an example third diagram840, a cell may have a carrier bandwidth842. A non-reduced capability UE may be configured with an initial downlink BWP844and a non-initial downlink BWP846. The initial downlink BWP844may be configured by SIB1 and/or by RRC signaling. As shown in the third diagram840, the non-reduced capability UE may receive a CD-SSB848and an NCD-SSB850within the initial downlink BWP844. The CD-SSB848may also configure a CORESET #0852within the initial downlink BWP844. The third diagram840also illustrates that the NCD-SSB850may overlap with the non-initial downlink BWP846.

In an example fourth diagram860, a cell may have a carrier bandwidth862. A non-reduced capability UE may be configured with an initial downlink BWP864and a non-initial downlink BWP866. The initial downlink BWP864may be configured by SIB1 and/or by RRC signaling. As shown in the fourth diagram860, the non-reduced capability UE may receive a CD-SSB868within the initial downlink BWP864. The CD-SSB868may also configure a CORESET #0870within the initial downlink BWP864. In the example fourth diagram860, the initial downlink BWP864and the non-initial downlink BWP866are non-overlapping. Additionally, the non-reduced capability UE may not receive an SSB within the non-initial downlink BWP866.

As shown in the example diagrams ofFIG.8, for a non-reduced capability UE, the initial downlink BWP includes at least the CD-SSB. The initial downlink BWP may also include the NCD-SSB (e.g., as shown in the example third diagram840). Additionally, for the non-reduced capability UE, the non-initial downlink BWP may include a CD-SSB (e.g., as shown in the first diagram800), may include an NCD-SSB (e.g., as shown in the first diagram800, the second diagram820, and the third diagram840), may include the CD-SSB and the NCD-SSB (e.g., as shown in the first diagram800), or may include no SSB (e.g., as shown in the fourth diagram860).

It may be appreciated that other examples may include additional or alternate combinations of a CD-SSB, an NCD-SSB, a CD-SSB and an NCD-SSB, and no SSB within an initial downlink BWP and a non-initial downlink BWP for a non-reduced capability UE.

In some aspects, CD-SSBs and NCD-SSBs transmitted by a same cell may share the same PSS/SSS sequences and PCI. The CD-SSBs and the NCD-SSBs may also include the same number/pattern of SS blocks, which may be indicated by an SSB position in burst field (e.g., which may be referred to as an “ssb-PositionInBurst” field or by another name) of SIB1 or may be indicated by a serving cell configuration common information element, which may be referred to as a “ServingCellConfigCommon” information element or by another name, of RRC signaling. The CD-SSB and the NCD-SSB may also have the same transmit power and the energy per resource element (EPRE) boosting ratio, at least for the purposes of RRM measurements and/or RLM measurements.

Within the channel bandwidth of a serving cell, the CD-SSB bursts and the NCD-SSB bursts may have the same periodicities or different periodicities. Additionally, a serving cell may use multiplexing when transmitting CD-SSB and NCD-SSB. For example, the CD-SSB bursts and the NCD-SSB bursts may be multiplexed in the time/frequency domain by time division multiplexing (TDM), frequency division multiplexing (FDM), or a hybrid of TDM and FDM.

FIG.9illustrates example diagrams showing multiplexing in time/frequency domain of CD-SSB bursts and NCD-SSB bursts, as presented herein. In the example diagrams, the CD-SSB bursts have a first periodicity (T1) and the NCD-SSB bursts have a second periodicity (T2). In some examples, the first periodicity and the second periodicity may be the same. In other examples, the first periodicity and the second periodicity may be different.

In the example ofFIG.9, a first diagram900illustrates CD-SSB bursts and NCD-SSB bursts being multiplexed by TDM. For example, a CD-SSB burst may include a first CD-SSB902aand a second CD-SSB902bhaving a first periodicity (T1). An NCD-SSB burst may include a first NCD-SSB904aand a second NCD-SSB904bhaving a second periodicity (T2). In the example first diagram900, the SSBs of the respective CD-SSB burst and the NCD-SSB burst are transmitted in a same frequency range but at non-overlapping times and, thus, the CD-SSB burst and the NCD-SSB burst are multiplexed by TDM.

A second diagram920illustrates CD-SSB bursts and NCD-SSB busts being multiplexed by FDM. For example, a CD-SSB burst may include a first CD-SSB922a, a second CD-SSB922b, and a third CD-SSB922chaving a first periodicity (T1). An NCD-SSB burst may include a first NCD-SSB924aand a second NCD-SSB924bhaving a second periodicity (T2). In the example second diagram920, the SSBs of the respective CD-SSB burst and the NCD-SSB burst are transmitted in non-overlapping frequency ranges, but may overlap in time. For example, the first CD-SSB922aand the first NCD-SSB924aoverlap in time and the third CD-SSB922cand the second NCD-SSB924boverlap in time and, thus, the CD-SSB burst and the NCD-SSB burst are multiplexed by FDM.

A third diagram940illustrates CD-SSB bursts and NCD-SSB busts being multiplexed by a hybrid of TDM and FDM. For example, a CD-SSB burst may include a first CD-SSB942aand a second CD-SSB942bhaving a first periodicity (T1). An NCD-SSB burst may include a first NCD-SSB944aand a second NCD-SSB944bhaving a second periodicity (T2). In the example third diagram940, the SSBs of the respective CD-SSB burst and the NCD-SSB burst are transmitted in non-overlapping frequency ranges (e.g., FDM) and at non-overlapping times (e.g., TDM) and, thus, the CD-SSB burst and the NCD-SSB burst are multiplexed by a hybrid of TDM and FDM.

In some aspects, a UE may receive a configuration for a downlink BWP based on a capability of the UE (e.g., a UE capability). A UE capability may refer to a UE class or type, such as a reduced capability UE or a higher capability UE. In some aspects, the UE capability may additionally, or alternatively, indicate one or more specific granular capabilities of the UE, such as whether the UE supports a particular duplex mode type, one or more supported frequency ranges, etc. Additionally, or alternatively, the UE may receive a configuration for a downlink BWP based on a type of the downlink BWP. In some examples, the configuration may indicate that the downlink BWP includes both the CD-SSB and the NCD-SSB from a serving cell. In some such examples, the UE may not be expected to measure both CD-SSB bursts and NCD-SSB bursts within the same slot. For example, the UE may measure one of the CD-SSB or the NCD-SSB in a slot and skip a measurement of the other of the CD-SSB or the NCD-SSB in the slot.

In some examples, the UE may operate in TDD or HD-FDD and there may be a collision between SSB reception and uplink transmission at the UE. A collision may include an SSB overlapping with an uplink transmission in the time domain. In some examples, a collision may include an SSB and an uplink transmission non-overlapping in the time domain, but a DL/UL switching gap at the UE for SSB reception and UL transmission may be insufficient. For example, the UE may not have sufficient time to switch between a receiving mode to receive the SSB and a transmitting mode to transmit the uplink transmission. In such examples in which a collision may occur, the UE may prioritize SSB measurement defined by a configuration over a dynamically scheduled uplink transmission (e.g., determined via DCI) or an uplink transmission configured by higher layers (e.g., determined via a MAC-CE and/or by RRC signaling). For SSB bursts not defined by the configuration, the UE may prioritize the uplink transmission instead. For example, for intra-frequency and inter-frequency measurements, a configuration of a measurement object may indicate the frequency and/or time resources and subcarrier spacing of reference signals to be measurements. The reference signals may include CD-SSB, NCD-SSB, or CSI-RS provided by serving cells and/or neighboring cells. A UE may be configured with multiple reference signals for measurement. Although a configuration for a measurement object may indicate or define a reference signal, the configuration may not indicate and/or may not define all reference signals configured for the UE. Thus, in some examples, the configuration for the measurement may define an SSB burst including CD-SSBs and/or NCD-SSBs. In other examples, the configuration for the measurement object may not define or indicate an SSB burst.

For example, the measurement object of the UE may be defined by system information and/or RRC signaling. The measurement object may include CD-SSB bursts, NCD-SSB bursts, or a combination of CD-SSB bursts and NCD-SSB bursts distributed across different slots. The periodicity, number, and/or type of the SSB (e.g., CD-SSB, NCD-SSB, or a hybrid) bursts to be measured by the UE may be configured by the network in the configuration.

For example, the UE may be operating in a TDD mode or an HD-FDD mode and receive scheduling for an uplink transmission. Based on a determination that SSB reception and the uplink transmission may collide (e.g., an overlap in the time domain or based on the switching gap associated with the uplink transmission), the UE may either prioritize measuring the SSB or transmitting the uplink transmission. For example, the UE may measure an SSB that is defined by a configuration and skip transmission of the uplink transmission based on the collision. In other examples, the UE may skip measurement of an SSB that is not defined by a configuration configured for the UE and may transmit the uplink transmission based on the collision.

In some examples, the configuration may indicate that the downlink BWP includes only the CD-SSB transmitted by the serving cell. In some such examples, the configuration may indicate that the downlink BWP does not include NCD-SSB transmitted by the serving cell or the configuration of the NCD-SSB may not be signaled to the UE. In examples in which the configuration indicates that the downlink BWP includes only the CD-SSB transmitted by the serving cell, the UE may not be expected to measure the NCD-SSB outside the active downlink BWP, the measurement being for one or more of cell selection/reselection, RRM, RLM, BFD, link recovery, a tracking loop, or AGC.

In some examples, the configuration may indicate that the downlink BWP includes no SSB or the configuration for the SSB may not be signaled to the UE. In examples in which the configuration does not indicate the SSB from a serving cell, the UE may switch to a different BWP to measure the CD-SSB from the serving cell if the UE is in an RRC idle state or in an RRC inactive state. If the UE is in an RRC connected state, the UE may switch to the different BWP to measure the CD-SSB and/or the NCD-SSB from the serving cell.

In some examples, there may be a BWP switch delay associated with the priority handling of the UE. For example, when the UE operates in a TDD mode or an HD-FDD mode, the BWP switch delay in the RRC idle state, the RRC inactive state, or the RRC connected state may be included in a time gap consideration for collision handling between SSB measurement and uplink transmission.

FIG.10illustrates an example communication flow1000between a network entity1002and a UE1004, as presented herein. One or more aspects described for the network entity1002may be performed by a component of a base station or a network entity, such as a CU, a DU, and/or an RU. In the illustrated example, the communication flow1000facilitates techniques for different SSB transmission in the initial/non-initial downlink BWP of different UE types.

Aspects of the network entity1002may be implemented by the base station102ofFIG.1and/or the base station310ofFIG.3. Aspects of the UE1004may be implemented by the UE104ofFIG.1and/or the UE350ofFIG.3. Although not shown in the illustrated example ofFIG.10, it may be appreciated that in additional or alternative examples, the network entity1002and/or the UE1004may be in communication with one or more other base stations or UEs.

In the illustrated example ofFIG.10, the UE1004transmits a capability1010that is obtained (e.g., received) by the network entity1002. The capability1010may indicate whether the network entity1002is a reduced capability UE or a non-reduced capability UE (e.g., a higher capability UE). The UE1004may transmit the capability1010via DCI, a MAC control element (MAC-CE), and/or RRC signaling. For example, the UE1004may transmit the capability1010via a UE capability information message, which may be referred to as a “UECapabilityInformation” message, or by any other name.

The network entity1002may configure serving cell measurements for one or more downlink BWPs. For example, the network entity1002may output (e.g., transmit) a configuration1020that is received by the UE1004. The network entity1002may output the configuration1020via system information and/or RRC signaling. The configuration may indicate that a downlink BWP configured for the1004/includes a CD-SSB, includes an NCD-SSB, or that the downlink BWP does not include an SSB (e.g., an SSB is absent in the downlink BWP). In some examples, the configuration1020may be based on a duplex mode type, a frequency range (e.g., FR1 or FR2), a type of the downlink BWP (e.g., an initial downlink BWP or a non-initial downlink BWP), and/or a UE capability of the UE1004(e.g., a reduced capability UE or a non-reduced capability UE) indicated by the capability1010. For example, if a serving cell supports paired spectrum (e.g., an FDD mode), the configuration1020may configure the UE1004to switch the downlink BWP (e.g., for intra-frequency or inter-frequency measurements of an SSB) without switching its uplink BWP. In examples, in which the UE1004has the capability to support the FD-FDD mode, the configuration1020may configure the UE1004to measure SSB on downlink without interrupting its uplink transmission. In examples, in which the serving cell supports unpaired spectrum (e.g., a TDD mode), or the UE1004has the capability to support the HD-FDD mode (e.g., and not the FD-FDD mode), the configuration1020may configure the UE1004so that simultaneous downlink measurement and uplink transmission is not scheduled.

In the illustrated example ofFIG.10, the UE1004may perform a monitoring procedure1030to monitor a measurement object based on the configuration1020. For example, the UE1004may monitor an initial downlink BWP or a non-initial downlink BWP. The UE1004may monitor for a CD-SSB and/or an NCD-SSB in a downlink BWP, or may know that the downlink BWP does not include an SSB.

As shown inFIG.10, the network entity1002may output a CD-SSB1034that is received by the UE1004. Additionally, or alternatively, the network entity1002may output an NCD-SSB1036that is received by the UE1004. The network entity1002may output the CD-SSB1034and/or the NCD-SSB1036in an initial downlink BWP and/or a non-initial downlink BWP.

In some examples, the UE1004may perform a measurement procedure1040to measure a measurement object based on the configuration1020for a downlink BWP. For example, the UE1004may measure SSBs received in a slot.

In some examples, the UE1004may perform an abstaining procedure1042to skip performing measurements on measurement objects based on the configuration1020for a downlink BWP. In some examples, the UE1004may perform the abstaining procedure1042when the configuration1020indicates that the downlink BWP does not include any SSBs.

In some examples, the UE1004may perform the measurement procedure1040to measure a first subset of SSBs received in a downlink BWP and may also perform the abstaining procedure1042to skip performing measurements on a second subset of SSBs in the downlink BWP.

In some examples, UE1004may be configured so that collision occasions may occur between receiving an SSB and transmitting an uplink transmission. For example, the network entity1002may output uplink scheduling information1022that is received by the UE1004. The uplink scheduling information1022may include semi-static or dynamic scheduling information for an uplink transmission1046.

In some examples, the UE1004may determine, based on the uplink scheduling information1022and the configuration1020that a collision may occur between an SSB and the uplink transmission1046. In some such examples, the UE1004may determine to perform the measurement procedure1040to measure the received SSB (e.g., the CD-SSB1034and/or the NCD-SSB1036) and may perform a skipping procedure1044to skip transmitting the uplink transmission1046. In other examples, the UE1004may determine, based on the occurrence of the collision occasion, to perform the abstaining procedure1042to skip performing the measurement on the received SSB and to transmit the uplink transmission1046.

In some examples, the UE1004may determine, based on the configuration1020, that a downlink BWP does not include an SSB. In some such examples, the UE1004may perform a switching procedure1032to switch to a different BWP. The UE1004may then perform the measurement procedure1040to measure an SSB in the different BWP. In some examples, if the UE1004is in an RRC idle state, the UE1004may perform the switching procedure1032to measure the CD-SSB1034in the different BWP. In other examples, if the UE1004is in an RRC connected state or an RRC inactive state, the UE1004may perform the switching procedure1032to measure the CD-SSB1034or the NCD-SSB1036in the different BWP. In some examples, a BWP switch delay associated with switching to the different BWP to measure the CD-SSB1034or the NCD-SSB1036may be included in a time gap consideration with respect to collision occasions.

In some examples, the uplink transmission1046may include a PUSCH, a PUCCH, or an SRS. In some examples, the UE1004may fully skip transmission or partially skip transmission of the uplink transmission1046based in part on a switching gap. The switching gap may be determined based on a minimum time from reception to transmission (NRx-Tx) or a minimum time from transmission to reception (NTx-Rx).

The UE1004may fully skip the transmission (e.g., via the skipping procedure1044) by not transmitting the PUSCH or the PUCCH. For example, the UE1004may skip transmitting PUSCH or PUCCH if a last symbol of the PUSCH transmission or PUCCH transmission overlaps with the switching gap prior to a first symbol of the next earliest SSB. The UE1004may additionally, or alternatively, skip transmitting PUSCH or PUCCH if a first symbol of the PUSCH transmission or PUCCH transmission overlaps with the switching gap after a last symbol of the previous latest SSB.

The UE1004may partially skip the transmission (e.g., the via the skipping procedure1044) by not transmitting SRS. For example, the UE1004may not transmit SRS in symbols that overlap with the switching gap prior to a first symbol of the next earliest SSB. The UE1004may additionally, or alternatively, skip transmitting SRS in symbols that overlap with the switching gap after a last symbol of the previous latest SSB.

FIG.11is a flowchart1100of a method of wireless communication. The method may be performed by a UE (e.g., the UE104, and/or an apparatus1304ofFIG.13). The method may facilitate improving synchronization and measurements for reduced capability UEs.

At1102, the UE indicates a UE capability to a network, as described in connection with the capability1010ofFIG.10. For example, the UE may be a reduced capability or a higher capability UE. The indicating of the capability, at1102, may be performed by a cellular RF transceiver1322/the prioritization component198of the apparatus1304ofFIG.13.

At1104, the UE receives a configuration for a measurement object and a downlink BWP in system information or an RRC message, as described in connection with the configuration1020ofFIG.10. The configuration may indicate that the downlink BWP includes a CD-SSB, includes an NCD-SSB, or that an SSB is absent. The configuration for the measurement object and the downlink BWP may be based at least on one or more of a duplex mode type, a frequency range, a type of the downlink BWP, or the UE capability. The receiving of the configuration, at1104, may be performed by the cellular RF transceiver1322/the prioritization component198of the apparatus1304ofFIG.13.

FIG.12is a flowchart1200of a method of wireless communication. The method may be performed by a UE (e.g., the UE104, and/or an apparatus1304ofFIG.13). The method may facilitate improving synchronization and measurements for reduced capability UEs.

At1202, the UE indicates a UE capability to a network, as described in connection with the capability1010ofFIG.10. For example, the UE may be a reduced capability or a higher capability UE. The indicating of the capability, at1202, may be performed by a cellular RF transceiver1322/the prioritization component198of the apparatus1304ofFIG.13.

At1204, the UE receives a configuration for a measurement object and a downlink BWP in system information or an RRC message, as described in connection with the configuration1020ofFIG.10. The configuration may indicate that the downlink BWP includes a CD-SSB, includes an NCD-SSB, or that an SSB is absent. The configuration for the measurement object and the downlink BWP may be based at least on one or more of a duplex mode type, a frequency range, a type of the downlink BWP, or the UE capability. For example, the UE configuration may be different based on the UE being a reduced capability UE or a higher capability UE and/or may be different if the DL BWP is an initial DL BWP or a non-initial BWP. As an example, the configuration may be for a duplex mode including TDD, HD-FDD, or FD-FDD. If the UE supports FD-FDD, the UE may support simultaneous SSB measurement and UL transmission without collision handling. As an example, the frequency range may be FR1, FR2, a licensed spectrum or an unlicensed spectrum. The receiving of the configuration, at1204, may be performed by the cellular RF transceiver1322/the prioritization component198of the apparatus1304ofFIG.13.

In some aspects, the UE may have a reduced capability and the configuration, at1204, may be for an initial DL BWP that includes one of the CD-SSB or the NCD-SSB or the configuration may be for the initial DL BWP that does not include the SSB of the serving cell, as described in connection with the examples ofFIG.7. In some aspects, the UE may have a reduced capability and the configuration may be for a non-initial DL BWP that includes one of the CD-SSB or the NCD-SSB or the configuration may be for the non-initial DL BWP that does not include the SSB of the serving cell, as described in connection with the examples ofFIG.7.

In some aspects, the UE may be a higher capability UE and the configuration may be for an initial DL BWP that includes the CD-SSB or that includes the CD-SSB and the NCD-SSB of the serving cell, as described in connection with the examples ofFIG.8. In some aspects, the UE may be a higher capability UE and the configuration may be for a non-initial DL BWP for the UE in an RRC connected state and includes at least one of the CD-SSB or the NCD-SSB or the configuration may be for the non-initial DL BWP that does not include the SSB of the serving cell, as described in connection with the examples ofFIG.8.

In some aspects, the configuration (e.g., at1204) may be for the DL BWP that includes the CD-SSB and the NCD-SSB from a serving cell, the CD-SSB and the NCD-SSB sharing at least one of: a same primary synchronization signal sequence, a same secondary synchronization signal sequence, a PCI, a same number of SSBs transmitted in each SSB burst, a same pattern of SSBs transmitted in each SSB burst, a same transmission power, a same periodicity of an SSB burst, a same QCL resource, a same numerology for one or multiple physical signals or physical channels of the SSBs, or a same EPRE boosting ratio for the one or multiple physical signals or physical channels of the SSBs.

In some examples, CD-SSB bursts may be multiplexed in at least one of time or frequency with NCD-SSB bursts in the DL BWP, as described in connection with the examples ofFIG.9. For example, SSB includes PSS, SSS and PBCH (which may include DMRS), e.g., as described in connection withFIG.2C. In some aspects, a same numerology (e.g., subcarrier spacing and cyclic prefix) can be applied to all or a subset of the physical signals (PSS, SSS, DMRS of PBCH) and the physical channels (PBCH data REs without DMRS). In some aspects, EPRE boosting can be applied to all or a subset of the physical signals (PSS, SSS, DMRS of PBCH) and the physical channels (PBCH data REs without DMRS).

In some aspects, the configuration may be for the DL BWP including both the CD-SSB and the NCD-SSB from a serving cell, and the measurement object of the serving cell. In some such examples, the UE may, at1206, measure all or part of SSBs in one of the CD-SSB bursts or the NCD-SSB bursts in a slot, as described in connection with the measurement procedure1040ofFIG.10. The UE may also skip, at1208, a measurement of all or part of the SSBs in the other of the CD-SSB burst or the NCD-SSB burst in the slot, as described in connection with the abstaining procedure1042ofFIG.10. In some aspects, one SSB burst may include multiple SSBs, which may span multiple slots. For example, an SSB burst in FR1 may include up to eight SSBs or up to 64 for higher frequencies. Depending on the configuration of the measurement object, UE may selectively measure a subset of the SSBs transmitted in a SSB burst. The performing of1206and1208may be performed by the prioritization component198of the apparatus1304ofFIG.13.

In some aspects, the UE may operate, at1203, in a TDD mode or a HD-FDD mode. The UE may receive, at1210, scheduling (e.g., semi-static or dynamic scheduling information) for an uplink transmission, as described in connection with the uplink scheduling information1022ofFIG.10. As an example, semi-static UL scheduling may include the cell-specific configuration by SI, or a UE-specific configuration by a dedicated RRC or MAC-CE. Dynamic UL scheduling may include a dynamic UL grant in PDCCH or PDSCH (e.g. random access response for msg3). The uplink transmission may overlap in time, or a switching gap may overlap in time, with measurement of an SSB. The UE may receive, at1212, a measurement object configuration defined for the SSB of the serving cell, where the SSBs have an insufficient switching gap associated with the scheduled uplink transmission. An insufficient switching gap may correspond to one or more of SSBs that overlap with the UL transmission or the SSBs do not overlap with UL transmission. The UE may measure, at1206, a measurement object defined SSB, the SSB having an overlap in a time domain with one or more of the uplink transmission or a switching gap associated with the uplink transmission. The UE may skip, at1214, transmission of the uplink transmission fully or partially based at least on the UE capability for UL cancellation (e.g., whether the UE can cancel the UL transmission partially or fully may be an optional UE capability) and the switching gap between DL and UL in the time domain, as described in connection with the skipping procedure1044ofFIG.10. Aspects of1203,1206,1212, and1214may be performed by the prioritization component198of the apparatus1304ofFIG.13.

In some aspects, the UE may operate, at1203, in a TDD mode or a HD-FDD mode. The UE may receive, at1210, scheduling (e.g., semi-static or dynamic scheduling information) for an uplink transmission that overlaps with SSBs of an SSB burst that is not defined by a measurement configuration for the UE, as described in connection with the uplink scheduling information1022ofFIG.10. The UE may skip, at1216, measurement of one or multiple SSBs of an SSB burst that is not defined by a configuration configured for the UE, as described in connection with the abstaining procedure1042ofFIG.10. The UE may transmit, at1218, the uplink transmission that overlaps in time with the SSB, as described in connection with the uplink transmission1046ofFIG.10. Aspects of1203,1210,1216, and1218may be performed by the prioritization component198of the apparatus1304ofFIG.13.

In some aspects, the configuration, at1204, may be for the DL BWP that includes the CD-SSB and does not include the NCD-SSB from a serving cell, as described in connection with the initial downlink BWP704and the non-initial downlink BWP746ofFIG.7, and/or the initial downlink BWP804, the initial downlink BWP824, and the initial downlink BWP864ofFIG.8. The UE may skip, at1220, a measurement of the other of the NCD-SSB, as described in connection with the abstaining procedure1042ofFIG.10. The measurement may be for one or more of cell selection, cell reselection, radio resource management, radio link monitoring, beam management, UL resource selection, power control, timing advance validation, link recovery, a tracking loop, or automatic gain control. Aspects of1220may be performed by the prioritization component198of the apparatus1304ofFIG.13.

In some aspects, the configuration, at1204, may be for the DL BWP that does not include the SSB from a serving cell, as described in connection with the initial downlink BWP724, the initial downlink BWP764, and the non-initial downlink BWP766ofFIG.7, and/or the non-initial downlink BWP866ofFIG.8. The UE may switch, at1222, to a different BWP to measure the CD-SSB from the serving cell if the UE is in an RRC idle state, and the UE may switch, at1224, to the different BWP to measure the CD-SSB or the NCD-SSB from the serving cell if the UE is in an RRC connected state or an RRC inactive state, as described in connection with the switching procedure1032ofFIG.10. Aspects of1222and1224may be performed by the prioritization component198of the apparatus1304ofFIG.13.

In some aspects, the UE may operate, at1203, in a TDD mode or a HD-FDD mode, and a BWP switch delay associated with switching to the different BWP to measure the CD-SSB or the NCD-SSB may be included in a time gap consideration for at least measurement object configuration and collision handling between SSB measurement and uplink transmission. Aspects of1203may be performed by the prioritization component198of the apparatus1304ofFIG.13.

FIG.13is a diagram1300illustrating an example of a hardware implementation for an apparatus1304. The apparatus1304may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus1304may include a cellular baseband processor1324(also referred to as a modem) coupled to one or more transceivers (e.g., a cellular RF transceiver1322). The cellular baseband processor1324may include on-chip memory1324′. In some aspects, the apparatus1304may further include one or more subscriber identity modules (SIM) cards1320and an application processor1306coupled to a secure digital (SD) card1308and a screen1310. The application processor1306may include on-chip memory1306′. In some aspects, the apparatus1304may further include a Bluetooth module1312, a WLAN module1314, an SPS module1316(e.g., GNSS module), one or more sensor modules1318(e.g., barometric pressure sensor/altimeter; motion sensor such as inertial measurement unit (IMU), gyroscope, and/or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and/or other technologies used for positioning), additional memory modules1326, a power supply1330, and/or a camera1332. The Bluetooth module1312, the WLAN module1314, and the SPS module1316may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module1312, the WLAN module1314, and the SPS module1316may include their own dedicated antennas and/or utilize one or more antennas1380for communication. The cellular baseband processor1324communicates through transceiver(s) (e.g., the cellular RF transceiver1322) via one or more antennas1380with the UE104and/or with an RU associated with a network entity1302. The cellular baseband processor1324and the application processor1306may each include a computer-readable medium/memory, such as the on-chip memory1324′, and the on-chip memory1306′, respectively. The additional memory modules1326may also be considered a computer-readable medium/memory. Each computer-readable medium/memory (e.g., the on-chip memory1324′, the on-chip memory1306′, and/or the additional memory modules1326) may be non-transitory. The cellular baseband processor1324and the application processor1306are each responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor1324/application processor1306, causes the cellular baseband processor1324/application processor1306to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor1324/application processor1306when executing software. The cellular baseband processor1324/application processor1306may be a component of the UE350and may include the memory360and/or at least one of the TX processor368, the RX processor356, and the controller/processor359. In one configuration, the apparatus1304may be a processor chip (modem and/or application) and include just the cellular baseband processor1324and/or the application processor1306, and in another configuration, the apparatus1304may be the entire UE (e.g., see the UE350ofFIG.3) and include the additional modules of the apparatus1304.

As discussed supra, the prioritization component198is configured to indicate a UE capability to a network; and receive a configuration for a measurement object and a DL BWP in system information or a RRC message, the configuration indicating that the DL BWP includes a CD-SSB, includes a NCD-SSB, or that an SSB is absent, the configuration for the measurement object and the DL BWP being based at least on one or more of a duplex mode type, a frequency range, a type of the DL BWP, or the UE capability.

The prioritization component198may be within the cellular baseband processor1324, the application processor1306, or both the cellular baseband processor1324and the application processor1306. The prioritization component198may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.

As shown, the apparatus1304may include a variety of components configured for various functions. For example, the prioritization component198may include one or more hardware components that perform each of the blocks of the algorithm in the flowcharts ofFIG.11and/orFIG.12.

In one configuration, the apparatus1304, and in particular the cellular baseband processor1324and/or the application processor1306, includes means for indicating a UE capability to a network. The example apparatus1304also includes means for receiving a configuration for a measurement object and a DL BWP in system information or a RRC message, the configuration indicating that the DL BWP includes a CD-SSB, includes a NCD-SSB, or that an SSB is absent, the configuration for the measurement object and the DL BWP being based at least on one or more of a duplex mode type, a frequency range, a type of the DL BWP, or the UE capability.

In another configuration, the example apparatus1304also includes means for measuring all or part of SSBs in one of a CD-SSB burst or an NCD-SSB burst in a slot. The example apparatus1304also includes means for skipping a measurement of all or part of the SSBs in a different one of the CD-SSB burst or the NCD-SSB burst in the slot.

In another configuration, the example apparatus1304also includes means for operating in a TDD mode or a HD-FDD mode. The example apparatus1304also includes means for receiving semi-static or dynamic scheduling information for an uplink transmission. The example apparatus1304also includes means for receiving a measurement object configuration defined for the SSB of the serving cell, where SSBs have an insufficient switching gap associated with the uplink transmission. The example apparatus1304also includes means for skipping transmission of the uplink transmission fully or partially based at least on a UE capability for UL cancellation and the insufficient switching gap between DL and UL in a time domain.

In another configuration, the example apparatus1304also includes means for operating in a TDD mode or a HD-FDD mode. The example apparatus1304also includes means for receiving semi-static or dynamic scheduling information for an uplink transmission, which overlaps with SSBs of a SSB burst that is not defined by a measurement configuration for the UE. The example apparatus1304also includes means for skipping measurement of one or multiple SSBs of the SSB burst that is not defined by the configuration configured for the UE. The example apparatus1304also includes means for transmitting the uplink transmission.

In another configuration, the example apparatus1304also includes means for skipping a measurement of another NCD-SSB outside the DL BWP, the measurement being for one or more of cell selection, cell reselection, radio resource management, radio link monitoring, beam management, UL resource selection, power control, timing advance validation, link recovery, a tracking loop, or automatic gain control.

In another configuration, the example apparatus1304also includes means for switching to a different BWP to measure the CD-SSB from the serving cell if the UE is in an RRC idle state. The example apparatus1304also includes means for switching to the different BWP to measure the CD-SSB or the NCD-SSB from the serving cell if the UE is in an RRC connected state or an RRC inactive state.

In another configuration, the example apparatus1304also includes means for operating in a TDD mode or a HD-FDD mode, where a BWP switch delay associated with switching to the different BWP to measure the CD-SSB or the NCD-SSB is included in a time gap consideration for at least a measurement object configuration and collision handling between SSB measurement and uplink transmission.

The means may be the prioritization component198of the apparatus1304configured to perform the functions recited by the means. As described supra, the apparatus1304may include the TX processor368, the RX processor356, and the controller/processor359. As such, in one configuration, the means may be the TX processor368, the RX processor356, and/or the controller/processor359configured to perform the functions recited by the means.

FIG.14is a flowchart1400of a method of wireless communication. The method may be performed by a network entity (e.g., the base station102, and/or a network entity1602ofFIG.16). The method may facilitate improving synchronization and measurements for reduced capability UEs.

At1402, the network entity receives an indication of a UE capability of at least one UE, as described in connection with the capability1010ofFIG.10. For example, the UE may be a reduced capability or a higher capability UE. The receiving of the indication, at1402, may be performed by the configuration component199of the network entity1602ofFIG.16.

At1404, the network entity configures serving cell measurement and one or more DL BWPs, as described in connection with the configuration1020ofFIG.10. In some examples, the configuration for each downlink BWP may be based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability. In some examples, based on one or more of the duplex mode type, the frequency range, the DL BWP type, or the UE capability, the configuration of each DL BWP and a measurement object for a serving cell may include a CD-SSB, may include an NCD-SSB, or may not include an SSB of the serving cell, as described in connection with the examples ofFIG.7andFIG.8. The configuring, at1404, may be performed by the configuration component199of the network entity1602ofFIG.16.

FIG.15is a flowchart1500of a method of wireless communication. The method may be performed by a network entity (e.g., the base station102, and/or a network entity1602ofFIG.16). The method may facilitate improving synchronization and measurements for reduced capability UEs.

At1502, the network entity receives an indication of a UE capability of at least one UE, as described in connection with the capability1010ofFIG.10. For example, the UE may be a reduced capability or a higher capability UE. The receiving of the indication, at1502, may be performed by the configuration component199of the network entity1602ofFIG.16.

At1504, the network entity configures serving cell measurement and one or more DL BWPs, as described in connection with the configuration1020ofFIG.10. In some examples, the configuration for each downlink BWP may be based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability. In some examples, based on one or more of the duplex mode type, the frequency range, the DL BWP type, or the UE capability, the configuration of each DL BWP and a measurement object for a serving cell may include a CD-SSB, may include an NCD-SSB, or may not include an SSB of the serving cell, as described in connection with the examples ofFIG.7andFIG.8. The configuring, at1504, may be performed by the configuration component199of the network entity1602ofFIG.16.

In some examples, the network entity may transmit, at1506, the configuration for each downlink BWP for a serving cell in system information or an RRC message, as described in connection with the configuration1020ofFIG.10. The transmitting, at1506, may be performed by the configuration component199of the network entity1602ofFIG.16.

As an example, the UE capability may be a reduced capability and the configuration may be for an initial DL BWP that includes one of the CD-SSB or the NCD-SSB or the configuration may be for the initial DL BWP that does not include the SSB of the serving cell, as described in connection with the examples ofFIG.7.

In some aspects, the UE capability may be a reduced capability and the configuration may be for a non-initial DL BWP that includes one of the CD-SSB or the NCD-SSB or the configuration may be for the non-initial DL BWP that does not include the SSB of the serving cell, as described in connection with the examples ofFIG.7.

In some aspects, the UE capability may be a higher capability and the configuration may be for an initial DL BWP that includes the CD-SSB or that includes the CD-SSB and the NCD-SSB of the serving cell, as described in connection with the examples ofFIG.8. In some aspects, the UE capability may be a higher capability and the configuration may be for a non-initial DL BWP for the UE in an RRC connected state and includes at least one of the CD-SSB or the NCD-SSB or the configuration may be for the non-initial DL BWP that does not include the SSB of the serving cell, as described in connection with the examples ofFIG.8.

In some aspects, the configuration, at1504, may be for a first DL BWP that includes a CD-SSB and an NCD-SSB from a serving cell, the CD-SSB and the NCD-SSB sharing at least one of: a same primary synchronization signal sequence, a same secondary synchronization signal sequence, a PCI, a same number of SSBs transmitted in each SSB burst, a same pattern of SSBs transmitted in each SSB burst, a same transmission power, a same periodicity of an SSB burst, a same QCL resource, a same numerology for one or multiple physical signals or physical channels of the SSBs, or a same EPRE boosting ratio for the one or multiple physical signals or physical channels of the SSBs.

In some examples, the network entity may multiplex, at1508, CD-SSB bursts in at least one of time or frequency with NCD-SSB bursts in the first DL BWP, as described in connection with the examples ofFIG.9. For example, SSB includes PSS, SSS and PBCH (which may include DMRS), e.g., as described in connection withFIG.2C. In some aspects, a same numerology (e.g., subcarrier spacing and cyclic prefix) can be applied to all or a subset of the physical signals (PSS, SSS, DMRS of PBCH) and the physical channels (PBCH data REs without DMRS). In some aspects, EPRE boosting can be applied to all or a subset of the physical signals (PSS, SSS, DMRS of PBCH) and the physical channels (PBCH data REs without DMRS).

In some aspects, the network entity may transmit, at1510, a CD-SSB or an NCD-SSB on-demand in a first DL BWP of the one or more DL BWPs upon receiving a request of a first UE in an RRC idle, inactive or connected state, and where the first UE has a reduced or higher capability and is allowed to access the cell, as described in connection with the CD-SSB1034and/or the NCD-SSB1036ofFIG.13.

FIG.16is a diagram1600illustrating an example of a hardware implementation for a network entity1602. The network entity1602may be a BS, a component of a BS, or may implement BS functionality. The network entity1602may include at least one of a CU1610, a DU1630, or an RU1640. For example, depending on the layer functionality handled by the configuration component199, the network entity1602may include the CU1610; both the CU1610and the DU1630; each of the CU1610, the DU1630, and the RU1640; the DU1630; both the DU1630and the RU1640; or the RU1640. The CU1610may include a CU processor1612. The CU processor1612may include on-chip memory1612′. In some aspects, may further include additional memory modules1614and a communications interface1618. The CU1610communicates with the DU1630through a midhaul link, such as an F1 interface. The DU1630may include a DU processor1632. The DU processor1632may include on-chip memory1632′. In some aspects, the DU1630may further include additional memory modules1634and a communications interface1638. The DU1630communicates with the RU1640through a fronthaul link. The RU1640may include an RU processor1642. The RU processor1642may include on-chip memory1642′. In some aspects, the RU1640may further include additional memory modules1644, one or more transceivers1646, antennas1680, and a communications interface1648. The RU1640communicates with the UE104. The on-chip memories (e.g., the on-chip memory1612′, the on-chip memory1632′, and/or the on-chip memory1642′) and/or the additional memory modules (e.g., the additional memory modules1614, the additional memory modules1634, and/or the additional memory modules1644) may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. Each of the CU processor1612, the DU processor1632, the RU processor1642is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the processor(s) when executing software.

As discussed supra, the configuration component199is configured to receive an indication of a UE capability of at least one UE. The configuration component199may also be configured to configure serving cell measurement and one or more DL BWPs, a configuration for each DL BWP being based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

The configuration component199may be within one or more processors of one or more of the CU1610, DU1630, and the RU1640. The configuration component199may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.

The network entity1602may include a variety of components configured for various functions. For example, the configuration component199may include one or more hardware components that perform each of the blocks of the algorithm in the flowcharts ofFIG.14and/orFIG.15.

In one configuration, the network entity1602includes means for receiving an indication of a UE capability of at least one UE. The example network entity1602also includes means for configuring serving cell measurement and one or more DL BWPs, a configuration for each DL BWP being based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

In another configuration, the example network entity1602also includes means for multiplexing CD-SSB bursts in at least one of time or frequency with NCD-SSB bursts in the DL BWP.

In another configuration, the example network entity1602also includes means for transmitting a CD-SSB or an NCD-SSB on-demand in a first DL BWP of the one or more DL BWPs upon receiving a request of a first UE in an RRC idle, inactive or connected state, where the first UE has a reduced or higher capability and is allowed to access a serving cell.

In another configuration, the example network entity1602also includes means for transmitting the configuration for each DL BWP for a serving cell in system information or an RRC message.

The means may be the configuration component199of the network entity1602configured to perform the functions recited by the means. As described supra, the network entity1602may include the TX processor316, the RX processor370, and the controller/processor375. As such, in one configuration, the means may be the TX processor316, the RX processor370, and/or the controller/processor375configured to perform the functions recited by the means.

Aspects disclosed herein provide techniques for different SSB transmission in the initial/non-initial downlink BWP of different UE types (e.g., a reduced capability UE or a non-reduced capability UE) when a cell allows different UE types to access the cell. That is, when a cell supports reduced capability UE and non-reduced capability UE co-existence, different SSB transmissions in the initial/non-initial downlink BWP of the different UE type may be supported. Additionally, aspects disclosed herein provide priority rules for SSB-based measurements (e.g., for RO selection, time/frequency tracking, link recovery, RRM measurements, RLM measurements, BFD measurements, and other tasks).

Aspect 1 is a method of wireless communication at a UE, comprising: indicating a UE capability to a network; and receiving a configuration for a measurement object and a DL BWP in system information or a RRC message, the configuration indicating that the DL BWP includes a CD-SSB, includes a NCD-SSB, or that an SSB is absent, the configuration for the measurement object and the DL BWP being based at least on one or more of a duplex mode type, a frequency range, a type of the DL BWP, or the UE capability.

Aspect 2 is the method of aspect 1, further including that the UE has a reduced capability and the configuration is for an initial DL BWP that includes one of the CD-SSB or the NCD-SSB or the configuration is for the initial DL BWP that does not include the SSB of a serving cell.

Aspect 3 is the method of aspect 1, further including that the UE has a reduced capability and the configuration is for a non-initial DL BWP that includes one of the CD-SSB or the NCD-SSB or the configuration is for the non-initial DL BWP that does not include the SSB of a serving cell.

Aspect 4 is the method of aspect 1, further including that the UE is a higher capability UE and the configuration is for an initial DL BWP that includes the CD-SSB or that includes the CD-SSB and the NCD-SSB of a serving cell.

Aspect 5 is the method of aspect 1, further including that the UE is a higher capability UE and the configuration is for a non-initial DL BWP for the UE in a RRC connected state and includes at least one of the CD-SSB or the NCD-SSB or the configuration is for the non-initial DL BWP that does not include the SSB of a serving cell.

Aspect 6 is the method of any of aspects 1 to 5, further including that the configuration is for the DL BWP that includes the CD-SSB and the NCD-SSB from a serving cell, the CD-SSB and the NCD-SSB sharing at least one of: a same primary synchronization signal sequence, a same secondary synchronization signal sequence, a PCI, a same number of SSBs transmitted in each SSB burst, a same pattern of SSBs transmitted in each SSB burst, a same transmission power, a same periodicity of an SSB burst, a same QCL resource, a same numerology for one or multiple physical signals or physical channels of the SSBs, or a same EPRE boosting ratio for the one or multiple physical signals or physical channels of the SSBs.

Aspect 7 is the method of aspect 6, further including that CD-SSB bursts are multiplexed in at least one of time or frequency with NCD-SSB bursts in the DL BWP.

Aspect 8 is the method of any of aspects 1 to 7, further including that the configuration is for the DL BWP including both the CD-SSB and the NCD-SSB from a serving cell, and the measurement object of the serving cell, the method further including: measuring all or part of SSBs in one of a CD-SSB burst or an NCD-SSB burst in a slot; and skipping a measurement of all or part of the SSBs in a different one of the CD-SSB burst or the NCD-SSB burst in the slot.

Aspect 9 is the method of any of aspects 1 to 8, further including: operating in a TDD mode or a HD-FDD mode; receiving semi-static or dynamic scheduling information for an uplink transmission; receiving a measurement object configuration defined for the SSB of a serving cell, where SSBs have an insufficient switching gap associated with the uplink transmission; and skipping transmission of the uplink transmission fully or partially based at least on a UE capability for UL cancellation and the insufficient switching gap between DL and UL in a time domain.

Aspect 10 is the method of any of aspects 1 to 8, further including: operating in a TDD mode or a HD-FDD mode; receiving semi-static or dynamic scheduling information for an uplink transmission that overlaps with SSBs of an SSB burst that is not defined by a measurement configuration for the UE; skipping measurement of one or multiple SSBs of the SSB burst that is not defined by the measurement object configured for the UE; and transmitting the uplink transmission.

Aspect 11 is the method of any of aspects 1 to 5, further including that the configuration is for the DL BWP includes the CD-SSB and does not include the NCD-SSB from a serving cell, the method further including: skipping a measurement of another NCD-SSB outside the DL BWP, the measurement being for one or more of cell selection, cell reselection, radio resource management, radio link monitoring, beam management, UL resource selection, power control, timing advance validation, link recovery, a tracking loop, or automatic gain control.

Aspect 12 is the method of any of aspects 1 to 5, further including that the configuration is for the DL BWP does not include the SSB from a serving cell, the method further includes: switching to a different BWP to measure the CD-SSB from the serving cell if the UE is in an RRC idle state; and switching to the different BWP to measure the CD-SSB or the NCD-SSB from the serving cell if the UE is in an RRC connected state or an RRC inactive state.

Aspect 13 is the method of any of aspects 1 to 12, further including: operating in a TDD mode or a HD-FDD mode, where a BWP switch delay associated with switching to the different BWP to measure the CD-SSB or the NCD-SSB is included in a time gap consideration for at least a measurement object configuration and collision handling between SSB measurement and uplink transmission.

Aspect 14 is an apparatus for wireless communication at a UE including at least one processor coupled to a memory and configured to implement any of aspects 1 to 13.

In aspect 15, the apparatus of aspect 14 further includes at least one antenna coupled to the at least one processor.

In aspect 16, the apparatus of aspect 14 or 15 further includes a transceiver coupled to the at least one processor.

Aspect 17 is an apparatus for wireless communication including means for implementing any of aspects 1 to 13.

In aspect 18, the apparatus of aspect 17 further includes at least one antenna coupled to the means to perform the method of any of aspects 1 to 13.

In aspect 19, the apparatus of aspect 17 or 18 further includes a transceiver coupled to the means to perform the method of any of aspects 1 to 13.

Aspect 20 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 1 to 13.

Aspect 21 is a method of wireless communication at a network entity, including: receiving an indication of a UE capability of at least one UE; and configuring serving cell measurement and one or more DL BWPs, a configuration for each DL BWP being based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

Aspect 22 is the method of aspect 21, further including that, based on one or more of the duplex mode type, the frequency range, the DL BWP type, or the UE capability, the configuration of each DL BWP and a measurement object for a serving cell includes a CD-SSB, includes an NCD-SSB, or does not include an SSB of the serving cell.

Aspect 23 is the method of any of aspects 21 and 22, further including that the UE capability is a reduced capability and the configuration is for an initial DL BWP that includes one of the CD-SSB or the NCD-SSB or the configuration is for the initial DL BWP that does not include the SSB of the serving cell.

Aspect 24 is the method of any of aspects 21 and 22, further including that the UE capability is a reduced capability and the configuration is for a non-initial DL BWP that includes one of the CD-SSB or the NCD-SSB or the configuration is for the non-initial DL BWP that does not include the SSB of the serving cell.

Aspect 25 is the method of any of aspects 21 and 22, further including that the UE capability is a higher capability and the configuration is for an initial DL BWP that includes the CD-SSB or that includes the CD-SSB and the NCD-SSB of the serving cell.

Aspect 26 is the method of any of aspects 21 and 22, further including that the UE capability is a higher capability and the configuration is for a non-initial DL BWP for the at least one UE in an RRC connected state and includes at least one of the CD-SSB or the NCD-SSB or the configuration is for the non-initial DL BWP that does not include the SSB of the serving cell.

Aspect 27 is the method of any of aspects 21 to 26, further including that the configuration is for a first DL BWP of the one or more DL BWPs that includes a CD-SSB and a NCD-SSB from a serving cell, the CD-SSB and the NCD-SSB sharing at least one of: a same primary synchronization signal sequence, a same secondary synchronization signal sequence, a PCI, a same number of SSBs transmitted in each SSB burst, a same pattern of SSBs transmitted in each SSB burst, a same transmission power, a same periodicity of an SSB burst, a same quasi co-location (QCL) resource, a same numerology for one or multiple physical signals or physical channels of the SSBs, or a same EPRE boosting ratio for the one or multiple physical signals or physical channels of the SSBs.

Aspect 28 is the method of any of aspects 21 to 27, further including: multiplexing CD-SSB bursts in at least one of time or frequency with NCD-SSB bursts in the first DL BWP.

Aspect 29 is the method of any of aspects 21 to 24, 26, and 27, further including: transmitting a CD-SSB or an NCD-SSB on-demand in a first DL BWP of the one or more DL BWPs upon receiving a request of a first UE in an RRC idle, inactive or connected state, where the first UE has a reduced or higher capability and is allowed to access a serving cell.

Aspect 30 is the method of any of aspects 21 to 29, further including: transmitting the configuration for each DL BWP for a serving cell in system information or an RRC message.

Aspect 31 is an apparatus for wireless communication at a network entity including at least one processor coupled to a memory and configured to implement any of aspects 21 to 30.

In aspect 32, the apparatus of aspect 31 further includes at least one antenna coupled to the at least one processor.

In aspect 33, the apparatus of aspect 31 or 32 further includes a transceiver coupled to the at least one processor.

Aspect 34 is an apparatus for wireless communication including means for implementing any of aspects 21 to 30.

In aspect 35, the apparatus of aspect 34 further includes at least one antenna coupled to the means to perform the method of any of aspects 21 to 30.

In aspect 36, the apparatus of aspect 34 or 35 further includes a transceiver coupled to the means to perform the method of any of aspects 21 to 30.

Aspect 37 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 21 to 30.