Techniques for facilitating priority rules for measurements based on cell-defined SSBS and / or non-cell-defined SSBS - Patent Application 20070123333

Abstract

Disclosed herein are apparatuses, methods, and computer-readable media for facilitating priority rules for measurements based on CD-SSB and / or NCD-SSB. An exemplary method for wireless communication in a UE includes indicating UE capabilities to a network. The exemplary method also includes receiving a configuration of measurement objects and DL BWPs, the configuration indicating that the DL BWP includes CD-SSB, includes NCD-SSB, or that no SSB is present. The configuration of measurement objects and DL BWPs may be based at least on one or more of a duplex mode type, a frequency range, a type of DL BWP, or a UE capability.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority to PCT Application No. PCT / CN2021 / 135450, filed December 3, 2021, entitled "TECHNIQUES TO FACILITATE PRIORITY RULES FOR MEASUREMENTS BASED ON CELL-DEFINING SSBS AND / OR NON-CELL-DEFINING SSBS," the entire contents of which are expressly incorporated by reference into this specification.

[0002] The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems that utilize cell-defined (CD) synchronization signal blocks (SSBs) and non-cell-defined (NCD) SSBs. [Background technology]

[0003]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004]

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that allows various wireless devices to communicate at a city, country, region, or even global level. An exemplary telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0005]

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all aspects contemplated. This summary is not intended to identify key or critical elements of all aspects, nor is it intended to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006]

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

[0007]

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

[0008] To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of only a few of the various ways in which the principles of the various aspects may be employed. [Brief description of the drawings]

[0009] [Figure 1]

[0009] FIG. 1 illustrates an example of a wireless communication system and access network. [Figure 2A]

[0010] FIG. 2 illustrates an example of a first frame in accordance with various aspects of the present disclosure. [Figure 2B]

[0011] FIG. 1 illustrates an example of a downlink (DL) channel in a subframe, in accordance with various aspects of the present disclosure. [Figure 2C]

[0012] FIG. 2 illustrates an example of a second frame according to various aspects of the present disclosure. [Figure 2D]

[0013] FIG. 1 illustrates an example of an uplink (UL) channel in a subframe, in accordance with various aspects of the present disclosure. [Diagram 3]

[0014] FIG. 1 illustrates an example of a base station and user equipment (UE) in an access network. [Figure 4]

[0015] 1 illustrates a resource diagram showing multiple BWPs in accordance with various aspects of the present disclosure. [Diagram 5]

[0016] 1 illustrates an example diagram illustrating an initial downlink BWP that may be configured within a serving cell's carrier bandwidth for a reduced capability UE, in accordance with various aspects of the present disclosure. [Figure 6]

[0017] 1 illustrates an example Master Information Block (MIB) message in accordance with various aspects of the present disclosure. [Figure 7]

[0018] 1 illustrates an example diagram illustrating SSB transmissions for initial downlink BWP and non-initial downlink BWP that may be configured within a serving cell's carrier bandwidth for a reduced capability UE in accordance with various aspects of the present disclosure. [Figure 8]

[0019] 1 illustrates an example diagram illustrating SSB transmission for initial downlink BWP and non-initial downlink BWP that may be configured within a carrier bandwidth of a serving cell for a non-reduced capability UE in accordance with various aspects of the present disclosure. [Figure 9]

[0020] 1 illustrates an example diagram illustrating multiplexing in the time / frequency domain of CD-SSB and NCD-SSB bursts in accordance with various aspects of the present disclosure. [Figure 10]

[0021] 1 illustrates an example communication flow between a network entity and a UE, in accordance with various aspects of the present disclosure. [Figure 11]

[0022] 1 is a flowchart of a method of wireless communication in a UE in accordance with the teachings disclosed herein. [Figure 12]

[0023] 1 is a flowchart of a method of wireless communication in a UE in accordance with the teachings disclosed herein. [Figure 13]

[0024] FIG. 2 illustrates an example of a hardware implementation for an exemplary device and / or network entity. [Figure 14]

[0025] 1 is a flowchart of a method of wireless communication in a network entity in accordance with the teachings disclosed herein. [Figure 15]

[0026] 1 is a flowchart of a method of wireless communication in a network entity in accordance with the teachings disclosed herein. [Figure 16]

[0027] FIG. 2 illustrates an example of a hardware implementation for an exemplary network entity. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010]

[0028] Aspects disclosed herein provide techniques for different SSB transmissions in the initial / non-initial downlink BWP for different UE types (e.g., reduced capability UEs or non-reduced capability UEs) when a cell allows different UE types to access the cell. That is, different SSB transmissions in the initial / non-initial downlink BWP for different UE types can be supported when a cell supports coexistence of reduced capability UEs and non-reduced capability UEs. 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).

[0011]

[0029] The Detailed Description of the Invention described below in conjunction with the accompanying drawings illustrates various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The Detailed Description of the Invention includes specific details intended to provide a thorough understanding of the various concepts. However, these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0012]

[0030] Several aspects of a telecommunications system are presented with reference to various apparatus and methods that are described in the Detailed Description below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0013]

[0031] As an example, the elements, or any portion of the elements, or any combination of the elements, may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphic processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chips (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0014]

[0032] Thus, in one or more exemplary aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0015]

[0033] Although aspects, implementations, and / or use cases are described in this application by way of example for some embodiments, additional or different aspects, implementations, and / or use cases may occur in many different configurations and scenarios. The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, the aspects, implementations, and / or use cases may occur via integrated chip implementations and other non-modular component-based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some embodiments may or may not be specifically targeted to a use case or application, but a wide variety of combination applicability of the described embodiments may occur. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, summers / analog summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or separated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0016]

[0034] The deployment of a communication system such as a 5G NR system can be configured in multiple ways with various components or parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of the network, a Radio Access Network (RAN) node, a core network node, a network element, or a network equipment such as a base station (BS), or one or more units (or one or more components) performing a base station function can be implemented in an aggregated or separated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, an access point (AP), a transmit / receive point (TRP), or a cell) can be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a separated base station.

[0017]

[0035] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A separated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units, such as one or more centralized or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0018]

[0036] Base station operation or network design may take into account the aggregated nature of base station functions. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as the network configuration supported by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units in various physical locations, as well as distributing functions virtually for at least one unit, which may allow flexibility in network design. Various units of a disaggregated base station, or a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0019]

[0037] FIG. 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a non-aggregated base station architecture. The non-aggregated base station architecture may include one or more CUs (e.g., CU 110) that may directly communicate with the core network 120 via a backhaul link or indirectly communicate with the core network 120 through one or more non-aggregated base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) (e.g., near RT RIC 125) via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework (e.g., SMO framework 105), or both). The CU 110 may communicate with one or more DUs (e.g., DU 130) via respective midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs (e.g., RU 140) via respective fronthaul links. The RUs 140 may communicate with a respective UE (e.g., the UE 104) via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be served by multiple RUs simultaneously.

[0020]

[0038] Each of the units, i.e., the CU (e.g., CU 110), DU (e.g., DU 130), RU (e.g., RU 140), and quasi-RT RIC (e.g., quasi-RT RIC 125), non-RT RIC (e.g., non-RT RIC 115), and SMO framework 105, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. In addition, a unit may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive and / or transmit signals to one or more of the other units over a wireless transmission medium.

[0021]

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

[0022]

[0040] The DU 130 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.), at least in part according to a functional division such as that defined by 3GPP. In some aspects, the DU 130 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with a control function hosted by the CU 110.

[0023]

[0041] The lower layer functions may be implemented by one or more RUs. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node hosting 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, etc.), or both, based at least in part on a functional division such as a lower layer functional division. In such an architecture, the RU 140 may be implemented to handle over the air (OTA) communications with one or more UEs (e.g., UE 104). In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by a corresponding DU. In some scenarios, this configuration may enable the DU(s) and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0024]

[0042] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may 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 instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CUs, DUs, RUs, and quasi-RT RICs. In some implementations, the SMO framework 105 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO framework 105 may communicate directly with one or more RUs via an O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0025]

[0043] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 125. The non-RT RIC 115 may be coupled to the quasi-RT RIC 125 or may communicate with the quasi-RT RIC 125 (e.g., via an A1 interface). The quasi-RT RIC 125 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources by data collection and action via an interface connecting one or more CUs, one or more DUs, or both, and the O-eNB to the quasi-RT RIC 125 (e.g., via an E2 interface).

[0026]

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

[0027]

[0045] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is shown with a dotted line to indicate that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (high-power cellular base station) and / or a small cell (low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include home evolved Node Bs (eNBs) (HeNBs) that may serve restricted groups known as closed subscriber groups (CSGs). A communication link between a RU (e.g., RU 140) and a UE (e.g., UE 104) may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the RU 140, and / or downlink (DL) (also referred to as forward link) transmissions from the RU 140 to the UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna techniques including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use spectrum with a bandwidth of up to YMHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in a carrier aggregation of up to YxMHz (x component carriers) in total, used for transmission in each direction. The carriers may or may not be adjacent to each other. The carrier allocation may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers.The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0028]

[0046] Certain UEs may communicate with each other using Device-to-Device (D2D) communications (e.g., D2D communications link 158). The D2D communications link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communications link 158 may use one or more sidelink channels, such as a Physical Sidelink Broadcast CHannel (PSBCH), a Physical Sidelink Discovery CHannel (PSDCH), a Physical Sidelink Shared CHannel (PSSCH), and a Physical Sidelink Control CHannel (PSCCH). The D2D communications may be via various wireless D2D communications systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0029]

[0047] The wireless communication system may further include a Wi-Fi AP 150 that communicates with the UE 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the UE 104 / Wi-Fi AP 150 may perform clear channel assessment (CCA) before communicating to determine if a channel is available.

[0030]

[0048] The electromagnetic spectrum is often further divided into various classes, bands, channels, etc. based on frequency / wavelength. For 5G NR, two initial operating bands have been identified with frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU).

[0031]

[0049] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as a frequency range designated FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, and thus may in effect extend the characteristics of FR1 and / or FR2 to the mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency ranges designated FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0032]

[0050] With the above aspects in mind, unless otherwise indicated, as used herein, terms such as "sub-6 GHz" may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, as used herein, unless otherwise indicated, terms such as "millimeter wave" may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0033]

[0051] The base station 102 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 / UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0034]

[0052] The base station 102 may include and / or be referred to as a gNB, NodeB, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 may be implemented as an aggregated (monolithic) base station having an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a baseband unit (BBU) (including CU and DU) and a RU, or as a non-aggregated base station including one or more of a CU, a DU, and / or a RU. The set of base stations, which may include non-aggregated base stations and / or aggregated base stations, may be referred to as a Next Generation (NG)RAN (NG-RAN).

[0035]

[0053] The core network 120 may include an Access and Mobility Management Function (AMF) (e.g., AMF 161), a Session Management Function (SMF) (e.g., SMF 162), a User Plane Function (UPF) (e.g., UPF 163), a Unified Data Management (UDM) (e.g., UDM 164), one or more Location Servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports authentication and key agreement (AKA) credential generation, user identity handling, access authorization, and subscription management. The one or more location servers 168 are shown as including a Gateway Mobile Location Center (GMLC) (e.g., GMLC 165) and a Location Management Function (LMF) (e.g., LMF 166). In general, however, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Positioning Center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the position of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the position of the UE 104. Positioning the UE 104 may include signal measurements, position estimation, and optional velocity calculations based on these measurements. The signal measurements may be performed by the UE 104 and / or a serving base station (e.g., base station 102).The measured signals may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite position / location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensors, motion sensors), NR Enhanced Cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time multi-RTT), DL Angle of Departure (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0036]

[0054] Examples of UEs include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small cooking appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation configuration. One or more of these devices may collectively access the network and / or may individually access the network.

[0037]

