CN117813903A - BWP configuration for UEs with different capabilities - Google Patents

Abstract

A User Equipment (UE) having a first capability is to perform 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 a UE having a second capability, the first capability being associated with a lower maximum UE bandwidth than the second capability. After the initial access, the UE switches to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability to perform random access, paging, system acquisition, measurement and data communication procedures.

Description

BWP configuration for UEs with different capabilities

Cross Reference to Related Applications

The present application claims the benefit and priority of U.S. provisional application Ser. No. 63/234,674, entitled "BWP Configurations for UEs Having Different Capabilities", filed 8/18 of 2021, and U.S. non-provisional patent application Ser. No. 17/871,879, entitled "BWP CONFIGURATIONS FOR UES HAVING DIFFERENT CAPABILITES", filed 22 of 2022, the disclosures of which are expressly incorporated herein by reference in their entireties.

Technical Field

The present disclosure relates generally to communication systems, and more particularly, to bandwidth part (BWP) based wireless communication.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources. Examples of such multiple-access techniques 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.

These multiple access techniques have been employed in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example of a telecommunications standard is 5G new air interface (NR). The 5G NR is part of the ongoing mobile broadband evolution promulgated by the third generation partnership project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the internet of things (IoT)) and other requirements. The 5G NR includes services associated with enhanced mobile broadband (emmbb), large-scale machine type communication (emtc), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements in the 5G NR technology are needed. Furthermore, these improvements are applicable to other multiple access techniques and telecommunication standards employing these techniques.

Disclosure of Invention

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. This summary neither identifies key or critical elements of all aspects nor delineates 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.

Wireless communications may support reduced capability devices in addition to higher capability devices. In some examples, a reduced capability UE may have reduced transmission or reception bandwidth compared to other UEs. Aspects presented herein provide configuration and signaling support for reduced capability UEs that enable joint optimization of DL/UL BWP configuration, coexistence of different UE capabilities, power saving for reduced capability UEs, mitigation of resource fragmentation on DL/UL, and/or signaling overhead reduction.

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

In one aspect of the disclosure, methods, computer-readable media, and apparatuses are provided for wireless communication at a User Equipment (UE) having a first capability associated with a lower maximum UE bandwidth 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 a first-capable UE and a second-capable UE. After the initial access, the apparatus switches to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability.

In another aspect of the disclosure, methods, computer-readable media, and apparatuses for wireless communication at a network entity are provided. The apparatus performs an initial access with a UE having a first capability associated with a lower maximum UE bandwidth than a second capability, at least a portion of the initial access being based on an initial downlink BWP shared between the UE having the first capability and the UE having the second capability. For communication with the UE, the apparatus switches to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability.

To the accomplishment of the foregoing and related ends, 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 various aspects may be employed and the present specification is intended to include all such aspects and their equivalents.

Drawings

Fig. 1 is a diagram illustrating an example of a wireless communication system and access network in accordance with various aspects presented herein.

Fig. 2A is a diagram illustrating an example of a first frame in accordance with aspects of the present disclosure.

Fig. 2B is a diagram illustrating an example of DL channels within a subframe according to aspects of the present disclosure.

Fig. 2C is a diagram illustrating an example of a second frame in accordance with aspects of the present disclosure.

Fig. 2D is a diagram illustrating an example of UL channels within a subframe in accordance with various aspects of the disclosure.

Fig. 3 is a diagram illustrating an example of a base station and a User Equipment (UE) in an access network in accordance with various aspects presented herein.

Fig. 4 is an example resource diagram illustrating an example bandwidth portion (BWP) within a carrier bandwidth in accordance with various aspects presented herein.

Fig. 5A illustrates an example of Downlink (DL) BWP and Uplink (UL) BWP in carrier bandwidth according to various aspects presented herein.

Fig. 5B illustrates a time diagram showing a guard period for switching between UL BWP and DL BWP according to various aspects presented herein.

Fig. 6 illustrates example aspects of BWP for reduced capability UEs including shared initial DL BWP according to various aspects presented herein.

Fig. 7 illustrates example aspects of BWP for reduced capability UEs including shared initial DL BWP according to various aspects presented herein.

Fig. 8 illustrates example aspects of BWP for reduced capability UEs including shared initial DL BWP according to various aspects presented herein.

Fig. 9 is an example communication flow between a UE and a base station that includes using shared initial DL BWP and dedicated active DL BWP for reduced capability UEs in accordance with various aspects presented herein.

Fig. 10 illustrates example aspects of BWP for reduced capability UEs including shared initial DL BWP and dedicated initial DL BWP according to various aspects presented herein.

Fig. 11 is an example communication flow between a UE and a base station that includes using shared initial DL BWP and dedicated initial DL BWP for reduced capability UEs in accordance with various aspects presented herein.

Fig. 12 illustrates example aspects of BWP for reduced capability UEs including shared initial DL BWP and dedicated initial DL BWP according to various aspects presented herein.

Fig. 13 is a flow chart of a method of wireless communication at a UE in accordance with various aspects presented herein.

Fig. 14 is a flow chart of a method of wireless communication at a UE in accordance with various aspects presented herein.

Fig. 15 is a diagram illustrating an example of a hardware implementation for an example apparatus in accordance with various aspects presented herein.

Fig. 16 is a flow chart of a method of wireless communication at a network entity in accordance with various aspects presented herein.

Fig. 17 is a flow chart of a method of wireless communication at a network entity in accordance with various aspects presented herein.

Fig. 18 is a diagram illustrating an example of a hardware implementation for an example network entity in accordance with various aspects presented herein.

Fig. 19 is a diagram illustrating an example exploded base station architecture in accordance with various aspects presented herein.

Detailed Description

Wireless communications may support reduced capability devices in addition to higher capability devices. In some examples, a reduced capability UE may have a reduced transmission bandwidth or reception bandwidth compared to other UEs. Aspects presented herein provide configuration and signaling support for reduced capability UEs that enable joint optimization of DL/UL BWP configuration, coexistence of different UE capabilities, power saving for reduced capability UEs, mitigation of resource fragmentation on DL/UL, and/or signaling overhead reduction. In some aspects, UEs with different levels of capabilities (such as reduced capability UEs and non-reduced capability (or higher capability) UEs) may share initial DL BWP and CORESET 0 for initial access. For example, the UE may monitor resources of CORESET 0 to receive system information that enables the UE to perform initial access. In some aspects, for example, shared CORESET 0 and shared System Information Blocks (SIBs) may carry information for UEs with greater bandwidth capabilities and UEs with reduced bandwidth capabilities. In some aspects, separate initial BWP may be provided for UEs with reduced bandwidth, e.g., dedicated initial downlink BWP and/or dedicated initial uplink BWP. In some aspects, the reduced capability UE may transmit a random access message, such as a random access preamble, using a dedicated initial BWP. Aspects presented herein may provide for configuration of BWP for and after initial access that supports reduced bandwidth according to reduced capability UEs, while maintaining flexibility in configuring bandwidth for higher capability UEs.

The various configurations are described below in connection with the detailed description set forth in the drawings, and are 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, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts.

Aspects of a telecommunications system are also presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and are 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 upon the particular application and design constraints imposed on the overall system.

As an example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" that includes 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, system on a chip (SoC), baseband processors, field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system may execute the software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Thus, in one or more example aspects, implementations, and/or use cases, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or code. Computer readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can 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 these 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.

Although aspects, implementations, and/or examples are described herein by way of illustration of some examples, additional or different aspects, implementations, and/or examples may be produced in many different arrangements 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 arrangements. For example, implementations and/or uses may be generated via integrated chip implementations and other non-module component-based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail/procurement devices, medical devices, artificial Intelligence (AI) -enabled devices, etc.). While some examples may or may not be specific to each use case or application, broad applicability of the described aspects may occur. Aspects, implementations, and/or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregate, distributed, or Original Equipment Manufacturer (OEM) devices or systems incorporating one or more aspects of the techniques herein. In some practical environments, a device incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes a plurality of 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 may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disassembled components, end-user devices, and the like, of various sizes, shapes, and configurations.

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network 100. A wireless communication system, also referred to as a Wireless Wide Area Network (WWAN), includes a base station 102, a UE 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G core (5 GC)). Base station 102 may include a macrocell (high power cellular base station) and/or a small cell (low power cellular base station). The macrocell includes a base station. Small cells include femto cells, pico cells, and micro cells.

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

The base station 102 or 180 may include a BWP component 199 configured to perform an initial access with the UE 104 having a first capability associated with a lower maximum UE bandwidth than a second capability, at least a portion of the initial access being 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 also be configured to switch to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability for communication with the UE 104. Although the following description may focus on 5 GNRs, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

A base station 102 configured for 4G LTE, which is collectively referred to as evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), may interface with EPC 160 through a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR, which is collectively referred to as a next generation RAN (NG-RAN), may interface with a core network 190 through a second backhaul link 184. Among other functions, the base station 102 may perform one or more of the following functions: user data transfer, radio channel encryption and decryption, integrity protection, header compression, mobile control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio Access Network (RAN) sharing, multimedia Broadcast Multicast Services (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) over 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.

The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the 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 comprising both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved node B (eNB) (HeNB), which may provide services to a restricted group known as a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the UE 104 may include Uplink (UL) (also referred to as a reverse link) transmissions from the UE 104 to the base station 102 and/or Downlink (DL) (also referred to as a forward link) transmissions from the base station 102 to the UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques including spatial multiplexing, beamforming, and/or transmission diversity. The communication link may be through one or more carriers. For each carrier allocated in carrier aggregation up to yxmhz (x component carriers) in total for transmission in each direction, the base station 102/UE 104 may use a spectrum up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than 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).

Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more side link channels such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems such as, for example, wiMedia, bluetooth, zigBee, wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communication system may also include a Wi-Fi Access Point (AP) 150 that communicates with Wi-Fi Stations (STAs) 152 via a communication link 154, e.g., in the 5GHz unlicensed spectrum or the like. When communicating in the unlicensed spectrum, STA 152/AP 150 may perform Clear Channel Assessment (CCA) prior to communication to determine whether a channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5GHz, etc.) as used by the Wi-Fi AP 150. Small cells 102' employing NR in the unlicensed spectrum may improve access network coverage and/or increase access network capacity.

The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5GNR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6GHz, FR1 is commonly referred to as (interchangeably) the "below 6GHz" band in various documents and articles. With respect to FR2, a similar naming problem sometimes occurs, which is commonly (interchangeably) referred to in documents and articles as the "millimeter wave" band, although it differs from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics and may therefore effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above, unless specifically stated otherwise, it should be understood that if the term "below 6GHz" or the like is used herein, it may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that if the term "millimeter wave" or the like is used herein, it may be broadly meant to include mid-band frequencies, frequencies that may be within FR2, FR4-a or FR4-1 and/or FR5, or may be within the EHF band.

Base station 102, whether small cell 102' or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, a gndeb (gNB), or another type of base station. Some base stations (such as the gNB 180) may operate in the traditional below 6GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. Millimeter-wave base station 180 may compensate for path loss and short range using beamforming 182 with UE 104. 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.

The base station 180 may transmit the beamformed signals to the UEs 104 in one or more transmission directions 182'. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 182 ". The UE 104 may also transmit the beamformed signals to the base station 180 in one or more transmission directions. The base station 180 may receive the beamformed signals from the UEs 104 in one or more receive directions. The base stations 180/UEs 104 may perform beam training to determine the best receive direction and transmit direction for each of the base stations 180/UEs 104. The transmission and reception directions of the base station 180 may be the same or different. The transmission and reception directions of the UE 104 may be the same or different.

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.MME 162 may communicate 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, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are communicated through the serving gateway 166, which itself is 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 BM-SC 170 are connected to an IP service 176.IP services 176 may include the internet, intranets, 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 a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to allocate MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and collecting eMBMS related charging information.

The core network 190 may include access and mobility management functions (AMFs) 192, other AMFs 193, session Management Functions (SMFs) 194, and User Plane Functions (UPFs) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node for handling signaling between the UE 104 and the core network 190. In general, AMF 192 provides QoS flows and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. The UPF 195 provides UE IP address assignment as well as other functions. The UPF 195 is connected to an IP service 197.IP services 197 may include internet, intranet, IP Multimedia Subsystem (IMS), packet Switched (PS) streaming (PSs) services, and/or other IP services.

A base station may include and/or be referred to as a gNB, a node B, eNB, an access point, a base station transceiver, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a transmit-receive 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 UEs 104 include a cellular telephone, a smart phone, 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 electricity meter, an air pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similarly functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network in common and/or individually.

Deployment of a communication system, such as a 5G new air interface (NR) system, may be arranged with various components or parts in a number of ways. In a 5G NR system or network, a network node, network entity, mobility element of a network, radio Access Network (RAN) node, core network node, network element, or network equipment, such as a Base Station (BS), or one or more units (or one or more components) performing base station functionality may be implemented in an aggregated or decomposed architecture.

The aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. The split 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 central or Centralized Units (CUs), one or more Distributed Units (DUs), or one or more Radio Units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as virtual units, i.e., virtual Central Units (VCUs), virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs).

Base station type operation or network design may take into account the aggregate nature of the base station functionality. For example, the split base station may be used in an Integrated Access Backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration advocated by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). The decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Each element of the split base station or split RAN architecture may be configured for wired or wireless communication with at least one other element.

Fig. 19 shows a diagram illustrating an example split base station 1900 architecture. The split base station 1900 architecture may include one or more Central Units (CUs) 1910 that may communicate directly with the core network 1920 via a backhaul link, or indirectly with the core network 1920 through one or more split 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. CU 1910 can communicate with one or more Distributed Units (DUs) 1930 via a respective medium range link, such as an F1 interface. The DUs 1930 may communicate with one or more Radio Units (RUs) 1940 via respective forward links. RU 1940 may communicate with respective UEs 104 via one or more Radio Frequency (RF) access links. In some implementations, the UE 104 may be served simultaneously by multiple RUs 1940.

Each of the units (i.e., CU 1910, DU 1930, RU 1940, and near RT RIC 1925, non-RT RIC 1915, and SMO framework 1905) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via wired or wireless transmission media. Each of the units or an associated processor or controller providing instructions to a communication interface of the units may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a Radio Frequency (RF) transceiver) configured to receive or transmit signals to one or more of the other units over a wireless transmission medium, or both.

In some aspects, 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 CU 1910. CU 1910 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 1910 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bi-directionally with the CU-CP unit via an interface, such as an E1 interface. CU 1910 can be implemented to communicate with DU 1930 for network control and signaling as needed.

The DU 1930 may correspond to a logic 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 high 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 functional splits, such as those defined by the 3 rd generation partnership project (3 GPP). In some aspects, the DU 1930 may also 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 control functions hosted by the CU 1910.

The lower layer functionality may be implemented by one or more RUs 1940. In some deployments, RU 1940 controlled by DU 1930 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transforms (FFTs), inverse FFTs (iffts), digital beamforming, physical Random Access Channel (PRACH) extraction and filtering, etc.) or both based at least in part on a functional split (such as a lower layer functional split). In such an architecture, RU 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 communication with the control plane and user plane of RU 1940 can be controlled by a corresponding DU 1930. In some scenarios, this configuration may enable DUs 1930 and CUs 1910 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

SMO framework 1905 may be configured to support RAN deployment and deployment of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, SMO framework 1905 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via operation and maintenance interfaces (such as O1 interfaces). For virtualized network elements, 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, CU 1910, DU 1930, RU 1940, and near RT RIC 1925. In some implementations, SMO framework 1905 may communicate with hardware aspects of the 4G RAN, such as open eNB (O-eNB) 1911, via an O1 interface. Additionally, in some implementations SMO framework 1905 can communicate directly with one or more RUs 1940 via an O1 interface. SMO framework 1905 may also include a non-RT RIC 1915 configured to support the functionality of SMO framework 1905.

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 updating, or policy-based guidance of applications/features in the near-RT RIC 1925. The non-RT RIC 1915 may be coupled to or in communication with a near-RT RIC 1925 (such as via an A1 interface). The near RT RIC 1925 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 1910, one or more DUs 1930, or both, and an O-eNB with the near RT RIC 1925.

In some implementations, to generate the AI/ML model to be deployed in the near RT RIC 1925, the non-RT RIC 1915 may receive parameters or external enrichment information from an external server. Such information may be utilized by near RT RIC 1925 and may be received at SMO framework 1905 or non-RT RIC 1915 from a non-network data source or from a network function. In some examples, the non-RT RIC 1915 or near-RT RIC 1925 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 1915 may monitor long-term trends and patterns of performance and employ AI/ML models to perform corrective actions through SMO framework 1905 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

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

Fig. 2A-2D illustrate frame structures, and aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and/or different channels. One frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. The subframe may also include a micro slot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the Cyclic Prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The 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 known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on CP and parameter set (numerology). The parameter set defines a subcarrier spacing (SCS) and effectively defines a symbol length/duration that is equal to 1/SCS.

For normal CP (14 symbols/slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8 and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols/slot and 2 ^μ Each slot/subframe. The subcarrier spacing may be equal to 2 ^μ *15kHz, where μ is the parameter set 0 to 4. Thus, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length/duration is inversely related to the subcarrier spacing. Fig. 2A to 2D provide examples of a normal CP having 14 symbols per slot and a parameter set μ=2 having 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67 mus. Within the frame set, there may be one or more different bandwidth portions (BWP) of the frequency division multiplexing (see fig. 2B). Each BWP may have a specialA fixed parameter set and CP (normal or extended).

The resource grid may be used to represent a frame structure. Each slot includes Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)) that extend for 12 consecutive subcarriers. The resource grid is divided into a plurality of Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As illustrated in fig. 2A, some of the REs carry a reference (pilot) signal (RS) for the UE. The RSs may include demodulation RSs (DM-RSs) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs may also include beam measurement RSs (BRSs), beam Refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

Fig. 2B illustrates an example of various DL channels within a subframe of a frame. A Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in one OFDM symbol of an RB. The PDCCH within one BWP may be referred to as a control resource set (CORESET). The 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 occasion on CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. The additional BWP may be located at a higher and/or lower frequency on the channel bandwidth. The Primary Synchronization Signal (PSS) may be within 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. The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine a Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. A Physical Broadcast Channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS)/PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and a System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) that are not transmitted over the PBCH, and paging messages.

As illustrated in fig. 2C, some REs carry DM-RS (denoted 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 a Physical Uplink Control Channel (PUCCH) and DM-RS for a Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS may be transmitted in the previous or the previous two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations according to whether the short PUCCH or the long PUCCH is transmitted and according to a specific PUCCH format used. The UE may transmit a Sounding Reference Signal (SRS). The SRS may be transmitted in the last symbol of the 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 of the UL.

Fig. 2D illustrates examples of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries Uplink Control Information (UCI) such as a scheduling request, a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), and hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and/or Negative ACKs (NACKs)). PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSR), power Headroom Reports (PHR), and/or UCI.

Fig. 3 is a block diagram of a base station 310 in an access network in communication with a UE 350. In DL, IP packets may be provided to controller/processor 375. 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. Controller/processor 375 provides RRC layer functionality associated with broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection setup, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification) and handover support functions; RLC layer functionality associated with transmission of upper layer Packet Data Units (PDUs), error correction by ARQ, concatenation of RLC Service Data Units (SDUs), segmentation and reassembly, re-segmentation of RLC data PDUs and re-ordering 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), de-multiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, prioritization and logical channel prioritization.

Transmit (TX) processor 316 and Receive (RX) processor 370 implement layer 1 functionality associated with a variety of signal processing functions. Layer 1, which includes the Physical (PHY) layer, may include error detection on the transport channel, forward Error Correction (FEC) decoding/decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation/demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the 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 decoded 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 the individual streams combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel for carrying the time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to produce a plurality of spatial streams. The channel estimates from channel estimator 374 may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate may be derived from reference signals 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 318 Tx. Each transmitter 318Tx may modulate a Radio Frequency (RF) carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (Rx) processor 356.TX processor 368 and RX processor 356 implement layer 1 functionality associated with various signal processing functions. RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for UE 350. If multiple spatial streams are destined for UE 350, they may be combined into a single OFDM symbol stream by RX processor 356. 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 signal constellation points most likely to be transmitted by the base station 310. These soft decisions may be based on channel estimates computed by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to a controller/processor 359 for implementing layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. Memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, 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.

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., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression/decompression and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with upper layer PDU delivery, error correction by ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling and logical channel prioritization.

TX processor 368 can use channel estimates derived from reference signals or feedback transmitted by base station 310 using channel estimator 358 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial streams generated by Tx processor 368 may be provided to different antenna 352 via separate transmitters 354 Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the Rx processor 370.

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

At least one of TX processor 368, RX processor 356, and controller/processor 359 may be configured to perform various aspects related to BWP component 198 of fig. 1.

At least one of TX processor 316, RX processor 370, and controller/processor 375 may be configured to perform various aspects related to BWP component 199 of fig. 1.

Wireless communications may support reduced capability devices in addition to higher capability devices. Examples of higher capability devices include, among other examples, high-end smart phones, internet of vehicles (V2X) devices, URLLC devices, eMBB devices, and the like. The reduced capability devices may include lower capability devices and mid-range devices and use cases. The reduced capability devices may include, among other examples, wearable devices, industrial Wireless Sensor Networks (IWSNs), surveillance cameras, low-end smart phones, and the like. Communication systems such as NR communication systems may support both higher-capability devices and reduced-capability devices. The reduced capability devices may be referred to as RedCap devices, NR lightweight devices, lower layer devices, etc. The reduced capability UEs may communicate based on various types of wireless communications. For example, the smart wearable device may transmit or receive communications based on a low power wide area network (LPWA)/mctc, the loose IoT device may transmit or receive communications based on URLLC, the sensor/camera may transmit or receive communications based on eMBB, and so on.

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

In another example, a reduced capability UE may have at least 10dB lower uplink transmission power than a higher capability UE. As another example, a reduced capability UE may have a reduced number of receive antennas compared to other UEs. For example, a UE with reduced capability may have only a single receive antenna and may experience a lower equivalent received signal-to-noise ratio (SNR) than a UE with higher capability that may have multiple antennas. A reduced capability UE may also have reduced computational complexity than other UEs.

It may be helpful to make the communication scalable and deployable in a more efficient and economical manner. For example, peak throughput, latency, and/or reliability requirements of reduced capability devices may be relaxed or reduced. In some examples, power consumption, complexity, reduction in production costs, and/or reduction in 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 acceptable time delay of an industrial wireless sensor may be up to 10ms or 5ms. The data rate may be lower and may include more uplink traffic than downlink traffic. As another example, the video surveillance device may have an acceptable latency of up to about 500 ms.

The carrier bandwidth may span a contiguous set of PRBs, for example, from a common resource block for a given parameter set on a given carrier. The base station may configure one or more bandwidth parts (BWP) having a smaller bandwidth span than the carrier bandwidth. One or more of the BWP may be configured for downlink communication and may be referred to as Downlink (DL) BWP. Fig. 4 illustrates a resource diagram 400 showing a plurality of BWP (e.g., BWP 1, BWP 2, and BWP 3) configured within a frequency span of a carrier bandwidth. One DL BWP may be active at a time, and in case of no measurement gap or BWP handover gap, it may not be desirable for the UE to receive PDSCH, PDCCH, CSI-RS or TRS outside the active BWP. Each DL BWP may include at least one control resource set (CORESET). In fig. 4, BWP may be DL BWP and is illustrated as having CORESET within BWP. In other examples, BWP may be UL BWP and may not include CORESET configuration. One or more of the BWP may be configured for uplink communication and may be referred to as Uplink (UL) BWP. For a UE, one UL BWP may be active at a time, and the UE may not transmit PUSCH or PUCCH outside the active BWP. The use of BWP may reduce bandwidth monitored by the UE and/or used for transmission, which may help the UE save battery power.

CORESET corresponds in time and frequency to the set of physical resources used by the UE to monitor PDCCH/DCI. Each CORESET includes one or more resource blocks in the frequency domain and one or more symbols in the time domain. For example, CORESET may include a plurality of RBs in the frequency domain, 1, 2, or 3 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), e.g., 6 REGs, one of which may correspond to one RB (e.g., 12 REs) during one OFDM symbol. REGs within CORESET may be numbered in ascending order in a time-prioritized manner, starting with 0 for the lowest numbered resource block in the first OFDM symbol and control resource set. The UE may be configured with multiple CORESETs, each CORESET associated with a CCE-to-REG mapping. The search space may include CCE sets, e.g., at different aggregation levels. For example, the search space may indicate a number of candidates to decode (e.g., in which the UE performs decoding). CORESET may include multiple search space sets.

Fig. 5A illustrates an example 500 in which DL BWP 504 within a TDD carrier bandwidth 502 configured for reduced capability UEs is misaligned with UL BWP 506 for reduced capability UEs. If DL BWP and UL BWP are not aligned, for example, at the center frequency, a guard period may be provided between downlink and uplink resources in order to enable the UE to switch between BWP. For example, at 508, the UE may change between downlink reception in DL BWP 504 and uplink transmission in UL BWP 506. Similarly, at 510, the UE may change between uplink transmission in UL BWP 506 and downlink reception in DL BWP 504.

