BWP configuration for UEs with different capabilities

Abstract

A user equipment (UE) having a first capability associated with a maximum UE bandwidth lower than a second capability performs at least a portion of an initial access based on an initial downlink bandwidth portion (BWP) shared between the UE having the first capability and the UE having the second capability, and after the initial access, the UE switches to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability to perform random access, paging, system acquisition, measurement, and data communication procedures.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of and priority to U.S. Provisional Application No. 63 / 234,674, entitled "BWP Configurations for UEs Having Different Capabilities," filed on August 18, 2021, and U.S. Non-Provisional Application No. 17 / 871,879, entitled "BWP CONFIGURATIONS FOR UES HAVING DIFFERENT CAPABILITIES," filed on July 22, 2022, which are expressly incorporated by reference in their entireties.

[0002] TECHNICAL FIELD The present disclosure relates generally to communication systems, and more particularly to bandwidth part (BWP) based wireless communications. [Background technology]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcast. Typical wireless communication systems may utilize 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] These multiple access technologies are being adopted in various telecommunications standards to provide common protocols that allow different wireless devices to communicate at city, national, regional, and even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services related to 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. There is a need for further improvements in 5G NR technology that may also be applicable to other multiple access technologies and telecommunications standards that utilize those technologies. Summary of the Invention

[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 contemplated aspects. It 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] In addition to higher capability devices, wireless communications may support reduced capability devices. In some examples, reduced capability UEs may have reduced transmission or reception bandwidths compared to other UEs. Aspects presented herein provide configuration and signaling support for reduced capability UEs that enable joint optimization of DL / UL BWP configurations, coexistence of different UE capabilities, power savings for reduced capability UEs, mitigation of resource fragmentation on DL / UL, and / or reduced signaling overhead. [Means for solving the problem]

[0007] In some aspects, UEs with different levels of capability, such as reduced capability UEs and non-reduced (or higher) capability UEs, may share an initial DL BWP for initial access. In some aspects, a separate initial BWP, e.g., a dedicated initial downlink BWP and / or a dedicated initial uplink BWP, may be provided for UEs with reduced bandwidth. Aspects presented herein may provide for configuration of BWPs for initial access and thereafter that support reduced bandwidth according to reduced capability UEs while maintaining flexibility in configuring bandwidth for higher capability UEs.

[0008] In one aspect of the disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication in a UE having a first capability associated with a maximum user equipment (UE) bandwidth lower than a second capability. The apparatus performs at least a portion of an initial access based on an initial downlink bandwidth portion (BWP) shared between the UE having the first capability and the UE having the second capability. After the initial access, the apparatus switches to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability.

[0009] In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus for wireless communication in a network entity are provided. The apparatus performs an initial access with a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, and the initial access is based at least in part on an initial downlink BWP shared between the UE having the first capability and the UE having the second capability. The apparatus switches to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability for communication with the UE.

[0010] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of the various aspects may be employed and the description is intended to include all such aspects and their equivalents. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 illustrates an example of a wireless communication system and an access network in accordance with various aspects presented herein. [Figure 2A] FIG. 2 illustrates an example of a first frame in accordance with various aspects of the present disclosure. [Figure 2B] FIG. 1 illustrates an example of a DL channel in a subframe in accordance with various aspects of the present disclosure. [Figure 2C] FIG. 2 illustrates an example of a second frame, according to various aspects of the present disclosure. [Figure 2D] FIG. 1 illustrates an example of a UL channel in a subframe in accordance with various aspects of the present disclosure. [Diagram 3] FIG. 2 illustrates an example of a base station and user equipment (UE) in an access network in accordance with various aspects presented herein. [Figure 4]FIG. 1 is an example resource diagram illustrating an example bandwidth portion (BWP) within a carrier bandwidth, in accordance with various aspects presented herein. [Figure 5A] 1 illustrates an example of a downlink (DL) BWP and an uplink (UL) BWP in a carrier bandwidth in accordance with various aspects presented herein. [Figure 5B] 1 illustrates a time diagram illustrating a guard period for switching between a UL BWP and a DL BWP in accordance with various aspects presented herein. [Figure 6] 1 illustrates an example aspect of a BWP for reduced capability UEs, including a shared initial DL BWP, in accordance with various aspects presented herein. [Figure 7] 1 illustrates an example aspect of a BWP for reduced capability UEs, including a shared initial DL BWP, in accordance with various aspects presented herein. [Figure 8] 1 illustrates an example aspect of a BWP for reduced capability UEs, including a shared initial DL BWP, in accordance with various aspects presented herein. [Figure 9] 1 is an example communication flow between a UE and a base station including use of a shared initial DL BWP and a dedicated active DL BWP for reduced capability UEs, in accordance with various aspects presented herein. [Figure 10] 1 illustrates example aspects of BWPs for reduced capability UEs, including a shared initial DL BWP and a dedicated initial DL BWP, in accordance with various aspects presented herein. [Figure 11] 1 is an example communication flow between a UE and a base station including use of a shared initial DL BWP and a dedicated initial DL BWP for reduced capability UEs, in accordance with various aspects presented herein. [Figure 12] 1 illustrates example aspects of BWPs for reduced capability UEs, including a shared initial DL BWP and a dedicated initial DL BWP, in accordance with various aspects presented herein. [Figure 13] 1 is a flowchart of a method of wireless communication in a UE in accordance with various aspects presented herein. [Figure 14] 1 is a flowchart of a method of wireless communication in a UE in accordance with various aspects presented herein. [Figure 15] FIG. 2 illustrates an example of a hardware implementation for an exemplary apparatus in accordance with various aspects presented herein. [Figure 16] 1 is a flowchart of a method of wireless communication in a network entity in accordance with various aspects presented herein. [Figure 17] 1 is a flowchart of a method of wireless communication in a network entity in accordance with various aspects presented herein. [Figure 18] FIG. 2 illustrates an example of a hardware implementation for an exemplary network entity in accordance with various aspects presented herein. [Figure 19] FIG. 1 illustrates a diagram illustrating an example of a disaggregated base station architecture in accordance with various aspects presented herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] In addition to higher capability devices, wireless communications may support reduced capability devices. In some examples, reduced capability UEs may have a reduced transmission or reception bandwidth than other UEs. Aspects presented herein provide configuration and signaling support for reduced capability UEs that enable joint optimization of DL / UL BWP configurations, coexistence of different UE capabilities, power savings for reduced capability UEs, mitigation of resource fragmentation on DL / UL, and / or reduced signaling overhead. In some aspects, UEs with different levels of capabilities, such as reduced capability UEs and non-reduced (or higher) capability UEs, may share an initial DL BWP and CORESET 0 for initial access. UEs may, for example, monitor resources of CORESET 0 to receive system information that enables the UE to perform initial access. In some aspects, a shared CORESET 0, for example, and a shared system information block (SIB) may carry information for UEs with larger bandwidth capabilities and UEs with reduced bandwidth capabilities. In some aspects, a separate initial BWP, e.g., a dedicated initial downlink BWP and / or a dedicated initial uplink BWP, may be provided for UEs with reduced bandwidth. In some aspects, reduced capability UEs may use a dedicated initial BWP to transmit random access messages, such as a random access preamble. Aspects presented herein may provide for configuration of BWPs for initial access and thereafter that support reduced bandwidth for reduced capability UEs while maintaining flexibility in configuring bandwidth for higher capability UEs.

[0013] The detailed description set forth below in conjunction with the drawings describes various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing 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 to avoid obscuring such concepts.

[0014] Several aspects of a telecommunications system are presented with reference to various apparatus and methods that are described in the following detailed description 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.

[0015] As an example, an element or any portion of an element or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), 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 functionality 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, executable files, threads of execution, procedures, functions, etc., or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0016] 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 on a computer-readable medium 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 and not limitation, such computer-readable media may comprise 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.

[0017] Although aspects, implementations, and / or use cases are described in this application by way of illustration to several examples, additional or different aspects, implementations, and / or use cases may arise 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, implementations and / or applications may arise with 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 examples may or may not be specifically targeted to a use case or application, but a wide variety of applicability of the described aspects may arise. 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 aspects of the technology herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementation and practice of the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily includes several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or non-aggregated components, end-user devices, etc. of various sizes, shapes, and configurations.

[0018] FIG. 1 illustrates an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., 5G Core (5GC)). The base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). The macro cells include base stations. The small cells include femto cells, pico cells, and micro cells.

[0019] In some aspects, the UE 104 may have a first capability associated with a lower maximum UE bandwidth than a second capability. The UE may be a reduced-capability UE in some aspects. The UE 104 may include a BWP component 198 configured to perform at least a portion of an initial access with the base station 102 or 180 based on an initial downlink BWP shared between the UE with the first capability and the UE with the second capability, and to switch to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability.

[0020] The base station 102 or 180 may include a BWP component 199 configured to perform initial access with a UE 104 having a first capability associated with a lower maximum UE bandwidth than a second capability, where at least a portion of the initial access is based on an initial downlink BWP shared between the UE having the first capability and the UE having the second capability. The base station 102 or 180 may be further configured to switch to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability for communication with the UE 104. The following description may focus on 5G NR, but the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0021] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 through a second backhaul link 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: forwarding of user data, encryption and decryption of radio channels, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) via a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0022] The base stations 102 may wirelessly communicate with the UE 104. Each of the base stations 102 may provide communication coverage to a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB) that may provide service to a limited group known as a closed subscriber group (CSG). A communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102, and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna technology, 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 bandwidth up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in carrier aggregation with up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. The carrier allocation may be asymmetric with respect to 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).

[0023] Several UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL WWAN spectrum. The D2D communication links 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 communication may be through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0024] The wireless communication system may further include a Wi-Fi access point (AP) 150 in communication with a Wi-Fi station (STA) 152 via a communication link 154, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communicating to determine if a channel is available.

[0025] The small cell 102' may operate in a licensed and / or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) used by the Wi-Fi AP 150. A small cell 102' utilizing NR in an unlicensed frequency spectrum may provide increased coverage to and / or increase the capacity of an access network.

[0026] The electromagnetic spectrum is often subdivided 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).

[0027] 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 frequency range designation 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 features 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 range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0028] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "mmWave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band.

[0029] The base station 102, whether a small cell 102′ or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as the gNB 180, may operate at millimeter wave and / or quasi-millimeter wave frequencies in the conventional sub-6 GHz spectrum in communication with the UE 104. When the gNB 180 operates at millimeter wave or quasi-millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 for the UE 104 to compensate for path loss and short distances. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0030] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit direction and receive direction for the base station 180 may be the same or different. The transmit direction and receive direction for the UE 104 may be the same or different.

[0031] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to an IP Service 176. The IP services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services in the public land mobile network (PLMN), and may be used to schedule MBMS transmissions.The MBMS Gateway 168 may be used to deliver MBMS traffic to base stations 102 that belong to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a particular service, and may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0032] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through the UPF 195. The UPF 195 provides IP address allocation for the UE as well as other functions. The UPF 195 is connected to IP Services 197. The IP services 197 may include the Internet, an intranet, IP Multimedia Subsystem (IMS), Packet Switch (PS) Streaming (PSS) services, and / or other IP services.

[0033] A base station may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small cooking appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UEs 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or any 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 individually access the network.

[0034] The deployment of a communication system such as a 5G New Radio (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 base station functionality can be implemented in an aggregated or non-aggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit reception point (TRP), or cell) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a non-aggregated base station.

[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 non-aggregated base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more centralized units (CU), one or more distributed units (DU), or one or more radio units (RU)). 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 may be 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 also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

[0037] FIG. 19 shows a diagram illustrating an example disaggregated base station 1900 architecture. The disaggregated base station 1900 architecture may include one or more central units (CUs) 1910 that may communicate directly with a core network 1920 via a backhaul link or indirectly with the core network 1920 through one or more disaggregated base station units (such as a near real-time (near RT) RAN Intelligent Controller (RIC) 1925 via an E2 link, or a non-real-time (non-RT) RIC 1915 associated with a Service Management and Orchestration (SMO) framework 1905, or both). The CUs 1910 may communicate with one or more distributed units (DUs) 1930 via respective midhaul links, such as an F1 interface. The DUs 1930 may communicate with one or more radio units (RUs) 1940 via respective fronthaul links. The RUs 1940 may communicate with each UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 1940 simultaneously.

[0038] Each of the units, i.e., CU1910, DU1930, RU1940, as well as quasi-RT RIC1925, non-RT RIC1915, and SMO framework 1905, 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 over a wired transmission medium with one or more of the other units. Additionally, a unit may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver), configured to receive and / or transmit signals over a wireless transmission medium with one or more of the other units.

[0039] In some aspects, the CU 1910 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 1910. The CU 1910 may be configured to handle user plane functions (i.e., central unit-user plane (CU-User Plane, CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 1910 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface, when implemented in an O-RAN configuration. The CU 1910 may be implemented to communicate with the DU 1930, as necessary, for network control and signaling.

[0040] The DU 1930 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 1940. In some aspects, the DU 1930 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 and demodulation, etc.) at least in part according to a functional division such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 1930 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 1930 or with a control function hosted by the CU 1910.

[0041] The lower layer functionality may be implemented by one or more RUs 1940. In some deployments, the RUs 1940 controlled by the DUs 1930 may correspond to logical nodes 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 RUs 1940 may be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 1940 may be controlled by the corresponding DUs 1930. In some scenarios, this configuration may enable the DUs 1930 and CUs 1910 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0042] The SMO framework 1905 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 1905 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 1905 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 1990) to perform network element lifecycle 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, a CU 1910, a DU 1930, a RU 1940, and a Near-RT RIC 1925. In some implementations, the SMO framework 1905 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 1911, via an O1 interface. Additionally, in some implementations, the SMO framework 1905 can communicate directly with one or more RUs 1940 via an O1 interface. The SMO framework 1905 may also include a non-RT RIC 1915 configured to support the functionality of the SMO framework 1905.

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

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

[0045] 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 Figures 2A, 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, although any particular subframe may 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) (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.

[0046] 2A-2D show a frame structure, aspects of the present disclosure may be applicable to other wireless communication techniques 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 that 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. With a normal CP, each slot may include 14 symbols, and with an extended CP, each slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also called single carrier frequency division multiple access (SC-FDMA) 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), which effectively defines the symbol length / duration equal to 1 / SCS.

[0047] [Table 1]

[0048] 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 two slots / subframes. The subcarrier spacing is 2 μ* may be equal to 15 kHz, where μ is a 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 / duration 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 approximately 16.67 μs. Within a set of frames, there may be one or more different Bandwidth Parts (BWPs) (see Figure 2B) that are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