[0055] 1, in some aspects, a device in communication with a base station, such as a UE 104 in communication with a network entity, such as the base station 102 or components of the base station (e.g., the CU 110, the DU 130, and / or the RU 140), may be configured to manage one or more aspects of wireless communications. For example, the UE 104 may include a prioritization component 198 configured to facilitate application of priority rules for measurements based on CD-SSB and / or NCD-SSB.

[0038]

[0056] In some aspects, the prioritization component 198 may be configured to indicate the UE capabilities to the network. The example prioritization component 198 may also be configured to receive a configuration of the measurement object and DL BWP in the system information or RRC message, where the configuration indicates that the DL BWP includes CD-SSB, includes NCD-SS, or no SSB is present. The configuration of the measurement object and DL BWP may be based at least on one or more of a duplex mode type, a frequency range, a type of DL BWP, or a UE capability.

[0039]

[0057] In another configuration, a network entity, such as the base station 102 or components of the base station (e.g., the CU 110, the DU 130, and / or the RU 140), may be configured to manage one or more aspects of wireless communications. For example, the base station 102 may include a component 199 configured to facilitate application of priority rules for measurements based on CD-SSB and / or NCD-SSB.

[0040]

[0058] In some aspects, the configuration component 199 may be configured to receive an indication of UE capabilities of at least one UE. The example configuration component 199 may also be configured to configure serving cell measurements and one or more DL BWPs, where the configuration of each DL BWP is based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

[0041]

[0059] The following description may focus on 5G NR, however, the concepts described herein may be applicable to other similar domains, such as 5G Advanced, 6G, LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0042]

[0060] FIG. 2A is a diagram 200 illustrating an example of a first subframe in a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of a DL channel in a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe in a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of a UL channel in a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL, or time division duplexed (TDD) where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. In the example provided by FIG. 2A, FIG. 2C, the 5G NR frame structure is assumed to be TDD, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible for DL / UL use, and subframe 3 is configured with slot format 1 (all UL). Subframes 3 and 4 are shown with slot formats 1 and 28, respectively, but any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format through a received slot format indicator (SFI) (either dynamically through DL control information (DCI) or semi-statically / statically through Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure, which is TDD.

[0043]

[0061] 2A-2D illustrate a frame structure, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 subframes (1 ms) of equal size. Each subframe may include one or more time slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) Spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to single stream transmission). The number of slots in a subframe is based on the CP and numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0044] [Table 1]

[0045]

[0062] For the normal CP (14 symbols / slot), the different numerologies μ0-4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For the extended CP, numerology 2 allows 4 slots per subframe. Thus, for the normal CP and numerology μ, 14 symbols / slot and 2 μ There are slots / subframes. The subcarrier spacing is 2 μ*15 kHz, where μ is the numerology 0-4. Thus, numerology μ=0 has a subcarrier spacing of 15 kHz and numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length / period is inversely proportional to the subcarrier spacing. Figures 2A-2D provide an example of a normal CP with 14 symbols per slot and a numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a set of frames, there may be one or more different Bandwidth Parts (BWPs) (see Figure 2B), which are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

[0046]

[0063] A resource grid may be used to represent the frame structure. Each time slot contains Resource Blocks (RBs) (also called Physical RBs (PRBs)), which span 12 consecutive subcarriers. The resource grid is divided into multiple Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0047]

[0064] As shown in Figure 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (shown as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0048]

[0065] FIG. 2B illustrates an example of various DL channels in a subframe of a frame. A physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), where each CCE includes 6 RE groups (REGs), and each REG includes 12 consecutive REs in an OFDM symbol of an RB. The PDCCHs in one BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring opportunity on the CORESET, a UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space), where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be placed at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the timing of the subframe / symbol and the physical layer identity. A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identity and the timing of the radio frame. Based on the physical layer identity and the group number of the physical layer cell identity, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. A physical broadcast channel (PBCH) carrying a master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN).The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0049]

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

[0050]

[0067] 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be arranged as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH may be used to carry data, as well as buffer status reports (BSRs), power headroom reports (PHRs), and / or UCIs.

[0051]

[0068] FIG. 3 is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. In the illustrated example of FIG. 3, the first wireless device may include a base station 310, and the second wireless device may include a UE 350, and the base station 310 may communicate with the UE 350 in an access network. As shown in FIG. 3, the base station 310 includes a transmit processor (TX processor 316), a transmitter 318Tx, a receiver 318Rx, an antenna 320, a receive processor (RX processor 370), a channel estimator 374, a controller / processor 375, and a memory 376. The exemplary UE 350 includes an antenna 352, a transmitter 354Tx, a receiver 354Rx, a RX processor 356, a channel estimator 358, a controller / processor 359, a memory 360, and a TX processor 368. In other examples, the base station 310 and / or the UE 350 may include additional or alternative components.

[0052]

[0069] In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes a Radio Resource Control (RRC) layer, and Layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting system information (e.g., MIBs, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping of logical channels to transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0053]

[0070] The TX processor 316 and the RX processor 370 implement Layer 1 functionality related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 processes mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. A channel estimate from a channel estimator 374 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna of the antennas 320 via a separate transmitter (e.g., transmitter 318Tx). Each transmitter 318Tx can modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

[0054]

[0071] At the UE 350, each receiver 354Rx receives a signal through a corresponding antenna of the antennas 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, two or more of the multiple spatial streams may be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by a channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to a controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0055]

[0072] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 performs demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0056]

[0073] Similar to the functionality described in connection with DL transmissions by the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIBs, SIBs) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with forwarding of higher layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping of logical channels to transport channels, multiplexing of MAC SDUs onto the TB, demultiplexing of MAC SDUs from the TB, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0057]

[0074] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to enable spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas of the antennas 352 via separate transmitters (e.g., transmitters 354Tx). Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0058]

[0075] The UL transmissions are processed at the base station 310 in a manner similar to that described for the receiver functions at the UE 350. Each receiver 318Rx receives a signal through a corresponding antenna of the antennas 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0059]

[0076] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 performs demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0060]

[0077] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to implement aspects associated with the prioritization component 198 of FIG.

[0061]

[0078] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to implement aspects associated with the components 199 in FIG.

[0062]

[0079] A wireless communication system, such as an NR communication system, may support high capability devices and reduced capability devices. Examples of high capability devices include premium smartphones, V2X devices, URLLC devices, eMBB devices, etc., among others. Examples of reduced capability (RedCap) devices may include wearable devices (e.g., smart watches, augmented reality glasses, virtual reality glasses, health and medical monitoring devices, etc.), industrial wireless sensor networks (IWSNs) (e.g., pressure sensors, humidity sensors, motion sensors, thermal sensors, accelerometers, actuators, etc.), surveillance cameras, low-end smartphones, etc., among others. Reduced capability devices may be referred to as NR lite devices, low tier devices, low tier devices, etc.

[0063]

[0080] A reduced capability UE may communicate based on various types of wireless communications. For example, a smart wearable device may transmit or receive communications based on Low Power Wide Area (LPWA) / mMTC, an IoT device may transmit or receive communications based on URLLC, a sensor / camera may transmit or receive communications based on eMBB, etc. In some examples, a reduced capability UE may have an uplink transmit power that is less than the uplink transmit power of a high capability UE. For example, a reduced capability UE may have an uplink transmit power that is at least 10 dB lower than the uplink transmit power of a high capability UE. In another example, a reduced capability UE may have a reduced transmit or receive bandwidth than other UEs. For example, a reduced capability UE may have an operating bandwidth of 5 MHz to 20 MHz for both transmit and receive, in contrast to a high capability UE 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 a maximum bandwidth of 100 MHz during and after initial access in FR2.

[0064]

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

[0065]

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

[0066]

[0083] It may be useful for communications to be scalable and deployable in a more efficient and cost-effective manner. For example, it may be possible to relax or reduce peak throughput, latency, and / or reliability requirements for reduced capability devices. In some examples, reduced power consumption, complexity, production costs, and / or reduced system overhead may be prioritized. As an example, industrial sensors may have an acceptable latency of up to about 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. Data rates may be lower and may include more uplink traffic than downlink traffic. As another example, video surveillance devices may have an acceptable latency of up to about 500 ms.

[0067]

[0084] A carrier bandwidth may span, for example, a contiguous set of PRBs from a common resource block for a given numerology on a given carrier. A base station may configure one or more BWPs having a bandwidth span smaller 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.

[0068]

[0085] FIG. 4 illustrates a resource diagram 400 showing multiple BWPs (e.g., BWP1, BWP2, and BWP3) configured within a frequency span of a carrier bandwidth 402. 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 the active BWP without a measurement gap or BWP switching gap. Each DL BWP may include at least one control resource set (CORESET). In FIG. 4, the BWP may be a DL BWP and is shown as having a CORESET within the BWP. In other examples, the BWP may be a 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 for a UE at a time, and the UE may not transmit PUSCH or PUCCH outside the active BWP. Use of the BWP may reduce the bandwidth monitored by and / or used for transmission by the UE, which may help the UE conserve battery power.

[0069]

[0086] A CORESET corresponds to a set of physical resources in time and frequency that a UE uses to monitor the PDCCH / DCI. Each CORESET includes one or more resource blocks in the frequency domain and one or more symbols in the time domain. As an example, a CORESET may include multiple RBs in the frequency domain and one, two, or three consecutive symbols in the time domain. A resource element (RE) is a unit that indicates one subcarrier in frequency on a single symbol in time. A control channel element (CCE) includes resource element groups (REGs), e.g., six REGs, in which case a REG may correspond to one RB (e.g., 12 REs) in one OFDM symbol. REGs in a CORESET may be numbered in ascending order in a time-prioritized manner, starting from 0 for the first OFDM symbol and the lowest-numbered resource block in the control resource set. A UE may be configured with multiple CORESETs, with each CORESET associated with a CCE-to-REG mapping. The search space may include a set of CCEs, for example, at different aggregation levels. For example, the search space may indicate, for example, the number of candidates to be decoded for which the UE performs decoding. A CORESET may include multiple search space sets.

[0070]

[0087] In some aspects, UEs with different levels of capabilities, such as reduced capability UEs and non-reduced (or high) capability UEs, may share an initial DL BWP (e.g., BWP1) and CORESET#0 (e.g., CORESET404) for initial access. The UE may, for example, monitor resources of CORESET404 to receive system information that enables the UE to perform initial access. A cell-defined SSB (CD-SSB) may be transmitted within a bandwidth supported by the reduced capability UE. As an example, BWP1 may be an initial DL BWP and may, for example, be configured for both reduced capability UEs and high capability UEs. The UE may, for example, be configured with a different BWP as an active DL BWP after performing initial access. For example, in FIG. 4, BWP2 may be configured for low capability UEs and high capability UEs may be configured with an active DL BWP3. FIG. 4 shows that BWP1 may include SSB408.

[0071]

[0088] The network may output one or more synchronization signal blocks (SSBs) to the UE, and the UE may process (e.g., decode) the SSB to acquire system information and begin communication with the network. The SSB may include synchronization signals, such as the PSS, PBCH, and SSS, which are sometimes referred to as acquisition signals. The SSB may occupy resources in the time domain and / or frequency domain. The PSS, PBCH, and SSS may each occupy a different set of symbols and subcarriers in the SSB.

[0072]

[0089] A cell providing access to a reduced capability UE may configure a separate initial BWP for the reduced capability UE. FIG. 5 illustrates an example diagram 500 illustrating an initial downlink BWP 510 that may be configured within a serving cell's carrier bandwidth 502 for the reduced capability UE to receive CD-SSB, SI, paging information, etc. In some aspects, the initial downlink BWP 510 may be configured with CD-SSB 512, CORESET#0 (e.g., CORESET 514), and resources of the CORESET or common search space (CSS) (e.g., resources 516) 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 BWP 510, e.g., CORESET 514 of the serving cell, to receive CD-SSB, SI, and / or paging information. An idle or inactive reduced capability UE may switch to a separate BWP to perform random access, small data transfer (SDT), or to initiate a transition to a connected mode.