Fig. 5B illustrates a time diagram 550 showing that a guard period 518 or time gap may be provided between downlink reception 512 in DL BWP (e.g., 504) and uplink transmission 514 in UL BWP (e.g., 506) to allow the UE to switch between BWP. Similarly, a guard period 520 may be provided between uplink transmission 514 in UL BWP (e.g., 506) and downlink reception 516 in DL BWP (e.g., 504). In some aspects, the guard period may be between 50 microseconds and 200 microseconds for the UE to re-tune between BWPs. In some aspects, timeline changes, such as type B half-duplex frequency division duplexing, may not be supported for reduced capability UEs. The guard period or time gap at each handoff between downlink communications (on DL BWP) and uplink communications (on UL BWP) may result in increased latency, reduced peak data rates of DL and/or UL, etc. in communications between the UE and the base station. Misalignment BWP for DL and UL communications may result in loss of channel reciprocity, increased UE complexity or power consumption, RF retuning, additional CSI measurement and reporting, additional collision handling procedures, additional restrictions on DL/UL handover locations, and/or coexistence challenges for multiplexing/scheduling of different UE types.

In some aspects, UEs with different levels of capabilities (such as reduced capability UEs and non-reduced capability (or higher capability) UEs) may share initial DL BWP and CORESET 0 for initial access. For example, the UE may monitor resources of CORESET 0 to receive system information that enables the UE to perform initial access. Cell definition SSB (CS-SSB) may be transmitted within a maximum bandwidth supported by a 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. For example, after performing initial access, the UE may be configured with a BWP different from the active DL BWP. For example, fig. 6 illustrates that a reduced capability UE may be configured with an active DL BWP 606 for a lower capability UE and a higher capability UE may be configured with an active DL BWP 608 for a higher capability UE.

In some aspects, the reduced capability UEs may be configured with separate initial DL BWP (e.g., which may be different from CORESET 0) instead of the shared initial DL BWP illustrated in fig. 6. In such examples, the non-cell-defined SSB (NCD-SSB) may be transmitted within an initial BWP configured for the reduced capability UE. The NCD-SSB may provide a quasi co-located (QCL) source or reference signal for the UE to determine parameters for use in monitoring and receiving one or more of random access msg2 (e.g., random Access Response (RAR)), random access msg4, or paging messages 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.).

After initial access for synchronization purposes, the UE continues to measure SSS or TRS of the serving cell, e.g., to maintain synchronization with the serving cell. To support cell-level mobility, the UE may measure SSBs of the serving cell and one or more neighboring cells. If the reduced capability UE is operating in an active DL BWP within the SSB, such as illustrated in fig. 6, where SSB resources are in the initial DL BWP 604 instead of the active DL BWP 606 and 608, the UE may be configured with an intra-frequency L3 measurement gap to enable the UE to switch from the active DL BWP 606 or 608 without the SSB to the initial DL BWP 610 in order to measure the SSB, e.g. if the SSB is not transmitted in the active downlink BWP, as shown in fig. 6. For example, the network may configure periodic measurement gaps for the UE via RRC signaling. When the 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 RSs, such as an initial DL BWP, for example. Periodic or semi-static TRS/CSI-RS/PRS may be transmitted within active DL BWP 606 and may be used for time/frequency tracking, L1 measurements for link maintenance, or as QCL source for paging, wake-up signal (WUS) monitoring, and reception, etc. In some aspects, RRM measurement relaxation 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 (e.g., due to measurement gaps), a load imbalance may occur over the frequency of the carrier bandwidth 602.

Aspects presented herein provide BWP including initial and active BWP that addresses 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 a base station in the same carrier bandwidth. In TDD operation, DL BWP and UL BWP of a reduced capability UE may be aligned or misaligned at a center frequency. For example, in some aspects, the center frequencies of DL BWP and UL BWP may be aligned. In other aspects, the center frequencies of DL BWP and UL BWP may not be aligned. Alignment of BWP at center frequency can enable TDD DL and UL communications without time gaps or guard periods to allow return between UL BWP and DL BWP. Misalignment of BWP at the center frequency may require TDD DL and UL communications to be configured with a time gap or guard period to allow frequency return between UL BWP and DL BWP. The uplink channels (e.g., PUCCH, PUSCH, PRACH and/or SRS) of the reduced capability UEs may be mapped to RBs at the carrier edge, which may reduce resource fragmentation. As an example, the first hop of the PUCCH may be at a first edge of the BWP and the second hop may be at a second edge of the BWP. In some aspects, the network may disable uplink channels or hopping of uplink signals, for example, during and/or after initial access. For example, frequency hopping may be disabled based on DCI, MAC-CE or System Information (SI) from the network.

In some aspects, BWP (such as DL BWP and/or 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 different BWP configurations may exist for UEs in RRC idle, RRC inactive and/or RRC connected states.

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

Fig. 7 illustrates an example 700 in which a reduced capability UE and a non-reduced capability UE 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., UEs of reduced capability and UEs of non-reduced capability) may share common CD-SSB 710, CORESET 0 (e.g., in initial DL BWP 704), and initial UL BWP 706. In initial UL BWP, frequency hopping of PUCCH and/or PUSCH may be disabled for reduced capability UEs. As illustrated at 708, PUCCH resources for reduced capability UEs may be provided at the frequency edge of the shared UL BWP 706.

After initial access, the reduced capability UE may operate in active DL BWP 714 and active UL BWP 712, e.g., for reduced capability UEs, but not for higher capability UEs. Active DL BWP 714 and active UL BWP 712 may be referred to as dedicated to reduced capability UEs. The active DL BWP 714 for the reduced capability UE may include a configuration for periodic or semi-static TRSs and/or periodic CSI-RS and/or PRSs. The active DL BWP 714 for the reduced capability UE may include a configuration for Common Search Space (CSS) for the UE to monitor and receive WUS, paging and system information updates, and other downlink signals from the network. If no SSB is transmitted in the active DL BWP 714, an L3 intra-frequency measurement gap may be provided to enable the UE to switch to measurement of SSB in the initial DL BWP 704, as described in connection with fig. 6. As illustrated in fig. 7, the UE may receive an RRC message providing a System Information (SI) update to a lower capability UE in an active DL BWP 714.

During and after initial access, a reduced capability UE may not desire to operate in a DL BWP or UL BWP that is wider than its maximum UE bandwidth associated with the reduced capability. The reduced capability UEs may support different center frequencies for DL BWP and UL BWP. For example, in TDD operation, the UE may support different center frequencies for active DL BWP and active UL BWP with the same BWP identifier (e.g., which may be referred to as "BWP-id").

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

Fig. 9 illustrates an example communication flow 900 between a reduced capability UE 902 and a base station 904 based on initial DL BWP and UL BWP (e.g., as described in connection with fig. 7 and/or 8) shared between the reduced capability UE and a higher capability UE. The reduced capabilities of 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 in which the UE monitors downlink communications or transmits uplink communications and does not transmit and receive in overlapping times. At 906, the UE 902 may receive system information 906. The system information may be used for wireless communication with the base station 904 in a carrier bandwidth (e.g., 802 in fig. 8). The system information may indicate BWP as a subset of frequency resources of a carrier bandwidth for the UE to perform initial access. The system information may be specific to reduced capability UEs, e.g., including information applicable to reduced capability UEs but not to higher capability UEs. The UE 902 may receive the system information 906 in a separate SIB for the reduced capability UE than the SIB with the system information applicable to the higher capability UE. The UE 902 may receive system information 906 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, base station 904 may transmit a common or shared SIB in CORESET 0 shared by reduced capability UEs and higher capability UEs (e.g., in initial DL BWP 704 or 804).

At 908, UE 902 may perform an initial access procedure, such as a RACH procedure, in an initial DL BWP (e.g., shared initial DL BWP 704 or 804) and an initial UL BWP (e.g., shared initial UL BWP 706 or 806), which is common to reduced capability UEs and higher capability UEs. As part of the initial access, the UE 902 may transmit and receive random access messages 910 with the base station 904. As an example, in the shared initial DL BWP and the shared initial UL BWP, the UE may transmit random access Msg 1 with a preamble to the base station 904, may receive Msg 2 from the base station, may transmit Msg 3 to the base station, and/or may receive Msg 4 from the base station, e.g., as described in connection with fig. 7 or 8. At 910, the UE 902 may transmit a random access message, such as Msg 1, in a random access occasion based on the SSB-to-RO mapping for the reduced capability UE. 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 SSB-to-preamble mapping may be based on mapping patterns configured separately for reduced capability UEs. The separate configuration may be received in system information 906 in the shared initial DL BWP. Similar to UE 902, at 912, the base station may perform an initial access procedure with the UE 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.

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

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

An active DL BWP dedicated to the reduced capability UE (e.g., 714 or 814) may have an associated configuration for 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 CSS configured for the UE to monitor to receive pages 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 configured periodic TRSs and/or periodic CSI-RSs and/or Positioning RSs (PRSs). The active DL BWP may include a configured non-CD SSB. The active DL BWP may include a CSS and CORESET for configuration of system information update of the reduced capability UE. The active DL BWP may include a configured re-synchronization reference signal indicating system information update for the reduced capability UE.

As illustrated at 922, UE 902 may monitor and/or receive PDSCH, PDCCH, TRS, CSI-RS, PRS, or non-CD SSB in active DL BWP dedicated to reduced capability UEs. At 926, UE 902 may transmit PUSCH, PUCCH, and/or SRS in an active UL BWP for the reduced capability UE.

Fig. 10 illustrates an example 1000 in which a reduced capability UE and a non-reduced capability UE may share an initial DL BWP 1004 with a higher capability UE within a carrier bandwidth 1002 instead of an initial UL BWP 1006 that is instead configured for the higher capability UE instead of the reduced capability UE. This allows for greater flexibility in the configuration of the initial UL BWP 1006, which may have a greater bandwidth than supported by the reduced capability UE. The reduced capability UE may perform initial access using an initial UL BWP 1011 dedicated to the reduced capability UE. After initial access, the reduced capability UE may switch to active UL BWP 1012 and active DL BWP 1014, both 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 specific to the reduced capability UE to complete the initial access.

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

After initial access, the reduced capability UE may operate in active DL BWP 1014 and 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 the reduced capability UE may include a configuration for periodic or semi-static TRSs and/or periodic CSI-RSs. The active DL BWP 1014 for the reduced capability UE may include a configuration for the CSS for monitoring and receiving WUS, paging or system information updates and other downlink signals from the network. If SSB is not transmitted in the active DL BWP 1014, as shown in fig. 10, the L3 intra-frequency measurement gap in the case where SSB is not transmitted in the active downlink BWP enables the UE to switch to measurement of SSB (e.g., 1010) in the initial DL BWP 1004, as described in connection with fig. 6. As illustrated in fig. 10, the UE may receive an RRC message in the active DL BWP 1014 that provides SI update to the lower capability UE.

During and after initial access, a reduced capability UE may not desire to operate in a DL BWP or UL BWP that is wider than its maximum UE bandwidth associated with the reduced capability. The reduced capability UEs may support different center frequencies for DL BWP and UL BWP. For example, in TDD operation, the UE may support different center frequencies for active DL BWP and active UL BWP with the same BWP identifier (e.g., which may be referred to as "BWP-id"), e.g., as illustrated in the example in fig. 8.

The shared initial DL BWP 1004 may carry some information that enables the reduced capability UE to start accessing the network and provide information on dedicated initial BWP resources for the reduced capability UE. For example, a dedicated initial DL BWP for a reduced capability UE instead of a higher capability UE may carry system information dedicated to the reduced capability UE, and the system information may be different from the system information in DL BWP 1004 for the higher capability UE.

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 the reduced capability UE and a higher capability UE and a second initial DL BWP dedicated to the reduced capability UE, e.g., as described in connection with fig. 10. The reduced capabilities of UE 1102 may include a reduced operating bandwidth, or a lower maximum UE bandwidth that is smaller than the higher capability UE. The UE 1102 may operate based on TDD in which the UE monitors downlink communications or transmits uplink communications and does not transmit and receive in overlapping times. Both the initial BWP and the active BWP for the reduced capability UE may be configured separately by the network.

UE 1102 may receive system information 1105, for example, in a shared initial DL BWP. System information 1105 may be used to wirelessly communicate with base station 1104 in a carrier bandwidth (e.g., 1002 in fig. 10). System information 1105 may indicate BWP as a subset of frequency resources for the carrier bandwidth for the UE to perform initial access. The system information 1105 may be specific to a reduced capability UE, for example, including information applicable to reduced capability UEs but not to higher capability UEs. The UE 1102 may receive the system information 1105 in a separate SIB for the reduced capability UE than the SIB with the system information applicable to the higher capability UE. 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 that is shared by reduced capability UEs and higher capability UEs (e.g., in the initial DL BWP 1004).

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

At 1106, UE 1102 may switch to dedicated initial DL BWP and initial UL BWP (e.g., 1013 and 1011). UE 1102 may switch to performing at least a portion of initial access procedure 1108. Thus, base station 1104 can perform a similar handoff at 1107 to perform initial access and/or capability exchange at 1112.