[0049] A resource grid may be used to represent the frame structure. Each time slot contains a resource block (RB) (also called physical RB (PRB)) that spans 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (RE). The number of bits carried by each RE depends on the modulation scheme.

[0050] 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) (denoted as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signal (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).

[0051] FIG. 2B shows 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). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) may be in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS.The physical broadcast channel (PBCH), which carries the master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called 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.

[0052] As shown in FIG. 2C, some of the REs carry DM-RS (denoted 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 particular 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 structure, and the UE may transmit the SRS on 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.

[0053] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be located as shown. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCIs.

[0054] 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets may be provided to a controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functionality. 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 functionality associated with 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 broadcast of measurement configurations for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with forwarding of 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 functionality associated with mapping between logical channels and 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.

[0055] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles 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 a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams may be spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with the respective spatial stream for transmission.

[0056] At the UE 350, each receiver 354Rx receives a signal via its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides this information to a receive (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 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. Multiple spatial streams may be combined into a single OFDM symbol stream by the RX processor 356 if they are destined for the UE 350. 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 functionality.

[0057] 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.

[0058] Similar to the functionality described in connection with DL transmissions by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIBs, SIBs) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with forwarding of upper 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 functionality associated with mapping between logical channels and 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.

[0059] 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 as well as to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

[0060] The UL transmissions are processed at the base station 310 in a manner similar to that described with respect to the receiver functions at the UE 350. Each receiver 318Rx receives a signal via its respective antenna 320. Each receiver 318Rx recovers the information modulated onto an RF carrier and provides the information to the RX processor 370.

[0061] 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.

[0062] 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 BWP component 198 of FIG.

[0063] 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 BWP component 199 of FIG.

[0064] In addition to higher capability devices, wireless communications may support reduced capability devices. Examples of higher capability devices include premium smartphones, vehicle-to-everything (V2X) devices, URLLC devices, eMBB devices, etc., among others. Reduced capability devices may include lower capability devices and medium capability devices and use cases. Reduced capability devices may include wearables, industrial wireless sensor networks (IWSNs), surveillance cameras, low-end smartphones, etc., among other examples. A communication system, such as an NR communication system, may support both higher capability devices and reduced capability devices. Reduced capability devices may be referred to as RedCap devices, NR light devices, low-tier devices, lower tier devices, etc. Reduced capability UEs may communicate based on various types of wireless communications. For example, smart wearables may transmit or receive communications based on low power wide area (LPWA) / mMTC, mitigated IoT devices may transmit or receive communications based on URLLC, sensors / cameras may transmit or receive communications based on eMBB, etc.

[0065] In some examples, a reduced capability UE may have a reduced transmission or reception bandwidth than other UEs. For example, a reduced capability UE may have an operating bandwidth of 5 MHz to 20 MHz for both transmission and reception, in contrast to other UEs that may have a bandwidth of up to 100 MHz. As an example, an FR1 reduced capability UE may have a maximum bandwidth of 20 MHz during and after initial access. An FR2 reduced capability UE may have a maximum bandwidth of 100 MHz during and after initial access. The operating bandwidth may correspond to a maximum UE bandwidth, and a reduced capability UE may have a lower maximum UE bandwidth than a higher capability UE. In some aspects, a reduced capability UE, whether in the downlink or uplink, may not be configured with a non-initial BWP wider than the reduced capability UE's maximum bandwidth.

[0066] As another example, a reduced capability UE may have an uplink transmit power that is at least 10 dB lower than a higher capability UE. As a further example, a reduced capability UE may have a reduced number of receive antennas compared to other UEs. For example, 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 higher capability UE that may have multiple antennas. A reduced capability UE may also have reduced computational complexity than other UEs.

[0067] 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, an industrial wireless sensor may have an acceptable latency of up to about 100 ms. In some safety-related applications, the latency of an industrial wireless sensor 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, a video surveillance device may have an acceptable latency of up to about 500 ms.

[0068] 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 bandwidth portions (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 downlink (DL) BWP. FIG. 4 shows a resource diagram 400 illustrating multiple BWPs (e.g., BWP1, BWP2, and BWP3) configured within a frequency span of a carrier bandwidth. One DL BWP may be active at a time, and a UE may not be expected to receive PDSCH, PDCCH, CSI-RS, or TRS outside of an active BWP without a measurement gap or BWP switching gap. Each DL BWP may include at least one control resource set (CORESET). 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 of an active BWP. Use of a BWP may reduce the bandwidth monitored by the UE and / or used for transmission, which may help the UE conserve battery power.

[0069] 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 a resource element group (REG), for example, 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, each CORESET being 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] 5A illustrates an example 500 in which a DL BWP 504 in a TDD carrier bandwidth 502 configured for a reduced capability UE is not aligned with a UL BWP 506 for the reduced capability UE. When the DL BWP and UL BWP are not aligned, for example in center frequency, a guard time period may be provided between downlink and uplink resources to allow the UE to switch between the BWPs. For example, the UE may change 508 between downlink reception in the DL BWP 504 and uplink transmission in the UL BWP 506. Similarly, the UE may change 510 between uplink transmission in the UL BWP 506 and downlink reception in the DL BWP 504.

[0071] FIG. 5B illustrates a time diagram 550 showing that a guard period 518 or time gap may be provided between a downlink reception 512 in a DL BWP (e.g., 504) and an uplink transmission 514 in a UL BWP (e.g., 506) to allow a UE to switch between BWPs. Similarly, a guard period 520 may be provided between an uplink transmission 514 in a UL BWP (e.g., 506) and a downlink reception 516 in a DL BWP (e.g., 504). In some aspects, the guard period may be between 50-200 μsec for a UE to retune between BWPs. Timeline changes such as Type-B half-duplex frequency division duplexing may not be supported for reduced capability UEs in some aspects. The guard period or time gap at each switch between downlink communication (on a DL BWP) and uplink communication (on a UL BWP) may cause increased latency, reduced peak data rates for DL ​​and / or UL, etc., in communications between the UE and the base station. Non-matching BWPs for DL ​​and UL communications may result in loss of channel reciprocity, increased UE complexity or power consumption, RF retuning, additional CSI measurements and reporting, additional collision handling procedures, additional restrictions on DL / UL switching locations, and / or coexistence challenges for multiplexing / scheduling of different UE types.

[0072] In some aspects, UEs with different levels of capabilities, such as reduced capability UEs and non-reduced (or higher) capability UEs, may share an initial DL BWP and CORESET 0 for initial access. The UE may, for example, monitor resources of CORESET 0 to receive system information that enables the UE to perform initial access. A cell-defining SSB (CS-SSB) may be transmitted within the maximum bandwidth supported by the reduced capability UE. FIG. 6 illustrates an example 600 in which an initial DL BWP 604 within a carrier bandwidth 602 may be shared, e.g., configured for both reduced capability UEs and higher capability UEs. The UEs may be configured with different BWPs as active DL BWPs, e.g., after performing initial access. For example, FIG. 6 illustrates that a reduced capability UE may be configured with an active DL BWP 606 for the lower capability UE, and a higher capability UE may be configured with an active DL BWP 608 for the higher capability UE.

[0073] In some aspects, the reduced capability UE may be configured with a separate initial DL BWP, which may be different from CORESET 0, for example, rather than the shared initial DL BWP shown in FIG. 6. In such an example, a non-cell-defining SSB (NCD-SSB) may be transmitted within the initial BWP configured for the reduced capability UE. The NCD-SSB may provide a quasi-co-location (QCL) source or reference signal for the UE to determine parameters to use when monitoring and receiving one or more of the random access msg2 (e.g., a random access response (RAR), a random access msg4, or a paging message from a network entity such as a base station). The UE may use the NCD-SSB received in the BWP configured for the reduced capability UE for L1 and L3 measurements (e.g., RSRP measurements, path loss measurements, radio resource management (RRM) measurements, etc.).

[0074] The UE continues to measure the SSS or TRS of the serving cell after initial access for synchronization purposes, e.g., to maintain synchronization with the serving cell. To support cell-level mobility, the UE may measure the SSB of the serving cell and one or more neighbor cells. As shown in FIG. 6, when a reduced capability UE operates in an active DL BWP in SSB and the SSB resources are in the initial DL BWP 604 but not in the active DL BWPs 606 and 608, e.g., when the SSB is not transmitted in the active downlink BWP as shown in FIG. 6, the UE may be configured with an intra-frequency L3 measurement gap to allow the UE to switch from the active DL BWP 606 or 608 without SSB to the initial DL BWP 610 to measure the SSB. The network may configure periodic measurement gaps for the UE, e.g., via RRC signaling. When a measurement gap begins, the reduced capability UE may suspend reception of downlink control and / or data in the active DL BWP 606 and may switch to another BWP configured with DL RS, such as the initial DL BWP. Periodic or semi-static TRS / CSI-RS / PRS may be transmitted in the active DL BWP 606 and may be used for time / frequency / frequency tracking, L1 measurements for link maintenance, or as a QCL source for paging, monitoring and receiving wake up signals (WUS), etc. In some aspects, RRM measurement mitigation may not be configured for the serving cell. If the active BWP 606 or 608 does not include periodic or semi-static SSB, TRS, PRS, or CSI-RS, load imbalance may occur across frequencies of the carrier bandwidth 602, for example due to the measurement gap.

[0075] Aspects presented herein provide a BWP, including an initial BWP and an active BWP that address capabilities supported by reduced capability UEs as well as capabilities supported by higher capability UEs. Joint optimization of DL / UL BWP resource mapping for reduced capability UEs may provide or improve coexistence of reduced capability UEs and higher capability UEs exchanging wireless communications with base stations in the same carrier bandwidth. In TDD operation, the DL BWP and UL BWP of a reduced capability UE may or may not be aligned in center frequency. For example, the center frequencies of the DL BWP and UL BWP may be aligned in some aspects. In other aspects, the center frequencies of the DL BWP and the UL BWP may not be aligned. Alignment of the BWPs in center frequency may enable TDD DL and UL communications without a time gap or guard period to enable back-off between the UL BWP and DL BWP. Misalignment of the BWPs in center frequency may require that the TDD DL and UL communications be configured with a time gap or guard period to enable back-off between the UL BWP and DL BWP. The uplink channels (e.g., PUCCH, PUSCH, PRACH, and / or SRS) of a reduced capability UE may be mapped to RBs at carrier edges, which may reduce resource fragmentation. As an example, the first hop of the PUCCH may be at the first edge of the BWP and the second frequency hop may be at the second edge of the BWP. In some aspects, frequency hopping of the uplink channels or signals may be disabled by the network, for example, during and / or after initial access. Frequency hopping may be disabled, for example, based on DCI, MAC-CE, or system information (SI) from the network.

[0076] In some aspects, a BWP, such as a DL BWP and / or a UL BWP, may be configured separately for reduced capability UEs. The BWP may be configured separately for reduced capability UEs in different connected states, such that there may be different BWP configurations for UEs in RRC idle, RRC inactive, and / or RRC connected states.

[0077] Aspects presented herein provide configuration and signaling support for reduced capability UEs that enable joint optimization of DL / UL BWP configurations, coexistence of different UE capabilities, power savings for reduced capability UEs, mitigation of resource fragmentation on DL / UL, and / or reduced signaling overhead.

[0078] 7 shows an example 700 in which reduced capability UEs and non-reduced capability UEs may share an initial DL BWP 704 and an initial UL BWP 706 within a carrier bandwidth 702. During initial access, UEs of different capabilities (e.g., reduced capability UEs and non-reduced capability UEs) may share a common CD-SSB 710, CORESET 0 (e.g., in the initial DL BWP 704), and the initial UL BWP 706. Frequency hopping for PUCCH and / or PUSCH may be disabled for reduced capability UEs in the initial UL BWP. As shown at 708, PUCCH resources for reduced capability UEs may be provided at the frequency edges of the shared UL BWP 706.

[0079] After initial access, the reduced capability UE may operate in an active DL BWP 714 and active UL BWP 712 for reduced capability UEs, for example, but not for higher capability UEs. The active DL BWP 714 and active UL BWP 712 may be referred to as being dedicated to reduced capability UEs. The active DL BWP 714 for reduced capability UEs may include configuration for periodic or semi-static TRS and / or periodic CSI-RS and / or PRS. The active DL BWP 714 for reduced capability UEs may include configuration for a common search space (CSS) for the UE to monitor and receive WUS, paging, and system information updates from the network, among other downlink signals. If no SSB is transmitted in the active DL BWP 714, an L3 intra-frequency measurement gap may be provided to allow the UE to switch to measuring the SSB in the initial DL BWP 704, as described in connection with FIG. 6. As shown in FIG. 7, the UE may receive an RRC message in an active DL BWP 714 that provides system information (SI) updates to the lower capability UE.

[0080] During and after initial access, a reduced capability UE may not be expected to operate in a DL BWP or UL BWP wider than its maximum UE bandwidth associated with its reduced capability. A reduced capability UE may support different center frequencies for DL ​​BWP and UL BWP. For example, a UE may support different center frequencies for an active DL BWP and an active UL BWP with the same BWP identifier (e.g., sometimes referred to as a "BWP-id") in TDD operation.

[0081] Figure 8 shows an example 800 similar to Figure 7 in which an active DL BWP 814 that is dedicated to reduced capability UEs may have a different center frequency than an active UL BWP 812 that is dedicated to reduced capability UEs. Additionally or alternatively, a shared initial DL BWP 804 for initial access that may be common to both reduced capability UEs and higher capability UEs may have a different center frequency than a shared initial UL BWP 806 for initial access that is common to both reduced capability UEs and higher capability UEs.

[0082] FIG. 9 illustrates an example communication flow 900 between a reduced capability UE 902 and a base station 904 based on an initial DL BWP and UL BWP shared between the reduced capability UE and a higher capability UE, e.g., as described in connection with FIG. 7 and / or FIG. 8. The reduced capability of the UE 902 may include a reduced operating bandwidth or a lower maximum UE bandwidth that is smaller than a higher capability UE. The UE 902 may operate based on TDD, where the UE monitors downlink communications or transmits uplink communications and does not transmit and receive at overlapping times. At 906, the UE 902 may receive system information 906. The system information may be for wireless communications with a carrier bandwidth, e.g., 802 in FIG. 8, a base station 904. The system information may indicate the BWP as a subset of frequency resources of the carrier bandwidth for the UE to perform initial access. The system information may be dedicated to the reduced capability UE, e.g., including information applicable to the reduced capability UE and not applicable to the higher capability UE. The UE 902 may receive system information 906 in a separate SIB for reduced capability UEs that is different from a SIB having system information applicable to higher capability UEs. The UE 902 may receive system information 906 in a SIB carrying system information for both reduced capability UEs and higher capability UEs. A common SIB may have different information elements for higher capability UEs and reduced capability UEs. For example, the base station 904 may transmit a common or shared SIB in CORESET 0 (e.g., in the initial DL BWP 704 or 804) that is shared by reduced capability UEs and higher capability UEs.

[0083] At 908, the UE 902 may perform an initial access procedure, such as a RACH procedure, in an initial DL BWP (e.g., a shared initial DL BWP 704 or 804) and an initial UL BWP (e.g., a shared initial UL BWP 706 or 806) that are common to reduced capability UEs and higher capability UEs. As part of the initial access, the UE 902 may transmit and receive a random access message 910 with the base station 904. As an example, the UE may transmit a random access Msg1 with a preamble to the base station 904, receive Msg2 from the base station, transmit Msg3 to the base station, and / or receive Msg4 from the base station in the shared initial DL BWP and the shared initial UL BWP, e.g., as described in connection with FIG. 7 or FIG. 8. The UE 902 may transmit a random access message, such as Msg1, during a random access occasion based on the SSB-to-RO mapping for reduced capability UEs at 910. The SSB to RO mapping may be based on the CD-SSB received in the shared initial DL BWP. The SSB to RO mapping and the SSB to preamble mapping may be based on a mapping pattern configured separately for reduced capability UEs. The separate configuration may be received in system information 906 in the shared initial DL BWP. Similar to the UE 902, the base station may perform an initial access procedure with the UE at 912 based on a shared initial DL BWP and a shared initial UL BWP that are common to both reduced capability UEs and higher capability UEs.

[0084] The UE may receive an indication or configuration of an active DL BWP and an active UL BWP that are dedicated to reduced capability UEs but not to higher capability UEs. The active DL BWP and active UL BWP may correspond to 712 and 714, or 812 and 814 in FIG. 7 or FIG. 8. The UE 902 may receive the configuration of the dedicated active DL BWP and the dedicated active UL BWP in the system information for reduced capability UEs, e.g., at 906, in the shared initial DL BWP. The system information 906 may be broadcast for reception by any reduced capability UE. The UE 902 may receive the configuration of the dedicated active DL BWP and the active UL BWP in RRC signaling from the base station 904, e.g., at 914. The RRC signaling may be directed to the UE 902 in unicast signaling from the base station 904. In some aspects, the UE 902 may determine or identify a dedicated active DL BWP and active UL BWP configuration based on a rule, a lookup table, or based on previously known information without explicit signaling of the configuration from the base station 904. The use of a lookup table or rules may reduce signaling overhead while allowing a reduced capability UE to communicate based on an active DL / UL BWP supported by the UE's bandwidth capabilities.

[0085] At 918, the UE 902 switches from transmitting and receiving (or monitoring) based on a shared initial DL BWP and a shared initial UL BWP to transmitting and receiving (or monitoring) based on an active DL BWP and an active UL BWP that are dedicated to reduced capability UEs. The base station 904 may perform a similar switch at 920 for communication with the UE 902. For example, the UE may switch from BWPs 704 and 706 to BWPs 712 and 714 in FIG. 7. In FIG. 8, the UE may switch from BWPs 804 and 806 to BWPs 812 and 814. The UE 902 may perform the switch at 918 after completion and exchange of capability signaling 914 in the shared initial DL BWP (e.g., 704 or 804). The UE 902 may indicate 914 the UE's reduced bandwidth capabilities to the base station 904 in a capability signaling exchange that may inform the base station 904 that the UE switches to monitoring / transmitting in an active DL BWP or an active UL BWP for the reduced capability UE. The switch may be triggered 918 by a signal 916 from the base station 904. The signal 916 may include a MAC-CE that is broadcast, multicast, or unicast. The signal 916 may include an RRC reconfiguration from the base station 904. The RRC reconfiguration may be unicast to the UE 902. The signal 916 may include a DCI that is multicast or broadcast to the reduced capability UE. In some aspects, the UE may switch 918 without a signal 916 from the base station. In such an example, the UE may perform the switch 918 based on a timer. The UE 902 may receive a timer configuration in the system information 906, e.g., in system information that is dedicated to reduced capability UEs. The timer may indicate that the UE will perform the switch after a configured number of subframes, a configured number of slots, or a configured amount of time following a reference point in time, such as following a capability exchange message, a RACH message, or another signal sent by the UE or received from the base station.

[0086] An active DL BWP dedicated to a reduced capability UE, e.g., 714 or 814, may have associated configurations for a CSS and one or more RSs within the bandwidth of the active DL BWP. For example, the active DL BWP may include a CORESET and a CSS configured for the UE to monitor and receive paging from the network, WUS from the base station, system information updates, or group common power control for PUCCH / PUSCH / SRS. The active DL BWP may include a configured periodic TRS and / or a periodic CSI-RS and / or a positioning RS (PRS). The active DL BWP may include a configured non-CD SSB. The active DL BWP may include a CORESET and a CSS configured for system information updates for reduced capability UEs. The active DL BWP may include a configured resynchronization reference signal indicating a system information update for reduced capability UEs.

[0087] The UE 902 may monitor and / or receive a PDSCH, a PDCCH, a TRS, a CSI-RS, a PRS, or a non-CD SSB in an active DL BWP that is dedicated to reduced capability UEs, as shown at 922. At 926, the UE 902 may transmit a PUSCH, a PUCCH, and / or an SRS in an active UL BWP for reduced capability UEs.

[0088] FIG. 10 shows an example 1000 in which reduced capability UEs and non-reduced capability UEs may share an initial DL BWP 1004 with higher capability UEs within a carrier bandwidth 1002, but not an initial UL BWP 1006, which is instead configured for higher capability UEs and not configured for reduced capability UEs. This allows for more flexibility in the configuration of the initial UL BWP 1006, which may have a larger bandwidth than the bandwidth capability supported by the reduced capability UE. The reduced capability UE may perform initial access using an initial UL BWP 1011, which is dedicated to the reduced capability UE. After initial access, the reduced capability UE may switch to an active UL BWP 1012 and an active DL BWP 1014, both of which are dedicated to the reduced capability UE. The reduced capability UE may use the shared initial DL BWP 1004 for at least a portion of the initial access, and may change to a different initial DL BWP 1013, which is specific to the reduced capability UE, to complete the initial access.

[0089] During initial access, different capability UEs (e.g., reduced capability UEs and non-reduced capability UEs) may share a common CD-SSB 1010, CORESET0 (e.g., initial DL BWP 1004). In contrast to FIG. 7 and FIG. 8, reduced capability UEs may switch to a separately configured pair of initial DL BWP 1013 and initial UL BWP 1011 configured for reduced capability UEs to complete the initial access procedure. In some aspects, the initial DL BWP 1013 and the initial UL BWP 1011 may be at the frequency edge of the carrier. UEs may exchange random access messages, including, for example, any of random access msg1 (e.g., including a RACH preamble), msg2 (e.g., RAR), msg3, or msg4, in the corresponding initial DL BWP 1013 or initial UL BWP 1011. Frequency hopping for PUCCH and / or PUSCH may be disabled for reduced capability UEs in the initial UL BWP 1011.

[0090] After initial access, the reduced capability UE may operate in an active DL BWP 1014 for reduced capability UEs and an active UL BWP 1012 for reduced capability UEs, but not for higher capability UEs. Similar to the active DL BWP 714 in FIG. 7, the BWP 1014 for reduced capability UEs may include configuration for periodic or semi-static TRS and / or periodic CSI-RS. The active DL BWP 1014 for reduced capability UEs may include configuration for CSS, for the UE to monitor and receive WUS, paging, or system information updates from the network, among other downlink signals. If no SSB is transmitted in the active DL BWP 1014, the L3 intra-frequency measurement gap allows the UE to switch to measuring the SSB (e.g., 1010) in the initial DL BWP 1004, as described in connection with FIG. 6, if no SSB is transmitted in the active downlink BWP as shown in FIG. 10. As shown in FIG. 10, the UE may receive an RRC message in an active DL BWP 1014 that provides an SI update to the lower capability UE.

[0091] During and after initial access, a reduced capability UE may not be expected to operate in a DL BWP or UL BWP wider than its maximum UE bandwidth associated with the reduced capability. A reduced capability UE may support different center frequencies for DL ​​BWP and UL BWP. For example, a UE may support different center frequencies for an active DL BWP and an active UL BWP with the same BWP identifier (e.g., may be referred to as "BWP-id") in TDD operation, e.g., as shown in the example in FIG. 8.

[0092] The shared initial DL BWP 1004 may carry some information that enables reduced capability UEs to initiate access with the network and provides information about dedicated initial BWP resources for reduced capability UEs. For example, a dedicated initial DL BWP for reduced capability UEs, but not for higher capability UEs, may carry system information that is dedicated to reduced capability UEs and may differ from the system information in the DL BWP 1004 for higher capability UEs.

[0093] FIG. 11 illustrates an example communication flow 1100 between a reduced capability UE 1102 and a base station 1104 based on a first initial DL BWP shared between reduced capability UEs and higher capability UEs and a second initial DL BWP dedicated to the reduced capability UE, e.g., as described in connection with FIG. 10. The reduced capability of the UE 1102 may include a reduced operating bandwidth or a lower maximum UE bandwidth that is smaller than a higher capability UE. The UE 1102 may operate based on TDD, where the UE monitors downlink communications or transmits uplink communications and does not transmit and receive at overlapping times. Both the initial BWP and the active BWP for the reduced capability UE may be configured separately by the network.

[0094] The UE 1102 may receive system information 1105, for example, in a shared initial DL BWP. The system information 1105 may be for wireless communication with a carrier bandwidth, for example, base station 1104 at 1002 in FIG. 10. The system information 1105 may indicate the BWP as a subset of frequency resources of the carrier bandwidth for the UE to perform initial access. The system information 1105 may be dedicated to reduced capability UEs, for example, including information applicable to reduced capability UEs and not applicable to higher capability UEs. The UE 1102 may receive system information 1105 in a separate SIB for reduced capability UEs that is different from a SIB having system information applicable to higher capability UEs. The UE 1102 may receive system information 1105 in a SIB carrying system information for both reduced capability UEs and higher capability UEs. The common SIB may have different information elements for higher capability UEs and reduced capability UEs. For example, the base station 1104 may transmit a common or shared SIB in CORESET 0 (eg, in the initial DL BWP 1004) that is shared by reduced capability UEs and higher capability UEs.

[0095] The UE may receive a configuration of an initial DL BWP (e.g., 1013) and an initial UL BWP (e.g., 1011) configured for the reduced capability UE (e.g., dedicated / specific). The UE 1102 may receive a configuration of an initial DL / UL BWP for the reduced capability UE in the system information 1105 for the reduced capability UE, e.g., in a shared initial DL BWP (e.g., 1004). In some aspects, the UE 1102 may determine the initial DL BWP (e.g., 1013) and the initial UL BWP (e.g., 1011) for the reduced capability UE based on a lookup table, a rule, or information known to the UE 1102 without explicit signaling from the base station 1104.

[0096] The UE 1102 may switch 1106 to the dedicated initial DL BWP and initial UL BWP (e.g., 1013 and 1011). The UE 1102 may switch to perform at least a portion of the initial access procedure 1108. Accordingly, the base station 1104 may perform a similar switch 1107 to perform the initial access and / or capability exchange 1112.

[0097] At 1108, the UE 1102 may perform at least a portion of an initial access procedure, such as a RACH procedure, in a dedicated initial DL BWP (e.g., initial DL BWP 1013) and a dedicated initial UL BWP (e.g., initial UL BWP 1011) that is dedicated to reduced capability UEs. As part of the initial access, the UE 1102 may transmit and receive a random access message 1110 with the base station 1104. As an example, the UE may transmit a random access Msg1 with a preamble to the base station 904, receive Msg2 from the base station, transmit Msg3 to the base station, and / or receive Msg4 from the base station in the dedicated initial DL BWP (e.g., 1013) and the dedicated initial UL BWP (e.g., 1011), e.g., as described in connection with FIG. 10. In some aspects, a dedicated physical random access channel (PRACH) resource may be configured for reduced capability UEs, which may enable the network to identify the reduced capability of the UE during initial access and schedule Msg3 / PUCCH in the UL BWP supported by the UE. The UE 1102 may transmit 1110 a random access message such as Msg1 during a random access occasion (RO) based on the SSB-to-RO mapping for the reduced capability UE. The base station 1104 may configure SSB-to-RO mapping patterns separately for reduced capability UEs and higher capability UEs, e.g., in separate system information or other signaling. In some aspects, the non-CD-SSB in the dedicated initial DL BWP 1013 for reduced capability UEs may be the reference SSB for SSB-to-RO mapping and / or SSB-to-preamble mapping. One or more of the parameters of the non-CD SSB may be the same as for the CD-SSB, such as periodicity, block index, power offset, center frequency, numerology, etc. The shared parameters may be configured in conjunction with the CD-SSB or may be configured separately from the CD-SSB. The configuration for the non-CD SSB may be selected to help ensure measurement accuracy for reduced capability UEs having reduced receive branches and / or reduced antenna efficiency.If the parameters of the non-CD SSBs (e.g., periodicity, block index, power offset, center frequency, numerology, etc.) are configured separately or differently from the CD-SSBs, the parameters may be indicated to the reduced capability UE in various ways. As a first example, the parameters of the non-CD SSBs that are the basis for the SSB-to-RO or SSB-to-preamble mapping may be configured in the system information 1105 (e.g., in a separate SIB for higher capability UEs, or in a different IE for higher capability UEs within the same SIB). The parameters of the non-CD SSBs may be configured in the broadcast PDCCH. The UE 1102 may determine one or more of the parameters of the non-CD SSBs based on rules or lookup tables, or based on information known to the UE. The parameters of the non-CD SSBs may be indicated to the UE or determined by the UE based on any combination of system information, PDCCH, lookup tables, or rules.

[0098] If a non-CD SSB is configured in a dedicated initial DL BWP (e.g., 1013) or a dedicated active DL BWP (e.g., 1014), the UE 1102, as well as higher capability UEs, may use the SSB for L1 and / or L3 measurements. The reduced capability UE 1102, as well as higher capability UEs, may use the SSB to perform time / frequency tracking and / or other link maintenance procedures in the RRC connected state. The reduced capability UE, as well as higher capability UEs, may use the non-CD SSB to perform timing advance (TA), resource mapping, and beam management in small data transmissions (SDT).

[0099] A dedicated initial DL BWP (e.g., 1013) and a dedicated active DL BWP (e.g., 1014) may at least partially overlap in the frequency domain with the CD-SSB (e.g., 1010) or CORESET 0 of the shared initial DL BWP 1004. Figure 12 shows an example 1200 in which a dedicated active DL BWP 1214 and a dedicated initial DL BWP 1213 partially overlap in the frequency domain with the CD-SSB 1210 of the shared CORESET 0 / shared initial DL BWP 1204 for a carrier bandwidth 1202.

[0100] The UE 1102 may receive an indication or configuration of an active DL BWP (e.g., 1014) and an active UL BWP (e.g., 1012) that are dedicated to reduced capability UEs, but not to higher capability UEs. The UE 1102 may receive a dedicated active DL BWP and active UL BWP configuration in system information 1109 for reduced capability UEs in a dedicated initial DL BWP (e.g., 1013). The system information 1109 may be broadcast for reception by any reduced capability UEs. The UE 1102 may receive a dedicated active DL BWP and active UL BWP configuration in RRC signaling from the base station 1104. The RRC signaling may be directed to the UE 1102 in unicast signaling from the base station 1104. In some aspects, the UE 1102 may determine or identify the configuration of the dedicated active DL BWP 1014 and active UL BWP 1012 based on a rule, a lookup table, or based on previously known information without explicit signaling of the configuration from the base station 1104. The use of a lookup table or rule may reduce signaling overhead while allowing a reduced capability UE to communicate based on the active DL / UL BWPs supported by the UE's bandwidth capabilities.

[0101] At 1118, the UE 1102 switches from transmission and reception (or monitoring) based on the dedicated initial DL BWP 1013 and the dedicated initial UL BWP 1011 to transmission and reception (or monitoring) based on the active DL BWP 1014 and the active UL BWP 1014, which are dedicated to reduced capability UEs. The base station 1104 may perform a corresponding switch at 1120 for communication with the UE 1102. The UE 1102 may perform the switch at 1118 after completing the exchange of capability signaling 1114 in the dedicated initial DL BWP (e.g., 1013). The switch may be triggered at 1118 by a signal 1116 from the base station 1104. The signal 1116 may include a MAC-CE that is broadcast, multicast, or unicast. The signal 1116 may include an RRC reconfiguration from the base station 1104. The RRC reconfiguration may be unicast to the UE 1102. The signal 1116 may include a DCI that is multicast or broadcast to the reduced capability UEs. In some aspects, the UE may switch 1118 without the signal 1116 from the base station. In such an example, the UE 1102 may perform the switch 1118 based on a timer. The UE 1102 may receive a timer configuration in the system information 1106, e.g., in system information that is dedicated to reduced capability UEs. The timer may indicate that the UE will perform the switch after a configured number of subframes, a configured number of slots, or a configured amount of time following a reference time point, such as following a capability exchange message, a RACH message, or another signal sent by the UE or received from the base station.

[0102] An active DL BWP dedicated to a reduced capability UE, e.g., 1014, may have associated configurations for a CSS and one or more RSs within the bandwidth of the active DL BWP. For example, the active DL BWP may include a CORESET and a CSS configured for the UE to monitor and receive paging from the network, system information updates, WUS from the base station 1104, or group common power control for PUCCH / PUSCH / SRS. The active DL BWP may include configured periodic or semi-static TRS and / or periodic CSI-RS and / or PRS. The active DL BWP may include configured non-CD SSBs. The active DL BWP may include a CORESET and a CSS configured for system information updates for reduced capability UEs. The active DL BWP may include a configured resynchronization reference signal indicating a system information update for reduced capability UEs.

[0103] The UE 1102 may monitor and / or receive a PDSCH, a PDCCH, a TRS, a CSI-RS, a PRS, or a non-CD SSB in an active DL BWP that is dedicated to reduced capability UEs, as shown at 1122. At 1126, the UE 1102 may transmit a PUSCH, a PUCCH, and / or an SRS in an active UL BWP for reduced capability UEs.

[0104] 13 is a flowchart 1300 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 350, 902, 1102, device 1504). The method may provide for configuration of a BWP for initial access and thereafter that provides a reduced bandwidth supported by reduced capability UEs while maintaining flexibility in configuring bandwidth for higher capability UEs. A UE performing the method may have a first capability associated with a lower maximum UE bandwidth than a second capability. For example, the UE may be a reduced capability UE.