[0073]

[0090] A reduced capability UE may receive an initial BWP pair configuration including an initial RedCap downlink BWP 520 and an initial RedCap uplink BWP 530 for random access or SDT. The initial RedCap downlink BWP 520 may include resources 522 configured for a CORESET or CSS for initial access by the reduced capability UE. The initial RedCap uplink BWP 530 may include PUCCH resources, such as a random access channel occasion (e.g., RO 532). The network may assume that an idle or inactive reduced capability UE that performs random access in a separate initial BWP (e.g., sends a random access message in the initial RedCap uplink BWP 530 and / or monitors a downlink response in the initial RedCap downlink BWP 520) does not monitor paging in the CORESET 514.

[0074]

[0091] In some aspects, a separate initial BWP for reduced capability UEs (e.g., initial RedCap downlink BWP 520) may include CD-SSB and specific CORESET resources, such as CORESET#0 resources. In other aspects, the initial RedCap downlink BWP for reduced capability UEs may not include CD-SSB (e.g., may be referred to as SSB-less BWP and configured without CD-SSB resources, such as may not include CD-SSB), may not include specific CORESET resources, such as CORESET#0, or resources in CORESET for receiving SIB1, OSI, or paging information. In the illustrated example of FIG. 5, the initial RedCap downlink BWP 520 does not include CD-SSB or CORESET#0, e.g., for random access.

[0075]

[0092] In some aspects in FR1, in a separate initial DL BWP (e.g., initial RedCap downlink BWP 520, etc.) that does not include CD-SSB and CORESET#0 (e.g., does not include the entire CORESET#0), the initial RedCap downlink BWP 520 may be configured for random access rather than paging in idle / inactive mode. The initial RedCap downlink BWP 520 may not include SSB, CORESET#0, or SIB resources. For example, the network may assume that a reduced capability UE performing random access in the initial RedCap downlink BWP 520 does not monitor paging in a BWP that includes CORESET 514 (e.g., does not monitor paging in the initial downlink BWP 510). If the BWP is configured for paging, the reduced capability UE may be assumed that the BWP includes a non-cell-defined SSB (NCD-SSB) for the serving cell, but may not be assumed that the BWP includes CORESET#0 / SIB. In an RRC configured active DL BWP configured for a UE in connected mode, if the active DL BWP does not include CD-SSB and CORESET#0 in its entirety, a reduced capability UE may be assumed that the active DL BWP includes NCD-SSB for the serving cell, e.g., instead of CORESET#0 / SIB. In some aspects, a reduced capability UE may indicate the UE's ability to not use NCD-SSB. For example, a reduced capability UE may optionally support related operations for wireless communications based on a reference signal, such as CSI-RS, and may report that capability to the network.

[0076]

[0093] If the network configures a separate initial / RRC configured DL BWP for a reduced capability UE to include the entire CORESET#0, the reduced capability UE may assume that the separate initial BWP includes the CD-SSB. The network may choose to configure SSB or MIB configured CORESET#0 or SIB1 in the respective DL BWP. If a separate SIB configured initial DL BWP for a reduced capability UE includes the entire CORESET#0, the reduced capability UE may use the bandwidth and location of CORESET#0 for downlink reception during initial access. The periodicity of the NCD-SSB may be different from that of the CD-SSB. In some aspects, the periodicity of the NCD-SSB may not be smaller than that of the CD-SSB.

[0077]

[0094] In some aspects in FR2, a separate initial DL BWP (e.g., initial RedCap downlink BWP 520) that does not include the entire CD-SSB and CORESET#0 may be configured for random access rather than paging in idle / inactive mode. The initial RedCap downlink BWP 520 may not include SSB, CORESET#0, or SIB resources. For example, the network may assume that a reduced capability UE performing random access in the initial RedCap downlink BWP 520 does not monitor paging in a BWP including CORESET 514 (e.g., does not monitor paging in the initial downlink BWP 510). If the initial RedCap downlink BWP is configured for paging, the reduced capability UE may assume that the initial RedCap downlink BWP includes NCD-SSB for the serving cell rather than CORESET#0 or SIB resources.

[0078]

[0095] In an RRC configured active DL BWP configured for a UE in connected mode, if the active DL BWP does not include CD-SSB and CORESET#0 in its entirety, a reduced capability UE may be assumed that the active DL BWP includes NCD-SSB for the serving cell, e.g., instead of CORESET#0 / SIB. In some aspects, a reduced capability UE may indicate the UE's ability to not use NCD-SSB. For example, a reduced capability UE may optionally support related operations for wireless communications based on a reference signal, such as CSI-RS, and may report that capability to the network.

[0079]

[0096] In multiplexing pattern 1 of SSB and CORESET#0, if a separate initial DL BWP is configured via RRC to include the entire CORESET#0, the reduced capability UE may assume that the separate initial DL BWP includes CD-SSB. The network may choose to configure SSB or MIB configured CORESET#0 or SIB1 in the respective DL BWP. If a separate SIB configured initial DL BWP for the reduced capability UE includes the entire CORESET#0, the reduced capability UE may use the bandwidth and location of CORESET#0 for downlink reception during initial access. The periodicity of NCD-SSB may be different from that of CD-SSB. In some aspects, the periodicity of NCD-SSB may not be smaller than that of CD-SSB.

[0080]

[0097] As mentioned above, the SSB includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a PBCH. The possible time locations of the SSB within a half-frame may be determined by the subcarrier spacing, and the periodicity of the half-frame transmitting the SSB may be configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions, for example using different beams, covering the coverage area of ​​a cell.

[0081]

[0098] The 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 obtaining other system information. For example, the minimum system information may include a Master Information Block (MIB) and a System Information Block 1 (SIB1). The MIB may include cell barring status information and cell physical layer information to facilitate reception of further system information, e.g., CORESET#0 configuration. SIB1 may define scheduling of other system information blocks and may include information for initial access. SIB1 may also be referred to as remaining minimum system information (RMSI). The MIB may be carried on the PBCH of the SSB and may provide the UE with parameters (e.g., CORESET#0 configuration) for monitoring the PDCCH to schedule the PDSCH carrying SIB1.

[0082]

[0099] Within the frequency span of a carrier, one or more SSBs may be transmitted. The Physical Cell Identification (PCI) of SSBs transmitted at 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 an RMSI (e.g., SIB1), the SSB is called a Cell-Defined SSB (CD-SSB). A Primary Cell (PCell) is associated with a CD-SSB located on a synchronization raster. A frequency may be configured on a synchronization raster if it is also identifiable by a Global Synchronization Channel Number (GSCN).

[0083]

[0100] In some examples, the MIB may indicate that the SSB is not associated with an RMSI (e.g., there is no associated SIB1). When an SSB is not associated with an RMSI, the SSB may be referred to as a non-cell-defining SSB (NCD-SSB). A CD-SSB is transmitted on a synchronous raster, while an NCD-SSB may be transmitted on or outside the synchronous raster. The UE may determine whether the SSB is a CD-SSB or an NCD-SSB based on the MIB of the SSB. FIG. 6 illustrates an example MIB message 600 presented herein. The MIB message 600 may be transmitted from the network to the UE. The example MIB message 600 includes different fields, including an SSB subcarrier offset field 602, which may be referred to as a "ssb-SubcarrierOffset" field or any other name. The SSB subcarrier offset field 602 includes an SSB type indicator (K) that signals a frequency domain offset between the SSB and the entire resource block grid in number of subcarriers. SSB ) For example, in FR1, K SSB can be a 5-bit value, and in FR2, K SSB can be a 4-bit value. Referring to FR1, K SSB The value of is 0 or more and less than 24 (for example, 0≦K SSB <24), the UE may determine that the SSB is CD-SSB, and K SSB The value of is 24 or more and less than 32 (for example, 24≦K SSB <32), the UE may determine that the SSB is an NCD-SSB. SSB The value of is 0 or more and less than 12 (for example, 0≦K SSB <12), the UE may determine that the SSB is CD-SSB, and K SSB The value of is 12 or more and less than 16 (for example, 12≦K SSB <16), the UE may determine that the SSB is an NCD-SSB.

[0084]

[0101] As shown in FIG. 6, the SSB Subcarrier Offset field 602 is an integer between 0 and 15 and can therefore be represented by 4 bits. SSB The value of K can be between 0 and 31, which corresponds to 5 bits. SSB For example, the PBCH payload for 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.

[0085]

[0102] The example MIB message 600 also includes a PDCCH SIB1 configuration field 604, which may be referred to as a "pdcch-ConfigSIB1" field or any other name. The PDCCH SIB1 configuration field 604 may determine a common CORESET, a common search space, and PDCCH parameters. If the SSB subcarrier offset field 602 indicates that SIB1 is not present, the PDCCH SIB1 configuration field 604 may indicate a frequency location where the UE may find an SSB with SIB1, or a frequency range where the network does not provide an SSB with SIB1. Thus, when the SSB is a CD-SSB, the PDCCH SIB1 configuration field 604 points to a valid configuration for CORESET#0 and a type0 PDCCH CSS set, which may be referred to as a "Type0-PDCCH CSS set" or any other name. When the SSB is an NCD-SSB, the SSB (eg, the PDCCH SIB1 configuration field 604) does not point to a valid configuration of CORESET#0 and type0 PDCCH CSS set.

[0086]

[0103] In some aspects, a UE may use NCD-SSB for serving and non-serving cell measurements for all RRC modes (e.g., idle, inactive, and / or connected). The UE may use the measurements to facilitate 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).

[0087]

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

[0088]

[0105] On a cell that supports both reduced and non-reduced capability UEs (e.g., high capability UEs) for access, the CD-SSB and NCD-SSB of the serving cell may serve different roles. For example, for cell selection / reselection, a UE (e.g., reduced capability UE or non-reduced capability UE) searches for the CD-SSB and decodes the included system information. The 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.

[0089]

[0106] Aspects disclosed herein provide techniques for different SSB transmissions in the initial / non-initial downlink BWP for different UE types (e.g., reduced capability UEs or non-reduced capability UEs) when a cell supports different UE types to access the cell. That is, different SSB transmissions in the initial / non-initial downlink BWP for different UE types can be supported when a cell supports coexistence between reduced capability UEs and non-reduced capability UEs. 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).

[0090]

[0107] In some aspects, SSB transmissions in a downlink BWP for a reduced capability UE may be based on UE capabilities, deployment (e.g., duplex mode and / or frequency range such as FR1 or FR2), and coexistence needs. For an initial downlink BWP, a reduced capability UE may be configured with CD-SSB transmitted by the serving cell, NCD-SSB transmitted by the serving cell, or no SSB transmitted (e.g., no SSB is present). Additionally, for a non-initial downlink BWP, a reduced capability UE may be configured with CD-SSB transmitted by the serving cell, NCD-SSB transmitted by the serving cell, or no SSB transmitted by the serving cell.

[0091]

[0108] FIG. 7 shows an example diagram illustrating SSB transmissions for initial downlink BWP and non-initial downlink BWP that may be configured within a serving cell's carrier bandwidth for a reduced capability UE as presented herein. In the example first diagram 700, a cell may have a carrier bandwidth 702. A reduced capability UE may be configured with an initial downlink BWP 704 and a non-initial downlink BWP 706. As shown in the first diagram 700, a reduced capability UE may receive a CD-SSB 708 within the initial downlink BWP 704. The CD-SSB 708 may also configure a CORESET#0 710 within the initial downlink BWP 704. The first diagram 700 also shows that a reduced capability UE may receive an NCD-SSB 712 within the non-initial downlink BWP 706.

[0092]