At 1108, 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 are dedicated to the reduced capability UE. 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, in a dedicated initial DL BWP (e.g., 1013) and a dedicated initial UL BWP (e.g., 1011), the UE may transmit random access Msg1 with a preamble to the base station 904, may receive Msg 2 from the base station, may transmit Msg 3 to the base station, and/or may receive Msg 4 from the base station, e.g., as described in connection with fig. 10. In some aspects, dedicated Physical Random Access Channel (PRACH) resources 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 Msg 3/PUCCH within UL BWP supported by the UE. At 1110, the UE 1102 may transmit a random access message, such as Msg1, in a random access occasion (RO) based on the SSB-to-RO mapping for the reduced capability UE. The base station 1104 may configure the SSB-to-RO mapping pattern 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 the reduced capability UE may be a 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 the parameters for the CD-SSB, such as periodicity, block index, power offset, center frequency, parameter set, etc. The sharing parameters may be configured in conjunction with the CD-SSB or may be configured separately from the CD-SSB. Configurations for non-CD SSBs may be selected to help ensure measurement accuracy for UEs with reduced reception branches and/or reduced capability of antenna efficiency. If parameters of the non-CD SSB (e.g., periodicity, block index, power offset, center frequency, parameter set, etc.) are configured separately or differently from the CD-SSB, the parameters may be indicated to the reduced capability UE in various ways. As a first example, parameters of a non-CD SSB that underlie the SSB-to-RO mapping or SSB-to-preamble mapping may be configured in system information 1105 (e.g., in a separate SIB as compared to higher capability UEs, or in the same SIB but a different IE as compared to higher capability UEs). Parameters of the non-CD SSB may be configured in the broadcast PDCCH. The UE 1102 may determine one or more of the parameters of the non-CD SSB based on rules or a look-up table or based on information known to the UE. Parameters of the non-CD SSB may be indicated to the UE or determined by the UE based on any combination of system information, PDCCH, look-up table, or rules.

If the non-CD SSB is configured in dedicated initial DL BWP (e.g., 1013) or dedicated active DL BWP (e.g., 1014), UE 1102 as well as higher-capability UEs may use SSB for L1 and/or L3 measurements. Reduced capability UEs 1102, as well as higher capability UEs, may use SSBs to perform time/frequency tracking and/or other link maintenance procedures in the RRC connected state. Reduced capability UEs as well as higher capability UEs may use non-CD SSBs to perform Timing Advance (TA), resource mapping, and beam management in Small Data Transmissions (SDT).

The dedicated initial DL BWP (e.g., 1013) and the dedicated active DL BWP (e.g., 1014) may at least partially overlap with the CD-SSB (e.g., 1010) or CORESET 0 of the shared initial DL BWP 1004 in the frequency domain. Fig. 12 illustrates 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 a CD-SSB 1210 of a shared CORESET 0/shared initial DL BWP 1204 for a carrier bandwidth 1202.

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 rather than higher capability UEs. UE 1102 may receive the configuration of dedicated active DL BWP and active UL BWP in system information 1109 for the reduced capability UE (in dedicated initial DL BWP (e.g., 1013)). System information 1109 may be broadcast for reception by any reduced capability UEs. UE 1102 may receive a configuration of dedicated active DL BWP and active UL BWP from base station 1104 in RRC signaling. RRC signaling may be directed to UE 1102 in unicast signaling from base station 1104. In some aspects, UE 1102 may determine or identify the configuration of dedicated active DL BWP 1014 and active UL BWP 1012 based on rules, based on a look-up table, or based on previously known information without explicit signaling from the configuration of base station 1104. The use of a lookup table or rule may reduce signaling overhead while enabling a reduced capability UE to communicate based on active DL/UL BWP supported by the bandwidth capability of the UE.

At 1118, UE 1102 switches from transmitting and receiving (or monitoring) based on dedicated initial DL BWP 1013 and dedicated initial UL BWP 1011 to transmitting and receiving (or monitoring) based on active DL BWP 1014 and active UL BWP 1014 dedicated to reduced capability UEs. At 1120, the base station 1104 can perform a corresponding handover to communicate with the UE 1102. After the exchange of capability signaling 1114 is completed in the dedicated initial DL BWP (e.g., 1013), UE 1102 may perform a handover at 1118. At 1118, the handoff may be triggered by signal 1116 from base station 1104. Signal 1116 may comprise a broadcast, multicast, or unicast MAC-CE. Signal 1116 may include an RRC reconfiguration from base station 1104. The RRC reconfiguration may be unicast to the UE 1102. Signal 1116 may include DCI that is multicast or broadcast to UEs of reduced capability. In some aspects, at 1118, the UE may perform handover without a signal 1116 from the base station. In such examples, UE 1102 may perform handover based on a timer at 1118. UE 1102 may receive the timer configuration in system information 1106 (e.g., in system information specific to the reduced capability UE). The timer may instruct the UE to perform the handover after a configured number of subframes, a configured number of slots, or a configured amount of time after a reference point in time, such as after a capability exchange message, a RACH message, or another signal transmitted by the UE or received from the base station.

An active DL BWP (e.g., 1014) dedicated to the reduced capability UE may have an associated configuration for CSSs and one or more RSs within the bandwidth of the active DL BWP. For example, the active DL BWP may include a CORESET and CSS configured for the UE to monitor to receive pages 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 TRSs and/or periodic CSI-RS and/or PRSs. The active DL BWP may include a configured non-CD SSB. The active DL BWP may include a CSS and CORESET for configuration of system information update of the reduced capability UE. The active DL BWP may include a configured re-synchronization reference signal indicating system information update for the reduced capability UE.

As illustrated at 1122, the UE 1102 may monitor and/or receive PDSCH, PDCCH, TRS, CSI-RS, PRS, or non-CD SSB in active DL BWP dedicated to the reduced capability UE. At 1126, UE 1102 may transmit PUSCH, PUCCH, and/or SRS in an active UL BWP for the reduced capability UE.

Fig. 13 is a flow chart 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 a configuration for initial access and BWP after initial access that provides 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.

At 1302, the UE performs at least a portion of an initial access based on an initial downlink BWP shared between the first capable UE and the second capable UE. "first-capable UE" or "first-capable UE" may refer to a UE supporting the first capability. "UE with the second capability" or "UE with the second capability" may refer to a UE supporting the second capability. The initial access may be performed, for example, by BWP component 198 and/or initial BWP component 1540 of device 1504 in fig. 15. Fig. 9 illustrates an example in which a UE 902 performs initial access in a shared initial DL BWP. Fig. 11 illustrates an example in which a UE 1102 performs a part of initial access in a shared initial DL BWP and performs a part of initial access in a dedicated DL BWP for a reduced capability UE.

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

The UE may perform initial access based on an initial uplink BWP dedicated to the UE having the first capability. Performing the initial access may include transmitting a random access preamble during an RO having an SSB-to-RO mapping (e.g., which may be referred to as a spatial reference for a random access procedure) for the UE having the first capability that is different from an SSB-to-RO mapping for the UE having the second capability. The mapping of RO to SSB provides a spatial reference for RO. The SSB-to-RO mapping for the first capable UE is based on non-CD SSBs. 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: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set. 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: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set. The one or more parameters may be from at least one of system information, broadcast physical downlink control channel, look-up table, or rules. 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 made by the first capable UE and the second capable 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 having the first capability and the UE having the second capability, and wherein the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP being no greater than a lower maximum UE bandwidth of the UE having the first capability and the second capability. The initial uplink BWP and the second initial downlink BWP may be at edges of the carrier bandwidth.

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 BWP component 198 and/or active BWP component 1542 of device 1504 in fig. 15. Fig. 9 and 11 illustrate examples of UEs 902 and 1102 switching to dedicated active DL BWP for reduced capability UEs. In some aspects, at 1302, the UE may perform initial access based on the initial downlink BWP and an initial uplink BWP shared between the first-capable UE and the second-capable UE, and the UE may switch to an active downlink BWP and an active uplink BWP dedicated to the first-capable UE after performing the initial access. Fig. 9 illustrates an example aspect in which a UE uses a shared initial DL BWP and a shared initial UL BWP. The initial downlink BWP may include CORESET 0 or CD-SSB configured for the UE having the first capability and the UE having the second capability, wherein the initial downlink BWP and the initial uplink BWP have bandwidths at a center frequency of the carrier bandwidth, which are not greater than a lower maximum UE bandwidth of the UE having the first capability.

In some aspects, the UE may also receive system information or system information updates in the initial downlink BWP, the system information being included in SIBs dedicated to the UE of the first capability. In some aspects, the UE may also receive system information or system information updates in the initial downlink BWP, the system information including separate information specific 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.

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

In some aspects, the UE may also receive configurations for active downlink BWP and active uplink BWP. The configuration for active downlink BWP may include one or more of the following: periodic or semi-static TRS, periodic or semi-static CSI-RS, periodic or semi-static PRS, CSS or CORESET for paging, WUS, system information update or group common power control, non-CD SSB, additional CORESET or additional CSS for system information update, resynchronization reference signals for UE synchronization in DRX mode or for indicating system information update and UE synchronization in assisted discontinuous reception, or L3 intra-frequency measurement gaps. The configuration may be received in system information dedicated to the UE having the first capability. The configuration may be received in RRC signaling for the UE. The configuration of the active downlink BWP or the active uplink BWP may be based on rules or a look-up table.

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

In some aspects, a UE may receive a first configuration of a second initial downlink BWP specific to the UE with the first capability and may receive a second configuration of an active downlink BWP. In some aspects, a first configuration of a second initial downlink BWP may be received within the first initial downlink BWP in a SIB dedicated to the UE of the first capability. In some aspects, the first configuration of the second initial downlink BWP may be received within the first initial downlink BWP as information specific to the first-capable UE in a SIB carrying information for the first-capable UE and the second-capable UE. In some aspects, the first configuration of the second initial downlink BWP may be received within CORESET 0 in system information specific to the UE of the first capability. In some aspects, a second configuration of active downlink BWP may be received in a second initial downlink BWP. In some aspects, the configuration of the second initial downlink BWP may be based on a lookup table or rule.

Fig. 14 is a flow chart 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 a configuration for initial access and BWP after initial access that provides 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.

At 1402, the UE may perform at least a portion of the initial access based on an initial downlink BWP shared between the first-capable UE and the second-capable UE. The initial access may be performed, for example, by the BWP component 198 of the device 1504 in fig. 15. Fig. 11 illustrates an example in which a UE 1102 performs a part of initial access in a shared initial DL BWP and performs a part of initial access in a dedicated DL BWP for a reduced capability UE. Fig. 9 illustrates an example in which a UE 902 performs 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 the first-capable UE and the second-capable UE and based in part on a second initial downlink BWP dedicated to the first-capable UE.

For example, the UE may perform initial access based on an initial uplink BWP dedicated to the UE having the first capability. As an example, the UE may perform initial access based in part on a first initial downlink BWP shared between the first-capable UE and the second-capable UE and based in part on a second initial downlink BWP dedicated to the first-capable UE. The initial downlink BWP may include CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability. As illustrated at 1412, the UE may receive a first configuration of a second initial downlink BWP dedicated to the UE with the first capability, wherein the first configuration of the second initial downlink BWP is received within the first initial downlink BWP 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 having the first capability may not include CORESET 0 or CD-SSB. As illustrated at 1414, the UE may transmit a random access preamble during a random access occasion (RO) in the second initial downlink BWP, the RO having a Synchronization Signal Block (SSB) to RO mapping to the CD-SSB in the first initial downlink BWP.

As illustrated at 1404, the UE may receive a configuration for a non-cell-defined SSB (non-CD SSB) in an active downlink BWP dedicated to the first-capable UE.

At 1406, the UE may switch to an active downlink BWP and an active uplink BWP dedicated to the UE with the first capability. The BWP handover 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 device 1504 in fig. 15. Fig. 9 and 11 illustrate examples of UEs 902 and 1102 switching to dedicated active DL BWP for reduced capability UEs. In some aspects, at 1302, the UE may perform initial access based on the initial downlink BWP and an initial uplink BWP shared between the first-capable UE and the second-capable UE, and the UE may switch to an active downlink BWP and an active uplink BWP dedicated to the first-capable UE after performing the initial access. Fig. 9 illustrates an example aspect in which a UE uses a shared initial DL BWP and a shared initial UL BWP. The initial downlink BWP may include CORESET 0 or CD-SSB configured for the UE having the first capability and the UE having the second capability, wherein the initial downlink BWP and the initial uplink BWP have bandwidths at a center frequency of the carrier bandwidth, which are not greater than a lower maximum UE bandwidth of the UE having the first capability.

At 1408, the UE may perform at least one of layer 1 (L1) measurements or layer 3 (L3) measurements on non-CD SSBs in an active downlink BWP dedicated to the UE having the first capability. The receiving and measuring may be performed, for example, by the UE 104, 350 or the BWP component 198 of the device 1504.