[0105] At 1302, the UE performs at least a portion of the initial access based on an initial downlink BWP shared between a UE having a first capability and a UE having a second capability. A "UE having a first capability" or a "UE of a first capability" may refer to a UE supporting a first capability. A "UE having a second capability" or a "UE of a second capability" may refer to a UE supporting a second capability. The initial access may be performed, for example, by the BWP component 198 and / or the initial BWP component 1540 of the apparatus 1504 in FIG. 15. FIG. 9 illustrates an example of a UE 902 performing initial access in a shared initial DL BWP. FIG. 11 illustrates an example of a UE 1102 performing initial access in a portion of a shared initial DL BWP and in a portion of a dedicated DL BWP for a reduced capability UE.

[0106] The UE may perform initial access based in part on a first initial downlink BWP shared between the UE with the first capability and the UE with the second capability, and in part on a second initial downlink BWP that is dedicated to the UE with the first capability. The BWP switching of the reduced capability UE may be configured for TDD mode, full-duplex frequency division duplex (FD-FDD) mode, or half-duplex frequency division duplex (HD-FDD) mode.

[0107] The UE may perform initial access based on an initial uplink BWP that is dedicated to UEs with a first capability. Performing initial access may include transmitting a random access preamble in a RO with an SSB-to-RO mapping (e.g., sometimes referred to as a spatial reference for the random access procedure) for UEs with the first capability that is different from that for UEs with the second capability. The RO-to-SSB mapping provides a spatial reference for the RO. The SSB-to-RO mapping for UEs with the first capability is based on a non-CD SSB. One or more parameters for the non-CD SSB may be configured independently of the CD-SSB, where the one or more parameters include at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology. The one or more parameters for the non-CD SSB may be the same parameters as those for the CD-SSB, where the one or more parameters include at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology. The one or more parameters may be from at least one of system information, a broadcast physical downlink control channel, a look-up table, or a rule. The non-CD SSB may be configured in at least one of the second initial downlink BWP or the active downlink BWP and is common to measurements by the UE with the first capability and the UE with the second capability. At least one of the second initial downlink BWP or the active downlink BWP may overlap in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP. The initial downlink BWP may include CORESET 0 or CD-SSB configured for the UE with the first capability and the UE with the second capability, and the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are equal to or less than the lower maximum UE bandwidth of the UE with the first capability and the UE with the second capability.The initial uplink BWP and the second initial downlink BWP may be at the edge of the carrier bandwidth.