[0109] In the illustrated example of Figure 7, if the downlink BWP includes only CD-SSB, the reduced capability UE is not supposed to measure NCD-SSB outside of the active downlink BWP, e.g., for RRM, RLM, BFD, link recovery, tracking loop, and / or AGC. For example, in the first diagram 700, the initial downlink BWP 704 includes CD-SSB 708 and does not include NCD-SSB. In such a scenario, the reduced capability UE may be configured to not measure NCD-SSB 712 outside of the initial downlink BWP 704.

[0093]

[0110] In the example second diagram 720, a cell may have a carrier bandwidth 722. A reduced capability UE may be configured with an initial downlink BWP 724 and a non-initial downlink BWP 726. As shown in the second diagram 720, a reduced capability UE may receive an NCD-SSB 728 within the non-initial downlink BWP 726. A reduced capability UE may also receive a CD-SSB 730 outside of the initial downlink BWP 724 and the non-initial downlink BWP 726. For example, a reduced capability UE may receive a CD-SSB 730 within a third BWP 732. The CD-SSB 730 may also be configured with a CORESET#0 734 within the third BWP 732.

[0094]

[0111] In example third diagram 740, a cell may have a carrier bandwidth 742. A reduced capability UE may be configured with an initial downlink BWP 744 and a non-initial downlink BWP 746. As shown in the third diagram 740, the reduced capability UE may receive a CD-SSB 748 within the non-initial downlink BWP 746. The CD-SSB 748 may also configure a CORESET#0 750 within the non-initial downlink BWP 746. The third diagram 740 also shows that the reduced capability UE may receive an NCD-SSB 752 within the initial downlink BWP 744.

[0095]

[0112] In the example fourth diagram 760, a cell may have a carrier bandwidth 762. A reduced capability UE may be configured with an initial downlink BWP 764 and a non-initial downlink BWP 766. As shown in the fourth diagram 760, a reduced capability UE may not receive an SSB in the initial downlink BWP 764 and may not receive an SSB in the non-initial downlink BWP 766. However, similar to the example second diagram 720, a reduced capability UE may receive a CD-SSB 768 in a third BWP 770. The CD-SSB 768 may also configure a CORESET#0 772 in the third BWP 770.

[0096]

[0113] As shown in the example diagram of Figure 7, for a reduced capability UE, the initial downlink BWP may include a CD-SSB (e.g., as shown in the first diagram 700), may include an NCD-SSB (e.g., as shown in the third diagram 740), or may not include an SSB (e.g., as shown in the second diagram 720 and the fourth diagram 760). In addition, for a reduced capability UE, the non-initial downlink BWP may include a CD-SSB (e.g., as shown in the third diagram 740), may include an NCD-SSB (e.g., as shown in the first diagram 700 and the second diagram 720), or may not include an SSB (e.g., as shown in the fourth diagram 760).

[0097]

[0114] It will be appreciated that other examples may include additional or alternative combinations of CD-SSB, NCD-SSB, and no SSB within the initial downlink BWP and non-initial downlink BWP for reduced capability UEs.

[0098]

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

[0099]

[0116] FIG. 8 illustrates an example diagram illustrating SSB transmissions for initial downlink BWP and non-initial downlink BWP that may be configured within a serving cell's carrier bandwidth for a non-reduced capability UE as presented herein. In the example first diagram 800, a cell may have a carrier bandwidth 802. A non-reduced capability UE may be configured with an initial downlink BWP 804 and a non-initial downlink BWP 806. The initial downlink BWP 804 may be configured by SIB1 and / or RRC signaling. In the example first diagram 800, the initial downlink BWP 804 and the non-initial downlink BWP 806 overlap in frequency resources. A non-reduced capability UE may receive a CD-SSB 808 within the initial downlink BWP 804. The CD-SSB 808 may also comprise a CORESET#0 810. The first diagram 800 also illustrates that a non-reduced capability UE may receive an NCD-SSB 812 within the non-initial downlink BWP 806. In the first exemplary diagram 800 , the non-initial downlink BWP 806 overlaps with the CD-SSB 808 and the NCD-SSB 812 .

[0100]

[0117] In the example second diagram 820, the cell may have a carrier bandwidth 822. A non-reduced capability UE may be configured with an initial downlink BWP 824 and a non-initial downlink BWP 826. The initial downlink BWP 824 may be configured by SIB1 and / or RRC signaling. As shown in the second diagram 820, a non-reduced capability UE may receive a CD-SSB 828 within the initial downlink BWP 824. The CD-SSB 828 may also comprise a CORESET#0 830. As shown in the second diagram 820, a non-initial downlink BWP 826 may partially overlap with the initial downlink BWP 824. In addition, a non-reduced capability UE may receive an NCD-SSB 832 within the non-initial downlink BWP 826.

[0101]

[0118] In example third diagram 840, a cell may have a carrier bandwidth 842. A non-reduced capability UE may be configured with an initial downlink BWP 844 and a non-initial downlink BWP 846. The initial downlink BWP 844 may be configured by SIB1 and / or RRC signaling. As shown in the third diagram 840, a non-reduced capability UE may receive a CD-SSB 848 and an NCD-SSB 850 in the initial downlink BWP 844. The CD-SSB 848 may also configure a CORESET#0 852 in the initial downlink BWP 844. The third diagram 840 also shows that the NCD-SSB 850 may overlap with the non-initial downlink BWP 846.

[0102]

[0119] In the example fourth diagram 860, the cell may have a carrier bandwidth 862. A non-reduced capability UE may be configured with an initial downlink BWP 864 and a non-initial downlink BWP 866. The initial downlink BWP 864 may be configured by SIB1 and / or RRC signaling. As shown in the fourth diagram 860, a non-reduced capability UE may receive a CD-SSB 868 in the initial downlink BWP 864. The CD-SSB 868 may also configure a CORESET#0 870 in the initial downlink BWP 864. In the example fourth diagram 860, the initial downlink BWP 864 and the non-initial downlink BWP 866 do not overlap. In addition, a non-reduced capability UE may not receive an SSB in the non-initial downlink BWP 866.

[0103]

[0120] As shown in the example diagram of Figure 8, for a non-reduced capability UE, the initial downlink BWP includes at least a CD-SSB. The initial downlink BWP may also include a NCD-SSB (e.g., as shown in the example third diagram 840). In addition, for a non-reduced capability UE, the non-initial downlink BWP may include a CD-SSB (e.g., as shown in the first diagram 800), may include a NCD-SSB (e.g., as shown in the first diagram 800, the second diagram 820, and the third diagram 840), may include a CD-SSB and a NCD-SSB (e.g., as shown in the first diagram 800), or may not include a SSB (e.g., as shown in the fourth diagram 860).

[0104]

[0121] It will be appreciated that other examples may include additional or alternative combinations of CD-SSB, NCD-SSB, CD-SSB and NCD-SSB, and no SSB within the initial downlink BWP and non-initial downlink BWP for non-reduced capability UEs.

[0105]

[0122] In some aspects, CD-SSBs and NCD-SSBs transmitted by the same cell may share the same PSS / SSS sequence and PCI. CD-SSBs and NCD-SSBs may also include the same number / pattern of SS blocks, which may be indicated by the SSB position in the burst field of SIB1 (e.g., the "ssb-PositionInBurst" field or otherwise) or by the serving cell configuration common information element of RRC signaling, the "ServingCellConfigCommon" information element or otherwise. CD-SSBs and NCD-SSBs may also have the same transmit power and energy per resource element (EPRE) boost ratio, at least for purposes of RRM and / or RLM measurements.

[0106]

[0123] Within the channel bandwidth of the serving cell, the CD-SSB bursts and the NCD-SSB bursts may have the same periodicity or different periodicities. In addition, the serving cell may use multiplexing when transmitting the CD-SSB and the 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.

[0107]

[0124] FIG. 9 shows an example diagram illustrating multiplexing in the time / frequency domain of CD-SSB and NCD-SSB bursts as presented herein. In the example diagram, 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.

[0108]

[0125] In the example of Figure 9, a first diagram 900 illustrates a CD-SSB burst and an NCD-SSB burst being multiplexed by TDM. For example, the CD-SSB burst may include a first CD-SSB 902a and a second CD-SSB 902b having a first periodicity (T1). The NCD-SSB burst may include a first NCD-SSB 904a and a second NCD-SSB 904b having a second periodicity (T2). In the exemplary first diagram 900, the SSBs of the CD-SSB burst and the NCD-SSB burst are transmitted within the same frequency range but at non-overlapping times, and thus the CD-SSB burst and the NCD-SSB burst are multiplexed by TDM.

[0109]

[0126] The second diagram 920 illustrates a CD-SSB burst and an NCD-SSB burst being multiplexed by FDM. For example, the CD-SSB burst may include a first CD-SSB 922a, a second CD-SSB 922b, and a third CD-SSB 922c having a first periodicity (T1). The NCD-SSB burst may include a first NCD-SSB 924a and a second NCD-SSB 924b having a second periodicity (T2). In the example second diagram 920, the SSBs of the 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-SSB 922a and the first NCD-SSB 924a overlap in time, and the third CD-SSB 922c and the second NCD-SSB 924b overlap in time, and thus the CD-SSB bursts and the NCD-SSB bursts are multiplexed by FDM.

[0110]

[0127] A third diagram 940 illustrates a CD-SSB burst and an NCD-SSB burst being multiplexed by a hybrid of TDM and FDM. For example, a CD-SSB burst may include a first CD-SSB 942a and a second CD-SSB 942b having a first periodicity (T1). An NCD-SSB burst may include a first NCD-SSB 944a and a second NCD-SSB 944b having a second periodicity (T2). In the exemplary third diagram 940, the SSBs of the CD-SSB burst and the NCD-SSB burst are transmitted in non-overlapping frequency ranges (e.g., FDM) and in 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.

[0111]

[0128] In some aspects, the UE may receive a configuration of the downlink BWP based on the capabilities of the UE (e.g., UE capabilities). The UE capabilities may refer to a UE class or type, such as a reduced capability UE or a high capability UE. In some aspects, the UE capabilities may additionally or alternatively indicate one or more specific fine-grained 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 of the downlink BWP based on the type of the downlink BWP. In some examples, the configuration may indicate that the downlink BWP includes both CD-SSB and NCD-SSB from the serving cell. In some such examples, the UE may not be expected to measure both CD-SSB and NCD-SSB bursts in the same slot. For example, the UE may measure either CD-SSB or NCD-SSB in a slot and skip measuring the other of CD-SSB or NCD-SSB in the slot.

[0112]

[0129] In some examples, the UE may operate in TDD or HD-FDD and there may be collisions between SSB reception and uplink transmission at the UE. The collisions may include SSBs that overlap with uplink transmissions in the time domain. In some examples, the collisions may include SSBs and uplink transmissions that do not overlap in the time domain, but there may be insufficient DL / UL switching gaps at the UE for SSB reception and UL transmission. For example, the UE may not have enough time to switch between a receive mode to receive SSBs and a transmit mode to transmit uplink transmissions. In such examples where collisions may occur, the UE may prioritize SSB measurements defined by configuration over dynamically scheduled uplink transmissions (e.g., determined via DCI) or uplink transmissions configured by higher layers (e.g., determined via MAC-CE and / or by RRC signaling). For SSB bursts not defined by configuration, the UE may prioritize uplink transmissions instead. For example, for intra-frequency and inter-frequency measurements, the configuration to be measured may indicate the frequency and / or time resources of the reference signal to be measured and the subcarrier spacing. The reference signals may include CD-SSB, NCD-SSB, or CSI-RS provided by the serving cell and / or neighboring cells. The UE may be configured with multiple reference signals for measurements. Although the measurement configuration may indicate or define the reference signals, the configuration may not indicate and / or define all reference signals configured for the UE. Thus, in some examples, the measurement configuration may define SSB bursts that include CD-SSB and / or NCD-SSB. In other examples, the measurement configuration may not define or indicate SSB bursts.