As illustrated at 1410, the UE may receive a system information update in RRC signaling in an active downlink BWP dedicated to the first capable UE. The receiving may be performed, for example, by the UE 104, 350 or the BWP component 198 of the device 1504. Fig. 10 shows an example of an active downlink BWP 1014 for a UE with reduced bandwidth capability, which dedicated active downlink BWP comprises RRC signaling for System Information (SI) update.

In some aspects, a UE may receive a first configuration of a second initial downlink BWP specific to a UE having a first capability. The UE may also receive a second configuration of active downlink BWP in a second initial downlink BWP. The receiving may be performed, for example, by the UE 104, 350 or the BWP component 198 of the device 1504.

Performing the initial access may include transmitting a random access preamble during an RO having an SSB-to-RO mapping for the UE having the first capability that is different from an SSB-to-RO mapping for the UE having the second capability. The SSB-to-RO mapping for the first capable UE is based on non-CD SSBs. 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: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set. 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: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set. The one or more parameters may be from at least one of system information, broadcast physical downlink control channel, look-up table, or rules. 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 made by the first capable UE and the second capable 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 having the first capability and the UE having the second capability, and wherein the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP being no greater than a lower maximum UE bandwidth of the UE having the first capability. The initial uplink BWP and the second initial downlink BWP may be at edges of the carrier bandwidth.

In some aspects, the UE may also receive system information or system information updates in the initial downlink BWP, the system information being included in SIBs dedicated to the UE of the first capability. In some aspects, the UE may also receive system information or system information updates in the initial downlink BWP, the system information including separate information specific 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.

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

In some aspects, the UE may also receive configurations for active downlink BWP and active uplink BWP. The configuration for active downlink BWP may include one or more of the following: periodic or semi-static TRS, periodic or semi-static CSI-RS, periodic or semi-static PRS, CSS or CORESET for paging, WUS, system information update or group common power control, non-CD SSB, additional CORESET or additional CSS for system information update, re-synchronization reference signals for UE synchronization in DRX mode or for indicating system information update and UE synchronization in assisted discontinuous reception, or L3 intra-frequency measurement gaps in case SSB is not transmitted in active downlink BWP. The configuration may be received in system information dedicated to the UE having the first capability. The configuration may be received in RRC signaling for the UE. The configuration of the active downlink BWP or the active uplink BWP may be based on rules or a look-up table.

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

In some aspects, a UE may receive a first configuration of a second initial downlink BWP specific to the UE with the first capability and may receive a second configuration of an active downlink BWP. In some aspects, a first configuration of a second initial downlink BWP may be received within the first initial downlink BWP in a SIB dedicated to the UE of the first capability. In some aspects, the first configuration of the second initial downlink BWP may be received within the first initial downlink BWP as information specific to the first-capable UE in a SIB carrying information for the first-capable UE and the second-capable UE. In some aspects, the first configuration of the second initial downlink BWP may be received within CORESET 0 in system information specific to the UE of the first capability. In some aspects, a second configuration of active downlink BWP may be received in a second initial downlink BWP. In some aspects, the configuration of the second initial downlink BWP may be based on a lookup table or rule.

Fig. 15 is a diagram 1500 illustrating an example of a hardware implementation for the device 1504. The apparatus 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 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 also include one or more Subscriber Identity Module (SIM) cards 1520 and an application processor 1506 coupled to the Secure Digital (SD) card 1508 and the screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the apparatus 1504 may also 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., barometric pressure sensor/altimeter, motion sensors such as Inertial Management Units (IMUs), gyroscopes, and/or accelerometers, light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), acoustic navigation and ranging (sonor), magnetometers, audio, and/or other techniques for positioning), an additional memory module 1526, a power source 1530, and/or a camera 1532. Bluetooth module 1512, WLAN module 1514, and SPS module 1516 may include an on-chip Transceiver (TRX) (or in some cases, only a Receiver (RX)). Bluetooth module 1512, WLAN module 1514, and SPS module 1516 may include their own dedicated antennas and/or communicate using antenna 1580. The cellular baseband processor 1524 communicates with the UE 104 and/or RU associated with the network entity 1502 through 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. Additional memory modules 1526 may also be considered to be computer-readable media/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 on computer-readable media/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 the various functions described above. The computer readable medium/memory can also be used for storing data that is manipulated by the cellular baseband processor 1524/applications processor 1506 when executing software. The cellular baseband processor 1524/application processor 1506 may be a component of the UE 350 and may include memory 360 and/or at least one of: a TX processor 368, an RX processor 356, and a controller/processor 359. In one configuration, the apparatus 1504 may be a processor chip (modem and/or application) and include only the cellular baseband processor 1524 and/or the application processor 1506, while in another configuration, the apparatus 1504 may be an entire UE (see, e.g., 350 of fig. 3) and include additional modules of the apparatus 1504.

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 the first-capable UE and the second-capable UE (e.g., as described in connection with 1302 in fig. 13), and to switch to an active downlink BWP and an active uplink BWP dedicated to the first-capable UE, e.g., as described in connection with 1304 in fig. 13. As an example, BWP component 198 may include an initial BWP component 1540 configured to perform at least a portion of the initial access based on an initial downlink BWP shared between the first-capable UE and the second-capable UE, e.g., as described in connection with 1302 in fig. 13. The BWP component 198 may also be configured to perform any aspect of the algorithm in the flowcharts of fig. 13, 14 and/or aspects performed by the UE in fig. 9 and/or 11.

The apparatus 1504 may include additional components to perform each of the blocks of the algorithms in the flowcharts of fig. 13, 14 and/or aspects performed by the UE in fig. 9 and/or 11. Accordingly, each block in the flowchart of fig. 13 and/or aspects performed by the UE in fig. 9 and/or 11 may be performed by components, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 1504 may include various components configured for various functions. In one configuration, the apparatus 1504 and in particular the cellular baseband processor 1524 and/or the application processor 1506 may include: means for performing at least a portion of an initial access based on an initial downlink BWP shared between the first-capable UE and the second-capable UE; 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 also 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 also include means for receiving system information in the initial downlink BWP, the system information including separate information specific 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 also include means for receiving a configuration for an active downlink BWP and an active uplink BWP. The apparatus 1504 may also 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 having the first capability and for receiving a second configuration of an active downlink BWP. The apparatus 1504 may include: the apparatus includes means for receiving a first configuration of a second initial downlink BWP dedicated to a UE having a first capability, wherein the first configuration of the second initial downlink BWP is received within 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 having the first capability; and means for performing at least one of L1 or L3 measurements on non-CD SSBs in an active downlink BWP dedicated to the first capable UE. The apparatus 1504 may include means for performing each of the blocks of the algorithms in the flowcharts of fig. 13, 14 and/or aspects performed by the UE in fig. 9 and/or 11. The means may be one or more of the components of the device 1504 configured to perform the functions recited by the means. As described above, the apparatus 1504 may include a TX processor 368, an RX processor 356, and a controller/processor 359. Thus, in one configuration, the means may be TX processor 368, RX processor 356, and controller/processor 359 configured to perform the functions recited by the means.

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

At 1602, the network entity performs an initial access having a first capability associated with a lower maximum UE bandwidth than a second capability, at least a portion of the initial access being based on an initial downlink BWP shared between the first and second capable UEs. This initial access may be performed, for example, by BWP component 199 of network entity 1802 in fig. 18. Fig. 9 illustrates an example in which the base station 904 performs initial access in the shared initial DL BWP. Fig. 11 illustrates an example in which a base station 1104 performs a part of initial access in a shared initial DL BWP and performs a part of initial access in a dedicated DL BWP for a reduced capability UE.

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

Performing the initial access may include receiving a random access preamble during an RO having an SSB-to-RO mapping for the UE having the first capability, the SSB-to-RO mapping being different from an SSB-to-RO mapping for the UE having the second capability. The SSB-to-RO mapping for the first capable UE is based on non-CD SSBs. 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: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set. 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: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set. The one or more parameters may be from at least one of system information, broadcast physical downlink control channel, look-up table, or rules. 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 made by the first capable UE and the second capable 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 having the first capability and the UE having the second capability, and 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 the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are not greater than the lower maximum UE bandwidth of the UE having the first capability and the second capability. The initial uplink BWP and the second initial downlink BWP may be at edges of the carrier bandwidth.

At 1604, the network entity switches to an active downlink BWP and an active uplink BWP dedicated to the first capable UE for communication with the UE. The switching may be performed, for example, by BWP component 199 of network entity 1802 in fig. 18. Fig. 9 and 11 illustrate examples in which base stations 904 and 1104 switch to dedicated active DL BWP for a reduced capability UE. In some aspects, at 1602, the network entity may perform initial access based on the initial downlink BWP and an initial uplink BWP shared between the first-capable UE and the second-capable UE, and the base station may switch to active downlink BWP and active uplink BWP dedicated to the first-capable UE after performing the initial access. Fig. 9 illustrates example aspects 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 the UE having the first capability and the UE having the second capability, wherein the initial downlink BWP and the initial uplink BWP have bandwidths at a center frequency of the carrier bandwidth, which are not greater than a lower maximum UE bandwidth of the UE having the first capability.

In some aspects, the network entity may also transmit system information or system information updates in the initial downlink BWP, the system information being included in SIBs dedicated to UEs of the first capability. In some aspects, the network entity may also transmit system information or system information updates in the initial downlink BWP, the system information including separate information specific 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.

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

In some aspects, the network entity may also transmit configurations for active downlink BWP and active uplink BWP. The configuration for active downlink BWP may include one or more of the following: periodic or semi-static TRS, periodic or semi-static CSI-RS, 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, resynchronization reference signals for UE synchronization in Discontinuous Reception (DRX) mode and indicating system information update, or layer 3 (L3) intra-frequency measurement gaps. The configuration may be transmitted in system information dedicated to the UE having the first capability. The configuration may be transmitted in RRC signaling for the UE. The configuration of the active downlink BWP or the active uplink BWP may be based on rules or a look-up table.

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

In some aspects, the network entity may also transmit a first configuration of a second initial downlink BWP specific to the first capable UE 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 within the first initial downlink BWP in a SIB dedicated to the UE of the first capability. In some aspects, the first configuration of the second initial downlink BWP may be transmitted within the first initial downlink BWP as information specific to the first-capable UE in a SIB carrying information for the first-capable UE and the second-capable UE. In some aspects, the first configuration of the second initial downlink BWP may be transmitted within CORESET 0 in system information specific to the UE of the first capability. In some aspects, a second configuration of active downlink BWP may be received in a second initial downlink BWP. In some aspects, the configuration of the second initial downlink BWP may be based on a lookup table or rule.

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

At 1702, the network entity may perform an initial access having a first capability associated with a lower maximum UE bandwidth than a second capability, at least a portion of the initial access being based on an initial downlink BWP shared between the first and second capable UEs. The initial access may be performed, for example, by the BWP component 199 of the base station 102 or 310 or the network entity 1802. Fig. 11 illustrates an example in which a base station 1104 performs a part of initial access in a shared initial DL BWP and performs a part of initial access in a dedicated DL BWP for a reduced capability UE.

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

At 1706, to communicate with the UE, the network entity may switch to active downlink BWP and active uplink BWP dedicated to the UE with the first capability. The switching may be performed, for example, by BWP component 199 of network entity 1802 in fig. 18. Fig. 9 and 11 illustrate examples in which base stations 904 and 1104 switch to dedicated active DL BWP for a reduced capability UE.

For example, the network entity may perform initial access with the UE based on an initial uplink BWP dedicated to the UE having 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 first-capable UE and the second-capable UE and based in part on a second initial downlink BWP dedicated to the first-capable UE. The initial downlink BWP may include CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability. As illustrated at 1712, the network entity may output a first configuration of a second initial downlink BWP dedicated to the first capable UE for transmission, wherein the first configuration of the second initial downlink BWP is received within the first initial downlink BWP in a SIB carrying information for the first capable UE and the second capable UE. The second initial downlink BWP dedicated to the UE having the first capability may not include CORESET 0 or CD-SSB. As illustrated at 1714, the network entity may obtain (e.g., receive) the 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.

As illustrated at 1708, the network entity may output the system information update in RRC signaling in an active downlink BWP dedicated to the first capable UE. The outputting may be performed, for example, by the BWP component 199 of the UE 104, 350 or the device 1504. Fig. 10 shows an example of an active downlink BWP 1014 for a UE with reduced bandwidth capability, which dedicated active downlink BWP comprises RRC signaling for System Information (SI) update.

In some aspects, a UE may receive a first configuration of a second initial downlink BWP specific to a UE having a first capability. The UE may also receive a second configuration of active downlink BWP in a second initial downlink BWP. The receiving may be performed, for example, by the BWP component 199 of the base station 102 or 310 or the network entity 1802.

Fig. 9 illustrates an example in which the base station 904 performs initial access in the shared initial DL BWP. In some aspects, the network entity may perform initial access based in part on a first initial downlink BWP shared between the first-capable UE and the second-capable UE and based in part on a second initial downlink BWP dedicated to the first-capable UE. The network entity may perform initial access based on an initial uplink BWP dedicated to the UE having the first capability. The network entity may configure BWP handover for the reduced capability UE for TDD mode, FD-FDD mode, or HD-FDD mode.