[0108] At 1304, the UE switches to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability. The switching may be performed, for example, by the BWP component 198 and / or the active BWP component 1542 of the apparatus 1504 in FIG. 15. FIG. 9 and FIG. 11 show examples of UEs 902 and 1102 switching to a dedicated active DL BWP for reduced capability UEs. In some aspects, the UE may perform an initial access at 1302 based on an initial downlink BWP and an initial uplink BWP shared between the UE with the first capability and the UE with the second capability, and the UE may switch to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability after performing the initial access. FIG. 9 shows an example aspect of a UE using a shared initial DL BWP and a shared initial UL BWP. The initial downlink BWP may include CORESET 0 or CD-SSB configured for a UE with a first capability and a UE with a second capability, and the initial downlink BWP and the initial uplink BWP have a bandwidth at a center frequency of the carrier bandwidth, the bandwidth being less than or equal to a lower maximum UE bandwidth of the UE with the first capability.

[0109] In some aspects, the UE may further receive system information or system information updates in the initial downlink BWP, the system information included in a SIB dedicated to the first capability UEs. In some aspects, the UE may further receive system information or system information updates in the initial downlink BWP, the system information including separate information dedicated to the first capability UEs in a SIB carrying information for the first capability UEs and the second capability UEs.

[0110] Performing the initial access may include transmitting a random access preamble in a RO having an SSB-to-RO mapping based on CD-SSB. Performing the initial access may include transmitting a random access preamble in a RO having an SSB-to-RO mapping or an SSB-to-preamble mapping configured for the UE having the first capability.

[0111] In some aspects, the UE may further receive a configuration for an active downlink BWP and an active uplink BWP. The configuration for the active downlink BWP may include one or more of a periodic or semi-static TRS, a periodic or semi-static CSI-RS, a periodic or semi-static PRS, paging, a WUS, a CSS or CORESET for system information update or group-wide power control, a non-CD SSB, an additional CORESET or additional CSS for system information update, a resynchronization reference signal for UE synchronization in DRX mode or indicating a system information update and to assist UE synchronization in discontinuous reception, or an L3 intra-frequency measurement gap. The configuration may be received in system information that is dedicated to the UE with the first capability. The configuration may be received in RRC signaling for the UE. The configuration for the active downlink BWP or active uplink BWP may be based on a rule or a lookup table.

[0112] In some aspects, the UE may further perform a capability signaling procedure indicating that the UE has the first capability, and after completing the capability signaling procedure, the UE switches to an active downlink BWP and an active uplink BWP based on at least one of a MAC-CE, an RRC reconfiguration, a DCI, or a timer configured in the system information for the UE with the first capability.

[0113] In some aspects, the UE may receive a first configuration of a second initial downlink BWP dedicated to UEs having a first capability and may receive a second configuration of an active downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be received in a SIB dedicated to UEs of the first capability in the first initial downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be received as information dedicated to UEs of the first capability in a SIB carrying information for UEs of the first capability and UEs of the second capability in the first initial downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be received in system information in CORESET 0, which system information is dedicated to UEs of the first capability. In some aspects, the second configuration of the active downlink BWP may be received in the second initial downlink BWP. In some aspects, the configuration of the second initial downlink BWP may be based on a lookup table or a rule.

[0114] 14 is a flowchart 1400 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 350, 902, 1102, device 1504). The method may provide for configuration of a BWP for initial access and thereafter that provides a reduced bandwidth supported by reduced capability UEs while maintaining flexibility in configuring bandwidth for higher capability UEs. A UE performing the method may have a first capability associated with a lower maximum UE bandwidth than a second capability. For example, the UE may be a reduced capability UE.

[0115] At 1402, the UE may perform at least a portion of the initial access based on an initial downlink BWP shared between a UE having a first capability and a UE having a second capability. The initial access may be performed, for example, by the BWP component 198 of the apparatus 1504 in FIG. 15. FIG. 11 shows an example of a UE 1102 performing initial access in a shared initial DL BWP and in a dedicated DL BWP for a reduced capability UE. FIG. 9 shows an example of a UE 902 performing initial access in a shared initial DL BWP. The UE may perform initial access based in part on a first initial downlink BWP shared between a UE having a first capability and a UE having a second capability, and in part on a second initial downlink BWP that is dedicated to the UE having the first capability.

[0116] For example, the UE may perform initial access based on an initial uplink BWP dedicated to UEs with a first capability. As an example, the UE may perform initial access based in part on a first initial downlink BWP shared between UEs with a first capability and UEs with a second capability, and in part on a second initial downlink BWP dedicated to UEs with a first capability. The initial downlink BWP may include CORESET 0 and a CD-SSB configured for UEs with a first capability and UEs with a second capability. As shown at 1412, the UE may receive a first configuration of a second initial downlink BWP dedicated to UEs with a first capability, the first configuration of the second initial downlink BWP being received in the first initial downlink BWP within a SIB carrying information about UEs with the first capability and UEs with the second capability. The second initial downlink BWP dedicated to UEs with a first capability may not include CORESET 0 or a CD-SSB. As shown in 1414, the UE may transmit a random access preamble during a random access occasion (RO) in the second initial downlink BWP, where the RO has a synchronization signal block (SSB)-to-RO mapping to the CD-SSB in the first initial downlink BWP.

[0117] As shown at 1404, the UE may receive a configuration for a non-cell defined SSB (non-CD SSB) in an active downlink BWP that is dedicated to the UE having the first capability.

[0118] At 1406, the UE may switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE with the first capability. The BWP switching of the reduced capability UE may be configured for TDD mode, FD-FDD mode, or HD-FDD mode. The switching may be performed, for example, by the BWP component 198 of the apparatus 1504 in FIG. 15. FIG. 9 and FIG. 11 show examples of UEs 902 and 1102 switching to a dedicated active DL BWP for reduced capability UEs. In some aspects, the UE may perform an initial access at 1302 based on an initial downlink BWP and an initial uplink BWP shared between the UE with the first capability and the UE with the second capability, and the UE may switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE with the first capability after performing the initial access. FIG. 9 shows an example aspect of a UE using a shared initial DL BWP and a shared initial UL BWP. The initial downlink BWP may include CORESET 0 or CD-SSB configured for a UE with a first capability and a UE with a second capability, and the initial downlink BWP and the initial uplink BWP have a bandwidth at a center frequency of the carrier bandwidth, the bandwidth being less than or equal to a lower maximum UE bandwidth of the UE with the first capability.

[0119] At 1408, the UE may perform at least one of layer 1 (L1) or layer 3 (L3) measurements on the non-CD SSB in an active downlink BWP that is dedicated to UEs with the first capability. The reception and measurements may be performed by, for example, the BWP component 198 of, for example, the UE 104, 350, or the device 1504.

[0120] As shown at 1410, the UE may receive system information updates in RRC signaling in an active downlink BWP that is dedicated to UEs with the first capability. The reception may be performed by, for example, a BWP component 198 of, for example, the UE 104, 350, or the device 1504. Figure 10 shows an example of an active downlink BWP 1014 for a UE with reduced bandwidth capability, where the dedicated active downlink BWP includes RRC signaling for system information (SI) updates.

[0121] In some aspects, the UE may receive a first configuration of a second initial downlink BWP that is dedicated to the UE having the first capability. The UE may also receive a second configuration of an active downlink BWP in the second initial downlink BWP. The reception may be performed by, for example, the BWP component 198 of, for example, the UE 104, 350, or the device 1504.

[0122] Performing the initial access may include transmitting a random access preamble in the RO with an SSB-to-RO mapping for UEs with a first capability that is different from that for UEs with a second capability. The SSB-to-RO mapping for UEs with a first capability is based on a non-CD SSB. The one or more parameters for the non-CD SSB may be configured independently of the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology. The one or more parameters for the non-CD SSB may be the same parameters as for the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology. The one or more parameters may be from at least one of system information, a broadcast physical downlink control channel, a lookup table, or a rule. The non-CD SSB may be configured in at least one of the second initial downlink BWP or the active downlink BWP and is common to measurements by the first capability UE and the second capability UE. At least one of the second initial downlink BWP or the active downlink BWP may overlap in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP. The initial downlink BWP may include CORESET 0 or CD-SSB configured for the UE with the first capability and the UE with the second capability, the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are less than or equal to the lower maximum UE bandwidth of the UE with the first capability. The initial uplink BWP and the second initial downlink BWP may be at the edge of the carrier bandwidth.