[0113]

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

[0114]

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

[0115]

[0132] In some examples, the configuration may indicate that the downlink BWP includes only 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 that the configuration of NCD-SSB may not be signaled to the UE. In examples where the configuration indicates that the downlink BWP includes only CD-SSB transmitted by the serving cell, the UE may not be expected to measure NCD-SSB outside of an active downlink BWP, which may be for one or more of cell selection / reselection, RRM, RLM, BFD, link recovery, tracking loop, or AGC.

[0116]

[0133] In some examples, the configuration may indicate that the downlink BWP does not include SSB, or that the configuration of SSB may not be signaled to the UE. In examples where the configuration does not indicate SSB from the serving cell, the UE may switch to a different BWP to measure CD-SSB from the serving cell when the UE is in an RRC idle state or an RRC inactive state. When the UE is in an RRC connected state, the UE may switch to a different BWP to measure CD-SSB and / or NCD-SSB from the serving cell.

[0117]

[0134] In some examples, there may be a BWP switching delay associated with UE priority handling, for example, when the UE operates in TDD or HD-FDD mode, the BWP switching delay in RRC idle, RRC inactive, or RRC connected state may be included in the time gap considerations for collision handling between SSB measurements and uplink transmissions.

[0118]

[0135] 10 illustrates an example communication flow 1000 between a network entity 1002 and a UE 1004 as presented herein. One or more aspects described for the network entity 1002 may be performed by a component of a base station or a network entity, such as a CU, a DU, and / or a RU. In the illustrated example, the communication flow 1000 facilitates a technique for different SSB transmissions within initial / non-initial downlink BWP for different UE types.

[0119]

[0136] Aspects of the network entity 1002 may be implemented by the base station 102 of Figure 1 and / or the base station 310 of Figure 3. Aspects of the UE 1004 may be implemented by the UE 104 of Figure 1 and / or the UE 350 of Figure 3. Although not shown in the illustrated example of Figure 10, it should be appreciated that in additional or alternative examples, the network entity 1002 and / or the UE 1004 may communicate with one or more other base stations or UEs.

[0120]

[0137] In the depicted example of Figure 10, the UE 1004 transmits capabilities 1010 that are acquired (e.g., received) by the network entity 1002. The capabilities 1010 may indicate whether the network entity 1002 is a reduced capability UE or a non-reduced capability UE (e.g., a high capability UE). The UE 1004 may transmit the capabilities 1010 via DCI, a MAC control element (MAC-CE), and / or RRC signaling. For example, the UE 1004 may transmit the capabilities 1010 via a UE Capability Information message, which may be referred to as a "UECapabilityInformation" message or any other name.

[0121]

[0138] The network entity 1002 may configure serving cell measurements for one or more downlink BWPs. For example, the network entity 1002 may output (e.g., transmit) a configuration 1020 that is received by the UE 1004. The network entity 1002 may output the configuration 1020 via system information and / or RRC signaling. The configuration may indicate that the downlink BWP configured for 1004 includes a CD-SSB, includes a NCD-SSB, or that the downlink BWP does not include an SSB (e.g., no SSB is present in the downlink BWP). In some examples, the configuration 1020 may be based on a duplex mode type, a frequency range (e.g., FR1 or FR2), a type of downlink BWP (e.g., initial downlink BWP or non-initial downlink BWP), and / or a UE capability of the UE 1004 indicated by the capabilities 1010 (e.g., a reduced capability UE or a non-reduced capability UE). For example, if the serving cell supports paired spectrum (e.g., FDD mode), the configuration 1020 may configure the UE 1004 to switch downlink BWP (e.g., for intra-frequency or inter-frequency measurements of SSB) without switching its uplink BWP. In an example where the UE 1004 has the capability to support FD-FDD mode, the configuration 1020 may configure the UE 1004 to measure SSB on the downlink without interrupting its uplink transmission. In an example where the serving cell supports unpaired spectrum (e.g., TDD mode) or the UE 1004 has the capability to support HD-FDD mode (e.g., but not FD-FDD mode), the configuration 1020 may configure the UE 1004 such that downlink measurements and uplink transmissions are not scheduled at the same time.

[0122]

[0139] 10, the UE 1004 may perform a monitoring procedure 1030 to monitor measurement objects based on the configuration 1020. For example, the UE 1004 may monitor an initial downlink BWP or a non-initial downlink BWP. The UE 1004 may monitor for CD-SSBs and / or NCD-SSBs in the downlink BWP, or may know that the downlink BWP does not include an SSB.

[0123]

[0140] 10, the network entity 1002 may output a CD-SSB 1034 to be received by the UE 1004. Additionally or alternatively, the network entity 1002 may output an NCD-SSB 1036 to be received by the UE 1004. The network entity 1002 may output the CD-SSB 1034 and / or the NCD-SSB 1036 within an initial downlink BWP and / or a non-initial downlink BWP.

[0124]

[0141] In some examples, the UE 1004 may perform a measurement procedure 1040 to measure a measurement object based on the downlink BWP configuration 1020. For example, the UE 1004 may measure an SSB received in a slot.

[0125]

[0142] In some examples, the UE 1004 may perform the suppression procedure 1042 to skip performing measurements of the measurement object based on the configuration 1020 of the downlink BWP. In some examples, the UE 1004 may perform the suppression procedure 1042 when the configuration 1020 indicates that the downlink BWP does not include any SSBs.

[0126]

[0143] In some examples, the UE 1004 may perform a measurement procedure 1040 to measure a first subset of SSBs received within the downlink BWP and may also perform a suppression procedure 1042 to skip performing measurements of a second subset of SSBs within the downlink BWP.

[0127]

[0144] In some examples, the UE 1004 may be configured such that collision occasions may occur between receiving SSBs and transmitting uplink transmissions. For example, the network entity 1002 may output uplink scheduling information 1022 that is received by the UE 1004. The uplink scheduling information 1022 may include semi-static or dynamic scheduling information for the uplink transmissions 1046.

[0128]

[0145] In some examples, the UE 1004 may determine, based on the uplink scheduling information 1022 and the configuration 1020, that a collision may occur between the SSB and the uplink transmission 1046. In some such examples, the UE 1004 may determine to perform a measurement procedure 1040 to measure the received SSB (e.g., the CD-SSB 1034 and / or the NCD-SSB 1036) and may perform a skip procedure 1044 to skip transmitting the uplink transmission 1046. In other examples, the UE 1004 may determine, based on the occurrence of a collision occasion, to perform a suppression procedure 1042 to skip performing measurements on the received SSB and to transmit the uplink transmission 1046.

[0129]

[0146] In some examples, the UE 1004 may determine, based on the configuration 1020, that the downlink BWP does not include an SSB. In some such examples, the UE 1004 may perform a switching procedure 1032 to switch to a different BWP. The UE 1004 may then perform a measurement procedure 1040 to measure an SSB in the different BWP. In some examples, when the UE 1004 is in an RRC idle state, the UE 1004 may perform a switching procedure 1032 to measure a CD-SSB 1034 in a different BWP. In other examples, when the UE 1004 is in an RRC connected state or an RRC inactive state, the UE 1004 may perform a switching procedure 1032 to measure a CD-SSB 1034 or an NCD-SSB 1036 in a different BWP. In some examples, the BWP switching delay associated with switching to a different BWP to measure a CD-SSB 1034 or an NCD-SSB 1036 may be included in the time gap considerations for collision occasions.

[0130]

[0147] In some examples, the uplink transmission 1046 may include a PUSCH, a PUCCH, or an SRS. In some examples, the UE 1004 may fully skip or partially skip the transmission of the uplink transmission 1046 based in part on a switching gap. The switching gap is a minimum time from reception to transmission (N Rx-Tx ), or the minimum time between transmission and reception (N Tx-Rx ) may be determined based on the

[0131]

[0148] The UE 1004 may skip a transmission entirely (e.g., via skip procedure 1044) by not transmitting a PUSCH or PUCCH. For example, the UE 1004 may skip a PUSCH or PUCCH transmission if the last symbol of the PUSCH or PUCCH transmission overlaps with a switching gap before the first symbol of an immediately following SSB. The UE 1004 may additionally or alternatively skip a PUSCH or PUCCH transmission if the first symbol of the PUSCH or PUCCH transmission overlaps with a switching gap after the last symbol of a immediately preceding SSB.

[0132]

[0149] The UE 1004 may partially skip a transmission (e.g., via a skip procedure 1044) by not transmitting the SRS. For example, the UE 1004 may not transmit the SRS in a symbol that overlaps with a switching gap before the first symbol of an immediately following SSB. The UE 1004 may additionally or alternatively skip transmitting the SRS in a symbol that overlaps with a switching gap after the last symbol of an immediately preceding SSB.

[0133]

[0150] 11 is a flowchart 1100 of a method of wireless communication. The method may be performed by a UE (e.g., the UE 104 and / or the apparatus 1304 of FIG. 13). The method may facilitate improved synchronization and measurement for reduced capability UEs.

[0134]

[0151] At 1102, the UE indicates UE capabilities to the network as described in connection with capabilities 1010 of Figure 10. For example, the UE may be a reduced capability UE or a high capability UE. The indicating of capabilities at 1102 may be performed by the cellular RF transceiver 1322 / prioritization component 198 of the apparatus 1304 of Figure 13.

[0135]

[0152] At 1104, the UE receives a configuration of the measurement object and the downlink BWP in a system information or RRC message, as described in connection with the configuration 1020 of FIG. 10. The configuration may indicate that the downlink BWP includes a CD-SSB, includes a NCD-SSB, or that there is no SSB. The configuration of 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 a UE capability. Receiving the configuration at 1104 may be performed by the cellular RF transceiver 1322 / prioritization component 198 of the apparatus 1304 of FIG. 13.

[0136]

[0153] 12 is a flowchart 1200 of a method of wireless communication. The method may be performed by a UE (e.g., the UE 104 and / or the device 1304 of FIG. 13). The method may facilitate improved synchronization and measurement for reduced capability UEs.

[0137]

[0154] At 1202, the UE indicates UE capabilities to the network as described in connection with capabilities 1010 of Figure 10. For example, the UE may be a reduced capability UE or a high capability UE. The indicating of capabilities at 1202 may be performed by the cellular RF transceiver 1322 / prioritization component 198 of the apparatus 1304 of Figure 13.

[0138]

[0155] At 1204, the UE receives a configuration of measurement objects and downlink BWP in a system information or RRC message, as described in connection with the configuration 1020 of FIG. 10. The configuration may indicate that the downlink BWP includes CD-SSB, NCD-SSB, or no SSB. The configuration of measurement objects and downlink BWP may be based on at least one or more of a duplex mode type, a frequency range, a type of downlink BWP, or a UE capability. For example, the UE configuration may be different based on whether the UE is a reduced capability UE or a high capability UE, and / or may be different when 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 measurements and UL transmissions without collision processing. As an example, the frequency range may be FR1, FR2, licensed spectrum, or unlicensed spectrum. Receiving the configuration at 1204 may be performed by the cellular RF transceiver 1322 / prioritization component 198 of the device 1304 of FIG.

[0139]

[0156] In some aspects, the UE may have reduction capability, as described in connection with the example of Figure 7, and the configuration in 1204 may be for an initial DL BWP that includes one of CD-SSB or NCD-SSB, or the configuration may be for an initial DL BWP that does not include an SSB of the serving cell. In some aspects, the UE may have reduction capability, as described in connection with the example of Figure 7, and the configuration may be for a non-initial DL BWP that includes one of CD-SSB or NCD-SSB, or the configuration may be for a non-initial DL BWP that does not include an SSB of the serving cell.

[0140]