Performing the initial access may include receiving a random access preamble during an RO having an SSB-to-RO mapping for the UE having the first capability, the SSB-to-RO mapping being different from an SSB-to-RO mapping for the UE having the second capability. The SSB-to-RO mapping for the first capable UE is based on non-CD SSBs. 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: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set. 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: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set. The one or more parameters may be from at least one of system information, broadcast physical downlink control channel, look-up table, or rules. 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 made by the first capable UE and the second capable 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 having the first capability and the UE having the second capability, and 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 the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are not greater than the lower maximum UE bandwidth of the UE having the first capability and the second capability. The initial uplink BWP and the second initial downlink BWP may be at edges of the carrier bandwidth.

At 1706, to communicate with the UE, the network entity switches to active downlink BWP and active uplink BWP dedicated to the UE with the first capability. The handover may be performed, for example, by the BWP component 199 of the base station 102 or 310 or the network entity 1802. Fig. 9 and 11 illustrate examples in which base stations 904 and 1104 switch to dedicated active DL BWP for a reduced capability UE. In some aspects, at 1702, the network entity may perform initial access based on the initial downlink BWP and an initial uplink BWP shared between the first-capable UE and the second-capable UE, and the base station may switch to an active downlink BWP and an active uplink BWP dedicated to the first-capable UE after performing the initial access. Fig. 9 illustrates example aspects 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 the UE having the first capability and the UE having the second capability, wherein the initial downlink BWP and the initial uplink BWP have bandwidths at a center frequency of the carrier bandwidth, which are not greater than a lower maximum UE bandwidth of the UE having the first capability.

In some aspects, the network entity may also output system information or system information updates for transmission (e.g., transmission) in the initial downlink BWP, the system information being included in SIBs dedicated to UEs of the first capability. In some aspects, the network entity may also transmit system information or system information updates in the initial downlink BWP, the system information including separate information specific 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.

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

In some aspects, the base station may also transmit configurations for active downlink BWP and active uplink BWP. The configuration for active downlink BWP may include one or more of the following: periodic or semi-static TRS, periodic or semi-static CSI-RS, 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, re-synchronization reference signals for UE synchronization in Discontinuous Reception (DRX) mode and indicating system information update, or L3 intra-frequency measurement gaps in case SSB is not transmitted in active downlink BWP. The configuration may be transmitted in system information dedicated to the UE having the first capability. The configuration may be transmitted in RRC signaling for the UE. The configuration of the active downlink BWP or the active uplink BWP may be based on rules or a look-up table.

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

In some aspects, the base station may also transmit a first configuration of a second initial downlink BWP specific to the first capable UE 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 within the first initial downlink BWP in a SIB dedicated to the UE of the first capability. In some aspects, the first configuration of the second initial downlink BWP may be transmitted within the first initial downlink BWP as information specific to the first-capable UE in a SIB carrying information for the first-capable UE and the second-capable UE. In some aspects, the first configuration of the second initial downlink BWP may be transmitted within CORESET 0 in system information specific to the UE of the first capability. In some aspects, a second configuration of active downlink BWP may be received in a second initial downlink BWP. In some aspects, the configuration of the second initial downlink BWP may be based on a lookup table or rule.

Fig. 18 is a diagram 1800 illustrating an example of a hardware implementation of network entity 1802. The network entity 1802 may be a base station, a component of a base station, or may implement base station functionality. Network entity 1802 may include at least one of a CU 1810, a DU 1830, or an RU 1840. For example, depending on the layer functionality handled by component 199, network entity 1802 may include CU 1810; both CU 1810 and DU 1830; each of CU 1810, DU 1830 and RU 1840; DU 1830; both DU 1830 and RU 1840; or RU 1840.CU 1810 may include a CU processor 1812. The CU 1812 may include on-chip memory 1812'. In some aspects, CU 1810 may also include additional memory modules 1814 and a communication interface 1818.CU 1810 communicates with DU 1830 through a mid-range link (such as the F1 interface). The DU 1830 may include a DU processor 1832. The DU 1832 may include on-chip memory 1832'. In some aspects, the DU 1830 may also include an additional memory module 1834 and a communication interface 1838. The DU 1830 communicates with the RU 1840 over a forward link. RU 1840 can include an RU processor 1842.RU 1842 may include on-chip memory 1842'. In some aspects, RU 1840 may also include additional memory module 1844, one or more transceivers 1846, antenna 1880, and communications interface 1848.RU 1840 may communicate with UE 104. The on-chip memory 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 on computer-readable media/memory. The software, when executed by a corresponding processor, causes the processor to perform the various functions described supra. The computer readable medium/memory may also be used for storing data that is manipulated by a processor when executing software.

The network entity 1802 may include a BWP component 199, for example, as described in connection with any of fig. 1, 3, 16, or 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 the first-capable UE and the second-capable UE (e.g., as described in connection with 1602 in fig. 16), and to switch to an active downlink BWP and an active uplink BWP dedicated to the first-capable UE, e.g., as described in connection with 1604 in fig. 16. In some aspects, BWP component 199 may include an initial BWP configuration component 1845 configured to perform at least a portion of the initial access based on an initial downlink BWP shared between the first-capable UE and the second-capable UE, e.g., as described in connection with 1602 in fig. 16. BWP component 199 may further comprise an active BWP configuration component 1847 configured to switch to an active downlink BWP and an active uplink BWP dedicated to the first capable UE, e.g., as described in connection with 1604 in fig. 16.

The network entity 1802 may include additional components that perform each of the blocks of the algorithms in the flowcharts of fig. 16, 17 and/or aspects performed by the base station of fig. 9 or 11. As such, each block in the flow diagrams of fig. 16, 17 and/or aspects performed by the base station in fig. 9 or 11 may be performed by components and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

As shown, network entity 1802 may include various components configured for various functions. In one configuration, the network entity 1802 may include: means for performing an initial access with a UE having a first capability, the first capability being associated with a lower maximum UE bandwidth than a second capability, at least a portion of the initial access being 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 also include means for transmitting system information in the initial downlink BWP, the system information being included in a SIB dedicated to the UE of the first capability. The network entity 1802 may also include means for transmitting system information in the initial downlink BWP, the system information including separate information specific 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 comprise means for transmitting a configuration for active downlink BWP and active uplink BWP. The network entity 1802 may further comprise means for receiving capability signaling indicating that the UE has the first capability, wherein the base station switches to active downlink BWP and 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 specific to the UE having the first capability; and means for transmitting the second configuration of active downlink BWP. The network entity 1802 may also include means for performing initial access based in part on a first initial downlink BWP shared between the first capable UE and the second capable UE and based in part on a second initial downlink BWP dedicated to the first capable UE, wherein the initial downlink BWP includes CORESET 0 and CD-SSB configured for the first capable UE and the second capable UE. The network entity 1802 may further include means for outputting a first configuration of a second initial downlink BWP dedicated to the first capable UE for transmission, wherein the first configuration of the second initial downlink BWP is received within the first initial downlink BWP in a SIB carrying information for the first capable UE and the second capable UE, wherein the second initial downlink BWP dedicated to the first capable UE does not include CORESET 0 or CD-SSB. The network entity 1802 may further comprise 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 CD-SSBs in the first initial downlink BWP. The network entity 1802 may also include means for outputting for transmission a configuration of a non-CD SSB in an active downlink BWP dedicated to the first capable UE, the non-CD SSB for at least one of L1 measurements or L3 measurements for the first capable UE. The network entity 1802 may include means for performing any aspect of the algorithm in the flowcharts of fig. 16, 17 and/or aspects performed by the base station of fig. 9 or 11. The component may be one or more of the components of the network entity 1802 configured to perform the functions recited by the component. As described above, network entity 1802 can include TX processor 316, RX processor 370, and controller/processor 375. Thus, in one configuration, the means may be TX processor 316, RX processor 370, and controller/processor 375 configured to perform the functions recited by the means described in connection with fig. 3.

It is to be understood that the specific order or hierarchy of blocks in the processes/flow diagrams disclosed is merely an illustration of example approaches. It should be appreciated that the particular order or hierarchy of blocks in the process/flow diagram may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Accordingly, the claims are not to be limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. Terms such as "if", "when … …" and "at … …" indicate "under … … conditions", and do not mean an immediate time relationship or reaction. That is, these phrases, such as "when … …," do not mean an immediate action in response to or during the occurrence of an action, but simply suggest that an action will occur if a condition is met, but do not require specific or immediate time constraints 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. The term "some" means one or more unless specifically stated otherwise. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" include any combination of A, B and/or C, and may include a plurality of a, B, or C. Specifically, a combination 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" may be a alone, B alone, C, A and B, A and C, B and C, or a and B and C, wherein any such combination may comprise one or more members of A, B or C. A collection should be interpreted as a collection of elements, where the number of elements is one or more. Thus, for a collection of X, X will include one or more elements. If 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 indirectly between the first device and the second device through a set of devices. All structural and functional equivalents to the elements of the aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words "module," mechanism, "" element, "" device, "and the like are not to be construed as alternatives to the word" component. Accordingly, no claim element is to be construed as a functional element unless the element is explicitly stated using the phrase "means for … …".

As used herein, the phrase "based on" should not be construed to refer to a closed set of information, one or more conditions, one or more factors, and the like. In other words, the phrase "based on a" (where "a" may be information, conditions, factors, etc.) should be construed as "based at least on a" unless specifically stated differently.

The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

Aspect 1 is a method of wireless communication at a UE having a first capability associated with a lower maximum UE bandwidth than a second capability, the method comprising: 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 the UE having the second capability; and after the initial access, switching to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability.

In aspect 2, the method according to aspect 1 further comprises: the UE performs 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, wherein the UE switches to the active downlink BWP and the active uplink BWP dedicated to the UE having the first capability after performing the initial access, and the BWP switch of the UE is configured for a TDD mode, FD-FDD mode, or HD-FDD mode.

In aspect 3, the method according to aspect 1 or aspect 2 further comprises: the first initial downlink BWP comprises CORESET 0 or CD-SSB configured for the UE having the first capability and the UE having the second capability, and wherein the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, a first bandwidth of the first initial downlink BWP and a second bandwidth of the initial uplink BWP being not greater than the lower maximum UE bandwidth of the UE having the first capability and the second capability.

In aspect 4, the method according to any one of aspects 1 to 3 further comprises: system information or system information updates are received in the first initial downlink BWP, the system information being included in SIBs of the UE dedicated to the first capability.

In aspect 5, the method according to any one of aspects 1 to 3 further comprises: system information or system information updates are received in the first initial downlink BWP, the system information comprising separate information of the UE dedicated to the first capability in a SIB carrying information for the UE of the first capability and the UE of the second capability.

In aspect 6, the method according to any one of aspects 1 to 5 further comprises: performing the initial access includes transmitting a random access preamble during an RO having a CD-SSB based SSB-to-RO mapping.

In aspect 7, the method according to any one of aspects 1 to 5 further comprises: performing the initial access includes transmitting a random access preamble during an RO having either an SSB-to-RO mapping or an SSB-to-preamble mapping configured for the UE having the first capability.

In aspect 8, the method according to any one of aspects 1 to 7 further comprises: receiving a configuration for the active downlink BWP and the active uplink BWP, the configuration for the active downlink BWP comprising 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 the system information update, re-synchronization reference signals for UE synchronization in DRX mode and indicating the system information update, or L3 intra-frequency measurement gaps without SSB transmission in the active downlink BWP.

In aspect 9, the method according to aspect 8 further comprises: the configuration is received in system information dedicated to the UE having the first capability.

In aspect 10, the method of aspect 8 further comprising: the configuration is received in RRC signaling for the UE.

In aspect 11, the method according to any one of aspects 1 to 7 further comprises: the configuration of the active downlink BWP or the active uplink BWP is based on rules or a look-up table.

In aspect 12, the method according to any one of aspects 1 to 11 further comprises: performing a capability signaling procedure indicating that the UE has the first capability, wherein the UE switches to the active downlink BWP and the active uplink BWP after completing the capability signaling procedure and based on at least one of: MAC-CE, RRC reconfiguration, DCI, or timer configured in system information for the UE with the first capability.

In aspect 13, the method of aspect 1 further comprises: the UE performs the initial access based in part on a 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 dedicated to the UE having the first capability.

In aspect 14, the method of aspect 1 or aspect 13 further comprises: the UE performs the initial access based on an initial uplink BWP dedicated to the UE having the first capability.

In aspect 15, the method of aspect 14 further comprising: performing the initial access includes transmitting a random access preamble during an RO having an SSB-to-RO mapping for the UE having the first capability, the SSB-to-RO mapping being different from an SSB-to-RO mapping for the UE having the second capability.