[0123] In some aspects, the UE may further receive system information or system information updates in the initial downlink BWP, the system information included in a SIB dedicated to the first capability UEs. In some aspects, the UE may further receive system information or system information updates in the initial downlink BWP, the system information including separate information dedicated to the first capability UEs in a SIB carrying information for the first capability UEs and the second capability UEs.

[0124] Performing the initial access may include transmitting a random access preamble in a RO having an SSB-to-RO mapping based on CD-SSB. Performing the initial access may include transmitting a random access preamble in a RO having an SSB-to-RO mapping or an SSB-to-preamble mapping configured for the UE having the first capability.

[0125] In some aspects, the UE may further receive configurations for an active downlink BWP and an active uplink BWP. The configuration for the active downlink BWP may include one or more of periodic or semi-static TRS, periodic or semi-static CSI-RS, periodic or semi-static PRS, paging, WUS, CSS or CORESET for system information update or group-wide power control, non-CD SSB, additional CORESET or additional CSS for system information update, resynchronization reference signal for UE synchronization in DRX mode or indicating system information update and to assist UE synchronization in discontinuous reception, or L3 intra-frequency measurement gap when SSB is not transmitted in the active downlink BWP. The configuration may be received in system information that is dedicated to UEs with the first capability. The configuration may be received in RRC signaling for the UE. The configuration of the active downlink BWP or active uplink BWP may be based on a rule or a lookup table.

[0126] In some aspects, the UE may further perform a capability signaling procedure indicating that the UE has the first capability, and after completing the capability signaling procedure, the UE switches to an active downlink BWP and an active uplink BWP based on at least one of a MAC-CE, RRC reconfiguration, DCI), or a timer configured in system information for the UE with the first capability.

[0127] In some aspects, the UE may receive a first configuration of a second initial downlink BWP dedicated to UEs having a first capability and may receive a second configuration of an active downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be received in a SIB dedicated to UEs of the first capability in the first initial downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be received as information dedicated to UEs of the first capability in a SIB carrying information for UEs of the first capability and UEs of the second capability in the first initial downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be received in system information in CORESET 0, which system information is dedicated to UEs of the first capability. In some aspects, the second configuration of the active downlink BWP may be received in the second initial downlink BWP. In some aspects, the configuration of the second initial downlink BWP may be based on a lookup table or a rule.

[0128] FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1504. The apparatus 1504 may be a UE, may be a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1504 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., cellular RF transceivers). The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the apparatus 1504 may further include an application processor 1506 coupled to one or more subscriber identity module (SIM) cards 1520, a secure digital (SD) card 1508, and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the device 1504 may further include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., a barometric sensor / altimeter, an inertial management 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 1526, a power source 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include an on-chip transceiver (TRX) (or in some cases simply a receiver (RX)).The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include their own dedicated antennas and / or utilize an antenna 1580 for communication. The cellular baseband processor 1524 communicates with the UE 104 and / or RUs associated with the network entity 1502 through the transceiver 1522 via one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory module 1526 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including the execution of software stored in the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1524 / application processor 1506, causes the cellular baseband processor 1524 / application processor 1506 to perform various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1524 / application processor 1506 when executing the software. The cellular baseband processor 1524 / application processor 1506 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 1504 may be a processor chip (modem and / or application) and may include only the cellular baseband processor 1524 and / or the application processor 1506, and in another configuration, the device 1504 may be an entire UE (e.g., see 350 in FIG. 3) and may include additional modules of the device 1504.

[0129] The cellular baseband processor 1524 and / or the application processor 1506 may include a BWP component 198 configured to perform at least a portion of the initial access based on an initial downlink BWP shared between a UE having a first capability and a UE having a second capability, e.g., as described in connection with 1302 of FIG. 13, and to switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability, e.g., as described in connection with 1304 of FIG. 13. As an example, the BWP component 198 may include, e.g., an initial BWP component 1540 configured to perform at least a portion of the initial access based on an initial downlink BWP shared between a UE having a first capability and a UE having a second capability, e.g., as described in connection with 1302 of FIG. 13. The BWP component 198 may be further configured to perform any of the aspects of the algorithms in the flowcharts of FIG. 13, FIG. 14, and / or the aspects performed by the UE in FIG. 9 and / or FIG. 11.

[0130] The apparatus 1504 may include additional components that implement each of the blocks of the algorithms in the flowcharts of Figures 13, 14, and / or the aspects implemented by the UE in Figures 9 and / or 11. Thus, each block in the flowchart of Figure 13, and / or the aspects implemented by the UE in Figures 9 and / or 11 may be implemented by a component, and the apparatus may include one or more of those components. The components may be one or more hard components specifically configured to perform the described processes / algorithms, implemented by a processor configured to implement the described processes / algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0131] As shown, the apparatus 1504 may include various components configured for various functions. In one configuration, the apparatus 1504, in particular the cellular baseband processor 1524 and / or the application processor 1506, may include means for performing at least a portion of the initial access based on an initial downlink BWP shared between a UE having a first capability and a UE having a second capability, and means for switching to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability. The apparatus 1504 may further include means for receiving system information in the initial downlink BWP, the system information included in a SIB dedicated to the UE of the first capability. The apparatus 1504 may further include means for receiving system information in the initial downlink BWP, the system information including separate information dedicated to the UE of the first capability in a SIB carrying information for the UE of the first capability and the UE of the second capability. The apparatus 1504 may further include means for receiving a configuration for an active downlink BWP and an active uplink BWP. The apparatus 1504 may further include means for performing a capability signaling procedure indicating that the UE has the first capability. The apparatus 1504 may further include means for receiving a first configuration of a second initial downlink BWP dedicated to the UE with the first capability, and means for receiving a second configuration of an active downlink BWP. The apparatus 1504 may include means for receiving a first configuration of a second initial downlink BWP dedicated to the UE with the first capability, the first configuration of the second initial downlink BWP being received in the first initial downlink BWP in a SIB carrying information for the UE of the first capability and the UE of the second capability. The apparatus 1504 may include means for receiving a configuration for a non-CD SSB in an active downlink BWP dedicated to the UE with the first capability, and means for performing at least one of L1 measurements or L3 measurements on the non-CD SSB in the active downlink BWP dedicated to the UE with the first capability.The apparatus 1504 may include means for implementing each of the blocks of the algorithms in the flowcharts of Figures 13 and 14 and / or aspects implemented by the UE in Figures 9 and / or 11. The means may be one or more of the components of the apparatus 1504 configured to implement the functions recited by the means. As described above, the apparatus 1504 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 the controller / processor 359 configured to implement the functions recited by the means.

[0132] FIG. 16 is a flowchart 1600 of a method of wireless communication. The method may be implemented by a network entity, such as a base station or a component of a base station (e.g., base station 102 / 180, 310, 904, 1104, network entity 1802). The method may provide for configuration of a BWP for initial access and thereafter that provides a reduced bandwidth supported by reduced capability UEs while maintaining flexibility in configuring bandwidth for higher capability UEs. A network entity implementing the method may support communication with one or more UEs having a first capability associated with a maximum UE bandwidth lower than a second capability, and one or more UEs of a second capability. For example, a base station may communicate with reduced capability UEs and higher capability UEs.

[0133] In 1602, the network entity performs an initial access with a first capability associated with a maximum UE bandwidth lower than a second capability, and at least a portion of the initial access is based on an initial downlink BWP shared between a UE with the first capability and a UE with the second capability. The initial access may be performed, for example, by the BWP component 199 of the network entity 1802 in FIG. 18. FIG. 9 shows an example of a base station 904 performing initial access in a shared initial DL BWP. FIG. 11 shows an example of a base station 1104 performing initial access in a part of a shared initial DL BWP and in a part of a dedicated DL BWP for reduced capability UEs.

[0134] The network entity may perform the initial access based in part on a first initial downlink BWP shared between the UE with the first capability and the UE with the second capability and based in part on a second initial downlink BWP dedicated to the UE with the first capability. The network entity may perform the initial access based on an initial uplink BWP dedicated to the UE with the first capability. The network entity may configure BWP switching for the reduced capability UE for TDD mode, FD-FDD mode, or HD-FDD mode.

[0135] Performing the initial access may include receiving a random access preamble in the RO with an SSB-to-RO mapping for UEs with a first capability that is different from that for UEs with a second capability. The SSB-to-RO mapping for UEs with a first capability is based on a non-CD SSB. The one or more parameters for the non-CD SSB may be configured independently of the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology. The one or more parameters for the non-CD SSB may be the same parameters as for the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology. The one or more parameters may be from at least one of system information, a broadcast physical downlink control channel, a lookup table, or a rule. The non-CD SSB may be configured in at least one of the second initial downlink BWP or the active downlink BWP and is common to measurements by the first capability UE and the second capability UE. At least one of the second initial downlink BWP or the active downlink BWP may overlap in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP. The initial downlink BWP may include CORESET 0 and CD-SSB configured for the UE with the first capability and the UE with the second capability, the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are equal to or less than the lower maximum UE bandwidth of the UE with the first capability and the UE with the second capability. The initial uplink BWP and the second initial downlink BWP may be at the edge of the carrier bandwidth.

[0136] At 1604, the network entity switches to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability for communication with the UE. The switching may be performed, for example, by the BWP component 199 of the network entity 1802 in FIG. 18. FIG. 9 and FIG. 11 show examples of base stations 904 and 1104 switching to a dedicated active DL BWP for reduced capability UEs. In some aspects, the network entity may perform an initial access at 1602 based on an initial downlink BWP and an initial uplink BWP shared between the base station with the first capability and the UE with the second capability, and the base station may switch to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability after performing the initial access. FIG. 9 shows an example aspect of a base station 904 using a shared initial DL BWP and a shared initial UL BWP. The initial downlink BWP may include CORESET 0 and CD-SSB configured for a UE with a first capability and a UE with a second capability, and the initial downlink BWP and the initial uplink BWP have a bandwidth at a center frequency of the carrier bandwidth, the bandwidth being less than or equal to a lower maximum UE bandwidth of the UE with the first capability.

[0137] In some aspects, the network entity may further transmit system information or a system information update in the initial downlink BWP, the system information included in a SIB dedicated to the first capability UE. In some aspects, the network entity may further transmit system information or a system information update in the initial downlink BWP, the system information including separate information dedicated to the first capability UE in a SIB carrying information for the first capability UE and the second capability UE.

[0138] Performing the initial access may include receiving a random access preamble in a RO having an SSB-to-RO mapping based on CD-SSB. Performing the initial access may include receiving a random access preamble in a RO having an SSB-to-RO mapping or an SSB-to-preamble mapping configured for the UE having the first capability.

[0139] In some aspects, the network entity may further transmit configurations for an active downlink BWP and an active uplink BWP. The configurations for the active downlink BWP may include one or more of periodic or semi-static TRS, periodic or semi-static CSI-RS, CSS or CORESET for paging, system information update, WUS or group-wide power control, non-CD SSB, additional CORESET or additional CSS for system information update, resynchronization reference signal indicating system information update, or Layer 3 (L3) intra-frequency measurement gap for UE synchronization in discontinuous reception (DRX) mode. The configurations may be transmitted in system information that is dedicated to UEs having the first capability. The configurations may be transmitted in RRC signaling for the UE. The configurations for the active downlink BWP or active uplink BWP may be based on a rule or a lookup table.

[0140] In some aspects, the network entity may further perform a capability signaling procedure to learn that the UE has a first capability, and after completing the capability signaling procedure, the network entity switches to an active downlink BWP and an active uplink BWP based on at least one of a timer configured in the MAC-CE, RRC reconfiguration, DCI, or system information.

[0141] In some aspects, the network entity may further transmit a first configuration of a second initial downlink BWP dedicated to UEs having the first capability and may receive a second configuration of an active downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be transmitted in the first initial downlink BWP in a SIB dedicated to UEs of the first capability. In some aspects, the first configuration of the second initial downlink BWP may be transmitted in the first initial downlink BWP as information dedicated to UEs of the first capability in a SIB carrying information for UEs of the first capability and UEs of the second capability. In some aspects, the first configuration of the second initial downlink BWP may be transmitted in system information in CORESET 0, which system information is dedicated to UEs of the first capability. In some aspects, the second configuration of the active downlink BWP may be received in the second initial downlink BWP. In some aspects, the configuration of the second initial downlink BWP may be based on a lookup table or a rule.

[0142] FIG. 17 is a flowchart 1700 of a method of wireless communication. The method may be implemented by a network entity, such as a base station or a component of a base station (e.g., base station 102 / 180, 310, 904, 1104, network entity 1802). The method may provide for configuration of a BWP for initial access and thereafter that provides a reduced bandwidth supported by reduced capability UEs while maintaining flexibility in configuring bandwidth for higher capability UEs. A network entity implementing the method may support communication with one or more UEs having a first capability associated with a maximum UE bandwidth lower than a second capability, and one or more UEs of a second capability. For example, a base station may communicate with reduced capability UEs and higher capability UEs.

[0143] At 1702, the network entity may perform an initial access with a first capability associated with a maximum UE bandwidth lower than a second capability, where at least a portion of the initial access is based on an initial downlink BWP shared between a UE with the first capability and a UE with the second capability. The initial access may be performed by, for example, the base station 102 or 310, or by, for example, the BWP component 199 of the network entity 1802. Figure 11 shows an example of a base station 1104 performing a portion of the initial access in a shared initial DL BWP and a portion of the initial access in a dedicated DL BWP for reduced capability UEs.

[0144] As shown at 1704, the network entity may output a configuration for a non-CD SSB in an active downlink BWP dedicated to the UE with the first capability. The non-CD SSB may be for L1 and / or L3 measurements by the UE in an active downlink BWP dedicated to the UE with the first capability. The output may be performed by, for example, the base station 102 or 310, or by, for example, the BWP component 199 of the network entity 1802.

[0145] At 1706, the network entity may switch to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability for communication with the UE. The switching may be performed, for example, by the BWP component 199 of the network entity 1802 in Figure 18. Figures 9 and 11 show examples of base stations 904 and 1104 switching to a dedicated active DL BWP for reduced capability UEs.