[0157] In some aspects, the UE may be a high capability UE and the configuration may be for an initial DL BWP including CD-SSB or including CD-SSB and NCD-SSB of the serving cell, as described in conjunction with the example of Figure 8. In some aspects, the UE may be a high capability UE and the configuration may be for a non-initial DL BWP for a UE in an RRC connected state and may include at least one of CD-SSB or NCD-SSB, or the configuration may be for a non-initial DL BWP that does not include SSB of the serving cell, as described in conjunction with the example of Figure 8.

[0141]

[0158] In some aspects, the configuration (e.g., in 1204) may be of a DL BWP including CD-SSBs and NCD-SSBs from a serving cell, where the CD-SSBs and NCD-SSBs share at least one of the following: the same primary synchronization signal sequence, the same secondary synchronization signal sequence, PCI, the same number of SSBs transmitted in each SSB burst, the same pattern of SSBs transmitted in each SSB burst, the same transmit power, the same periodicity of the SSB bursts, the same QCL resource, the same numerology of one or more physical signals or physical channels of the SSBs, or the same EPRE boost ratio of one or more physical signals or physical channels of the SSBs.

[0142]

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

[0143]

[0160] In some aspects, the configuration may be of a DL BWP including both CD-SSBs and NCD-SSBs from the serving cell as well as a measurement target of the serving cell. In some such examples, the UE may measure 1206 all or a portion of one of the SSBs of the CD-SSB burst or the NCD-SSB burst in the slot as described in conjunction with the measurement procedure 1040 of FIG. 10. The UE may also skip measuring 1208 all or a portion of the other of the CD-SSB burst or the NCD-SSB burst in the slot as described in conjunction with the suppression procedure 1042 of FIG. 10. In some aspects, one SSB burst may include multiple SSBs that may span multiple slots. For example, an SSB burst in FR1 may include up to 8 SSBs, or up to 64 SSBs in higher frequencies. Depending on the measurement target configuration, the UE may selectively measure a subset of the SSBs transmitted in the SSB burst. Execution of 1206 and 1208 may be performed by prioritization component 198 of apparatus 1304 of FIG.

[0144]

[0161] In some aspects, the UE may operate in a TDD mode or an HD-FDD mode at 1203. The UE may receive 1210 scheduling of uplink transmissions (e.g., semi-static or dynamic scheduling information) as described in connection with the uplink scheduling information 1022 of FIG. 10. As an example, semi-static UL scheduling may include cell-specific configuration by SI or UE-specific configuration by dedicated RRC or MAC-CE. Dynamic UL scheduling may include dynamic UL grants (e.g., random access response to msg3) in the PDCCH or PDSCH. The uplink transmission may overlap in time with the measurement of the SSB, or the switching gap may overlap in time with the measurement of the SSB. The UE may receive 1212 a measurement target configuration defined for the SSB of the serving cell, the SSB having an insufficient switching gap associated with the scheduled uplink transmission. The insufficient switching gap may correspond to one or more of the SSBs overlapping with the UL transmission, or the SSBs not overlapping with the UL transmission. The UE may measure 1206 a defined SSB to be measured, the SSB having an overlap in the time domain with one or more of the uplink transmissions or switching gaps associated with the uplink transmissions. The UE may skip 1214 a transmission of the uplink transmission fully or partially based on at least the UE capability for UL cancellation (e.g., whether the UE can partially or fully cancel the UL transmission may be optional UE capability) and the switching gap between DL and UL in the time domain, as described in connection with the skip procedure 1044 of FIG. 10. Aspects of 1203, 1206, 1212, and 1214 may be performed by the prioritization component 198 of the apparatus 1304 of FIG. 13.

[0145]

[0162] In some aspects, the UE may operate in a TDD mode or an HD-FDD mode, at 1203. The UE may receive 1210 a scheduling (e.g., semi-static or dynamic scheduling information) of an uplink transmission that overlaps with an SSB of an SSB burst that is not defined by a measurement configuration of the UE, as described in conjunction with the uplink scheduling information 1022 of FIG. 10. The UE may skip 1216 a measurement of one or more SSBs of an SSB burst that is not defined by a configuration configured for the UE, as described in conjunction with the suppression procedure 1042 of FIG. 10. The UE may transmit 1218 an uplink transmission that overlaps in time with an SSB, as described in conjunction with the uplink transmission 1046 of FIG. 10. The aspects of 1203, 1210, 1216, and 1218 may be performed by a prioritization component 198 of the apparatus 1304 of FIG. 13.

[0146]

[0163] In some aspects, the configuration at 1204 may be for a DL BWP that includes a CD-SSB and does not include an NCD-SSB from the serving cell, as described in connection with the initial downlink BWP 704 and the non-initial downlink BWP 746 of FIG. 7 and / or the initial downlink BWP 804, the initial downlink BWP 824, and the initial downlink BWP 864 of FIG. 8. The UE may skip measuring the other of the NCD-SSBs at 1220, as described in connection with the suppression procedure 1042 of FIG. 10. The measurements 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, tracking loop, or automatic gain control. The aspect of 1220 may be performed by the prioritization component 198 of the apparatus 1304 of FIG. 13.

[0147]

[0164] In some aspects, the configuration at 1204 may be for a DL BWP that does not include an SSB from the serving cell, as described in connection with the initial downlink BWP 724, the initial downlink BWP 764, and the non-initial downlink BWP 766 of Figure 7, and / or the non-initial downlink BWP 866 of Figure 8. As described in connection with the switching procedure 1032 of Figure 10, the UE may switch to a different BWP to measure a CD-SSB from the serving cell when the UE is in an RRC idle state at 1222, and the UE may switch to a different BWP to measure a CD-SSB or an NCD-SSB from the serving cell when the UE is in an RRC connected state or an RRC inactive state at 1224. The aspects of 1222 and 1224 may be performed by the prioritization component 198 of the apparatus 1304 of Figure 13.

[0148]

[0165] In some aspects, the UE may operate in TDD mode or HD-FDD mode in 1203, and the BWP switching delay associated with switching to a different BWP for measuring CD-SSB or NCD-SSB may be included in at least the measurement object configuration and time gap considerations for collision handling between SSB measurements and uplink transmissions. The aspects of 1203 may be performed by the prioritization component 198 of the apparatus 1304 of FIG.

[0149]

[0166] FIG. 13 is a diagram 1300 illustrating an example of a hardware implementation for the device 1304. The device 1304 may be a UE, may be a component of a UE, or may implement UE functionality. In some aspects, the device 1304 may include a cellular baseband processor 1324 (also referred to as a modem) coupled to one or more transceivers (e.g., a cellular RF transceiver 1322). The cellular baseband processor 1324 may include an on-chip memory 1324'. In some aspects, the device 1304 may further include an application processor 1306 coupled to one or more subscriber identity module (SIM) cards 1320, a secure digital (SD) card 1308, and a screen 1310. The application processor 1306 may include an on-chip memory 1306'. In some aspects, the device 1304 may further include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), one or more sensor modules 1318 (e.g., a barometric sensor / altimeter, an inertial measurement unit (IMU), a motion sensor such as a gyroscope, and / or an accelerometer, light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies used for positioning), an additional memory module 1326, a power source 1330, and / or a camera 1332. The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include an on-chip transceiver (TRX) (or in some cases simply a receiver (RX)).The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include their own dedicated antennas and / or utilize one or more antennas 1380 for communication. The cellular baseband processor 1324 communicates with the UE 104 and / or RUs associated with the network entity 1302 through a transceiver (e.g., a cellular RF transceiver 1322) via one or more antennas 1380. The cellular baseband processor 1324 and the application processor 1306 may each include a computer-readable medium / memory, such as an on-chip memory 1324′ and an on-chip memory 1306′, respectively. The additional memory module 1326 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory (e.g., the on-chip memory 1324′, the on-chip memory 1306′, and / or the additional memory module 1326) may be non-transitory. The cellular baseband processor 1324 and the application processor 1306 are each responsible for general processing, including the execution of software stored in a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1324 / application processor 1306, causes the cellular baseband processor 1324 / application processor 1306 to perform various functions as described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1324 / application processor 1306 when executing the software. The cellular baseband processor 1324 / application processor 1306 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359.In one configuration, the device 1304 may be a processor chip (modem and / or application) and may include only the cellular baseband processor 1324 and / or the application processor 1306, while in another configuration, the device 1304 may be an entire UE (e.g., see UE 350 in FIG. 3) and may include additional modules of the device 1304.

[0150]

[0167] As described above, the prioritization component 198 is configured to indicate the UE capabilities to the network and receive in the system information or RRC message the configuration of the measurement objects and DL BWP, the configuration indicating that the DL BWP includes a CD-SSB, an NCD-SSB, or no SSB, and the configuration of the measurement objects and DL BWP is based at least on one or more of the duplex mode type, the frequency range, the type of DL BWP, or the UE capabilities.

[0151]

[0168] The prioritization component 198 may be within the cellular baseband processor 1324, the application processor 1306, or both the cellular baseband processor 1324 and the application processor 1306. The prioritization component 198 may be one or more hardware components specifically configured to perform the described processes / algorithms, may be implemented by one or more processors configured to execute the described processes / algorithms, may be stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0152]

[0169] As shown, the device 1304 may include various components configured for various functions. For example, the prioritization component 198 may include one or more hardware components that implement each of the algorithm blocks in the flowcharts of FIG. 11 and / or FIG.

[0153]

[0170] In one configuration, the apparatus 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, includes means for indicating the UE capabilities to the network. The example apparatus 1304 also includes means for receiving a configuration of the measurement object and the DL BWP in a system information or RRC message, the configuration indicating that the DL BWP includes a CD-SSB, includes a NCD-SSB, or no SSB is present, and the configuration of the measurement object and the DL BWP is based at least on one or more of a duplex mode type, a frequency range, a type of DL BWP, or a UE capability.

[0154]

[0171] In another configuration, the example apparatus 1304 also includes means for measuring all or a portion of one of the CD-SSB or NCD-SSB bursts in the slot. The example apparatus 1304 also includes means for skipping measurement of all or a portion of a different one of the CD-SSB or NCD-SSB bursts in the slot.

[0155]

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

[0156]

[0173] In another configuration, the exemplary apparatus 1304 also includes means for operating in a TDD mode or an HD-FDD mode. The exemplary apparatus 1304 also includes means for receiving semi-static or dynamic scheduling information for uplink transmissions that overlap with SSBs of SSB bursts not defined by a measurement configuration for the UE. The exemplary apparatus 1304 also includes means for skipping measurements of one or more SSBs of SSB bursts not defined by a configuration configured for the UE. The exemplary apparatus 1304 also includes means for transmitting an uplink transmission.

[0157]

[0174] In another configuration, the exemplary apparatus 1304 also includes means for skipping another NCD-SSB measurement outside the DL BWP, the measurement being one or more of cell selection, cell reselection, radio resource management, radio link monitoring, beam management, UL resource selection, power control, timing advance verification, link recovery, tracking loop, or automatic gain control.

[0158]

[0175] In another configuration, the example apparatus 1304 also includes means for switching to a different BWP to measure the CD-SSB from the serving cell when the UE is in an RRC idle state. The example apparatus 1304 also includes means for switching to a different BWP to measure the CD-SSB or the NCD-SSB from the serving cell when the UE is in an RRC connected state or an RRC inactive state.

[0159]

[0176] In another configuration, the exemplary apparatus 1304 also includes means for operating in TDD mode or HD-FDD mode, and the BWP switching delay associated with switching to a different BWP for measuring CD-SSB or NCD-SSB is included in at least the measurement target configuration and time gap considerations for collision handling between SSB measurements and uplink transmissions.

[0160]

[0177] The means may be the prioritization component 198 of the apparatus 1304 configured to perform the recited functions by said means. As described above, the apparatus 1304 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the recited functions by said means.

[0161]