In aspect 16, the method of aspect 15 further comprises: the SSB-to-RO mapping for the UE with the first capability is based on a non-CD SSB.

In aspect 17, the method of aspects 13, 15 or 16 further comprising: the one or more parameters for the non-CD SSB are the same parameters as for the CD-SSB, the one or more parameters including at least one of: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set.

In aspect 18, the method of aspects 13, 15 or 16 further comprising: configuring one or more parameters for the non-CD SSB independent of the CD-SSB, the one or more parameters including at least one of: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set.

In aspect 19, the method of aspect 18 further comprising: the one or more parameters are from at least one of system information, broadcast physical downlink control channel, look-up table, or rules.

In aspect 20, the method of aspect 16 further comprising: 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 made by the UE of the first capability and the UE of the second capability.

In aspect 21, the method of aspect 16 further comprising: at least one of the second initial downlink BWP or the active downlink BWP overlaps in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP.

In aspect 22, the method according to aspect 13 or 14 further comprises: the first initial downlink BWP comprises CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability, and wherein the first initial downlink BWP has a bandwidth at a center frequency of a carrier bandwidth, the bandwidth being not greater than the lower maximum UE bandwidth of the UE having the first capability, and wherein the initial uplink BWP and the second initial downlink BWP are at edges of the carrier bandwidth.

In aspect 23, the method according to any one of aspects 1 or 13 to 22 further comprises: receiving a first configuration of the second initial downlink BWP specific to the UE having the first capability; and receiving a second configuration of the active downlink BWP.

In aspect 24, the method of aspect 23 further comprising: the first configuration of the second initial downlink BWP is received within the first initial downlink BWP in a SIB of the UE dedicated to the first capability.

In aspect 25, the method of aspect 23 further comprising: the first configuration of the second initial downlink BWP is received within the first initial downlink BWP as information of the UE dedicated to the first capability in a SIB carrying information for the UE of the first capability and the UE of the second capability.

In aspect 26, the method of aspect 23 further comprising: the first configuration of the second initial downlink BWP is received in system information within CORESET 0, the system information being specific to the UE of the first capability.

In aspect 27, the method of aspect 23 further comprising: the second configuration of the active downlink BWP is received in the second initial downlink BWP.

In aspect 28, the method of any one of aspects 1 or 13 to 22 further comprises: the configuration of the second initial downlink BWP is based on a look-up table or rule.

In aspect 29, the method of aspect 1 further comprises: the initial access is performed based in part on a 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 dedicated to the UE having the first capability.

In aspect 30, the method of aspect 29 further comprising: the first initial downlink BWP includes CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability.

In aspect 31, the method of aspect 29 or aspect 30 further comprises: a first configuration is received of the second initial downlink BWP specific 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 SIB carrying information for the UE of the first capability and the UE of the second capability.

In aspect 32, the method according to any one of aspects 29 to 31 further comprises: the second initial downlink BWP dedicated to the UE having the first capability does not include the CORESET 0 or the CD-SSB.

In aspect 33, the method according to any one of aspects 29 to 32 further comprises: performing the initial access includes transmitting 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.

In aspect 34, the method according to any one of aspects 29 to 33 further comprises: a configuration is received for a non-CD SSB in the active downlink BWP dedicated to the UE having the first capability.

In aspect 35, the method of aspect 34 further comprising: at least one of L1 or L3 measurements is performed on the non-CD SSB in the active downlink BWP dedicated to the UE with the first capability.

In aspect 36, the method according to any one of aspects 29 to 35 further comprises: system information updates are received in RRC signaling in the active downlink BWP dedicated to the UE with the first capability.

In aspect 37, the method according to any one of aspects 29 to 36 further comprises: receiving a first configuration of the second initial downlink BWP specific to the UE having the first capability; and receiving a second configuration of the active downlink BWP in the second initial downlink BWP.

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

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

In aspect 40, the device of aspects 38 or 39 further comprises at least one of an antenna or a transceiver.

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

Aspect 42 is a method of wireless communication at a network entity, comprising: performing an initial access with a UE having a first capability, the first capability being associated with a lower maximum UE bandwidth than a second capability, at least a portion of the initial access being 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 dedicated to the UE having the first capability for communication with the UE.

In aspect 43, the method according to aspect 42 further comprises: the base station performs 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 switches to the active downlink BWP and the active uplink BWP dedicated to the UE having the first capability after performing the initial access.

In aspect 44, the method of aspect 42 or aspect 43 further comprises: the first initial downlink BWP comprises CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability, and wherein the first initial downlink BWP and the initial uplink BWP have bandwidths at a center frequency of a carrier bandwidth, the bandwidths being not greater than the lower maximum UE bandwidth of the UE having the first capability.

In aspect 45, the method according to any one of aspects 42 to 44 further comprises: system information is transmitted in the first initial downlink BWP, the system information being included in a SIB dedicated to the UE for the first capability.

In aspect 46, the method according to any one of aspects 42 to 44 further comprises: transmitting system information in the first initial downlink BWP, the system information comprising separate information of the UE dedicated to the first capability in a SIB carrying information for the UE of the first capability and the UE of the second capability.

In aspect 47, the method according to any one of aspects 42 to 46 further comprises: performing the initial access includes receiving a random access preamble from the UE during an RO having a CD-SSB based SSB-to-RO mapping.

In aspect 48, the method according to any one of aspects 42 to 46 further comprises: performing the initial access includes receiving a random access preamble from the UE during an RO having either an SSB-to-RO mapping or an SSB-to-preamble mapping configured for the UE having the first capability.

In aspect 49, the method according to any one of aspects 42 to 48 further comprises: transmitting a configuration for the active downlink BWP and the active uplink BWP, the configuration for the active downlink BWP comprising 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, re-synchronization reference signal for UE synchronization in DRX mode and indicating the system information update, or L3 intra-frequency measurement gap in case SSB is not transmitted in the active downlink BWP.

In aspect 50, the method of aspect 49 further comprising: the configuration is transmitted in system information dedicated to the UE having the first capability.

In aspect 51, the method of aspect 49 further comprising: the configuration is transmitted in RRC signaling to the UE.

In aspect 52, the method according to any one of aspects 42 to 48 further comprises: the configuration of the active downlink BWP or the active uplink BWP is based on rules or a look-up table.

In aspect 53, the method according to any one of aspects 42 to 52 further comprises: receiving capability signaling indicating that the UE has the first capability, wherein the base station switches to the active downlink BWP and the active uplink BWP after receiving the capability signaling and based on at least one of: MAC-CE, RRC reconfiguration, DCI, or timer configured in system information for the UE with the first capability.

In aspect 54, the method of aspect 42 further comprising: the initial access is based in part on a first initial downlink BWP shared between the UE having the first capability and the UE having the second capability and in part on a second initial downlink BWP dedicated to the UE having the first capability.

In aspect 55, the method according to aspects 42 or 54 further comprises: the initial access is also based on an initial uplink BWP dedicated to the UE having the first capability.

In aspect 56, the method according to any one of aspects 54 or 55 further comprises: performing the initial access includes receiving a random access preamble from the UE during an RO having an SSB-to-RO mapping for the UE having the first capability, the SSB-to-RO mapping being different from an SSB-to-RO mapping for the UE having the second capability.

In aspect 57, the method of aspect 56 further comprises: the SSB-to-RO mapping for the UE with the first capability is based on a non-CD SSB.

In aspect 58, the method of aspect 57 further comprising: the one or more parameters for the non-CD SSB are the same parameters as for the CD-SSB, the one or more parameters including at least one of: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set.

In aspect 59, the method of aspect 57 further comprising: configuring one or more parameters for the non-CD SSB independent of the CD-SSB, the one or more parameters including at least one of: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set.

In aspect 60, the method according to any one of aspects 57 to 59 further comprises: the one or more parameters are from at least one of system information, broadcast physical downlink control channel, look-up table, or rules.

In aspect 61, the method according to any one of aspects 57 to 59 further comprises: 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 made by the UE of the first capability and the UE of the second capability.

In aspect 62, the method according to any one of aspects 54 to 61 further comprises: at least one of the second initial downlink BWP or the active downlink BWP overlaps in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP.

In aspect 63, the method according to any one of aspects 54 to 62 further comprises: the first initial downlink BWP comprises CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability, and wherein the first initial downlink BWP has a bandwidth at a center frequency of a carrier bandwidth, the bandwidth being not greater than the lower maximum UE bandwidth of the UE having the first capability, and wherein the initial uplink BWP and the second initial downlink BWP are at edges of the carrier bandwidth.

In aspect 64, the method according to any one of aspects 54 to 63 further comprises: transmitting a first configuration of the second initial downlink BWP specific to the UE having the first capability; and transmitting a second configuration of the active downlink BWP.

In aspect 65, the method of aspect 64 further comprises: the first configuration of the second initial downlink BWP is transmitted within the first initial downlink BWP in a SIB of the UE dedicated to the first capability.

At aspect 66, the method of aspect 64 further comprising: the first configuration of the second initial downlink BWP is transmitted within the first initial downlink BWP as information of the UE dedicated to the first capability in a SIB carrying information for the UE of the first capability and the UE of the second capability.

In aspect 67, the method according to any one of aspects 64 to 66 further comprises: the first configuration of the second initial downlink BWP is transmitted in system information within CORESET 0, the system information being specific to the UE of the first capability.

In aspect 68, the method of aspect 64 further comprises: the second configuration of the active downlink BWP is transmitted in the second initial downlink BWP.

In aspect 69, the method according to any one of aspects 42 to 63 further comprises: the configuration of the second initial downlink BWP is based on a look-up table or rule.

In aspect 70, the method of aspect 42 further comprises: the initial access is performed based in part on a 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 dedicated to the UE having the first capability, wherein the first initial downlink BWP comprises CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability.

In aspect 71, the method according to aspect 70 further comprises: outputting for transmission a first configuration of the second initial downlink BWP specific 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 SIB carrying information for the UE of the first capability and the UE of the second capability, wherein the second initial downlink BWP specific to the UE of the first capability does not include the CORESET 0 or the CD-SSB.

In aspect 72, the method according to aspect 70 or 71 further comprises: performing the initial access includes 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.

In aspect 73, the method according to any one of aspects 70 to 72 further comprises: a configuration for a non-CD SSB in the active downlink BWP dedicated to the UE with the first capability is output for transmission, the non-CD SSB being used for at least one of L1 measurements or L3 measurements for the UE with the first capability.

In aspect 74, the method according to any one of aspects 70 to 73 further comprises: system information updates are output for transmission in RRC signaling in the active downlink BWP dedicated to the UE with the first capability.

Aspect 75 is an apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory and configured to perform the method of any one of claims 42 to 74 based at least in part on information stored in the memory.

Aspect 76 is an apparatus for wireless communication at a network entity, the apparatus comprising means for performing the method of any one of claims 42 to 74.

In aspect 77, the device of aspects 75 or 76 further comprising at least one of an antenna or a transceiver.

Aspect 78 is a non-transitory computer-readable medium storing computer-executable code at a network entity, which when executed by a processor causes the processor to perform the method of any one of claims 42 to 74.

Aspect 79 is a computer program product for wireless communication at a network entity, the computer program product comprising instructions which, when the program is executed by a computer, cause the network entity to perform the method according to any of aspects 42 to 74.

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

Aspect 81 is an apparatus for wireless communication at a UE having a first capability associated with a lower maximum UE bandwidth than a second capability, the apparatus comprising: a memory; and at least one processor coupled to the memory and configured to, based at least in part on the stored information in the memory: 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 the UE having the second capability; and after the initial access, switching to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability.

In aspect 82, the apparatus according to aspect 81 further comprises: 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 dedicated to the UE having the first capability.

In aspect 83, the apparatus according to aspect 82 further comprises: the first initial downlink BWP includes CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability.

In aspect 84, the apparatus according to aspects 82 or 83 further comprises: the at least one processor is further configured to: a first configuration is received of the second initial downlink BWP specific 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 SIB carrying information for the UE having the first capability and the UE having the second capability.

In aspect 85, the apparatus according to aspect 84 further comprising: the second initial downlink BWP dedicated to the UE having the first capability does not include the CORESET 0 or the CD-SSB.

In aspect 86, the apparatus according to any one of aspects 83 to 85 further comprises: to perform the initial access, the at least one processor is configured to: a random access preamble is transmitted 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.

In aspect 87, the apparatus according to any one of aspects 81 to 86 further comprises: the at least one processor is further configured to: a configuration is received for a non-CD SSB in the active downlink BWP dedicated to the UE having the first capability.

In aspect 88, the apparatus of aspect 87 further comprising: the at least one processor is further configured to: at least one of L1 or L3 measurements is performed on the non-CD SSB in the active downlink BWP dedicated to the UE with the first capability.

In aspect 89, the apparatus according to any of aspects 81 to 88 further comprises: the at least one processor is further configured to: system information updates are received in RRC signaling in the active downlink BWP dedicated to the UE with the first capability.

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