[0146] For example, the network entity may perform initial access with the UE based on an initial uplink BWP dedicated to the UE with the first capability. As an example, the network entity may perform initial access based in part on a first initial downlink BWP shared between the UE with the first capability and the UE with the second capability, and in part on a second initial downlink BWP dedicated to the UE with the first capability. The initial downlink BWP may include CORESET 0 and a CD-SSB configured for the UE with the first capability and the UE with the second capability. As shown in 1712, the network entity may output a first configuration of the second initial downlink BWP dedicated to the UE with the first capability for transmission, the first configuration of the second initial downlink BWP being received in the first initial downlink BWP within a SIB carrying information about the UE with the first capability and the UE with the second capability. The second initial downlink BWP dedicated to the UE with the first capability may not include CORESET 0 or a CD-SSB. As shown in 1714, the network entity may obtain, e.g., receive, a random access preamble during a RO in the second initial downlink BWP, where the RO has an SSB-to-RO mapping to a CD-SSB in the first initial downlink BWP.

[0147] As shown at 1708, the network entity may output the system information update in RRC signaling in an active downlink BWP that is dedicated to the UE with the first capability. The output may be performed by, for example, a BWP component 199 of, for example, the UE 104, 350, or the device 1504. Figure 10 shows an example of an active downlink BWP 1014 for a UE with reduced bandwidth capability, where the dedicated active downlink BWP includes RRC signaling for system information (SI) updates.

[0148] In some aspects, the UE may receive a first configuration of a second initial downlink BWP that is dedicated to the UE with the first capability. The UE may also receive a second configuration of an active downlink BWP in the second initial downlink BWP. The reception may be performed by, for example, the base station 102 or 310, or by, for example, the BWP component 199 of the network entity 1802.

[0149] FIG. 9 illustrates an example of a base station 904 performing initial access in a shared initial DL BWP. In some aspects, the network entity may perform the initial access based in part on a first initial downlink BWP shared between a UE with a first capability and a UE with a second capability, and in part on a second initial downlink BWP that is dedicated to the UE with the first capability. The network entity may perform the initial access based on an initial uplink BWP that is dedicated to the UE with the first capability. The network entity may configure BWP switching of reduced capability UEs for TDD mode, FD-FDD mode, or HD-FDD mode.

[0150] Performing the initial access may include receiving a random access preamble in the RO with an SSB-to-RO mapping for UEs with a first capability that is different from that for UEs with a second capability. The SSB-to-RO mapping for UEs with a first capability is based on a non-CD SSB. The one or more parameters for the non-CD SSB may be configured independently of the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology. The one or more parameters for the non-CD SSB may be the same parameters as for the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology. The one or more parameters may be from at least one of system information, a broadcast physical downlink control channel, a lookup table, or a rule. The non-CD SSB may be configured in at least one of the second initial downlink BWP or the active downlink BWP and is common to measurements by the first capability UE and the second capability UE. At least one of the second initial downlink BWP or the active downlink BWP may overlap in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP. The initial downlink BWP may include CORESET 0 and CD-SSB configured for the UE with the first capability and the UE with the second capability, the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are equal to or less than the lower maximum UE bandwidth of the UE with the first capability and the UE with the second capability. The initial uplink BWP and the second initial downlink BWP may be at the edge of the carrier bandwidth.

[0151] In 1706, the network entity switches to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability for communication with the UE. The switching may be performed by, for example, the base station 102 or 310, or by, for example, the BWP component 199 of the network entity 1802. FIG. 9 and FIG. 11 show examples of base stations 904 and 1104 switching to a dedicated active DL BWP for reduced capability UEs. In some aspects, the network entity may perform an initial access in 1702 based on an initial downlink BWP and an initial uplink BWP shared between the base station with the first capability and the UE with the second capability, and the base station may switch to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability after performing the initial access. FIG. 9 shows an example aspect of a base station 904 using a shared initial DL BWP and a shared initial UL BWP. The initial downlink BWP may include CORESET 0 and CD-SSB configured for a UE with a first capability and a UE with a second capability, and the initial downlink BWP and the initial uplink BWP have a bandwidth at a center frequency of the carrier bandwidth, the bandwidth being less than or equal to a lower maximum UE bandwidth of the UE with the first capability.

[0152] In some aspects, the network entity may further output system information or a system information update, e.g., for transmission, in the initial downlink BWP, the system information included in a SIB dedicated to the first capability UE. In some aspects, the network entity may further transmit system information or a system information update in the initial downlink BWP, the system information including separate information dedicated to the first capability UE in a SIB carrying information for the first capability UE and the second capability UE.

[0153] Performing the initial access may include receiving a random access preamble in a RO having an SSB-to-RO mapping based on CD-SSB. Performing the initial access may include receiving a random access preamble in a RO having an SSB-to-RO mapping or an SSB-to-preamble mapping configured for the UE having the first capability.

[0154] In some aspects, the base station may further transmit configurations for the active downlink BWP and the active uplink BWP. The configurations for the active downlink BWP may include one or more of periodic or semi-static TRS, periodic or semi-static CSI-RS, CSS or CORESET for paging, system information update, WUS or group-wide power control, non-CD SSB, additional CORESET or additional CSS for system information update, resynchronization reference signal indicating system information update for UE synchronization in discontinuous reception (DRX) mode, or L3 intra-frequency measurement gap when SSB is not transmitted in the active downlink BWP. The configurations may be transmitted in system information that is dedicated to UEs with the first capability. The configurations may be transmitted in RRC signaling for the UE. The configurations for the active downlink BWP or the active uplink BWP may be based on a rule or a lookup table.

[0155] In some aspects, the base station may further perform a capability signaling procedure to learn that the UE has a first capability, and the base station switches to an active downlink BWP and an active uplink BWP after completing the capability signaling procedure based on at least one of a timer configured in the MAC-CE, RRC reconfiguration, DCI, or system information.

[0156] In some aspects, the base station may further transmit a first configuration of a second initial downlink BWP dedicated to UEs having the first capability and may receive a second configuration of an active downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be transmitted in a SIB dedicated to UEs of the first capability in the first initial downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be transmitted as information dedicated to UEs of the first capability in a SIB carrying information for UEs of the first capability and UEs of the second capability in the first initial downlink BWP. In some aspects, the first configuration of the second initial downlink BWP may be transmitted in system information in CORESET 0, which system information is dedicated to UEs of the first capability. In some aspects, the second configuration of the active downlink BWP may be received in the second initial downlink BWP. In some aspects, the configuration of the second initial downlink BWP may be based on a lookup table or a rule.

[0157] FIG. 18 is a diagram 1800 illustrating an example of a hardware implementation for a network entity 1802. The network entity 1802 may be a base station, a component of a base station, or may implement base station functionality. The network entity 1802 may include at least one of a CU 1810, a DU 1830, or a RU 1840. For example, depending on the layer functionality processed by the component 199, the network entity 1802 may include a CU 1810, both a CU 1810 and a DU 1830, each of a CU 1810, a DU 1830, and a RU 1840, both a DU 1830, a DU 1830, and a RU 1840, or a RU 1840. The CU 1810 may include a CU processor 1812. The CU processor 1812 may include an on-chip memory 1812′. In some aspects, the CU 1810 may further include an additional memory module 1814 and a communication interface 1818. The CU 1810 communicates with the DU 1830 via a midhaul link, such as an F1 interface. The device 1830 may include a DU processor 1832. The DU processor 1832 may include an on-chip memory 1832'. In some aspects, the DU 1830 may further include an additional memory module 1834 and a communication interface 1838. The DU 1830 communicates with the RU 1840 via a fronthaul link. The RU 1840 may include a RU processor 1842. The RU processor 1842 may include an on-chip memory 1842'. In some aspects, the RU 1840 may further include an additional memory module 1844, one or more transceivers 1846, an antenna 1880, and a communication interface 1848. The RU 1840 communicates with the UE 104. The on-chip memories 1812', 1832', 1842' and the additional memory modules 1814, 1834, 1844 may each be considered a computer readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 1812, 1832, 1842 is responsible for general processing, including the execution of software stored in the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform various functions discussed above.The computer-readable medium / memory may also be used for storing data that is manipulated by the processor when executing the software.

[0158] The network entity 1802 may include a BWP component 199, e.g., as described in connection with any of FIG. 1, FIG. 3, FIG. 16, or FIG. 17. The BWP component 199 may be configured to perform at least a portion of the initial access based on an initial downlink BWP shared between a UE having a first capability and a UE having a second capability, e.g., as described in connection with 1602 of FIG. 16, and to switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability, e.g., as described in connection with 1604 of FIG. 16. In some aspects, the BWP component 199 may include an initial BWP configuration component 1845, which is configured to perform at least a portion of the initial access based on an initial downlink BWP shared between a UE having a first capability and a UE having a second capability, e.g., as described in connection with 1602 of FIG. 16. The BWP component 199 may further include an active BWP configuration component 1847 configured to switch to an active downlink BWP and an active uplink BWP that are dedicated to a UE having a first capability, for example, as described in connection with 1604 of FIG. 16 .

[0159] The network entity 1802 may include additional components that implement each of the blocks of the algorithms in the flowcharts of Figures 16, 17, and / or aspects performed by the base station in Figures 9 or 11. Thus, each of the blocks in the flowcharts of Figures 16, 17, and / or aspects performed by the base station in Figures 9 or 11 may be implemented by components, and an apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the described processes / algorithms, implemented by a processor configured to perform the described processes / algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0160] As shown, the network entity 1802 may include various components configured for various functions. In one configuration, the network entity 1802 may include means for performing initial access with a UE having a first capability associated with a lower maximum UE bandwidth than a second capability, where at least a portion of the initial access is based on an initial downlink BWP shared between the UE having the first capability and the UE having the second capability, and means for switching to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability for communication with the UE. The network entity 1802 may further include means for transmitting system information in the initial downlink BWP, where the system information is included in a SIB dedicated to the UE of the first capability. The network entity 1802 may further include means for transmitting system information in the initial downlink BWP, where the system information includes separate information dedicated to the UE of the first capability in a SIB carrying information for the UE of the first capability and the UE of the second capability. The network entity 1802 may further include means for transmitting configurations for an active downlink BWP and an active uplink BWP. The network entity 1802 may further include means for receiving a capability signaling indicating that the UE has a first capability, and the base station switches to the active downlink BWP and the active uplink BWP after receiving the capability signaling procedure. The network entity 1802 may further include means for transmitting a first configuration of a second initial downlink BWP dedicated to the UE having the first capability, and means for transmitting a second configuration of the active downlink BWP. The network entity 1802 may further include means for performing an initial access based in part on the first initial downlink BWP shared between the UE having the first capability and the UE having the second capability, and based in part on the second initial downlink BWP dedicated to the UE having the first capability, the initial downlink BWP including CORESET 0 and a cell CD-SSB configured for the UE having the first capability and the UE having the second capability.The network entity 1802 may further include means for outputting for transmission a first configuration of a second initial downlink BWP dedicated to the UE with the first capability, the first configuration of the second initial downlink BWP being received in a SIB carrying information for the UE with the first capability and the UE with the second capability, the second initial downlink BWP dedicated to the UE with the first capability does not include CORESET 0 or CD-SSB. The network entity 1802 may further include means for obtaining a random access preamble during an RO in the second initial downlink BWP, the RO having an SSB-to-RO mapping to the CD-SSB in the first initial downlink BWP. The network entity 1802 may further include means for outputting for transmission a configuration for a non-CD SSB in an active downlink BWP dedicated to the UE with the first capability, the non-CD SSB being for at least one of L1 measurements or L3 measurements for the UE with the first capability. The network entity 1802 may include means for implementing any of the aspects of the algorithms in the flowcharts of FIG. 16, FIG. 17, and / or any of the aspects implemented by the base station in FIG. 9 or FIG. 11. The means may be one or more of the components of the network entity 1802 configured to implement the functions recited by the means. As described above, the network entity 1802 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 the controller / processor 375 configured to implement the functions recited by the means described in connection with FIG. 3.

[0161] It is understood that the particular order or hierarchy of the blocks in the disclosed processes / flowcharts is illustrative of example approaches. Based on design preferences, it is understood that the particular order or hierarchy of the blocks in the processes / flowcharts may be rearranged. Further, some blocks may 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.

[0162] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications of 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 "one and only one" unless so expressly stated, but means "one or more." Terms such as "if," "when," and "while" indicate "under the condition that," rather than implying an immediate temporal relationship or reaction. That is, these phrases, e.g., "when," do not imply an immediate action in response to or during the occurrence of the action, but merely imply that the action will occur if a condition is met, but does not require a specific or immediate time 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" is not necessarily to be construed as preferred or advantageous over other aspects. Unless otherwise specified, 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 can include multiple A, multiple B, or multiple C. 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," "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 members 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 may be received / transmitted directly between the first device and the second device, or may be received / transmitted indirectly between the first device and the second device via a set of devices. All structural and functional equivalents of the elements of the various embodiments described throughout this disclosure that are known or that later become known to those skilled in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is 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 claim element should be construed as a means plus function unless the element is expressly recited using the phrase "means for."

[0163] As used herein, the phrase "based on" should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" may be information, a condition, a factor, etc.) shall be construed as "based at least on A," unless expressly stated otherwise.

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

[0165] Aspect 1 is a method of wireless communication in a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, the method including: performing at least a portion of an initial access based on a first initial downlink BWP shared between the UE having the first capability and a UE having the second capability; and switching after the initial access to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability.

[0166] In aspect 2, the method of aspect 1 further includes the UE performing initial access based on a first initial downlink BWP and an initial uplink BWP shared between the UE having the first capability and the UE having the second capability, and after performing the initial access, the UE switches to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability, and the BWP switching of the UE is configured for a TDD mode, a FD-FDD mode, or a HD-FDD mode.

[0167] In example 3, the method of example 1 or example 2 further includes the first initial downlink BWP including CORESET 0 or CD-SSB configured for the UE having the first capability and the UE having the second capability, the first initial downlink BWP and the initial uplink BWP having the same or different center frequencies and the same or different bandwidths, and the first bandwidth of the first initial downlink BWP and the second bandwidth of the initial uplink BWP are less than or equal to a lower maximum UE bandwidth of the UE having the first capability and the UE having the second capability.

[0168] In an aspect 4, the method of any of aspects 1 to 3 further includes receiving system information or a system information update in the first initial downlink BWP, where the system information is included in a SIB dedicated to the first capability UE.

[0169] In aspect 5, the method of any of aspects 1 to 3 further includes receiving system information or a system information update in a first initial downlink BWP, the system information including separate information dedicated to the first capability UE within a SIB carrying information for the first capability UE and the second capability UE.

[0170] In example 6, the method of any of examples 1-5 further includes, where performing initial access includes transmitting a random access preamble in the RO having an SSB-to-RO mapping based on CD-SSB.

[0171] In example 7, the method of any of examples 1 to 5 further includes that performing the initial access includes transmitting a random access preamble in an RO having an SSB-to-RO mapping or an SSB-to-preamble mapping configured for the UE having the first capability.