[0178] 14 is a flowchart 1400 of a method of wireless communication. The method may be performed by a network entity (e.g., the base station 102 and / or the network entity 1602 of FIG. 16). The method may facilitate improved synchronization and measurement for reduced capability UEs.

[0162]

[0179] At 1402, a network entity receives an indication of UE capabilities of at least one UE, as described in connection with capabilities 1010 of Figure 10. For example, the UE may be a reduced capability UE or a high capability UE. Receiving the indication at 1402 may be performed by component 199 of network entity 1602 of Figure 16.

[0163]

[0180] At 1404, the network entity configures serving cell measurements and one or more DL BWPs, as described in conjunction with the configuration 1020 of FIG. 10. In some examples, the configuration of 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, the configuration of each DL BWP and measurement object for the serving cell may include a CD-SSB, may include a NCD-SSB, or may not include an SSB of the serving cell, based on one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability, as described in conjunction with the examples of FIG. 7 and FIG. 8. The configuring at 1404 may be performed by the configuration component 199 of the network entity 1602 of FIG. 16.

[0164]

[0181] 15 is a flowchart 1500 of a method of wireless communication. The method may be performed by a network entity (e.g., the base station 102 and / or the network entity 1602 of FIG. 16). The method may facilitate improved synchronization and measurement for reduced capability UEs.

[0165]

[0182] At 1502, a network entity receives an indication of UE capabilities of at least one UE, as described in connection with capabilities 1010 of Figure 10. For example, the UE may be a reduced capability UE or a high capability UE. Receiving the indication at 1502 may be performed by component 199 of network entity 1602 of Figure 16.

[0166]

[0183] In 1504, the network entity configures serving cell measurements and one or more DL BWPs, as described in conjunction with the configuration 1020 of FIG. 10. In some examples, the configuration of 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, the configuration of each DL BWP and measurement object for the serving cell may include a CD-SSB, may include a NCD-SSB, or may not include an SSB of the serving cell, based on one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability, as described in conjunction with the examples of FIG. 7 and FIG. 8. The configuring in 1504 may be performed by the configuration component 199 of the network entity 1602 of FIG. 16.

[0167]

[0184] In some examples, the network entity may transmit, in 1506, the configuration of each downlink BWP for the serving cell in a system information or RRC message, as described in connection with the configuration 1020 of Figure 10. The transmitting in 1506 may be performed by the configuration component 199 of the network entity 1602 of Figure 16.

[0168]

[0185] As an example, the UE capabilities may be reduced capabilities and the configuration may be for an initial DL BWP including one of CD-SSB or NCD-SSB, or the configuration may be for an initial DL BWP that does not include SSB of the serving cell, as described in connection with the example of FIG.

[0169]

[0186] In some aspects, the UE capabilities may be reduced capabilities, as described in connection with the example of FIG. 7, and the configuration may be for a non-initial DL BWP that includes one of CD-SSB or NCD-SSB, or the configuration may be for a non-initial DL BWP that does not include an SSB of the serving cell.

[0170]

[0187] In some aspects, the UE capability may be high capability and the configuration may be for an initial DL BWP including CD-SSB or including CD-SSB and NCD-SSB of the serving cell, as described in conjunction with the example of Figure 8. In some aspects, the UE capability may be high capability and the configuration may be for a non-initial DL BWP for a UE in an RRC connected state including at least one of CD-SSB or NCD-SSB, or the configuration may be for a non-initial DL BWP that does not include SSB of the serving cell, as described in conjunction with the example of Figure 8.

[0171]

[0188] In some aspects, the configuration in 1504 may be of a first DL BWP including CD-SSBs and NCD-SSBs from a serving cell, where the CD-SSBs and NCD-SSBs share at least one of the following: the same primary synchronization signal sequence, the same secondary synchronization signal sequence, PCI, the same number of SSBs transmitted in each SSB burst, the same pattern of SSBs transmitted in each SSB burst, the same transmit power, the same periodicity of the SSB bursts, the same QCL resource, the same numerology of one or more physical signals or physical channels of the SSBs, or the same EPRE boost ratio of one or more physical signals or physical channels of the SSBs.

[0172]

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

[0173]

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

[0174]

[0191] FIG. 16 is a diagram 1600 illustrating an example of a hardware implementation for a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or a RU 1640. For example, depending on the layer functionality processed by the configuration component 199, the network entity 1602 may include a CU 1610, both the CU 1610 and the DU 1630, each of the CU 1610, the DU 1630, and the RU 1640, the DU 1630, both the DU 1630 and the RU 1640, or the RU 1640. The CU 1610 may include a CU processor 1612. The CU processor 1612 may include an on-chip memory 1612′. In some aspects, the network entity 1602 may further include an additional memory module 1614 and a communication interface 1618. The CU 1610 communicates with the DU 1630 via a midhaul link, such as an F1 interface. The device 1630 may include a DU processor 1632. The DU processor 1632 may include an on-chip memory 1632′. In some aspects, the DU 1630 may further include an additional memory module 1634 and a communication interface 1638. The DU 1630 communicates with the RU 1640 via a fronthaul link. The RU 1640 may include a RU processor 1642. The RU processor 1642 may include an on-chip memory 1642′. In some aspects, the RU 1640 may further include an additional memory module 1644, one or more transceivers 1646, an antenna 1680, and a communication interface 1648. The RU 1640 communicates with the UE 104. Each of the on-chip memory (e.g., on-chip memory 1612′, on-chip memory 1632′, and / or on-chip memory 1642′) and / or additional memory modules (e.g., additional memory module 1614, additional memory module 1634, and / or additional memory module 1644) may be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory.Each of the CU processor 1612, DU processor 1632, and RU processor 1642 is responsible for general processing, including the execution of software stored in a computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the processor when executing the software.

[0175]

[0192] As described above, the configuration component 199 is configured to receive an indication of UE capabilities of at least one UE. The configuration component 199 may also be configured to configure serving cell measurements and one or more DL BWPs, where the configuration of each DL BWP is based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

[0176]

[0193] The components 199 may be in one or more processors of one or more of the CU 1610, the DU 1630, and the RU 1640. The components 199 may be one or more hardware components specifically configured to perform the described processes / algorithms, may be implemented by one or more processors configured to execute the described processes / algorithms, may be stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0177]

[0194] The network entity 1602 may include various components configured for various functions. For example, the configuration components 199 may include one or more hardware components that execute each of the blocks of the algorithms in the flowcharts of FIG. 14 and / or FIG. 15.

[0178]

[0195] In one configuration, the network entity 1602 includes means for receiving an indication of UE capabilities of at least one UE. The example network entity 1602 also includes means for configuring serving cell measurements and one or more DL BWPs, each DL BWP configuration based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

[0179]

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

[0180]

[0197] In another configuration, the example network entity 1602 also includes means for transmitting the CD-SSB or NCD-SSB on demand within 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, the first UE having reduced or high capability and allowed to access the serving cell.

[0181]

[0198] In another configuration, the example network entity 1602 also includes means for transmitting the configuration of each DL BWP for the serving cell within a system information or RRC message.

[0182]

[0199] The means may be components 199 of the network entity 1602 configured to perform the recited functions by the means. As discussed above, the network entity 1602 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the recited functions by the means.

[0183]

[0200] Aspects disclosed herein provide techniques for different SSB transmissions in the initial / non-initial downlink BWP for different UE types (e.g., reduced capability UEs or non-reduced capability UEs) when a cell allows different UE types to access the cell. That is, different SSB transmissions in the initial / non-initial downlink BWP for different UE types can be supported when a cell supports coexistence of reduced capability UEs and non-reduced capability UEs. 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).

[0184]

[0201] It should be understood that the particular order or hierarchy of the blocks in the disclosed processes / flow charts is an example of an example approach. It should be understood that the particular order or hierarchy of the blocks in those processes / flow charts can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The accompanying method claims present elements of the various blocks in an example order and are not limited to the particular order or hierarchy presented.

[0185]

[0202] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims. Reference to an element in the singular does not mean "only one" unless so expressly stated, but rather means "one or more." Terms such as "if," "when," and "while" do not imply an immediate temporal relationship or reaction. That is, these phrases, such as "when," do not imply an immediate action in response to or during the occurrence of an action, but simply mean that an action will occur if a condition is met, but do not require a specific or immediate temporal constraint for the action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects. Unless expressly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple As, multiple Bs, or multiple Cs.Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination can include one or more elements of A, B, or C. A set should be interpreted as a set of elements, the number of elements being one or more. Thus, for a set of X, X will include one or more elements. When a first device receives data from or transmits data to a second device, the data can be received / transmitted directly between the first device and the second device, or indirectly between the first device and the second device via a set of devices. A device configured to "output" data, such as a transmission, signal, or message, may transmit the data, for example, using a transceiver, or may send the data to a device that transmits the data. A device configured to "receive" data, such as a transmission, signal, or message, may receive the data, for example, using a transceiver, or may obtain the data from a device that receives the data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later become known to those of skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," "device," and the like may not be substitutes for the word "means." Thus, no element of a claim should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

[0186]

[0203] As used herein, the phrase "based on" should not be construed as a reference to a closed set of information, condition(s), factor(s), etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) is to be construed as "based on at least A," unless expressly stated otherwise.

[0187]

[0204] The following aspects are exemplary only and can be combined with other aspects or teachings described herein without limitation.

[0188]

[0205] Aspect 1 is a method of wireless communication in a UE, comprising indicating UE capabilities to a network and receiving a configuration of measurement objects and DL BWP in system information or an RRC message, the configuration indicating that the DL BWP includes a CD-SSB, an NCD-SSB, or no SSB, and the configuration of measurement objects and DL BWP is based at least on one or more of a duplex mode type, a frequency range, a type of DL BWP, or the UE capabilities.

[0189]

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

[0190]

[0207] Example 3 is the method of example 1, further including that the UE has reduction capability and the configuration is for a non-initial DL BWP that includes one of CD-SSB or NCD-SSB, or the configuration is for a non-initial DL BWP that does not include an SSB of the serving cell.

[0191]

[0208] Example 4 is the method of example 1, further comprising: the UE being a high capability UE; and the configuration being for an initial DL BWP including CD-SSB or including CD-SSB and NCD-SSB of the serving cell.

[0192]

[0209] Example 5 is the method of example 1, further comprising: the UE is a high capability UE; and the configuration is for a non-initial DL BWP for the UE in an RRC connected state and includes at least one of a CD-SSB or an NCD-SSB; or the configuration is for a non-initial DL BWP that does not include an SSB of a serving cell.

[0193]

[0210] Example 6 is the method of any of examples 1 to 5, further including: the configuration is of a DL BWP including CD-SSBs and NCD-SSBs from a serving cell, and the CD-SSBs and NCD-SSBs share at least one of the following: the same primary synchronization signal sequence, the same secondary synchronization signal sequence, PCI, the same number of SSBs transmitted in each SSB burst, the same pattern of SSBs transmitted in each SSB burst, the same transmit power, the same periodicity of the SSB bursts, QCL resources, the same numerology for one or more physical signals or physical channels of the SSBs, or the same EPRE boost ratio for one or more physical signals or physical channels of the SSBs.

[0194]

[0211] Example 7 is the method of example 6, further comprising multiplexing the CD-SSB burst with the NCD-SSB burst in the DL BWP in at least one of time or frequency.

[0195]

[0212] Example 8 is the method of any of Examples 1 to 7, further including that the configuration is for a DL BWP including both CD-SSB and NCD-SSB from the serving cell and a measurement target of the serving cell, and the method further includes measuring all or a portion of an SSB of one of the CD-SSB or NCD-SSB bursts in the slot, and skipping measuring all or a portion of an SSB of a different one of the CD-SSB or NCD-SSB bursts in the slot.

[0196]

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

[0197]