In aspect 91, the apparatus according to any of aspects 82 to 90 further comprises: in the second initial downlink BWP or the active downlink BWP dedicated to the UE having the first capability, the one or more parameters for non-CD SSB include the same parameters as those for CD-SSB, including at least one of: periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or parameter set.

In aspect 92, the apparatus according to aspect 91 further comprises: 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 made by the UE with the first capability and the UE with the second capability.

In aspect 93, the apparatus of aspects 91 or 92 further comprises: at least one of the second initial downlink BWP or the active downlink BWP overlaps in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP.

In aspect 94, the apparatus according to aspect 82 further comprises: the first initial downlink BWP has a bandwidth at a center frequency of a carrier bandwidth that is not greater than the lower maximum UE bandwidth of the UE having the first capability, and wherein initial uplink BWP and the second initial downlink BWP are at edges of the carrier bandwidth.

In aspect 95, the apparatus according to aspect 82 further comprises: receiving a first configuration of the second initial downlink BWP specific to the UE having the first capability; and receiving a second configuration of the active downlink BWP in the second initial downlink BWP.

In aspect 96, the apparatus of aspect 95 further comprises: the first configuration of the second initial downlink BWP is received in one of: received in SIB dedicated to the UE having the first capability within the first initial downlink BWP or in system information dedicated to the UE having the first capability within CORESET 0.

In aspect 97, the apparatus according to aspect 82 further comprising: the configuration of the second initial downlink BWP is based on a look-up table or rule.

In aspect 98, the apparatus according to aspect 81 further comprises: 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, the BWP switch of the UE being configured for a TDD mode, FD-FDD mode, or HD-FDD mode, and wherein the first initial downlink BWP comprises CORESET 0 or CD-SSB configured for the UE having the first capability and the UE having the second capability, and wherein the first initial downlink BWP and the initial uplink BWP have a same or different center frequency and a same or different bandwidth, the first bandwidth of the first initial downlink BWP and the bandwidth of the UE being different from the second bandwidth of the UE having the second capability.

In aspect 99, the apparatus according to aspect 98 further comprises: the at least one processor is further configured to: receiving system information or system information updates in the first initial downlink BWP, the system information being included in a first SIB dedicated to the UE having the first capability or the system information updates being received in the first initial downlink BWP, the system information including separate information dedicated to the UE having the first capability in a second SIB carrying the separate information for the UE having the first capability and additional information for the UE having the second capability.

In aspect 100, the apparatus according to aspect 98 or 99 further comprises: to perform the initial access, the at least one processor is configured to: the random access preamble is transmitted during a first RO having a first SSB-to-RO mapping based on CD-SSB or during a second RO having a second SSB-to-RO mapping or SSB-to-preamble mapping configured for the UE having the first capability.

In aspect 101, the apparatus according to aspect 81 further comprises: wherein the at least one processor is further configured to: receiving a configuration for the active downlink BWP and the active uplink BWP, the configuration for the active downlink BWP comprising 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 the system information update, re-synchronization reference signals for UE synchronization in DRX mode and indicating the system information update, or L3 intra-frequency measurement gaps without SSB transmission in the active downlink BWP.

In aspect 102, the apparatus according to aspect 101 further comprises: the configuration is included in system information dedicated to the UE having the first capability or in RRC signaling for the UE.

In aspect 103, the apparatus according to aspect 81 further comprises: the configuration of the active downlink BWP or the active uplink BWP is based on rules or a look-up table.

In aspect 104, the apparatus according to any one of aspects 81 to 103 further comprises: the at least one processor is configured to perform a capability signaling procedure indicating that the UE has the first capability, wherein the at least one processor is configured to switch to the active downlink BWP and the active uplink BWP after completion of the capability signaling procedure and based on at least one of: MAC-CE, RRC reconfiguration, DCI, or timer configured in system information for the UE with the first capability.

Aspect 105 is an apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory and configured to, based at least in part on the stored information in the memory: performing an initial access with a UE having a first capability, the first capability being associated with a lower maximum UE bandwidth than a second capability, at least a portion of the initial access being 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 dedicated to the UE having the first capability in order to communicate with the UE after the initial access.

In aspect 106, the apparatus according to aspect 105 further comprises: the at least one processor is configured to perform the initial access based in part on a 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 dedicated to the UE having the first capability, wherein the first initial downlink BWP comprises CORESET 0 and CD-SSB configured for the UE having the first capability and the UE having the second capability.

In aspect 107, the apparatus of aspect 106 further comprises: outputting for transmission a first configuration of the second initial downlink BWP specific 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 SIB carrying information for the UE having the first capability and the second capability, wherein the second initial downlink BWP specific to the UE having the first capability does not include the CORESET 0 or the CD-SSB.

In aspect 108, the apparatus according to any one of aspects 105 to 107 further comprises: to perform the initial access, the at least one processor is configured to: a random access preamble is obtained 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.

In aspect 109, the apparatus according to any one of aspects 105 to 108 further comprises: the at least one processor is further configured to: a configuration for a non-CD SSB in the active downlink BWP dedicated to the UE with the first capability is output for transmission, the non-CD SSB being used for at least one of L1 measurements or L3 measurements for the UE with the first capability.

In aspect 110, the apparatus according to any one of aspects 105 to 109 further comprises: the at least one processor is further configured to: system information updates are output for transmission in RRC signaling in the active downlink BWP dedicated to the UE with the first capability.

Claims (30)

1. An apparatus for wireless communication at a User Equipment (UE) having a first capability, the first capability being associated with a lower maximum UE bandwidth than a second capability, the apparatus comprising:

A memory; and

at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor configured to:

performing at least a portion of an initial access based on a first 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, switching to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability.

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 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.

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

4. The apparatus of claim 3, wherein the at least one processor is further configured to:

a first configuration is received of the second initial downlink BWP specific 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) carrying 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 with the first capability does not include the CORESET 0 or the CD-SSB.

6. The apparatus of claim 3, wherein to perform the initial access, the at least one processor is configured to: a random access preamble is transmitted during a random access occasion (RO) in the second initial downlink BWP, the RO having a Synchronization Signal Block (SSB) to RO mapping to the CD-SSB in the first initial downlink BWP.

7. The apparatus of claim 2, wherein the at least one processor is further configured to:

a configuration for a non-cell-defining SSB (non-CD SSB) is received in the active downlink BWP dedicated to the UE having the first capability.

8. The apparatus of claim 7, wherein the at least one processor is further configured to:

at least one of a layer 1 (L1) measurement or a layer 3 (L3) measurement is performed on the non-CD SSB in the active downlink BWP dedicated to the UE having the first capability.

9. The apparatus of claim 2, wherein the at least one processor is further configured to:

system information updates are received in Radio Resource Control (RRC) signaling in the active downlink BWP dedicated to the UE with the first capability.

10. The apparatus of claim 2, wherein to perform the initial access, the at least one processor is configured to transmit a random access preamble during a random access occasion (RO) in the second initial downlink BWP, the RO having a non-cell-defined Synchronization Signal Block (SSB) (non-CD SSB) based SSB-to-RO mapping.

11. The apparatus of claim 2, wherein in the second initial downlink BWP or the active downlink BWP dedicated to the UE with the first capability, one or more parameters for non-cell-defined SSBs (non-CD SSBs) comprise the same parameters as for CD-SSBs, the one or more parameters comprising at least one of:

The cycle time of the process is set to be equal,

the block index is used to determine the block index,

a spatial reference for a random access procedure,

the power offset is used to determine the power offset,

center frequency, or

Parameter sets.

12. The apparatus of claim 11, 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 made by the UE with the first capability and the UE with the second capability.

13. The device of claim 11, 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.

14. The apparatus of claim 2, wherein the first initial downlink BWP has a bandwidth at a center frequency of a carrier bandwidth that is not greater than the lower maximum UE bandwidth of the UE having the first capability, and

wherein an initial uplink BWP and the second initial downlink BWP are located at edges of the carrier bandwidth.

15. The apparatus of claim 2, wherein the at least one processor is further configured to:

Receiving a first configuration of the second initial downlink BWP specific to the UE having the first capability; and

a second configuration of the active downlink BWP is received in the second initial downlink BWP.

16. The device of claim 15, wherein the first configuration of the second initial downlink BWP is received in one of:

received in a System Information Block (SIB) dedicated to the UE with the first capability within the first initial downlink BWP, or

Received in system information dedicated to the UE having the first capability within control resource set 0 (CORESET 0).

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

18. The apparatus of claim 1, wherein 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 an active downlink BWP and the active uplink BWP dedicated to the UE having the first capability after the initial access, and wherein 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 wherein the first initial downlink BWP comprises a control resource set 0 (CORESET 0) or a cell-defined synchronization signal block (CD-SSB) configured for the UE having the first capability and the UE having the second capability, and wherein the first and the first initial downlink BWP and the second BWP have different bandwidths than the first and second UE having the same or different bandwidths.

19. The apparatus of claim 18, wherein the at least one processor is further configured to:

receiving system information or system information updates 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

The system information or the system information update is received in the first initial downlink BWP, the system information comprising separate information dedicated to the UE having the first capability in a second SIB carrying the separate information for the UE having the first capability and additional information for the UE having the second capability.

20. The apparatus of claim 18, wherein to perform the initial access, the at least one processor is configured to:

the random access preamble is transmitted during a first random access occasion (RO) having a first SSB-to-RO mapping based on a cell-defined synchronization signal block SSB (CD-SSB), or during a second RO having a second SSB-to-RO mapping or SSB-to-preamble mapping configured for the UE having the first capability.

21. The apparatus of claim 1, wherein the at least one processor is further configured to:

receiving a configuration for the active downlink BWP and the active uplink BWP, the configuration for the active downlink BWP comprising one or more of:

periodic or semi-static Tracking Reference Signals (TRSs),

periodic or semi-static channel state information reference signals (CSI-RS),

periodic or semi-static Positioning Reference Signals (PRS),

a Common Search Space (CSS) or control resource set (CORESET) for paging, system information update, wake-up signal (WUS) or group common power control,

non-cell defined synchronization signal blocks (non-CD SSBs),

additional CORESET or additional CSS for the system information update,

UE synchronization in Discontinuous Reception (DRX) mode, a resynchronization reference signal indicating the system information update, or

Layer 3 (L3) intra-frequency measurement gap in case SSB is not transmitted in the active downlink BWP.

22. The apparatus of claim 21, wherein the configuration is included in system information dedicated to the UE with the first capability or in Radio Resource Control (RRC) signaling for the UE.

23. The device of claim 1, wherein a configuration of the active downlink BWP or the active uplink BWP is based on a rule or a look-up table.

24. The apparatus of claim 1, wherein the at least one processor is further configured to:

performing a capability signaling procedure indicating that the UE has the first capability, wherein the at least one processor is configured to switch to the active downlink BWP and the active uplink BWP after completion of the capability signaling procedure and based on at least one of:

medium access control-control element (MAC-CE),

radio Resource Control (RRC) reconfiguration,

downlink Control Information (DCI), or

A timer configured in system information for the UE having the first capability.

25. An apparatus for wireless communication at a network entity, the apparatus comprising:

a memory; and

at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor configured to:

performing an initial access with a User Equipment (UE) having a first capability, the first capability being associated with a lower maximum UE bandwidth than a second capability, at least a portion of the initial access being based on a first initial downlink bandwidth portion (BWP) shared between the UE having the first capability and the UE having the second capability; and

To communicate with the UE after the initial access, a switch is made to an active downlink BWP and an active uplink BWP dedicated to the UE having the first capability.

26. The apparatus of claim 25, wherein the at least one processor is configured to 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, wherein the first initial downlink BWP comprises a control resource set 0 (CORESET 0) and a cell-defined synchronization signal block (CD-SSB) configured for the UE with the first capability and the UE with the second capability.

27. The apparatus of claim 26, wherein the at least one processor is further configured to:

outputting for transmission a first configuration of the second initial downlink BWP specific 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) carrying information for the UE having the first capability and the second capability, wherein the second initial downlink BWP specific to the UE having the first capability does not include the CORESET 0 or the CD-SSB.

28. The apparatus of claim 26, wherein to perform the initial access, the at least one processor is configured to: a random access preamble is obtained during a random access occasion (RO) in the second initial downlink BWP, the RO having a Synchronization Signal Block (SSB) to RO mapping to the CD-SSB in the first initial downlink BWP.

29. The apparatus of claim 26, wherein the at least one processor is further configured to:

a configuration for a non-cell-defining SSB (non-CD SSB) in the active downlink BWP dedicated to the UE with the first capability is output for transmission, the non-CD SSB being used for at least one of layer 1 (L1) measurements or layer 3 (L3) measurements for the UE with the first capability.

30. The apparatus of claim 26, wherein the at least one processor is further configured to:

system information updates are output for transmission in Radio Resource Control (RRC) signaling in the active downlink BWP dedicated to the UE with the first capability.