[0172] In example 8, the method of any of examples 1-7 further includes receiving a configuration for an active downlink BWP and an active uplink BWP, where the configuration for the active downlink BWP includes one or more of a periodic or semi-static TRS, a periodic or semi-static CSI-RS, a periodic or semi-static PRS, a CSS or CORESET for paging, a system information update, a WUS or group common power control, a non-CD SSB, an additional CORESET or additional CSS for a system information update, a resynchronization reference signal indicating a system information update for UE synchronization in DRX mode, or an L3 intra-frequency measurement gap if no SSB is transmitted in the active downlink BWP.

[0173] In an aspect 9, the method of aspect 8 further includes the configuration being received in system information that is dedicated to the UEs having the first capability.

[0174] In example 10, the method of example 8 further includes the configuration being received in RRC signaling for the UE.

[0175] In an eleventh example, the method of any of the first to seventh examples further includes: configuring the active downlink BWP or the active uplink BWP based on a rule or a lookup table.

[0176] In example 12, any of the methods of examples 1 to 11 further includes performing a capability signaling procedure indicating that the UE has a first capability, and after completing the capability signaling procedure, the UE switches to an active downlink BWP and an active uplink BWP based on at least one of a MAC-CE, an RRC reconfiguration, a DCI, or a timer configured in system information for the UE having the first capability.

[0177] In example 13, the method of example 1 further includes the UE performing initial access based in part on a first initial downlink BWP shared between a UE having the first capability and a UE having the second capability, and based in part on a second initial downlink BWP that is dedicated to the UE having the first capability.

[0178] In example 14, the method of example 1 or example 13 further includes the UE performing the initial access based on an initial uplink BWP that is dedicated to the UE having the first capability.

[0179] In aspect 15, the method of aspect 14 further includes that performing the initial access includes transmitting a random access preamble in an RO having an SSB-to-RO mapping for the UE having the first capability that is different from that for the UE having the second capability.

[0180] In example 16, the method of example 15 further includes that the SSB-to-RO mapping for the UEs having the first capability is based on a non-CD SSB.

[0181] In example 17, the method of example 13, 15, or 16 further includes that the one or more parameters for the non-CD SSB may be the same parameters as for the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology.

[0182] In example 18, the method of example 13, 15, or 16 further includes one or more parameters for the non-CD SSB configured independently from the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology.

[0183] In aspect 19, the method of aspect 18 further includes the one or more parameters being from at least one of system information, a broadcast physical downlink control channel, a lookup table, or a rule.

[0184] In aspect 20, the method of aspect 16 further includes the non-CD SSB being configured in at least one of the second initial downlink BWP or the active downlink BWP and being common to measurements by the first capability UE and the second capability UE.

[0185] In example 21, the method of example 16 further includes at least one of the second initial downlink BWP or the active downlink BWP overlapping in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP.

[0186] In example 22, the method of example 13 or 14 further includes the first initial downlink BWP including CORESET 0 and a CD-SSB configured for a UE having a first capability and a UE having a second capability, the first initial downlink BWP having a bandwidth at a center frequency of a carrier bandwidth, the bandwidth being less than or equal to a lower maximum UE bandwidth of the UE having the first capability, and the initial uplink BWP and the second initial downlink BWP being at an edge of the carrier bandwidth.

[0187] In example 23, the method of any of examples 1 or 13 to 22 further includes receiving a first configuration of a second initial downlink BWP dedicated to a UE having the first capability, and receiving a second configuration of an active downlink BWP.

[0188] In example 24, the method of example 23 further includes a first configuration of a second initial downlink BWP being received in a SIB dedicated to the first capability UE in the first initial downlink BWP.

[0189] In aspect 25, the method of aspect 23 further includes the first configuration of the second initial downlink BWP being received in the first initial downlink BWP as information dedicated to the first capability UE within a SIB carrying information for the first capability UE and the second capability UE.

[0190] In example 26, the method of example 23 further includes: a first configuration of a second initial downlink BWP is received in system information in CORESET 0, the system information being dedicated to the first capability UE.

[0191] In example 27, the method of example 23 further includes a second configuration of the active downlink BWP being received in a second initial downlink BWP.

[0192] In example 28, the method of any of examples 1 or 13-22 further includes: configuring the second initial downlink BWP based on a lookup table or a rule.

[0193] In example 29, the method of example 1 further includes performing initial access based in part on a first initial downlink BWP shared between a UE having the first capability and a UE having the second capability, and based in part on a second initial downlink BWP that is dedicated to the UE having the first capability.

[0194] In aspect 30, the method of aspect 29 further includes the first initial downlink BWP including CORESET 0 and a CD-SSB configured for a UE having the first capability and a UE having the second capability.

[0195] In aspect 31, the method of aspect 29 or aspect 30 further includes receiving a first configuration of a second initial downlink BWP dedicated to UEs having the first capability, and the first configuration of the second initial downlink BWP is received in the first initial downlink BWP within a SIB carrying information regarding UEs of the first capability and UEs of the second capability.

[0196] In example 32, the method of any of examples 29-31 further includes, wherein the second initial downlink BWP dedicated to the UE having the first capability does not include CORESET 0 or CD-SSB.

[0197] In example 33, the method of any of examples 29 to 32 further includes that performing initial access includes transmitting a random access preamble during an RO in a second initial downlink BWP, the RO having an SSB-to-RO mapping to a CD-SSB in the first initial downlink BWP.

[0198] In example 34, the method of any of examples 29-33 further includes receiving a configuration for a non-CD SSB in an active downlink BWP that is dedicated to the UE having the first capability.

[0199] In example 35, the method of example 34 further includes performing at least one of L1 or L3 measurements on the non-CD SSB in an active downlink BWP that is dedicated to the UE having the first capability.

[0200] In example 36, the method of any of examples 29-35 further includes receiving a system information update in RRC signaling in an active downlink BWP dedicated to the UE having the first capability.

[0201] In example 37, the method of any of examples 29 to 36 further includes receiving a first configuration of a second initial downlink BWP dedicated to a UE having the first capability, and receiving a second configuration of an active downlink BWP in the second initial downlink BWP.

[0202] Aspect 38 is an apparatus for wireless communication in a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, the apparatus comprising a memory and at least one processor coupled to the memory, wherein based at least in part on information stored in the memory, the at least one processor is configured to perform a method as described in any of claims 1 to 37.

[0203] Aspect 39 is an apparatus for wireless communication in a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, the apparatus comprising means for performing a method according to any of claims 1 to 37.

[0204] In example 40, the apparatus of example 38 or 39 further includes at least one antenna or transceiver.

[0205] Aspect 41 is a non-transitory computer readable medium storing computer executable code in a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, the code, when executed by a processor, causing the processor to perform a method as described in any of claims 1 to 37.

[0206] Aspect 42 is a method of wireless communication in a network entity, the method including: performing initial access with a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, where at least a portion of the initial access is based on a first initial downlink BWP shared between the UE having the first capability and the UE having the second capability; and switching to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability for communication with the UE.

[0207] In aspect 43, the method of aspect 42 further includes the base station performing initial access based on a first initial downlink BWP and an initial uplink BWP shared between a UE having a first capability and a UE having a second capability, and after performing the initial access, switching to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability.

[0208] In example 44, the method of example 42 or example 43 further includes the first initial downlink BWP including CORESET 0 and a CD-SSB configured for a UE having a first capability and a UE having a second capability, and the first initial downlink BWP and the initial uplink BWP have a bandwidth at a center frequency of the carrier bandwidth, the bandwidth being less than or equal to a lower maximum UE bandwidth of the UE having the first capability.

[0209] In example 45, the method of any of examples 42-44 further includes transmitting system information in the first initial downlink BWP, where the system information is included in a SIB dedicated to the first capability UE.

[0210] In aspect 46, the method of any of aspects 42 to 44 further includes transmitting system information in a first initial downlink BWP, the system information including separate information dedicated to the first capability UE within a SIB carrying information for the first capability UE and the second capability UE.

[0211] In example 47, the method of any of examples 42-46 further includes that performing initial access includes receiving a random access preamble from the UE in a RO having an SSB-to-RO mapping based on CD-SSB.

[0212] In example 48, the method of any of examples 42-46 further includes that performing the initial access includes receiving a random access preamble from the UE in an RO having an SSB-to-RO mapping or an SSB-to-preamble mapping configured for the UE having the first capability.

[0213] In example 49, the method of any of examples 42-48 further includes transmitting a configuration for an active downlink BWP and an active uplink BWP, where the configuration for the active downlink BWP includes one or more of a periodic or semi-static TRS, a periodic or semi-static CSI-RS, a periodic or semi-static PRS, a CSS or CORESET for paging, a system information update, a WUS or group common power control, a non-CD SSB, a resynchronization reference signal indicating a system information update for UE synchronization in DRX mode, or an L3 intra-frequency measurement gap if an SSB is not transmitted in the active downlink BWP.

[0214] In aspect 50, the method of aspect 49 further includes the configuration being transmitted in system information that is dedicated to UEs having the first capability.

[0215] In aspect 51, the method of aspect 49 further includes the configuration being transmitted to the UE in RRC signaling.

[0216] In example 52, the method of any of examples 42-48 further includes: configuring the active downlink BWP or the active uplink BWP based on a rule or a lookup table.

[0217] In example 53, any of the methods of examples 42 to 52 further includes receiving capability signaling indicating that the UE has a first capability, and after receiving the capability signaling, the base station switches to an active downlink BWP and an active uplink BWP based on at least one of a MAC-CE, an RRC reconfiguration, a DCI, or a timer configured in the system information for the UE having the first capability.

[0218] In aspect 54, the method of aspect 42 further includes, the initial access being based in part on a first initial downlink BWP shared between a UE having the first capability and a UE having the second capability, and in part on a second initial downlink BWP that is dedicated to the UE having the first capability.

[0219] In example 55, the method of example 42 or 54 further includes the initial access being further based on an initial uplink BWP that is dedicated to UEs having the first capability.

[0220] In aspect 56, the method of either aspect 54 or 55 further includes that performing the initial access includes receiving a random access preamble from the UE in an RO having an SSB-to-RO mapping for the UE having the first capability that is different from that for the UE having the second capability.

[0221] In example 57, the method of example 56 further includes that the SSB to RO mapping for the UE having the first capability is based on a non-CD SSB.

[0222] In aspect 58, the method of aspect 57 further includes that the one or more parameters for the non-CD SSB may be the same parameters as those for the CD-SSB, the one or more parameters including at least one of periodicity, block index, spatial reference for the random access procedure, power offset, center frequency, or numerology.

[0223] In aspect 59, the method of aspect 57 further includes one or more parameters for the non-CD SSB being configured independently from the CD-SSB, the one or more parameters including at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology.

[0224] In example 60, the method of any of examples 57-59 further includes the one or more parameters being from at least one of system information, a broadcast physical downlink control channel, a lookup table, or a rule.

[0225] In example 61, the method of any of examples 57 to 59 further includes the non-CD SSB being configured in at least one of the second initial downlink BWP or the active downlink BWP and being common to measurements by the first capability UE and the second capability UE.

[0226] In example 62, the method of any of examples 54 to 61 further includes at least one of the second initial downlink BWP or the active downlink BWP overlapping in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP.

[0227] In example 63, the method of any of examples 54 to 62 further includes the first initial downlink BWP including CORESET 0 and a CD-SSB configured for a UE having a first capability and a UE having a second capability, the first initial downlink BWP having a bandwidth at a center frequency of the carrier bandwidth, the bandwidth being less than or equal to a lower maximum UE bandwidth of the UE having the first capability, and the initial uplink BWP and the second initial downlink BWP being at edges of the carrier bandwidth.

[0228] In aspect 64, the method of any of aspects 54 to 63 further includes transmitting a first configuration of a second initial downlink BWP dedicated to a UE having the first capability, and transmitting a second configuration of an active downlink BWP.

[0229] In aspect 65, the method of aspect 64 further includes the first configuration of the second initial downlink BWP being transmitted in the first initial downlink BWP within a SIB dedicated to the first capability UE.

[0230] In aspect 66, the method of aspect 64 further includes the first configuration of the second initial downlink BWP being transmitted in the first initial downlink BWP as information dedicated to the first capability UE within a SIB carrying information for the first capability UE and the second capability UE.

[0231] In example 67, the method of any of examples 64 to 66 further includes: a first configuration of the second initial downlink BWP is transmitted in system information in CORESET 0, the system information being dedicated to the first capability UE.

[0232] In aspect 68, the method of aspect 64 further includes a second configuration of the active downlink BWP being transmitted in a second initial downlink BWP.

[0233] In example 69, the method of any of examples 42-63 further includes: configuring the second initial downlink BWP based on a lookup table or a rule.

[0234] In aspect 70, the method of aspect 42 further includes performing initial access based in part on a first initial downlink BWP shared between a UE having the first capability and a UE having the second capability, and based in part on a second initial downlink BWP that is dedicated to the UE having the first capability, the first initial downlink BWP including CORESET 0 and a cell CD-SSB configured for the UE having the first capability and the UE having the second capability.

[0235] In aspect 71, the method of aspect 70 further includes outputting for transmission a first configuration of a second initial downlink BWP dedicated to UEs having the first capability, the first configuration of the second initial downlink BWP being received in a SIB in the first initial downlink BWP carrying information for UEs of the first capability and UEs of the second capability, and the second initial downlink BWP dedicated to UEs having the first capability does not include CORESET 0 or CD-SSB.

[0236] In aspect 72, the method of aspect 70 or 71 further includes that performing the initial access includes obtaining a random access preamble during a RO in a second initial downlink BWP, the RO having an SSB-to-RO mapping to a CD-SSB in the first initial downlink BWP.

[0237] In aspect 73, the method of any of aspects 70 to 72 further includes outputting a configuration for a non-CD SSB for transmission in an active downlink BWP that is dedicated to a UE having the first capability, the non-CD SSB being for at least one of L1 measurements or L3 measurements for the UE having the first capability.

[0238] In example 74, the method of any of examples 70-73 further includes outputting the system information update for transmission in an RRC signaling in an active downlink BWP that is dedicated to the UE having the first capability.

[0239] Embodiment 75 is an apparatus for wireless communication in a network entity, the apparatus comprising a memory and at least one processor coupled to the memory, wherein based at least in part on information stored in the memory, the at least one processor is configured to perform a method as described in any of claims 42 to 74.

[0240] Aspect 76 is an apparatus for wireless communication in a network entity, the apparatus comprising means for performing a method according to any of claims 42 to 74.

[0241] In example 77, the apparatus of example 75 or 76 further includes at least one of an antenna or a transceiver.