[0214] Example 10 is the method of any of Examples 1 to 8, further including operating in a TDD mode or an HD-FDD mode, receiving semi-static or dynamic scheduling information for uplink transmissions that overlap with SSBs of SSB bursts not defined by a measurement configuration for the UE, skipping measurements of one or more SSBs of SSB bursts not defined by a measurement object configured for the UE, and transmitting the uplink transmissions.

[0198]

[0215] Example 11 is the method of any of Examples 1 to 5, further including that the configuration is for a DL BWP that includes a CD-SSB from the serving cell and does not include an NCD-SSB, and the method further includes skipping measurements of another NCD-SSB outside the DL BWP, and the measurements are for one or more of cell selection, cell reselection, radio resource management, radio link monitoring, beam management, UL resource selection, power control, timing advance verification, link recovery, tracking loop, or automatic gain control.

[0199]

[0216] Example 12 is the method of any of Examples 1 to 5, further including that the configuration is for a DL BWP that does not include an SSB from the serving cell, and the method further includes switching to a different BWP to measure a CD-SSB from the serving cell when the UE is in an RRC idle state, and switching to the different BWP to measure a CD-SSB or an NCD-SSB from the serving cell when the UE is in an RRC connected state or an RRC inactive state.

[0200]

[0217] Example 13 is the method of any of Examples 1 to 12, further comprising operating in a TDD mode or an HD-FDD mode, and wherein a BWP switching delay associated with switching to a different BWP for measuring CD-SSB or NCD-SSB is included in at least the measurement target configuration and time gap considerations for collision handling between SSB measurements and uplink transmissions.

[0201]

[0218]

[0031] Example 14 is an apparatus for wireless communication in a UE, comprising at least one processor coupled to a memory and configured to perform the method of any of Examples 1-13.

[0202]

[0219] In example 15, the apparatus of example 14 further includes at least one antenna coupled to the at least one processor.

[0203]

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

[0204]

[0221] Example 17 is an apparatus for wireless communication comprising means for performing any of Examples 1 to 13.

[0205]

[0222] In an embodiment 18, the apparatus of embodiment 17 further comprises at least one antenna coupled to the means for performing the method of any of embodiments 1-13.

[0206]

[0223] In an embodiment 19, the apparatus of embodiments 17 or 18 further comprises a transceiver coupled to the means for performing the method of any of embodiments 1-13.

[0207]

[0224] Aspect 20 is a non-transitory computer-readable storage medium storing computer-executable code that, when executed by a processor, causes the processor to perform any of aspects 1 to 13.

[0208]

[0225] Aspect 21 is a method of wireless communication in a network entity, comprising receiving an indication of UE capabilities of at least one UE, and configuring serving cell measurements and one or more DL BWPs, where the configuration of each DL BWP is based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

[0209]

[0226] Example 22 is the method of example 21, further comprising: based on one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability, the measurement object configuration for each DL BWP and serving cell includes a CD-SSB, includes an NCD-SSB, or does not include an SSB of the serving cell.

[0210]

[0227] Example 23 is the method of any of examples 21 and 22, further including that the UE capabilities are reduced capabilities and the configuration is for an initial DL BWP that includes one of CD-SSB or NCD-SSB, or the configuration is for an initial DL BWP that does not include an SSB of the serving cell.

[0211]

[0228] Example 24 is the method of any of examples 21 and 22, further including that the UE capabilities are reduced capabilities and the configuration is for a non-initial DL BWP that includes one of CD-SSB or NCD-SSB, or the configuration is for a non-initial DL BWP that does not include an SSB of the serving cell.

[0212]

[0229] Example 25 is the method of any of examples 21 and 22, further comprising: the UE capability is high capability; and the configuration is for an initial DL BWP including CD-SSB or including CD-SSB and NCD-SSB of the serving cell.

[0213]

[0230] Example 26 is the method of any of Examples 21 and 22, further comprising: the UE capability is high capability; and the configuration is for a non-initial DL BWP of at least one UE in an RRC connected state, and includes at least one of a CD-SSB or an NCD-SSB; or the configuration is for a non-initial DL BWP that does not include an SSB of a serving cell.

[0214]

[0231] Example 27 is the method of any of examples 21 to 26, further including: the configuration is for a first DL BWP of one or more DL BWPs including a CD-SSB and an NCD-SSB from a serving cell, and the CD-SSB and the NCD-SSB share at least one of the following: the same primary synchronization signal sequence, the same secondary synchronization signal sequence, PCI, the same number of SSBs transmitted in each SSB burst, the same pattern of SSBs transmitted in each SSB burst, the same transmit power, the same periodicity of the SSB bursts, the same QCL resource, the same numerology for one or more physical signals or physical channels of the SSBs, or the same EPRE boost ratio for one or more physical signals or physical channels of the SSBs.

[0215]

[0232] Example 28 is the method of any of Examples 21 to 27, further comprising multiplexing the CD-SSB burst in at least one of time or frequency with the NCD-SSB burst in the first DL BWP.

[0216]

[0233] Example 29 is the method of any of Examples 21 to 24, 26, and 27, further comprising transmitting a CD-SSB or an NCD-SSB on demand within a first DL BWP of the one or more DL BWPs upon receiving a request from a first UE in an RRC idle state, an inactive state, or a connected state, where the first UE has reduced capability or high capability and is allowed to access the serving cell.

[0217]

[0234] Example 30 is the method of any of examples 21 to 29, further comprising sending the configuration of each DL BWP for the serving cell in a system information or RRC message.

[0218]

[0235]

[0031] Aspect 31 is an apparatus for wireless communication in a network entity, comprising at least one processor coupled to a memory and configured to perform any of aspects 21 to 30.

[0219]

[0236] In example 32, the apparatus of example 31 further includes at least one antenna coupled to the at least one processor.

[0220]

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

[0221]

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

[0222]

[0239] In example 35, the apparatus of example 34 further includes at least one antenna coupled to the means for performing the method of any of examples 21-30.

[0223]

[0240] In an embodiment 36, the apparatus of embodiment 34 or 35 further comprises a transceiver coupled to the means for performing the method of any of embodiments 21-30.

[0224]

[0241] Aspect 37 is a non-transitory computer-readable storage medium storing computer-executable code that, when executed, causes a processor to perform any of aspects 21 to 30.

Claims

1. 1. An apparatus for wireless communication in a user equipment (UE), comprising: Memory and and at least one processor coupled to the memory, the at least one processor comprising: Indicating UE capabilities to the network; 1. An apparatus configured to receive a configuration of a measurement object and a downlink (DL) bandwidth portion (BWP), the configuration indicating that the DL BWP includes a cell-defined synchronization signal block (CD-SSB), includes a non-CD-SSB (NCD-SSB), or no SSB is present, and the configuration of the measurement object and the DL BWP is based on at least one or more of a duplex mode type, a frequency range, a type of the DL BWP, or the UE capabilities.

2. 2. The apparatus of claim 1, wherein the UE has downlink 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.

3. the UE has mitigation capability; 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, or The configuration is of an initial DL BWP including the CD-SSB or including the CD-SSB and the NCD-SSB of a serving cell, or 2. The apparatus of claim 1, wherein the configuration is for a non-initial DL BWP for the UE in a Radio Resource Control (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.

4. The configuration is of the DL BWP including the CD-SSB and the NCD-SSB from a serving cell, and the CD-SSB and the NCD-SSB are The same primary synchronization signal sequence, The same secondary synchronization signal sequence, Physical Cell Identifier (PCI), The same number of SSBs transmitted in each SSB burst, The same pattern of SSB transmitted in each SSB burst, Same transmit power, The same periodicity of SSB bursts, The same quasi-collocated (QCL) resource, the same numerology for one or more physical signals or physical channels of said SSB; or the same energy per resource element (EPRE) boost ratio for the one or more physical signals or physical channels of the SSB; The device of claim 1 , wherein the device shares at least one of:

5. 5. The apparatus of claim 4, wherein CD-SSB bursts are multiplexed with NCD-SSB bursts in the DL BWP in at least one of time or frequency.

6. The configuration is of the DL BWP including both the CD-SSB and the NCD-SSB from a serving cell and the measurement target of the serving cell, and the at least one processor: measuring the SSB of all or part of one of the CD-SSB or NCD-SSB bursts in the slot; The apparatus of claim 1 , further configured to skip measuring the SSB of all or part of a different one of the CD-SSB burst or the NCD-SSB burst in the slot.

7. the at least one processor: Operates in time division duplex (TDD) mode or half duplex frequency division duplex (HD-FDD) mode; receiving semi-static or dynamic scheduling information for uplink transmissions; receiving a measurement object configuration defined for the SSB of a serving cell, where the SSB has an insufficient switching gap associated with the uplink transmission; 2. The apparatus of claim 1, further configured to: fully or partially skip transmission of the uplink (UL) transmission based at least in part on the UE capability for uplink (UL) cancellation and the insufficient switching gap between DL and UL in the time domain.

8. the at least one processor: Operates in time division duplex (TDD) mode or half duplex frequency division duplex (HD-FDD) mode; receiving semi-static or dynamic scheduling information for uplink transmissions that overlap with SSBs of SSB bursts not defined by a measurement configuration for the UE; skipping measurements of one or more SSBs of the SSB bursts that are not defined by the measurement object configured for the UE; The apparatus of claim 1 , further configured to transmit the uplink transmission.

9. the configuration is for the DL BWP including the CD-SSB from a serving cell and not including the NCD-SSB, and the at least one processor:

10. The apparatus of claim 1, further configured to skip another NCD-SSB measurement outside the DL BWP, the measurement being for one or more of cell selection, cell reselection, radio resource management, radio link monitoring, beam management, uplink resource selection, power control, timing advance verification, link recovery, tracking loop, or automatic gain control.

10. The configuration is for the DL BWP that does not include the SSB from a serving cell, and the at least one processor: When the UE is in a Radio Resource Control (RRC) idle state, switching to a different BWP to measure the CD-SSB from the serving cell; 2. The apparatus of claim 1, further configured to measure the CD-SSB or the NCD-SSB from the serving cell when the UE is in an RRC connected state or an RRC inactive state after the switch to the different BWP.

11. the at least one processor:

11. The apparatus of claim 10, further configured to operate in a time division duplex (TDD) mode or a half-duplex frequency division duplex (HD-FDD) mode, and wherein a BWP switching delay associated with switching to the different BWP for measuring the CD-SSB or the NCD-SSB is included in at least a measurement target configuration and a time gap consideration for collision handling between SSB measurements and uplink transmissions.

12. the at least one processor: The apparatus of claim 1 , further configured to receive the measurement object and the configuration of the DL BWP in a system information or radio resource control (RRC) message.

13. 1. A method of wireless communication in a user equipment (UE), comprising: Indicating UE capabilities to the network; receiving a configuration of a measurement object and a downlink (DL) bandwidth portion (BWP), wherein the configuration indicates that the DL BWP includes a cell-defined synchronization signal block (CD-SSB), includes a non-CD-SSB (NCD-SSB), or no SSB is present, and wherein the configuration of the measurement object and the DL BWP is based on at least one or more of a duplex mode type, a frequency range, a type of the DL BWP, or the UE capabilities.

14. 1. An apparatus for wireless communication in a network entity, comprising: Memory and and at least one processor coupled to the memory and the transceiver, the at least one processor comprising: receiving an indication of UE capabilities of at least one user equipment (UE); 1. An apparatus configured to perform serving cell measurements and configure one or more downlink (DL) bandwidth portions (BWPs), wherein the configuration of each DL BWP is based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or the UE capabilities.

15. 1. A method of wireless communication in a network entity, comprising: receiving an indication of UE capabilities of at least one user equipment (UE); and configuring one or more downlink (DL) bandwidth portions (BWPs), wherein the configuration of each DL BWP is based on at least one or more of a duplex mode type, a frequency range, a DL BWP type, or a UE capability.

Images