[0242] Aspect 78 is a non-transitory computer readable medium storing computer executable code in a network entity, the code, when executed by a processor, causing the processor to perform a method according to any of claims 42-74.

[0243] Example 79 is a computer program product for wireless communication in a network entity, the computer program product including instructions that, when executed by a computer, cause the network entity to perform a method according to any of examples 42 to 74.

[0244] Aspect 80 is a computer program product for wireless communication in a UE, the computer program product comprising instructions which, when executed by a computer, cause the UE to perform a method according to any of claims 1-37.

[0245] Aspect 81 is an apparatus for wireless communication in a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, the apparatus comprising: a memory; and at least one processor coupled to the memory, wherein based at least in part on information stored in the memory, the at least one processor is configured to perform at least a portion of an initial access based on a first initial downlink BWP shared between the UE having the first capability and the UE having the second capability, and to switch after the initial access to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability.

[0246] In aspect 82, the apparatus of aspect 81 further includes the at least one processor being configured to perform the initial access based in part on a first initial downlink BWP shared between a UE having the first capability and a UE having the second capability, and based in part on a second initial downlink BWP that is dedicated to the UE having the first capability.

[0247] In aspect 83, the apparatus of aspect 82 further includes that the first initial downlink BWP includes CORESET 0 and a CD-SSB configured for a UE having the first capability and a UE having the second capability.

[0248] In aspect 84, the apparatus of aspect 82 or 83 further includes, at least one processor configured to receive a first configuration of a second initial downlink BWP dedicated to a UE having the first capability, the first configuration of the second initial downlink BWP being received in the first initial downlink BWP within a SIB carrying information regarding the UE having the first capability and the UE having the second capability.

[0249] In aspect 85, the apparatus of aspect 84 further includes that the second initial downlink BWP dedicated to the UE having the first capability does not include CORESET 0 or CD-SSB.

[0250] In example 86, the apparatus of any of examples 83 to 85 further includes, to perform initial access, at least one processor is configured to transmit a random access preamble during an RO in a second initial downlink BWP, the RO having an SSB-to-RO mapping to a CD-SSB in the first initial downlink BWP.

[0251] In aspect 87, the apparatus of any of aspects 81 to 86 further includes that the at least one processor is further configured to receive a configuration for a non-CD SSB in an active downlink BWP that is dedicated to the UE having the first capability.

[0252] In aspect 88, the apparatus of aspect 87 further includes that the at least one processor is further configured to perform at least one of L1 measurements or L3 measurements on a non-CD SSB in an active downlink BWP that is dedicated to the UE having the first capability.

[0253] In aspect 89, the apparatus of any of aspects 81 to 88 further includes that the at least one processor is further configured to receive a system information update in RRC signaling in an active downlink BWP dedicated to the UE having the first capability.

[0254] In aspect 90, the apparatus of any of aspects 82 to 89 further includes, to perform initial access, at least one processor is configured to transmit a random access preamble during an RO in a second initial downlink BWP, the RO having an SSB-to-RO mapping based on the non-CD SSB.

[0255] In example 91, the apparatus of any of examples 82 to 90 further includes, in a second initial downlink BWP or an active downlink BWP that is dedicated to a UE having the first capability, the one or more parameters for the non-CD SSB include the same parameters as for the CD-SSB, and the one or more parameters include at least one of a periodicity, a block index, a spatial reference for the random access procedure, a power offset, a center frequency, or a numerology.

[0256] In aspect 92, the apparatus of aspect 91 further includes that the non-CD SSB is configured in at least one of the second initial downlink BWP or the active downlink BWP and is common to measurements by a UE having the first capability and a UE having the second capability.

[0257] In aspect 93, the apparatus of aspect 91 or 92 further includes at least one of the second initial downlink BWP or the active downlink BWP overlapping in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP.

[0258] In aspect 94, the apparatus of aspect 82 further includes: the first initial downlink BWP has a bandwidth at a center frequency of the carrier bandwidth, the bandwidth being less than or equal to a lower maximum UE bandwidth of the UE having the first capability; and the initial uplink BWP and the second initial downlink BWP are at edges of the carrier bandwidth.

[0259] In aspect 95, the aspect 82 apparatus further includes receiving a first configuration of a second initial downlink BWP dedicated to a UE having the first capability, and receiving a second configuration of an active downlink BWP in the second initial downlink BWP.

[0260] In aspect 96, the apparatus of aspect 95 further includes the first configuration of the second initial downlink BWP being received in one of a SIB in the first initial downlink BWP dedicated to the UE having the first capability, or system information in CORESET 0 dedicated to the UE having the first capability.

[0261] In aspect 97, the apparatus of aspect 82 further includes, wherein the configuration of the second initial downlink BWP is based on a lookup table or a rule.

[0262] In aspect 98, the apparatus of aspect 81 further includes, wherein the at least one processor is configured to perform initial access based on a first initial downlink BWP and an initial uplink BWP shared between a UE having a first capability and a UE having a second capability, and to switch to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability after the initial access, wherein the BWP switching of the UE is configured for a TDD mode, a FD-FDD mode, a HD-FDD mode, the first initial downlink BWP includes CORESET 0 or CD-SSB configured for the UE having the first capability and the UE having the second capability, the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the first bandwidth of the first initial downlink BWP and the second bandwidth of the initial uplink BWP are less than or equal to a lower maximum UE bandwidth of the UE having the first capability and the second capability.

[0263] In aspect 99, the apparatus of aspect 98 further includes the at least one processor being further configured to receive system information or a system information update in a first initial downlink BWP, where the system information is included in a first SIB dedicated to UEs having the first capability, or receive system information or a system information update in the first initial downlink BWP, where the system information includes separate information dedicated to UEs having the first capability in a second SIB carrying separate information for UEs having the first capability and additional information for UEs having the second capability.

[0264] In aspect 100, the apparatus of aspect 98 or 99 further includes, to perform initial access, the at least one processor is configured to transmit a random access preamble in a first RO having a first SSB-to-RO mapping based on CD-SSB, or transmit a random access preamble in a second RO having a second SSB-to-RO mapping or SSB-to-preamble mapping configured for a UE having the first capability.

[0265] In aspect 101, the apparatus of aspect 81 further includes, wherein the at least one processor is further configured to receive configurations for an active downlink BWP and an active uplink BWP, the configurations for the active downlink BWP including one or more of: periodic or semi-static TRS, periodic or semi-static CSI-RS, periodic or semi-static PRS, CSS or CORESET for paging, system information update, WUS or group common power control, non-CD SSB, additional CORESET or additional CSS for system information update, for UE synchronization in DRX mode, a resynchronization reference signal indicating a system information update, or an L3 intra-frequency measurement gap if SSB is not transmitted in the active downlink BWP.

[0266] In aspect 102, the apparatus of aspect 101 further includes the configuration being included in system information dedicated to the UE having the first capability or in RRC signaling for the UE.

[0267] In aspect 103, the apparatus of aspect 81 further includes, wherein the configuration of the active downlink BWP or the active uplink BWP is based on a rule or a lookup table.

[0268] In aspect 104, the apparatus of any of aspects 81 to 103 further includes, at least one processor configured to perform a capability signaling procedure indicating that the UE has a first capability, and the at least one processor configured to switch to an active downlink BWP and an active uplink BWP after completing the capability signaling procedure based on at least one of a MAC-CE, an RRC reconfiguration, a DCI, or a timer configured in system information for the UE having the first capability.

[0269] Aspect 105 is an apparatus for wireless communication in a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory, wherein based at least in part on information stored in the memory, the at least one processor is configured to: perform an initial access with a UE having a first capability associated with a lower maximum UE bandwidth than a second capability, where at least a portion of the initial access is based on a first initial downlink BWP shared between the UE having the first capability and the UE having the second capability; and after the initial access, switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability for communication with the UE.

[0270] In aspect 106, the apparatus of aspect 105 further includes, wherein the at least one processor is configured to perform the initial access based in part on a first initial downlink BWP shared between a UE having the first capability and a UE having the second capability, and based in part on a second initial downlink BWP that is dedicated to the UE having the first capability, the first initial downlink BWP including CORESET 0 and a cell CD-SSB configured for the UE having the first capability and the UE having the second capability.

[0271] In aspect 107, the apparatus of aspect 106 further includes outputting for transmission a first configuration of a second initial downlink BWP dedicated to UEs having the first capability, the first configuration of the second initial downlink BWP being received in a SIB in the first initial downlink BWP carrying information for UEs having the first capability and UEs of the second capability, and the second initial downlink BWP dedicated to UEs having the first capability does not include CORESET 0 or CD-SSB.

[0272] In aspect 108, the apparatus of any of aspects 105 to 107 further includes, to perform initial access, at least one processor is configured to obtain a random access preamble during a RO in the second initial downlink BWP, the RO having an SSB-to-RO mapping to a CD-SSB in the first initial downlink BWP.

[0273] In aspect 109, the apparatus of any of aspects 105 to 108 further includes the at least one processor being further configured to output a configuration for a non-CD SSB for transmission in an active downlink BWP dedicated to a UE having the first capability, the non-CD SSB being for at least one of L1 measurements or L3 measurements for the UE having the first capability.

[0274] In aspect 110, the apparatus of any of aspects 105 to 109 further includes that the at least one processor is further configured to output a system information update for transmission in an RRC signaling in an active downlink BWP that is dedicated to the UE having the first capability.

Claims

1. 1. An apparatus for wireless communication in a user equipment (UE) having a first capability associated with a maximum UE bandwidth that is lower than a second capability, comprising: Memory and at least one processor coupled to the memory, wherein based at least in part on information stored in the memory, the at least one processor: performing initial access at least in part based on a first initial downlink bandwidth portion (BWP) shared between the UE having the first capability and the UE having the second capability; The apparatus is configured to switch, after the initial access, to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability.

2. 2. The apparatus of claim 1, wherein the at least one processor is configured to perform the initial access based in part on the first initial downlink BWP shared between the UE having the first capability and the UE having the second capability, and based in part on a second initial downlink BWP that is dedicated to the UE having the first capability.

3. 3. The apparatus of claim 2, wherein the first initial downlink BWP includes a control resource set 0 (CORESET 0) and a cell-defined synchronization signal block (CD-SSB) configured for the UE having the first capability and the UE having the second capability.

4. the at least one processor:

4. The apparatus of claim 3, further configured to receive a first configuration of the second initial downlink BWP dedicated to the UE having the first capability, wherein the first configuration of the second initial downlink BWP is received within the first initial downlink BWP in a system information block (SIB) that carries information for the UE having the first capability and the UE having the second capability.

5. The apparatus of claim 4 , wherein the second initial downlink BWP dedicated to the UE having the first capability does not include the CORESET 0 or the CD-SSB.

6. the at least one processor: further configured to receive a configuration for non-cell defined SSB (non-CD SSB) in the active downlink BWP dedicated to the UE having the first capability; The at least one processor further comprises: and further configured to perform at least one of Layer 1 (L1) measurements or Layer 3 (L3) measurements on the non-CD SSB in the active downlink BWP dedicated to the UE having the first capability.

3. The apparatus of claim 2.

7. the at least one processor:

3. The apparatus of claim 2, further configured to receive system information updates in Radio Resource Control (RRC) signaling in the active downlink BWP dedicated to the UE having the first capability.

8. One or more parameters for a non-cell-defined SSB (non-CD SSB) in the second initial downlink BWP or the active downlink BWP, which is dedicated to the UE having the first capability, include the same parameters as for a CD-SSB, and the one or more parameters include: periodicity, Block Index, spatial criteria for random access procedures, Power Offset Center frequency, or Numerology The apparatus of claim 2 , comprising at least one of:

9. 9. The apparatus of claim 8, wherein the non-CD SSB is configured in at least one of the second initial downlink BWP or the active downlink BWP and is common to measurements by the UE having the first capability and the UE having the second capability.

10. 9. The apparatus of claim 8, wherein at least one of the second initial downlink BWP or the active downlink BWP overlaps in frequency with the CD-SSB or control resource set 0 (CORESET 0) of the first initial downlink BWP.

11. the first initial downlink BWP has a bandwidth at a center frequency of a carrier bandwidth, the bandwidth being less than or equal to the lower maximum UE bandwidth of the UE having the first capability; The apparatus of claim 2 , wherein the initial uplink BWP and the second initial downlink BWP are at edges of the carrier bandwidth.

12. the at least one processor: receiving a first configuration of the second initial downlink BWP dedicated to the UE having the first capability; and further configured to receive, in the second initial downlink BWP, a second configuration of the active downlink BWP; the first configuration of the second initial downlink BWP, a System Information Block (SIB) in the first initial downlink BWP that is dedicated to the UE having the first capability; or received in one of the pieces of system information dedicated to the UE having the first capability in control resource set 0 (CORESET 0); 3. The apparatus of claim 2.

13. The apparatus of claim 2 , wherein the configuration of the second initial downlink BWP is based on a look-up table or a rule.

14. the at least one processor is configured to perform the initial access based on the first initial downlink BWP and an initial uplink BWP shared between the UE having the first capability and the UE having the second capability, and to switch to the active downlink BWP and the active uplink BWP dedicated to the UE having the first capability after the initial access, wherein the BWP switching of the UE is configured for a time division duplex (TDD) mode, a full duplex frequency division duplex (FD-FDD) mode, or a half duplex frequency division duplex (HD-FDD) mode, and the first initial downlink BWP is based on a control resource set 0 (CORESET) configured for the UE having the first capability and the UE having the second capability. 0) or a cell-defined synchronization signal block (CD-SSB), wherein the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and a first bandwidth of the first initial downlink BWP and a second bandwidth of the initial uplink BWP are less than or equal to the lower maximum UE bandwidth of the UE having the first capability and the second capability; The at least one processor further comprises: receiving system information or a system information update in the first initial downlink BWP, the system information being included in a first System Information Block (SIB) dedicated to the UE having the first capability; or receiving the system information or the system information update in the first initial downlink BWP, wherein the system information includes separate information dedicated to the UEs having the first capability in a second SIB carrying separate information for the UEs having the first capability and additional information for the UEs having the second capability.

10. The apparatus of claim 1.

15. 1. An apparatus for wireless communication in a network entity, comprising: Memory and at least one processor coupled to the memory, wherein based at least in part on information stored in the memory, the at least one processor: conducting initial access with a user equipment (UE) having a first capability associated with a maximum UE bandwidth lower than a second capability, the initial access being based at least in part on a first initial downlink bandwidth portion (BWP) shared between a UE having the first capability and a UE having the second capability; switching to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability for communication with the UE after the initial access; The apparatus is configured to:

Images